Maintenance program records
ATR 72 maintenance program records review
This review examines the maintenance program an ATR 72 has been maintained to and confirms the program status rests on approved revisions and defensible task history. It is run for a lessor, operator, or manager who needs the program basis to hold before a transfer, a transaction, or induction onto a new program. The work checks the approved program revisions in use, the task escalations claimed, any bridging analysis between programs, and the source references behind the recorded status. You receive an exception list of program items that do not stand up, a map to the approvals behind them, and a closure plan for the gaps that affect the status.
When this review is needed
- An ATR 72 is transferring operators and the receiving side has to bridge its program to the incoming one.
- A sale or lease will test whether the program status is built on approved revisions.
- Task escalations were applied and the approvals supporting them have never been checked.
- A bridging analysis was done at a prior transfer and its basis has to be confirmed before the next.
The problem
A maintenance program status is only as sound as the approved revisions and escalation approvals behind it. A task interval that was escalated without the approval to support it, a program revision applied late, or a bridging analysis from a prior transfer that no one re-checked all leave the status resting on assumptions. Two operators rarely run the same program, so an ATR 72 moving between them carries a bridge that has to be defensible, not just present, and the source references behind the status are where that defensibility lives.
What gets reviewed
- Approved program revisions in use and their applicability to the aircraft
- Task escalations claimed and the approvals supporting each one
- Bridging analysis between the prior and current programs
- Recorded task status referenced back to the program that governs it
- Program items driven by AD or SB reconciled to those status lists
- Source references tying the status to the approved program documents
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 program revision applied to the aircraft is approved and applicable to its configuration
- Every task escalation claimed is supported by an approval, not applied by default
- The bridging analysis between programs is documented and internally consistent
- Recorded task intervals trace to the governing program revision, not a superseded one
- Program tasks tied to AD or SB action reconcile with those status lists
Evidence normally required
Common discrepancies
- A task escalation applied with no approval behind it
- A program revision recorded as in use later than it was actually applied
- A bridging analysis from a prior transfer that was never documented in the file
- A task interval traced to a superseded revision rather than the governing one
What is at stake
A status built on an unsupported escalation can put a task past its true interval, which surfaces at the first check under the new program. An undocumented bridge forces the receiving operator to reconstruct the program history or start conservatively, both of which cost time and access. A program basis a buyer cannot verify weakens the asset's value and reopens questions the transfer was meant to settle.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the governing program
Establish which approved revisions govern the aircraft and confirm their applicability.
Test the escalations
Check each escalation against the approval that permits it.
Verify the bridge
Confirm any bridging analysis is documented and consistent with both programs.
Plan the closures
List unsupported escalations and undocumented bridges and sequence their correction.
What the buyer receives
- An exception list of program items lacking approval, applicability, or a documented bridge
- A source map linking the status to the approved program revisions behind it
- A closure plan for the program gaps that affect the recorded status
Who uses the output
- Asset managers confirming the program basis before pricing or transfer
- Continuing-airworthiness teams bridging the aircraft onto a new program
- Records teams documenting escalations and bridges before the next transfer
How the work fits into the transaction or program
The maintenance program is the framework every task interval and check status is computed against, so its basis governs whether the recorded status can be trusted through a transfer. This review confirms that basis before induction or a transaction relies on it, and its closure plan drives the approvals and bridging documentation that have to be in place before the program status holds.
Aircraft-specific considerations
ATR 72 programs carry corrosion-prevention and control tasks and structural inspection intervals that a narrowbody program would structure differently, and regional operation drives fast cycle accumulation that makes escalations attractive and easy to overreach. Because these aircraft move between operators often, a defensible bridging analysis is central to the program status, and its absence is a recurring gap in transferred files.
Jurisdiction-specific considerations
An ATR 72 moving between the FAA and EASA systems has to bridge onto a program the receiving authority accepts, so the review notes where the current program's approvals would need re-establishing and where intervals differ between the two systems.
Regulatory limits
This work confirms that the program status is supported by approved revisions and documented escalations and bridging. It does not approve or revise the maintenance program, accept the aircraft onto a program, or make an airworthiness determination.
What this review does not cover
- Authoring, revising, or approving the maintenance program
- Accepting the aircraft onto any operator's program
- Any airworthiness determination on the program status
Specific to this review
- A task escalation is only defensible with the approval behind it, and an unsupported one can put a task past its true interval.
- A bridging analysis has to be documented to be usable, and a bridge done verbally at a prior transfer leaves the status unsupported.
- ATR 72 corrosion-control and structural intervals are where overreached escalations most often cause trouble at the next check.
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
Why check bridging if the aircraft has been flying on the program fine?
Flying without incident does not prove the bridge is documented or the escalations are approved. The receiving operator and a buyer test the program basis, so an undocumented bridge or unsupported escalation surfaces at transfer, which is what this review catches first.
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.