Program bridging
Maintenance-program bridging records review
A maintenance-program bridging review reconciles task accomplishment and intervals when an aircraft moves from one maintenance program to another. It serves operators changing program revision or authority, lessors placing an asset onto a new lessee's program, and management companies transferring a client aircraft. The trigger is a program change where the old and new task structures do not line up one to one. It maps each task across the two programs, confirms what has been accomplished translates correctly, and identifies tasks that need a bridging step. You receive a task-by-task bridging matrix, a list of items needing accomplishment or substantiation, and a forecast aligned to the new program.
When this review is needed
- An aircraft is moving to a different operator's program and the task structures differ.
- A program revision changes intervals or packaging and the open status has to be re-cast against it.
- An asset is changing authority and the prior program must be bridged onto the new basis.
- Tracking shows tasks that have no clear equivalent under the program the aircraft is moving to.
The problem
Two maintenance programs rarely map task for task. Intervals differ, tasks are split or combined, and accomplishment under the old program does not always satisfy the new one. Without a deliberate bridge, work gets double-counted, a task quietly disappears at the seam, or an item is treated as due that was already covered. Each of those costs hangar time or, worse, leaves a real task unbridged.
What gets reviewed
- The outgoing and incoming maintenance programs and their task structures
- Task-by-task mapping including split, combined, and renamed items
- Interval translation where the new program changes thresholds or packaging
- Work done under the old program checked for credit under the new one
- AD and SB embodiment carried correctly across the program change
- A reconciled forecast cast against the new 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
- Every outgoing task is mapped to its incoming equivalent or flagged as having none
- Interval translation preserves the more conservative position where the two programs differ
- Accomplishment claimed for credit actually satisfies the incoming task it is credited against
- No task is counted twice across the seam and none is dropped between programs
- AD and SB embodiment status carries across the change without losing effectivity
- The post-bridge forecast reconciles to the accomplished status, with no orphaned due items
Evidence normally required
Common discrepancies
- An outgoing task with no clean equivalent under the incoming program
- Interval translation that would relax a threshold rather than hold the conservative one
- A credit taken against a task the work does not fully satisfy
- A task double-counted because both programs claim it at the seam
- An SB whose effectivity is lost in the move between programs
- A post-bridge forecast with due items that reconcile to nothing accomplished
What is at stake
An unbridged program change produces a forecast that is wrong in both directions. Some tasks are repeated needlessly, others fall through the gap between programs, and the first check under the new program is scoped against a status that does not reconcile. Untangling it after the fact is far costlier than bridging it once at the change.
How the work runs
Set both programs side by side
Lay out the outgoing and incoming task structures and identify where they split, combine, or rename tasks.
Map task by task
Match each task across the programs, translate intervals to the conservative position, and flag items with no equivalent.
Test the credit
Confirm accomplishment claimed for credit actually satisfies the incoming task it is credited against.
Cast the new forecast
Produce a forecast on the incoming program that reconciles to accomplished status with no orphaned items.
What the buyer receives
- A task-by-task bridging matrix across the two programs
- A list of items needing accomplishment or substantiation to complete the bridge
- A reconciled forecast aligned to the incoming program
Who uses the output
- Continuing-airworthiness and planning teams running the new program
- Engineering deciding how to credit or re-accomplish bridged tasks
- Records teams holding the bridged status as the new baseline
How the work fits into the transaction or program
Bridging sits inside an induction or a transition, wherever the program changes. It takes the validated status into the new program so the first forecast and the first check under that program are built on a reconciled position.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Type matters because the source program structure differs across families. Where the type carries a sampling or escalation regime, the bridge has to handle how partially-sampled tasks translate, not only the named tasks themselves.
Jurisdiction-specific considerations
A program change that also crosses authorities can require the new authority to accept the bridge basis. Credit allowed under one authority's program is not automatically credit under another, so the bridge documents the basis for each carried item.
Regulatory limits
The review reconciles tasks, intervals, and accomplishment between programs and documents the bridge. It does not approve the maintenance program, grant credit on an authority's behalf, or make an airworthiness determination.
What this review does not cover
- Approval or acceptance of either maintenance program
- Physical accomplishment of any bridged task
- Any airworthiness determination or return to service
Specific to this review
- Two programs rarely map task for task, so the failure modes are double-counting on one side and a dropped task on the other, at the same seam.
- Where intervals differ, the bridge holds the more conservative position rather than adopting whichever program is more permissive.
- Accomplishment credit is tested against the specific incoming task, because work done under the old program does not always satisfy the new one in full.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
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 usually goes wrong without a bridge?
Tasks get double-counted or dropped at the boundary between the two programs, and accomplishment is credited where it does not fully satisfy the new task. The bridging matrix makes each of those decisions explicit and traceable.
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.
Walk through your situation with an engineer who has done this work.