Dash 8 repair approvals
De Havilland Dash 8 repair approval data records review
This review maps the structural repairs and alterations on a De Havilland Dash 8 and confirms each one rests on approved data with a supported return-to-service entry. It reads the damage reports, repair dispositions, and the approved-data reference behind every repair, and builds a location map of what has been done to the airframe. A records specialist runs it before a transaction or a check where a buyer or auditor will test the repair basis. You receive a supported exception list, a source map from each repair to its approval, and a closure plan for the repairs whose basis cannot yet be shown.
When this review is needed
- A Dash 8 with a long structural repair history is entering diligence and the basis will be tested.
- A buyer wants a repair map before pricing an airframe that has seen corrosion and damage work.
- An alteration is claimed but the approved data behind it has never been confirmed.
- A repair done under one authority has to be shown acceptable to another at a register change.
The problem
A repair is only as good as the data it was done to. On a Dash 8 that has flown corrosive coastal routes and accumulated structural work across operators, repairs pile up, and each one needs an approved-data reference and a return-to-service entry that ties back to it. A repair recorded without its disposition, or an alteration whose STC or approved data cannot be produced, leaves the airframe carrying work that a buyer cannot rely on and an auditor will question.
What gets reviewed
- Structural repairs mapped to their locations on the airframe
- Approved-data reference confirmed for each repair and alteration
- Repair dispositions and damage reports reconciled to the work recorded
- Return-to-service entries tied to the repair they close
- Alterations checked for a traceable STC or approved-data basis
- Repairs done under one authority screened for acceptability to another
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 recorded repair references approved or acceptable data appropriate to the damage
- The return-to-service entry for each repair follows from its disposition and data
- Alterations carry a traceable STC or approved-data basis for this serial number
- Damage reports and repair dispositions are internally consistent with the work done
- A repair approved under one authority has a stated basis for acceptance under the other
Evidence normally required
- The repair and alteration records for the airframe
- Damage reports and repair dispositions on file
- Approved-data references, STCs, and substantiation for each repair
- Return-to-service entries associated with the repairs
- The airframe location map or structural repair index if one exists
Common discrepancies
- A structural repair recorded with no approved-data reference behind it
- An alteration whose STC or approved data cannot be produced from the file
- A return-to-service entry that does not tie to any recorded disposition
- A repair done under one authority with no basis stated for the other
What is at stake
A repair without traceable approved data can force re-substantiation or, in the worst case, rework of the airframe, both far more expensive than confirming the basis up front. An alteration whose approval cannot be shown may have to be removed, and a repair done under one authority without an acceptable basis for another can stall a register change until the data is reconstructed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the repair map
Locate every recorded repair and alteration on the airframe and index it by position.
Confirm the basis
Tie each repair to its approved or acceptable data and each alteration to its STC.
Reconcile the closes
Check that return-to-service entries follow from the dispositions and data on file.
Flag the exposure
Record repairs and alterations without a traceable basis and the evidence needed to close them.
What the buyer receives
- A supported exception list of repairs and alterations lacking a traceable basis
- A source map from each repair to its approved data and return-to-service entry
- A closure plan for recovering or re-substantiating the missing repair data
Who uses the output
- Engineering deciding how to treat a repair with no traceable basis
- Asset managers pricing the exposure behind unsubstantiated structural work
- Buyers and auditors testing the repair basis against evidence
How the work fits into the transaction or program
Repair-approval verification feeds the configuration picture and the redelivery binder, since a buyer prices the airframe partly on its repair history. Its exception list drives re-substantiation while the data is still recoverable, before the repair basis has to hold up at a transaction or a register change.
Aircraft-specific considerations
Dash 8 airframes on regional coastal routes accumulate corrosion and structural repair work, so the repair history is denser than a lightly used jet's and the location map matters more. Structural repair history also interacts with high-cycle fatigue considerations on this family, so repairs near life-limited structure get particular attention in the review.
Jurisdiction-specific considerations
A repair approved under FAA data is not automatically acceptable to EASA and the reverse, so a Dash 8 moving between registers needs each repair's basis assessed for the receiving authority. The review flags repairs whose approval will need a bridging basis before the register change.
Regulatory limits
The review confirms that repairs and alterations rest on traceable approved data. It does not develop or approve repair data, perform or re-perform any repair, or make an airworthiness determination on the repaired structure.
What this review does not cover
- Developing, approving, or re-substantiating repair or alteration data as an authority
- Performing or re-performing any repair or alteration
- Any airworthiness determination on the repaired structure
Specific to this review
- A repair map is worth building because a buyer prices structural history by location, not by a count of repairs.
- An alteration without a producible STC or approved-data basis may have to be removed, which is far costlier than confirming the basis early.
- On a coastal-route Dash 8, corrosion repairs cluster in predictable areas, and that is where missing approved-data references most often turn up.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What happens to a repair whose approved data we cannot find?
It is carried as an exception with its residual exposure stated, and the closure plan sets out whether the data can be recovered, the repair re-substantiated, or the work reassessed. Leaving the basis undocumented is what forces a buyer or auditor to assume the worst and price or schedule against it.
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.