Structural repairs
De Havilland Dash 8 structural repair records review
This review builds a map of the structural repairs a Dash 8 has taken and confirms each one is backed by approved or acceptable data. It is run for a lessor, operator, or manager assessing or transferring the aircraft, often before a transaction or when repair history has accumulated across operators and heavy checks. It locates each repair, ties it to its approval basis and any repeat-inspection requirement, and checks the repair map against the damage and work records. You receive a supported exception list, a source map from each repair to its substantiation, and a closure plan for repairs whose basis or inspection status is unclear.
When this review is needed
- A Dash 8 has a repair history spread across heavy checks and operators that has never been consolidated.
- A buyer needs the structural condition and its documentation confirmed before pricing.
- A repair is recorded with no clear reference to the SRM or an approved repair design.
- A repeat inspection may be due on a past repair and no one has tracked whether it is being flown.
The problem
Structural repairs on a Dash 8 get recorded where they happen: a damage report in one heavy-check package, an approved repair design in another, a logbook entry that references neither cleanly. Over a high-cycle life with several operators, there is no single map of where the airframe has been repaired, on what basis, and with what ongoing inspection obligation. A repair can be entirely sound yet impossible to defend because its approval reference and its repeat-inspection requirement live in separate files that were never brought together.
What gets reviewed
- Each recorded structural repair located and placed on a consolidated repair map
- The approval basis for each repair, whether SRM, approved repair design, or accepted data
- Damage reports matched to the repair that addressed each finding
- Repeat or recurring inspection requirements attached to repairs and their current status
- Repairs that interact with or overlap AD-mandated structural inspections
- The repair map reconciled against the airframe's zonal and structural history
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 repair references approved or acceptable data appropriate to the structure and the jurisdiction
- A damage report is matched to the repair that closed it, with no orphaned findings
- Repeat-inspection requirements on repairs are captured and their next due status is current
- Repairs affecting AD-controlled structure are reconciled with the relevant AD status
- The consolidated map accounts for every repair the logbooks and check packages reference
Evidence normally required
- Damage reports and structural finding records across the airframe's history
- Approved repair designs, SRM references, and substantiation data
- Heavy-check work packages containing structural repairs
- Logbook entries recording structural repair accomplishment
- AD status for structural inspection directives affecting the airframe
Common discrepancies
- A recorded repair with no locatable reference to the SRM or an approved repair design
- A repeat-inspection requirement on a past repair that no program is currently tracking
- A damage report with no matching record of the repair that addressed it
- A repair on AD-controlled structure that was never reconciled with the AD status
What is at stake
A structural repair without traceable approved data can force re-substantiation or, in the worst case, rework before a buyer or receiving operator accepts the airframe. A repeat-inspection requirement that no one is tracking is a live continued-airworthiness gap, not just a paperwork one, and it is exactly the finding that stalls acceptance or triggers a grounding review at the worst moment.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Locate the repairs
Pull structural repairs from logbooks and check packages onto one consolidated map.
Validate the basis
Tie each repair to its SRM reference, approved design, or accepted data.
Track the inspections
Capture repeat-inspection requirements and confirm their current due status.
Flag the exceptions
List repairs without a basis or with lapsed inspections and set a closure path.
What the buyer receives
- A supported exception list of repairs missing an approval basis or inspection tracking
- A source map placing each repair on a consolidated structural map with its evidence
- A closure plan for untraced repairs and for repeat inspections that need reinstating
Who uses the output
- Records teams building a defensible structural repair history for the airframe
- Asset managers pricing structural condition against documented repairs
- Continuing-airworthiness teams reinstating repeat inspections that had lapsed from tracking
How the work fits into the transaction or program
The structural repair map underpins any assessment of airframe condition and feeds the AD status where structural inspection directives apply. Consolidating repairs and their inspection obligations here gives the AD and continued-airworthiness work a complete structural picture, rather than repairs scattered across check packages that no one has mapped.
Aircraft-specific considerations
Dash 8 airframes in intensive regional service accumulate high cycle counts, and fatigue-driven structure is where repairs and their repeat inspections concentrate. Repairs made under different operators and heavy-check providers rarely share a common format, so on this family the consolidation work is as much about locating repairs as validating them, and lapsed repeat inspections are a recurring live finding.
Jurisdiction-specific considerations
A structural repair approved under FAA data is not automatically acceptable on an EASA register, and vice versa, so a Dash 8 that has changed systems can carry repairs whose basis a receiving authority will want validated. The review flags where a repair's approval basis needs supplementing before the receiving operator relies on it.
Regulatory limits
The review consolidates and validates the records behind each structural repair. It does not inspect the structure, approve a repair design, or determine that the airframe is airworthy in its repaired condition.
What this review does not cover
- Physical inspection or non-destructive testing of the structure
- Designing, approving, or re-substantiating a repair
- Any airworthiness determination on the airframe structure
Specific to this review
- A repeat-inspection requirement that drops off the tracking program is a live continued-airworthiness gap, not just a records gap.
- On a high-cycle Dash 8, most structural repair evidence is scattered across separate heavy-check packages, so locating repairs is often harder than validating them.
- A structural repair can overlap an AD-mandated inspection zone, so the repair record and the AD status have to be read together, not in isolation.
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
Why do repeat inspections on repairs matter as much as the approval data?
A repair approved with a recurring inspection is only acceptable while that inspection is being flown. If the requirement fell off the tracking program at an operator change, the airframe carries an open obligation, which is a continued-airworthiness finding, not just a documentation one.
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.