Program bridging gap
Incomplete maintenance program bridging documentation
Incomplete bridging documentation means a maintenance program change was made without a full record of how each task moved from the old program to the new one, so some tasks have no traceable mapping. It is a problem for lessors, airlines, and MROs at an operator change, a program revision, or a registry transition. The check reads the bridging analysis against both programs and the accomplishment history. You receive a list of tasks with missing or unclear bridging and the path to close each.
When this review is needed
- An aircraft moves to a new operator's program and each task must map from the prior program to the new one.
- A program revision changed intervals or thresholds and the bridging analysis is partial.
- A registry transition requires the prior maintenance history to bridge into the receiving program.
The problem
When a program changes, every recurring task has to be carried across with its interval, its threshold, and its last accomplishment, and the bridging analysis is the record that shows it was. A task left out of the analysis, or bridged without its accomplishment history, can fall due on the wrong basis or fall out of the program entirely. The new program then looks complete while a task quietly lost its place.
What gets reviewed
- Each recurring task in the source program and its counterpart in the target program
- The interval, threshold, and last accomplishment carried across for each task
- The bridging analysis and the decisions it records
- Tasks with no clear counterpart in the new program
- Escalations, de-escalations, and one-time bridging actions
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 source-program task maps to a target-program task or a documented disposition
- Intervals and thresholds are carried across with their basis shown
- Last accomplishment is bridged so the next due point is correct
- Tasks with no counterpart are dispositioned, not silently dropped
- Bridging escalations and de-escalations carry the analysis behind them
Evidence normally required
- Source and target maintenance program documents
- The bridging analysis or transition mapping
- Task accomplishment history from the prior program
- Interval, threshold, and escalation records
Common discrepancies
- A recurring task with no mapping into the new program
- A bridged task missing the last accomplishment needed to set its due point
- An interval carried across with no recorded basis for the change
- A task dropped at transition with no disposition documenting why
What is at stake
An unbridged task can be flown past its due point because the new program never inherited it, or repeated unnecessarily because its prior accomplishment was lost. Closing the gap means reconstructing the mapping and the history, and at a transition incomplete bridging blocks the receiving operator from accepting the program basis.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Pair the programs
Set the source and target programs side by side and identify the recurring tasks each one carries.
Trace each mapping
Confirm every source task maps to a target task or a documented disposition, with its interval and threshold basis shown.
Bridge the history
Check that the last accomplishment carried across so the next due point lands correctly for each task.
Close the analysis
Reconstruct missing mappings, disposition tasks with no counterpart, and escalate the decisions that need it.
What the buyer receives
- A register of tasks with missing or unclear bridging
- The mapping and accomplishment history reconstructed for each affected task
- A closure path per task, whether bridging it, dispositioning it, or escalating the decision
Who uses the output
- Continuing-airworthiness staff loading the bridged tasks into the receiving program
- Engineering judging escalation and de-escalation decisions in the analysis
- Records teams completing the transition mapping before acceptance
How the work fits into the transaction or program
The review checks the completeness of the bridging itself within a program transition, so a task that exists in both programs but was never mapped is caught before the new program is relied on. It feeds the transition mapping and the discrepancy register.
Jurisdiction-specific considerations
A program accepted under one authority does not bridge automatically into another. Where the aircraft is moving registries, the bridging is read for whether the receiving authority accepts the mapping basis and the prior accomplishment history.
Regulatory limits
The review confirms whether the bridging is complete, traceable, and internally consistent. It does not approve a maintenance program, set intervals on the authority's behalf, or make an airworthiness determination.
What this review does not cover
- Approving the maintenance program or its intervals on the authority's behalf
- Authoring the operator's target program
- Issuing any airworthiness determination on the bridged status
Specific to this review
- A new program can read as complete while a task that lost its bridging mapping has quietly fallen out of scheduling.
- Bridging carries three things per task, the interval, the threshold, and the last accomplishment, and a gap in any one sets the next due point wrong.
- A task with no counterpart in the new program is treated as requiring a documented disposition, not as safe to drop.
Sources
Federal Aviation Administration. FAA acceptance criteria for electronic recordkeeping systems and electronic signatures.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Why does a complete-looking new program still need bridging checked?
The new program can list a full task set and still have dropped a task that existed in the prior program but was never mapped across. Bridging confirms each task moved with its interval, threshold, and last accomplishment, so nothing quietly fell out of scheduling.
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.