Dash 8 release docs
De Havilland Dash 8 authorized release documentation review
This review checks the authorized release paperwork behind the components installed on a De Havilland Dash 8: whether each installed serialized part is covered by a valid release certificate that matches the installation record. It reads FAA Form 8130-3, EASA Form 1, and dual-release certificates against part and serial numbers, and confirms the release supports the way the part was fitted. A records specialist runs it before a transaction or a lease return where a buyer will demand release evidence per component. You receive a supported exception list, a source map from each install to its release, and a closure plan for the missing or mismatched certificates.
When this review is needed
- A Dash 8 is entering diligence and the buyer will require a release certificate per installed component.
- A lease return demands dual-release evidence for parts fitted under one authority and returning to another.
- A component's provenance is questioned and the installation record has to be tied to its release.
- The component release file was assembled from mixed operator archives of uneven quality.
The problem
A release certificate only supports an installation if it matches the part, the serial number, and the way the part was fitted. On a Dash 8 that has been maintained across regions, the component release file collects certificates in several formats, some covering overhaul, some covering inspection, and some issued under an authority the receiving side will not accept without a dual release. A certificate on file that references a different serial number, or an install with no certificate at all, is a gap a buyer will find quickly.
What gets reviewed
- Each installed serialized component matched to a release certificate on file
- FAA Form 8130-3 and EASA Form 1 checked for the correct block entries and status
- Dual-release coverage confirmed where the part crosses between authorities
- The release basis, overhaul, inspection, or repair, reconciled to how the part was fitted
- Installation records tied to the release that authorizes each fitting
- Certificates screened for serial-number, part-number, and revision mismatches
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Each installed component has a release certificate whose part and serial numbers match the install
- The release basis stated on the certificate supports the way the part was returned to service
- Dual-release parts carry the second authority's release where the receiving side requires it
- Block entries on FAA Form 8130-3 and EASA Form 1 are complete and internally consistent
- No certificate in the file references a serial number that is not installed on the aircraft
Evidence normally required
- The component release file for the Dash 8 tail
- Installation records tying components to positions on the aircraft
- FAA Form 8130-3, EASA Form 1, and dual-release certificates as held
- The list of installed serialized components and their positions
- Any records standard the release evidence must satisfy for the transaction
Common discrepancies
- An installed component with no release certificate in the file
- A certificate whose serial number does not match the part actually fitted
- A single-release part fitted where the receiving authority requires a dual release
- A release issued on an inspection basis for a part the install treats as overhauled
What is at stake
A component installed without a valid matching release is treated as unsupported, which can force its removal or the recovery of paperwork that may no longer exist. A single-release part returning to a jurisdiction that requires dual release stalls acceptance, and mismatched certificates in the file undermine confidence in the rest of the release paperwork.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
List the installs
Enumerate installed serialized components and their positions on the aircraft.
Match to release
Tie each install to a release certificate and check part number, serial number, and basis.
Test the crossings
Confirm dual-release coverage where a part moves between FAA and EASA acceptance.
Record the gaps
Flag missing, mismatched, and single-release parts with the evidence needed to close each.
What the buyer receives
- A supported exception list of missing, mismatched, and single-release components
- A source map from each installation record to its release certificate
- A closure plan for recovering or reissuing the missing release evidence
Who uses the output
- Records teams assembling the component release file for diligence
- Continuing-airworthiness teams confirming installs are supported before an event
- Buyers and lessees verifying release evidence per installed component
How the work fits into the transaction or program
Release-document verification underpins the LLP trace and the redelivery binder, since both rest on the same certificates. Its exception list drives recovery from the shops and operators that issued the paperwork while they are still reachable, and its source map becomes the per-component evidence a buyer works through.
Aircraft-specific considerations
A Dash 8 component file leans heavily on propeller, landing-gear, and engine-accessory releases, and those parts cycle through shops often on a regional operation, multiplying the certificates that have to match. Parts fitted at line stations across several countries produce a mix of FAA and EASA releases in one file, so dual-release coverage is checked more carefully on this family than on a single-jurisdiction asset.
Jurisdiction-specific considerations
FAA and EASA accept each other's releases only under specific conditions, and a part returning across that boundary often needs a dual release the original certificate does not carry. The review flags each installed part whose single release will not satisfy the receiving authority.
Regulatory limits
The review confirms that installed components are supported by valid, matching release evidence. It does not issue or reissue any release certificate, return a part to service, or make an airworthiness determination on the installed configuration.
What this review does not cover
- Issuing or reissuing any authorized release certificate
- Physical inspection or return-to-service of installed components
- Any airworthiness determination on the aircraft
Specific to this review
- A release certificate that references the wrong serial number is worse than a missing one, because it looks like coverage until the numbers are compared.
- The release basis matters as much as the certificate: an inspection release does not support a part the install treats as overhauled.
- On a cross-jurisdiction Dash 8, dual-release gaps are common because parts were fitted under whichever authority held the line station.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
We have a certificate for every part. Why check them individually?
Having a certificate on file is not the same as having a matching one. The review confirms each release names the part and serial number actually installed, states a basis that supports the install, and satisfies the receiving authority. A certificate for the wrong serial number or the wrong basis reads as coverage until someone compares it to the install.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.