Program status diligence
Checking maintenance program records against data-room source files
A maintenance program source check reads the program status a seller posts against the approvals and revision records uploaded alongside it. It confirms that the program basis, the intervals on the task due list, and any escalations or bridging history are supported by documents in the room rather than by the summary alone. Diligence teams commission it after the data room opens and before the exception schedule is finalized. It returns a findings register the deal team can negotiate from.
When this review is needed
- The seller's due list was exported from a maintenance system whose program revision cannot be found in the uploads.
- The aircraft changed operators and the bridging between the old and new programs needs evidencing before pricing.
- Escalated intervals appear on the status and the approvals behind the escalations are missing from the room.
- The buyer's CAMO wants the program basis confirmed before it drafts the induction plan.
The problem
A task due list looks authoritative because software produced it, yet it only reflects whatever program revision was loaded when the export ran. Data rooms often carry the export and skip the approved program, its revision log, and the operator's variations, so nobody reading the room can say whether a due date rests on an approved interval or on an assumption keyed in years ago.
What gets reviewed
- The approved program document and its revision status located in the uploads and matched to the due-list export
- Interval escalations and permitted variations traced to their approvals
- Any bridging records reviewed where the aircraft moved between programs or operators
- Sampled tasks followed from the due list back to their last accomplishment records
- Out-of-phase and low-utilization adjustments checked for documented justification
- Program answers given in Q&A reconciled with the documents that arrive afterward
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 revision named on the due-list export exists in the room and is the approved one
- Each escalated interval carries an approval or an accepted justification in the uploads
- Sampled last-done dates on the status agree with the certification in the underlying work records
- Transition bridging accounts for every task affected by a program change, without silent deletions
- Utilization assumptions in the forecast agree with the hours and cycles reported elsewhere in the room
Evidence normally required
- Data-room access with the current index and Q&A thread
- The task due list or program status export the seller represents
- The approved maintenance program and its revision history, as uploaded
- Bridging documents from any operator or program transition
- Recent utilization reports for hours and cycles
Common discrepancies
- A due list generated against a program revision two issues older than the approved one
- Escalations inherited from a prior operator whose approval never transferred with the aircraft
- Bridging paperwork that covers airframe tasks but omits component and structural items
- Last-done dates that trace to a planning entry rather than to a certified work record
What is at stake
Intervals that cannot be traced to an approved basis become the buyer's problem at induction, when the receiving CAMO must rebuild compliance from source. Tasks may come due earlier than the priced forecast, a missed escalation approval can invalidate projected check dates, and the cost lands after the price is locked.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the program basis
Locate the approved program and its revision log, and establish which revision the due-list export was generated against.
Trace intervals and changes
Follow escalations, variations, and bridging entries to the approvals that authorize them.
Sample the status
Pull last-done evidence for a risk-weighted selection of tasks and compare it with the exported dates.
Hand over the register
Deliver findings with folder references and the Q&A requests that would close them.
What the buyer receives
Who uses the output
- The buyer's CAMO planning induction onto its own program
- Deal teams deciding which program gaps become closing conditions
- Technical advisors reconciling the maintenance forecast used in pricing
How the work fits into the transaction or program
Program status touches almost every other record in the room, so this check usually runs early in diligence. Its output tells the task-card and shop-visit reviewers where compliance claims are weakest, and it hands the buyer's CAMO a head start on the bridging work that follows closing.
Jurisdiction-specific considerations
Under EASA, Part-M and the CAMO regulation tie the aircraft maintenance program to an approval or a declared basis with a controlled revision trail. FAA operators under Part 121 or 135 hold program requirements in their operations specifications, while Part 91 aircraft may follow inspection programs with thinner paper trails, so what the room should contain depends on the operating history.
Regulatory limits
The check reports whether posted documents support the represented program status. It does not approve a maintenance program, declare compliance with any operating rule, or determine airworthiness; those functions remain with the operator, its CAMO, and the responsible authority.
What this review does not cover
- Building or bridging a maintenance program for the buyer
- Full task-by-task compliance verification across the program
- Forecasting maintenance cost or check pricing
Specific to this review
- Due-list exports carry no evidentiary weight on their own; the same system will happily print due dates against a superseded program revision.
- Escalation approvals are operator-specific in most regimes and rarely survive an aircraft sale, a detail sellers' summaries tend to gloss over.
- Gaps in bridging concentrate in component hard times and structural sampling tasks, the lines least visible on a headline due list.
- Sampling last-done evidence catches more than reading the status alone, because planning entries drift from certified records over time.
- Low-utilization operators accumulate calendar-driven findings that a cycles-based due list understates, so the sampling is weighted by how the aircraft was actually flown.
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 program is approved by the authority, so why would the status be wrong?
Approval attaches to a specific revision held by a specific operator. Due lists drift away from that revision through system updates, inherited escalations, and bridging shortcuts, so the check verifies the connection between the approved document and the export rather than assuming it.
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.