Cross-authority program bridging
Multi-jurisdiction fleet maintenance program records transition review
This review tests whether a fleet's maintenance program records will bridge onto the programs the receiving authorities require. It is run for the party moving tails across FAA, EASA, and TCCA registers, before the package is handed over. Each program revision, task escalation, and bridging analysis is traced to its source document and checked against what each receiving system will accept. You receive an evidence map keyed to the maintenance program status, a gap list where tasks or intervals do not bridge, and a request set for the program evidence each authority will demand.
When this review is needed
- Tails built on one operator's approved program are moving to registers whose receivers run different ones.
- Task escalations approved under one authority now have to be justified to another.
- A maintenance program status was assembled for one handover and now faces parallel bridging.
- Source-document references behind the program have drifted and need reconnecting before transfer.
The problem
Two operating systems rarely run the same maintenance program, so a fleet's task history has to bridge to each receiver's program rather than copy across. An escalation approved under one authority may not be granted by another, and a task interval that reads compliant under the outgoing program can leave a gap once mapped onto the receiving one. When the source documents behind the program are not linked, even a clean-looking status cannot be defended to a receiving authority that asks where a task came from.
What gets reviewed
- Approved program revisions confirmed current and traceable to their source documents
- Task escalations checked for a basis each receiving authority will accept
- Bridging analysis assessed where the outgoing program maps onto a receiver's program
- Task intervals reconciled so no gap opens when translated to the receiving program
- Source-document references reconnected to the tasks that rely on them
- Tasks and intervals that do not bridge cleanly mapped to the tail and the receiving 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
- Each program task traces to an approved revision and its underlying source document
- Escalations carry a basis the receiving authority will recognize
- Task intervals mapped onto the receiving program leave no unexplained gap
- The bridging analysis reconciles the outgoing and receiving program for each tail
- Source references cited by the program point to documents actually held in the package
Evidence normally required
- The maintenance program and its approved revisions for every tail
- Task escalation approvals and the analyses behind them
- The receiving programs the tails must bridge onto
- Source documents underlying the program tasks
- Current task and interval status per tail
Common discrepancies
- An escalation approved under the outgoing authority that a receiver will not carry across
- A task interval that opens a gap once mapped onto the receiving program
- A program task citing a source document the package does not contain
- A program revision superseded but still referenced by the current status
What is at stake
A tail bridged on an unverified program can carry hidden task or interval gaps that surface at the first check under the receiving system. An escalation that does not carry across can pull a task forward and force it before delivery, and a missing source reference can stall acceptance until the basis is reconstructed. Across a fleet, these compound into schedule risk against a fixed transition date.
How the work runs
Establish the receiving programs
Confirm the program each receiving authority requires and how the outgoing program maps onto it per tail.
Trace revisions and sources
Confirm program tasks trace to current approved revisions and to the source documents held in the package.
Bridge and test intervals
Map task history onto each receiving program, checking escalations and intervals for gaps that open on translation.
Flag and request
List tasks and escalations that do not bridge and request the program evidence each receiver requires.
What the buyer receives
- A transition evidence map linking each program task to its revision and source per authority
- A gap list where tasks or intervals do not bridge to a receiving program
- A document request set for the program and escalation evidence each receiver requires
Who uses the output
- Continuing-airworthiness leads bridging each tail onto the receiving program
- Fleet planners sequencing tasks that will not carry across and must be done before delivery
- Records teams reconnecting source references the receiving authority will ask for
How the work fits into the transaction or program
The review runs before handover so bridging gaps and unsupported escalations are found while the outgoing program and its approvals are still accessible. Its gap list drives the tasks that must be brought forward and the source evidence that must be reconnected before each tail bridges onto its receiving program.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
Receiving authorities approve maintenance programs on their own terms, and an escalation or interval granted by one may not be recognized by another. The review maps the outgoing program onto each receiver's program and flags the tasks and escalations that need a fresh basis rather than assuming the program transfers intact.
Regulatory limits
The review reconciles and bridges program records so each receiving authority can approve the program for the tail. It does not approve a maintenance program, grant an escalation, or make an airworthiness determination.
What this review does not cover
- Authoring, revising, or approving any maintenance program
- Granting or extending task escalations
- Any airworthiness determination on a tail or a fleet
Specific to this review
- Bridging is the core difficulty: task history is translated onto each receiver's intervals, not copied, so a task that reads compliant under the outgoing program can open a gap on the receiving one.
- Escalations are the least transferable element of a program, because the analysis one authority approved does not bind another to grant the same interval.
- A program can look complete and still fail acceptance if its source-document references point to documents that never made it into the package.
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
Can we hand over the program the outgoing authority already approved?
Not on its own. The receiving authority approves the program it will operate under, so the outgoing program's tasks and escalations have to bridge to that program. Gaps in the bridge, and escalations a receiver will not grant, are exactly what surface at the first check under the new system.
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.