Dash 8 program status
De Havilland Dash 8 maintenance program records review
This review confirms which approved maintenance program a De Havilland Dash 8 was actually run on and whether the recorded status reflects it. It reads the approved program revisions, the task escalations applied, and any bridging analyses, then reconciles them against the maintenance the tail actually accumulated. A records specialist runs it before a program bridge to a new operator or a transaction that tests the program basis. You receive a supported exception list, a source map from program status to the approved revisions behind it, and a closure plan for the tasks whose basis cannot be shown.
When this review is needed
- A Dash 8 is bridging to a new operator's program and its current program basis has to be settled.
- Task escalations were applied under a prior operator and their approval has to be confirmed.
- A buyer needs the program the tail ran on reconciled against the status the records report.
- A bridging analysis from an earlier transition has to be checked before another bridge is built on it.
The problem
The maintenance program is the frame the whole status picture hangs on, and a Dash 8 that has moved between operators may have been run on several. Task intervals get escalated with approvals that live in a program revision nobody transferred, bridging analyses accumulate one on top of another, and the status list reports next-due values computed against a program the tail is no longer on. Without settling which approved revision applies, every downstream due date is uncertain.
What gets reviewed
- The approved program revisions the tail was maintained to over its life
- Task escalations applied and the approval basis behind each
- Bridging analyses from prior transitions and their standing
- Next-due status reconciled against the applicable approved revision
- Source-document references tying program status to the approved program
- Program applicability confirmed for this serial number and its configuration
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
- The program status reported is computed against the approved revision actually in force
- Each task escalation carries a traceable approval appropriate to the program
- Bridging analyses from prior transitions are internally consistent and supported
- Next-due values follow from the applicable intervals for this serial number
- Program applicability aligns with the tail's configuration and modification state
Evidence normally required
- The approved maintenance program and its revision history for the tail
- Task escalation approvals applied over the tail's life
- Bridging analyses from prior operator transitions
- The current maintenance program status the records report
- Configuration and modification status affecting program applicability
Common discrepancies
- Program status computed against a revision the tail is no longer maintained to
- A task escalation with no traceable approval behind the extended interval
- A bridging analysis that does not reconcile with the program it claims to bridge to
- Program applicability that ignores a modification changing the task set
What is at stake
A tail bridged onto a new program from an unsettled basis carries interval and task gaps that surface at the first check under the new operator. Escalations without traceable approval can collapse the intervals a buyer priced against, and a bridging analysis built on an earlier one that itself does not hold compounds the error across the transition.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Settle the revision
Establish which approved program revision the tail was actually maintained to.
Substantiate escalations
Confirm each applied task escalation carries a traceable approval.
Check prior bridges
Reconcile earlier bridging analyses so a new bridge is not built on a weak one.
Reconcile the status
Recompute next-due against the applicable intervals and flag the mismatches.
What the buyer receives
- A supported exception list of unsubstantiated escalations and program mismatches
- A source map from program status to the approved revisions behind it
- A closure plan for confirming the program basis before the next bridge
Who uses the output
- Continuing-airworthiness teams settling the program basis before a bridge
- Asset managers pricing the exposure behind unsupported escalations
- Buyers verifying the program the tail was actually maintained to
How the work fits into the transaction or program
Program verification sits ahead of any bridge to a new operator, because the receiving program is mapped onto the one the tail actually ran. Its exception list drives the recovery of escalation approvals and program revisions while the prior operator can still supply them, and its source map anchors the status every task-card and AD check reconciles against.
Aircraft-specific considerations
Dash 8 tails often pass between regional operators, so operator-program bridging is a recurring feature of the records rather than a one-time event, and each bridge has to reconcile against the last. High-cycle regional utilization also makes interval escalations attractive to prior operators, so this family carries more escalation history to substantiate than a lower-utilization asset.
Jurisdiction-specific considerations
An approved program under FAA oversight maps differently onto an EASA CAMO-managed program, so a Dash 8 crossing that boundary needs its task set and intervals reconciled for the receiving system. The review notes where the program basis will need rework before the CAMO can adopt the tail.
Regulatory limits
The review confirms the program basis the tail was maintained to is traceable and internally consistent. It does not approve a maintenance program, authorize a task escalation, or make an airworthiness determination on the tail.
What this review does not cover
- Authoring, revising, or approving the maintenance program
- Approving any task escalation or interval extension
- Any airworthiness determination on the aircraft
Specific to this review
- Program status is only meaningful against the approved revision in force; a due date computed on the wrong revision is not a real due date.
- Task escalations are the most common unsupported item, because the approval often lived in a program revision the transfer did not carry.
- A bridging analysis built on an earlier one that does not hold compounds the error, so each prior bridge is checked before the next is trusted.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
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
The status report shows everything current. Why check the program behind it?
A status report is current only against whatever program it was computed on. If the tail was run on a different approved revision, or an escalation behind an interval has no approval, the due dates are wrong even though the report looks clean. Settling the program basis is what makes the status meaningful for a bridge or a buyer.
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.