737NG program basis
Boeing 737NG maintenance program records review
A 737NG maintenance program records review verifies that the airframe has been maintained against an approved program and that the program version on file matches the tasks actually accomplished. It suits teams pricing, transferring, or re-registering a Boeing 737NG when the program basis has to hold up under a buyer's technical scrutiny. The work traces approved revisions, sampling and escalation approvals, and any bridge from a prior operator's program to the current one. You receive an exception list tied to source documents, a map from each program element to its evidence, and a plan to close the gaps.
When this review is needed
- A 737NG is being priced and the buyer wants proof the program on file is the one the tasks were flown against.
- The aircraft changed operators and the receiving side needs the program bridge documented before induction.
- A registry change requires showing the program was approved and kept current under the outgoing authority.
- Task escalations were applied and someone must confirm each carried an approval before the interval moved.
The problem
The program a 737NG was actually maintained to is rarely a single tidy document. It is a base revision, a stack of amendments, sampling approvals, and an operator bridge, and the version quoted in a status list is often not the one the shop worked. Escalated intervals and self-imposed variations make it worse, because the approval that authorized the change lives in a different file than the task that used it.
What gets reviewed
- The base program revision and every amendment embodied over the aircraft's life
- Sampling, escalation, and reliability approvals that changed any task interval
- The bridge from a prior operator's program to the current maintained program
- Alignment between the program version on the status list and the version tasks were signed against
- Self-imposed variations and short-term extensions and their supporting authority
- Effectivity of program tasks for this serial number and configuration
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 embodied program revision is present and its effective date precedes the tasks that cite it
- Every escalated interval traces to a dated sampling or reliability approval, not a summary note
- The program bridge accounts for each interval carried across the operator change
- The status list program version matches the revision the accomplished tasks reference
- Short-term extensions were authorized and cleared within the window they granted
Evidence normally required
- The current approved maintenance program and its full revision history
- Sampling, escalation, and reliability approval letters affecting task intervals
- The program bridge or transfer analysis from any prior operator
- Maintenance status list showing the program version in force
- A sample of accomplished task cards citing program tasks and intervals
Common discrepancies
- An escalated interval in use with no approval letter behind the change
- The status list quoting a program revision the task cards never referenced
- A program bridge that omits several intervals carried across an operator change
- Short-term extensions applied but never formally cleared once the window closed
What is at stake
If the program basis cannot be reconstructed, every downstream status figure inherits the doubt. A buyer prices in the risk that intervals were escalated without authority, or discounts the asset until the bridge is proven. Left unresolved, the question resurfaces at the next induction, when the receiving CAMO refuses to accept intervals it cannot trace to an approved source.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the program lineage
Collect the base revision, every amendment, and each operator bridge so the maintained program can be reconstructed in order.
Trace interval authority
Match each escalation, sampling, and extension to the dated approval that authorized it before any task used the new interval.
Reconcile list to evidence
Compare the program version on the status list against the revision the accomplished task cards cite.
Report and plan closure
Deliver the exception list and source map, and name the owner for each missing approval or bridge element.
What the buyer receives
- An exception list keyed to each unproven program element and its missing evidence
- A source map linking program revisions, approvals, and the tasks that used them
- A closure plan naming who supplies each missing approval or bridge element
Who uses the output
How the work fits into the transaction or program
The program basis sits underneath every other 737NG records review, because task cards, non-routines, and status figures all reference intervals the program defines. Confirming the program first means the later reviews have a settled reference to check against rather than a moving one.
Aircraft-specific considerations
A 737NG that has passed through several operators usually carries more than one program lineage, and the bridge between them is where intervals quietly shift. Reliability-driven escalations are common on this type after high-cycle service, so the approval trail behind each moved interval matters more than on a young airframe. Engine and APU program elements are often managed on separate reliability data, which the airframe program has to reconcile rather than restate.
Jurisdiction-specific considerations
A 737NG maintained under an FAA operator program and later placed with an EASA operator, or the reverse, needs the program bridge to show how intervals map across the two frameworks. The review documents which authority approved each program version in force at the time, so the receiving side can see the basis rather than assume equivalence.
Regulatory limits
The review reports what the program evidence supports and where it is missing. It does not approve a maintenance program, grant an escalation, make an airworthiness determination, or substitute for the receiving operator's acceptance of the aircraft onto its own approved program.
What this review does not cover
- Drafting or submitting a new maintenance program for approval
- Physical inspection or condition survey of the aircraft
- Engine and APU on-condition reliability analysis beyond program reconciliation
Specific to this review
- The program version quoted on a 737NG status list frequently trails the revision the shop actually worked, so both are checked, not just the list.
- An interval escalation without its approval letter is treated as unproven, because the escalated task and its authority are usually filed apart.
- The operator bridge is the highest-risk element on a re-marketed 737NG, since intervals carried across a program change are where authority most often goes missing.
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
Does this review tell us whether the aircraft is airworthy?
No. It confirms the maintenance program basis is approved, current, and traceable to the tasks that used it. Airworthiness determinations and program acceptance stay with the receiving operator and its authority; this work gives them a documented basis to act on.
What if the aircraft was bridged between two operators' programs?
The bridge is the core of the review. We trace each interval carried across the change to its approval, flag any that moved without authority, and record which authority approved the program in force on each side of the transition.
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.