Program bridge evidence
Maintenance program records review for an FAA to EASA transition
When an aircraft leaves an FAA operator's program for an EASA registry, the receiving CAMO must build its maintenance program on the accomplishment history the records prove. This review checks that the program records can carry that weight: approved program revisions, task accomplishment status, escalation approvals, bridging analyses, and the source documents behind the maintenance program status. It is done during transition planning by a records specialist working for the lessor, buyer, or outgoing operator, and it yields an evidence map, a gap list, and document requests shaped around the questions an EASA program review raises.
When this review is needed
- The receiving CAMO has requested the current program, its approval history, and the task status to start its bridge analysis.
- The aircraft operated under escalated intervals and the approvals behind those escalations have to be produced.
- Program revisions across prior operators were never reconciled, and the current status list does not say which revision each task was accomplished under.
- Redelivery conditions require last-done next-due data that stands up to an independent program review.
The problem
A maintenance program status looks orderly until someone asks which approved revision governed each accomplishment and where the escalation approvals live. FAA operators revise programs through their own approval channels, and after two or three operators the paper trail behind interval changes scatters. The EASA-side CAMO cannot bridge tasks it cannot anchor, so every unanchored line becomes a conservative assumption, and conservative assumptions compress the maintenance the new operator must do immediately.
What gets reviewed
- Approved program revisions across the operating history, with the approval evidence for each
- Task accomplishment status reconciled to work orders, task cards, and check packages
- Escalation and interval-change approvals and the reliability data cited to justify them
- Bridging analyses from any earlier operator transitions still embedded in the status
- ICA incorporation for embodied modifications feeding program tasks
- Last-done next-due data quality for the tasks the receiving program will inherit
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 in the history has its approval record, and revision dates align with the accomplishments claimed under it
- Sampled task accomplishments trace from the status list to a signed task card or work-order entry
- Every escalated interval carries its approval and the analysis behind it, at the amendment level actually used
- Last-done next-due values recompute correctly from source documents, including any utilization corrections
- Tasks introduced by ICA from modifications appear in the status rather than only in the modification file
Evidence normally required
- Current maintenance program document and its revision and approval history
- Maintenance program status with last-done next-due data
- Task cards, work orders, and check packages supporting recent accomplishments
- Escalation approvals and supporting reliability analyses
- Prior bridging analyses from earlier operator or registry transitions
Common discrepancies
- Escalated intervals still applied in the status after the fleet-level approval behind them lapsed with the prior operator
- Status lines whose last-done source document cannot be produced, forcing a due-now assumption
- Program revisions applied retroactively in the tracking system, misdating accomplishment intervals
- ICA tasks from embodied STCs missing from the program even though the equipment is installed
What is at stake
Where the records cannot prove when a task was last done and under which interval, the receiving program treats it as due. Across an airframe that can mean early accomplishment of checks and tasks worth far more than the cost of settling the records, plus a compressed induction schedule at exactly the moment the new operator wants the aircraft flying.
How the work runs
Reconstruct the program history
Line up every program revision and approval across the operating history against the accomplishment record.
Sample and trace the status
Trace a risk-weighted sample of status lines to task cards and work orders, recomputing due points.
Test the bridge assumptions
Identify which lines the receiving CAMO can anchor and which will default to due-now without more evidence.
Deliver the gap and request set
Issue the evidence map, ranked gap list, and document requests to the parties holding source records.
What the buyer receives
- An evidence map linking program revisions, approvals, and task accomplishments
- A gap list marking which status lines will not survive the CAMO's bridge without more evidence
- A document request set for the operators, shops, and approval offices holding the missing pieces
- A summary of bridge risk the asset manager can use in delivery-condition discussions
Who uses the output
How the work fits into the transaction or program
This strand of the transition runs in parallel with the AD and modification reviews and hands its output directly to the receiving CAMO. Program evidence questions have long recovery times because they reach back through prior operators, so this review is scheduled early, and its gap list often drives the document requests for the whole transition.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
FAA operators maintain aircraft under programs approved through the 14 CFR 121.380 or 135.439 frameworks and their associated recordkeeping rules, while the receiving side works under EU 1321/2014, where the CAMO owns the program and the competent authority approves it. The two systems count and evidence intervals differently in places, and ICAO Annex 6 provides the common floor both refer back to. The review reads the records against the EASA expectations rather than the ones they were created under.
Regulatory limits
The review evaluates evidence. It does not write or approve a maintenance program, does not perform the CAMO's bridging analysis, does not extend or escalate any interval, and does not determine airworthiness. Program approval remains between the receiving CAMO and its competent authority.
What this review does not cover
- Authoring the EASA maintenance program or bridge document
- Reliability analysis or interval-escalation engineering
- Utilization forecasting or maintenance-cost modeling for the new operator
Specific to this review
- Bridging fails most often on interval provenance: the status shows a compliant last-done, but nobody can prove which approved interval governed it at the time.
- Escalations are operator approvals, and they die with the operator; an interval inherited from a prior program without fresh justification is the first thing a program reviewer resets.
- Tracking-system migrations between operators quietly rewrite accomplishment dates; recomputing a sample of next-due values from paper catches this fast.
- A due-now assumption on a handful of heavy structural tasks can move the induction check by weeks, which is why the gap list ranks items by maintenance value, never by count.
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). Export airworthiness approval requirements and special requirements of an importing authority.
Frequently asked questions
Who actually performs the bridging analysis, this review or the CAMO?
The CAMO. Bridging is the receiving organization's regulatory task under Part-M. This review makes the bridge feasible by proving, in advance, which accomplishments and intervals the records can support, so the CAMO analyzes against evidence instead of chasing documents mid-induction.
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.