Maintenance program records
Boeing 737 MAX maintenance program records review
This review examines the maintenance program records a Boeing 737 MAX has been operated to, confirming the program status the file asserts is supported and current. It runs at a program change, a transfer between operators, or a diligence pass, run by or for the party inheriting or relying on the program. It covers the approved program revision in use, the task escalations applied, the bridging analyses behind any program change, and the source references each program element rests on. You receive an exception list per program element, a source map to the approvals behind it, and a closure plan for the elements the file cannot substantiate.
When this review is needed
- A 737 MAX is moving to a new operator whose program the current status has to bridge onto.
- A task escalation was applied and the approval and analysis behind it have to be produced.
- A buyer will test whether the program revision in use is the approved current one.
- A prior program change left a bridging gap that was carried rather than closed.
The problem
The maintenance program is the framework every task status is computed against, and a 737 MAX that has moved between operators carries a program history that rarely reads as one continuous line. A revision in use may not be the current approved one, an escalation may be applied without the analysis that justified it, and a bridging analysis from an earlier operator change may cover only part of what the current status depends on. The program status looks settled while the approvals under it are incomplete.
What gets reviewed
- The approved program revision the aircraft is operated to
- Task escalations applied and the approval and analysis behind each
- Bridging analyses supporting any program change in the history
- Source references tying each program element to its approval
- Program-driven task status reconciled to the revision in use
- Elements carried from a prior operator's program without a supporting basis
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 revision in use is the current approved program revision for the aircraft
- Each task escalation carries the approval and the analysis that justified it
- A bridging analysis covers every task the current status depends on, not part of them
- Each program element traces to a source reference that supports it
- Task status computed against the program reconciles to the revision actually in use
Evidence normally required
- The maintenance program status and the revision in use
- Approved program revisions and their approval records
- Task escalation approvals and the supporting analyses
- Bridging analyses from prior program or operator changes
- The source references the program elements rest on
Common discrepancies
- A program revision in use that is not the current approved one
- A task escalation applied without the analysis that justified it on file
- A bridging analysis that covers only part of the tasks the status depends on
- A program element carried from a prior operator with no supporting basis
What is at stake
A program status resting on an unapproved revision or an unsupported escalation is a finding that surfaces at induction or diligence, and it can force a return to a more conservative interval until the approval is produced. A bridging gap left from an earlier change compounds at the next transfer, because the receiving operator inherits an analysis that never fully closed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the revision in use
Confirm the aircraft is operated to the current approved program revision.
Test escalations and additions
Check each escalation for its approval and the analysis that justified it.
Close the bridging
Confirm any bridging analysis covers every task the current status depends on.
Report the exceptions
Deliver the per-element exception list, source map, and closure plan.
What the buyer receives
- An exception list per program element graded by revision, escalation, and bridging
- A source map from each program element to its approval basis
- A closure plan for the elements the file cannot substantiate
Who uses the output
- Continuing-airworthiness teams bridging the program onto a new operator
- Asset managers testing whether the program status survives diligence
- Records teams recovering the approvals behind unsupported escalations
How the work fits into the transaction or program
The maintenance program is the framework the task-card and inspection status are computed against, so a program whose approvals are incomplete undermines every task figure above it. This review confirms the program the aircraft was operated to is approved and supported, and its exception list drives the bridging and approval recovery a transfer depends on.
Aircraft-specific considerations
The 737 MAX program reflects the type's return-to-service requirements and the configuration each operator embodied, so a task set can be right for one operator's configuration and short for another's. Where an operator applied a modification that changes a task's applicability, the program record has to show the escalation or addition that followed, which is the point a 737 MAX program most often diverges from the delivered baseline.
Jurisdiction-specific considerations
A 737 MAX moving between an FAA and an EASA operator has to bridge onto a program approved under the receiving authority, so escalations and intervals approved under one system are checked for whether the receiving side will recognize or require them to be restated.
Regulatory limits
This review confirms the program records are supported and internally consistent. It does not approve a maintenance program, authorize a task escalation, or make any airworthiness determination on the aircraft.
What this review does not cover
- Authoring, revising, or approving the maintenance program
- Approving a task escalation or interval change
- Any airworthiness determination on the aircraft
Specific to this review
- A task escalation is only as good as the analysis behind it, so an escalation applied without that analysis reverts to the conservative interval until it is produced.
- A bridging analysis that covers only part of the current status is worse than none, because it reads as complete while leaving tasks unsupported.
- On the 737 MAX, a modification an operator embodied can change a task's applicability, so the program record has to carry the escalation or addition that followed.
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 aircraft has been flying on this program. Why review it before a transfer?
Operating on a program is not the same as being able to produce the approvals under it. A revision may not be the current approved one, and an escalation may lack its analysis. A receiving operator bridges onto whatever the records can actually support, so this review finds the elements that will not carry across before the transfer relies on them.
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.