Deferred maintenance
De Havilland Dash 8 deferred maintenance records review
This review checks a Dash 8's deferred-maintenance position: what is open, under what MEL or deferral category, and whether each item is within its allowed interval. It is run for a lessor, operator, or manager assessing or transferring the aircraft, often before a deal or a program move when the open items have to be understood and bounded. It reconciles the current deferral log against the MEL, confirms each open item's clearing basis, and checks that cleared items actually closed. You receive a supported exception list, a source map from each deferral to its raising and clearing evidence, and a closure plan for anything open beyond its limit or missing its basis.
When this review is needed
- A buyer needs the open deferral position understood and bounded before pricing the aircraft.
- The deferral log has grown and no one has confirmed which items are still within their limits.
- A receiving operator needs open items reconciled to its own MEL before induction.
- A deferral appears cleared in one record but its clearing evidence cannot be found.
The problem
Deferred maintenance is a rolling position, not a fixed list: items are raised against the MEL, carried under a category with a time or cycle limit, and cleared when the corrective work is done. On a Dash 8 with a lean regional records team, the deferral log and the actual corrective entries can drift apart, so an item shows open when it was fixed, or shows cleared when the clearing entry never landed. An item carried past its category limit is a compliance problem hiding inside a housekeeping record.
What gets reviewed
- The current open-deferral list reconciled against the MEL categories and their limits
- Each open item confirmed within its time or cycle interval
- Clearing evidence matched to items the log shows as closed
- MEL and configuration-deviation references checked for applicability to this aircraft
- Deferrals that repeat, indicating an underlying condition rather than a single event
- Items carried across an operator change and whether they transferred cleanly
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
- Every open deferral cites a valid MEL or configuration-deviation category with a defined limit
- No open item exceeds the time or cycle interval its category allows
- Each item the log shows as cleared has a corrective entry that actually closes it
- The MEL referenced is the revision applicable to this aircraft and operator
- Recurring deferrals on the same system are identified rather than treated as unrelated events
Evidence normally required
- The current deferred-maintenance and open-item log
- The MEL and configuration-deviation list in use
- Corrective-action and clearing entries for closed deferrals
- Logbook entries recording deferral raising and clearance
- The operator's deferral procedures and category definitions
Common discrepancies
- An open item carried beyond the interval its MEL category allows
- A deferral marked cleared with no corrective entry behind the closure
- A recurring deferral on one system that points to an unresolved condition
- An open item that did not transfer cleanly across a change of operator
What is at stake
An item carried beyond its MEL category limit is a live dispatch problem, not a paperwork one, and it is the kind of finding that stops an induction or a sale in its tracks. A deferral that appears cleared without a corrective entry leaves an open item that the next operator inherits unknowingly, and reconciling the log after a transfer is far harder than confirming it while the corrective records are still to hand.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the open position
Take the current deferral log and the MEL revision in use as the position to test.
Check limits
Confirm each open item cites a valid category and sits within its time or cycle interval.
Verify clearances
Match each closed item to the corrective entry that actually resolved it.
Set the closures
List out-of-limit and unsupported items with a path to close each before transfer.
What the buyer receives
- A supported exception list of items open past their limit or missing a clearing basis
- A source map tying each deferral to its raising and corrective records
- A closure plan for out-of-limit items and for clearances that need supporting entries
Who uses the output
- Records teams confirming the deferral log reflects the aircraft's true open position
- Asset managers bounding the open-item exposure before a transaction
- Continuing-airworthiness teams clearing out-of-limit items before induction
How the work fits into the transaction or program
The deferral position is the current-condition layer on top of the aircraft's status records, and it moves faster than any of them. Reconciling it against the MEL and the corrective entries gives an incoming operator or a buyer a bounded, current picture of open work, which the redelivery and airworthiness-review records then depend on being accurate.
Aircraft-specific considerations
Dash 8 fleets run high daily utilization in regional service, so deferrals turn over quickly and a lean records team may not reconcile the log as often as the tempo demands. Different operators run different MEL revisions and category conventions, so a deferral carried across an operator change can reference a category that no longer maps cleanly, which is where out-of-limit and orphaned items concentrate on this family.
Jurisdiction-specific considerations
The MEL derives from a master minimum equipment list but is operator and authority specific, so a Dash 8 moving between FAA and EASA operators will have its open deferrals reassessed against a different MEL. The review notes where an open item's category and limit will change under the receiving operator's list.
Regulatory limits
The review reconciles the deferral records against the MEL limits and the corrective evidence on file. It does not clear a deferral, perform the corrective maintenance, or make a dispatch or airworthiness determination on any open item.
What this review does not cover
- Performing or signing off the corrective maintenance behind a deferral
- Approving or revising the operator's MEL
- Any dispatch or airworthiness determination on an open item
Specific to this review
- A deferral carried past its category limit is a dispatch-eligibility problem, so it is triaged ahead of items that are merely undocumented.
- The deferral log and the corrective entries drift apart most under high utilization, because the fix and the log update happen at different moments.
- A recurring deferral on one system usually signals an unresolved root cause rather than a string of unrelated write-ups, which changes how it is closed.
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.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
Frequently asked questions
What is the most urgent thing this review surfaces?
Any item carried beyond the interval its MEL category allows. That is a live dispatch-eligibility issue rather than a documentation gap, so it is flagged and sequenced ahead of items that are simply missing their clearing evidence.
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.