Deferrals and carry-overs
Deferred maintenance records reconciled with the engine-module file
A deferred-maintenance source review tests whether every deferral touching the engine was properly controlled while open and properly evidenced when closed. Operators, CAMO teams, and lessors use it at file transfers and ahead of audits, where the deferral log is an early target for sampling. Open items are checked for valid authority and limit tracking, cleared items for the corrective work that closed them, and carried-over shop workscope items for their reappearance in later records. Every line that fails those tests is logged as an exception.
When this review is needed
- A transfer requires certifying that no unresolved deferrals ride with the engine beyond those disclosed.
- Shop workscope items were descoped at the last visit and their carry-over trail needs proving.
- An audit sampled the deferral log and the hit rate demands a full review.
- Deferral tracking moved between systems and closure evidence did not visibly move with it.
The problem
Deferrals are managed for the present tense: what is open now and when it comes due. The historical record gets little attention, so items cleared years ago sit in the log with a status change and no cited closure, and workscope items descoped at a visit exist only in the shop's planning correspondence. The log reads clean while being unable to answer how any given line was actually resolved.
What gets reviewed
- Open deferrals checked for authority, category, and a tracked limit consistent with the controlling basis
- Cleared deferrals traced to corrective-action evidence, task cards, or shop records
- Limits tested for correct units, cycles versus hours versus calendar, against the controlling reference
- Visit-descoped workscope items followed into the deferral or planning record and onward to completion
- Repetitive deferrals of the same defect identified and their pattern documented
- Log migrations examined for lines whose closure evidence predates the current system
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 line carries a valid deferral authority and a due point the tracking actually enforces
- Every cleared line cites corrective evidence actually present in the file, dated consistently with the closure
- Limit units on each deferral match the controlling document, with no silent unit substitutions
- Descoped visit items reconcile to a later completion or a still-open tracked line
- No line was closed by migration default rather than by evidence
Evidence normally required
- The deferred maintenance log, current and historical
- Deferral authorities and category references applicable to the operation
- Task cards, shop records, and releases cited by cleared items
- Visit workscopes and descope correspondence for carry-over items
- System migration records where the log changed platforms
Common discrepancies
- Cleared lines whose cited closure document is nowhere in the file
- A deferral tracked in calendar days against a limit the controlling reference states in cycles
- Descoped workscope items that never reappear in any later visit or tracked line
- Blocks of closures dated to a system migration day, marking defaults rather than evidence
What is at stake
A deferral cleared without evidence reads as a defect that may still exist, and unlike most records gaps it implies a possible present-tense airworthiness question rather than a historical one. Auditors weight deferral findings accordingly, and a transfer counterparty can hold the disclosure representation open until every cleared line is proven.
How the work runs
Split the population
Separate open, cleared, and carried-over lines, each with its own test set.
Verify control
Check authority, category, and limit tracking on the open population.
Prove the closures
Trace cleared lines to corrective evidence, flagging migration defaults and bare status changes.
Reconcile carry-overs
Follow descoped visit work to completion or to a tracked open line, and report the exceptions.
What the buyer receives
- A line-status verification across the full log, open and cleared
- Trace-file exception entries with the failed test named per line
- A carry-over reconciliation covering descoped visit work
Who uses the output
- CAMO and reliability staff who own deferral control
- Records leads preparing disclosure schedules for transfer
- Audit-response teams sizing exposure after a sampled finding
How the work fits into the transaction or program
Deferral records intersect nearly every other part of the engine file: they receive descoped workscope from visits, create program-tracked limits, and close through task cards. This review is often sequenced last in a full file review so it can use the verified visit, card, and program evidence to test closures instead of taking the log's citations on faith.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA operations defer under MEL provisions and operational rules with records reaching back to 14 CFR 91.417, while EASA deferral and rectification-interval management sits with the Part-CAMO organization under Regulation 1321/2014, and ICAO Annex 6 retention expectations apply to international operations. The categories and extension mechanics differ between regimes, so a log spanning a registry change needs each era judged by its own rulebook.
Regulatory limits
The review verifies documentary control and closure; it does not authorize deferrals, grant extensions, or judge whether any open item is acceptable for continued operation. Those decisions stay with the operator, its CAMO, and the authority.
What this review does not cover
- Operational decisions on currently open deferrals
- Rectification of open defects
- MEL revision or authoring work
Specific to this review
- Migration-day closures are a recognizable artifact: dozens of lines closed on one date, all without cited evidence, marking a data conversion rather than maintenance.
- Unit mismatches on limits stay quiet until an engine's utilization profile shifts, at which point a days-based track of a cycles limit diverges fast.
- Descoped workscope is the least durable record in the chain, often existing only in planning correspondence that never enters the file.
- Repetitive deferral of one defect signals a reliability issue that the log format hides by treating each instance as new.
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
Our open deferral count is low. Is a historical review still worth it?
The open count measures today's workload, and the risk in a transfer or audit sits mostly in the cleared population, which is always far larger. A short open list built on unproven historical closures still fails sampling, so the historical trace is where the review earns its keep.
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.