Dash 8 AD status
De Havilland Dash 8 AD status records review
This review tests the De Havilland Dash 8 AD status list against the evidence that each directive was actually accomplished. It confirms applicability to this serial number, reads the method of compliance recorded for each open and closed AD, and checks that recurring items carry the next-due basis. A records specialist runs it before a transaction, a program bridge, or an audit that will scrutinize compliance. You receive a supported exception list, a source map from each AD line to its accomplishment record, and a closure plan for the directives that cannot yet be substantiated.
When this review is needed
- A Dash 8 is entering diligence and the buyer will test every open and closed AD against evidence.
- The tail is bridging to a new operator's program and the AD baseline has to be fixed first.
- A regulator or auditor has questioned the compliance position and a documented response is due.
- The status list was inherited from a prior operator and its provenance is unknown.
The problem
An AD status list is a summary, and a summary can assert compliance that the underlying records do not support. On a Dash 8 that has flown high-cycle regional sectors and changed operators, recurring inspections come due often, applicability turns on modification state, and accomplishment evidence gets separated from the line that references it. A directive marked closed with no traceable record behind it is indistinguishable from a real close until someone goes looking for the paperwork.
What gets reviewed
- Applicability of each AD to this Dash 8 serial number and its modification state
- Method of compliance recorded against each open and closed directive
- Accomplishment evidence located for every AD claimed complete
- Recurring AD next-due status computed from the correct interval basis
- Superseded and terminated directives reconciled so the list reflects current effectivity
- Alternative methods of compliance supported by their approval reference
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 closed AD is backed by a work record naming the directive and its method of compliance
- Applicability decisions align with the serial number's modification and configuration state
- Recurring AD next-due values follow from the recorded accomplishment date, hours, or cycles
- Superseded directives are shown as such and point to the superseding AD
- An alternative method of compliance carries the approval that authorizes its use
Evidence normally required
- The current AD status list for the Dash 8 tail
- Accomplishment records, work orders, and logbook entries referenced by the list
- The modification and configuration status that drives applicability
- Current utilization in hours and cycles for recurring-interval computation
- Any alternative method of compliance approvals on file
Common discrepancies
- A directive marked complete with no accomplishment record traceable to it
- A recurring AD whose next-due was computed from an interval that no longer applies
- An applicability call that ignores an embodied modification affecting the AD
- A superseded AD still tracked as active while the superseding directive is absent
What is at stake
An AD closed on the status list without accomplishment evidence forces a conservative assumption at the next transaction: the buyer treats it as open and prices or schedules accordingly. Recurring items with no next-due basis can silently run past their interval, and an applicability error means either an inapplicable AD is being tracked or an applicable one is being missed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix applicability
Confirm which directives apply to this serial number given its modification and configuration state.
Trace each close
Locate the accomplishment record and method of compliance behind every AD marked complete.
Recompute recurring items
Rebuild next-due values from the recorded accomplishment date, hours, and cycles.
List the exceptions
Record unsubstantiated, mis-applied, and stale lines with the evidence needed to close each.
What the buyer receives
Who uses the output
- Continuing-airworthiness teams fixing the compliance baseline before a program bridge
- Asset managers pricing the exposure behind unsubstantiated AD lines
- Buyers and auditors verifying the compliance position against evidence
How the work fits into the transaction or program
The AD review sets the compliance baseline that later status work and any program bridge depend on. Its exception list feeds remediation while the current holder still has access to the shops and operators that hold the accomplishment records, and its source map becomes part of the diligence data room.
Aircraft-specific considerations
Dash 8 operations run high cycle counts on regional sectors, so recurring structural and landing-gear directives come due frequently and their interval math has to be exact. Compliance also interacts with propeller and engine service history and with structural repairs, so applicability on this family often turns on the modification and repair state rather than the serial number alone.
Jurisdiction-specific considerations
A Dash 8 crossing between FAA and EASA oversight can be subject to directives from both the state of design and the state of registry. The review notes where a directive from one authority has a counterpart or a difference under the other so the receiving operator is not surprised at induction.
Regulatory limits
The review verifies that the recorded AD status is supported by evidence. It does not accomplish any directive, grant an alternative method of compliance, or determine that the aircraft is airworthy, all of which rest with the operator and the authority.
What this review does not cover
- Accomplishing or re-accomplishing any airworthiness directive
- Developing or approving an alternative method of compliance
- Any airworthiness determination on the aircraft
Specific to this review
- A closed AD line and an unsubstantiated one look identical on a status list; only the accomplishment record tells them apart.
- On a high-cycle Dash 8 the interval basis for recurring directives is the most common place status detaches from reality.
- Applicability can flip on an embodied modification, so the configuration state has to be settled before the AD list can be trusted.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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
The status list says every AD is complete. Why review it?
A status list is an assertion, not proof. The review confirms each closed directive has an accomplishment record behind it and that recurring items are computed on the correct interval. A buyer or auditor will do exactly this check, so finding an unsupported line first lets you close it while you still control the file.
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.