Program bridging
How to bridge an aircraft maintenance program
Bridging a maintenance program means moving an aircraft from one program to another so completed work carries over correctly and nothing falls due unexpectedly under the new program. It is read by airworthiness teams transitioning an aircraft at a change of operator or registry. The work covers the task-by-task mapping between the two programs, the interval and threshold differences, the last accomplishment for each task, the new due derived from it, and the documentation behind each carried-over item. You produce a bridging analysis, a revised due-list under the new program, and the documentation supporting every carried-over accomplishment.
When this review is needed
- An aircraft is moving to a new operator or registry and its maintenance program is changing with it.
- Two programs differ in intervals, thresholds, or task definitions and completed work has to be matched across them.
- A transition team needs a documented bridge so the new due-list can be reviewed and trusted.
- An incoming program contains tasks the outgoing one never required and their starting point has to be set.
The problem
Two maintenance programs can name similar tasks that cover different work, so a task done under the outgoing program does not always map one for one to its apparent counterpart. Intervals and thresholds shift between programs, and a carried-over accomplishment that ignores a threshold difference can land a task due immediately under the new program. The work is exacting because each task has to be matched on definition and on timing, not just on name, and a single miscarry surfaces as an unplanned due date after the transition.
What gets reviewed
- The outgoing and incoming programs mapped task by task
- Interval, threshold, and definition differences between the two
- The last accomplishment for each task under the outgoing program
- The new due derived from that accomplishment under the incoming program
- Incoming tasks with no outgoing counterpart and their starting point
- The documentation that supports each carried-over item
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 incoming task maps to its outgoing counterpart or is flagged as new
- The last accomplishment for each task traces to a source document
- New dues are derived correctly from the carried-over accomplishment
- Interval and threshold differences are documented rather than averaged over
- Each carried-over item is checked against the incoming threshold, not only its interval
Evidence normally required
- The outgoing maintenance program and the aircraft's accomplishment history
- The incoming maintenance program with intervals and thresholds
- Source documents for the last accomplishment of each affected task
- The transition date that anchors the new due calculations
Common discrepancies
- An incoming task with no clean counterpart in the outgoing program
- A carried-over accomplishment that does not trace to a source document
- A new due derived from an interval difference that was not accounted for
- A task that lands due immediately because the bridge missed its threshold
- Two similarly named tasks treated as equivalent when they cover different work
What is at stake
A task that falls due immediately because the bridge missed its incoming threshold disrupts the transition just as the aircraft changes hands. A carried-over accomplishment that does not trace to a source document leaves the new due-list resting on an assertion, and an incoming task with no clean counterpart can be missed entirely until it surfaces later as overdue.
How the work runs
Map task to task
Match each incoming task to its outgoing counterpart on definition and scope, flagging any incoming task that is genuinely new.
Carry the accomplishment
Trace the last accomplishment for each mapped task to a source document and carry it across to the new program.
Derive the new due
Calculate each new due from the carried accomplishment under the incoming interval and threshold.
Check the thresholds
Confirm no carried-over item lands due immediately because an incoming threshold was missed, and set starting points for new tasks.
What the buyer receives
- A bridging analysis mapping the two programs task by task
- A revised due-list under the incoming program
- Supporting documentation for each carried-over accomplishment
Who uses the output
- Airworthiness teams adopting the new program
- Records teams loading the revised due-list into tracking
- Transition managers confirming nothing falls due unexpectedly
How the work fits into the transaction or program
Bridging runs at the transition, after the records have been reconciled and before the new program governs the aircraft. Its revised due-list feeds the tracking system and the records baseline the aircraft carries under its new operator.
Jurisdiction-specific considerations
A change of registry often comes with a change of program basis, since each authority approves maintenance programs under its own framework. The bridge is built against the incoming authority's program rather than treating the two programs as interchangeable.
Regulatory limits
A bridge maps and documents how completed work carries into a new program. It does not approve the program, make an airworthiness determination, or guarantee an authority will accept the bridge, and the new due-list depends on the incoming program being correctly applied.
What this review does not cover
- Approving or issuing the incoming maintenance program
- Performing the maintenance tasks the new due-list schedules
- Any airworthiness determination or regulatory approval
Specific to this review
- A sound bridge turns on matching task definitions rather than intervals alone, because two programs can name similar tasks that cover different work and cannot be carried across one for one.
- A miscarried threshold can make a task fall due immediately under the new program, so each carried-over item is checked against the incoming threshold, not only its interval.
- An incoming task with no outgoing counterpart needs a deliberate starting point, because nothing in the old program's history sets when it first comes due.
Sources
Federal Aviation Administration. FAA acceptance criteria for electronic recordkeeping systems and electronic signatures.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Frequently asked questions
Why is matching task definitions harder than matching intervals?
Because two programs can give similar names to tasks that cover different work. An interval difference is arithmetic, but a definition mismatch means a task done under the old program may not actually satisfy its apparent counterpart in the new one, so the work has to be compared on what each task covers.
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.
Adapt the checklist to your asset, event, and jurisdiction.