787 program status
Boeing 787 family maintenance program records review
This review examines the maintenance program records governing a specific Boeing 787 family aircraft to confirm the program in use is approved, current, and traceable to its source revisions. A records specialist runs it for the operator or the party inducting the tail, usually before a program bridge or a transaction. It checks the approved program baseline, task escalations, sampling and bridging analyses, and the source-document references behind each interval. You receive an exception list against the program status, a source map from each task to its approval basis, and a closure plan for the intervals that cannot be tied back.
When this review is needed
- A 787 is moving to a new operator and the program has to bridge onto the receiving intervals.
- Escalations were applied to program tasks and the approval basis for them needs confirming.
- The program status references revisions that are not held in the records themselves.
- A buyer wants the program baseline verified before pricing the maintenance state.
The problem
A 787 maintenance program accumulates escalations, revisions, and bridging decisions across the life of the operator using it, and each one should trace to an approval and a source document. Over time the status list becomes a set of intervals that everyone runs to but few can tie back to the revision that set them. An escalation applied without its supporting analysis, or a task carried against a superseded revision, leaves the program looking current while resting on nothing an auditor would accept.
What gets reviewed
- The approved program baseline and the revision level the aircraft is actually run to
- Task escalations checked against the sampling or reliability analysis that authorized them
- Bridging analyses where the program was moved between operators or revisions
- Source-document references behind each interval and threshold in the status
- Structural, zonal, and systems task groups reconciled to the current program revision
- Any operator-specific variations and their approval relative to the type program
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 the aircraft is run to matches an approved program document in the file
- Each escalated interval is supported by the analysis that authorized the escalation
- Bridging decisions carry an analysis that maps the prior program onto the current one
- Structural and systems task thresholds trace to the correct source revision
- Operator variations from the type program carry the approval the change requires
Evidence normally required
- The current maintenance program status and interval list for the tail
- The approved program document and its revision history
- Escalation, sampling, and reliability analyses applied to the program
- Any bridging analysis from a prior operator or revision
- Source-document references for structural, zonal, and systems tasks
Common discrepancies
- An escalated interval with no sampling or reliability analysis to support it
- A program run to a revision that the records do not actually contain
- A bridging decision applied without an analysis mapping the prior program across
- An operator variation from the type program that lacks the approval it needed
What is at stake
A program interval that cannot be traced to an approved basis forces a conservative reset to the baseline, which can pull tasks forward and disrupt the maintenance plan. At a transfer, an unbridged or unsupported program surfaces at the first check under the new operator, and demonstrating the program was compliant after the fact is far harder than confirming it while the source revisions are in hand.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the baseline
Establish the approved program document and revision the aircraft is actually run to.
Trace the intervals
Tie each task, threshold, and escalation to its source revision and approval basis.
Check the bridges
Confirm any bridging or operator variation carries the analysis and approval it needs.
List the exceptions
Record untraceable intervals and sequence the analyses to recover or re-approve.
What the buyer receives
- An exception list against the program status with each untraceable interval
- A source map tying every task and threshold to its approval basis and revision
- A closure plan for the analyses to recover and the intervals to reset or re-approve
Who uses the output
- Continuing-airworthiness teams confirming the program is current and defensible
- Records teams assembling the program basis before a bridge or an audit
- Asset and acquisition teams pricing the maintenance state the program supports
How the work fits into the transaction or program
The program status sets the intervals that every task-card, structural, and component review measures against, so this review confirms that baseline before those downstream reviews rely on it. Its bridging findings feed the transition work when the tail moves operators, and its exception list drives the analyses that have to be recovered before an audit.
Aircraft-specific considerations
787 programs place heavy weight on scheduled structural and systems tasks tied to configuration and software state, so an escalation on this type can depend on data a metal-airframe program would not carry. Composite structure changes the inspection logic relative to older widebodies, which means the source revision behind a structural threshold matters more here. The review is scoped to the program this specific aircraft has been run to rather than the generic type program.
Jurisdiction-specific considerations
An FAA-accepted program and an EASA CAMO program structure approvals and escalations differently, so the review notes where a program task or escalation will need re-approval to satisfy the receiving authority.
Regulatory limits
The review confirms the program records are current and traceable to an approved basis. It does not approve or revise the maintenance program, escalate any task, or make an airworthiness determination on the aircraft.
What this review does not cover
- Authoring, revising, or approving the maintenance program
- Performing or approving a task escalation or reliability analysis
- Any airworthiness determination on the aircraft
Specific to this review
- An escalated interval is only as good as the analysis behind it, and that analysis is the document most often missing from a program status handed across a deal.
- Running an aircraft to a revision the records do not contain is a silent failure, because the intervals still look plausible until someone asks for the source.
- Structural task thresholds on a composite airframe trace to different logic than on a metal type, so the source revision has to be the right one, not merely a recent one.
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
What happens to an interval we cannot trace to an approved revision?
Until the supporting analysis or approved revision is recovered, the defensible position is to reset the interval to the approved baseline, which can pull the task forward. Recovering the source is usually cheaper than living with the reset, but it depends on whether the prior operator or the analysis author still holds the document.
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.