Air carrier fleet transition
Part 121 fleet-transition records review
A Part 121 fleet-transition records review checks that aircraft moving into or out of an air carrier's fleet carry records that satisfy carrier recordkeeping and bridge to the receiving maintenance program. It is run when a tail or a batch transfers between carriers, by or for the inducting operator. It covers AD and SB status, life-limited part trace, the prior program's task history, and the retention the air carrier rule requires. You receive an induction-readiness view per tail, a program-bridging gap list, and the evidence needed before the aircraft flies under the new certificate.
When this review is needed
- Aircraft are transferring between air carriers and have to induct under the receiving certificate.
- A batch of tails arrives on a deadline and each one needs a program-bridging read.
- The outgoing carrier's task history has to map onto the receiving carrier's program.
- Carrier recordkeeping retention has to be demonstrated for the transferred fleet.
The problem
Two carriers rarely run the same maintenance program, so a transferred aircraft's task history has to be bridged rather than copied. Status lists generated under the prior program do not automatically satisfy the receiving carrier's recordkeeping, and a batch transfer multiplies every per-tail discrepancy across a deadline that the schedule depends on.
What gets reviewed
- AD and SB status reconciled to accomplishment evidence under the receiving certificate
- Life-limited part trace carried across the transfer
- Prior program task history mapped onto the receiving carrier's program
- Carrier recordkeeping retention demonstrated for the transferred records
- Per-tail induction readiness across the batch
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
- Task history from the prior program bridges to the receiving carrier's intervals without an unexplained gap
- AD and SB status is supported by accomplishment evidence the receiving carrier can retain
- LLP trace carries across the transfer without a break at the prior operator
- The records present the retention the air carrier rule requires
- Each tail in the batch is tracked to an explicit induction-readiness state
Evidence normally required
Common discrepancies
- A task whose interval does not map cleanly between the two programs
- AD accomplishment evidence held by the prior carrier but not transferred
- An LLP trace that breaks at the outgoing operator
- A retention gap that the receiving carrier cannot demonstrate without rework
What is at stake
An aircraft inducted on an unbridged history can carry hidden task or interval gaps that surface at the first check under the new program. Across a batch, those gaps compound into schedule risk, and demonstrating carrier retention after the fact is far harder than confirming it at induction.
How the work runs
Map the programs
Compare the outgoing and receiving programs to define how task history bridges.
Reconcile status per tail
Confirm AD, SB, and LLP status against evidence the receiving carrier can retain.
Bridge the task history
Translate prior tasks onto the receiving program's intervals and flag the gaps.
Stage induction readiness
Sequence the batch so each tail meets the new certificate before it flies.
What the buyer receives
- An induction-readiness view per tail across the batch
- A program-bridging gap list mapping prior tasks to the receiving program
- The evidence required before each aircraft flies under the new certificate
Who uses the output
- Continuing-airworthiness teams clearing each tail to fly under the new certificate
- Fleet and maintenance planners sequencing a batch induction against a schedule
- Records teams demonstrating carrier retention for the transferred history
How the work fits into the transaction or program
The review sits at the point of induction, between the outgoing carrier's release and the first check under the receiving certificate. Its bridging gap list drives the work that has to clear before each tail enters revenue service on the new program.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Regulatory limits
The review bridges and reconciles records so the receiving carrier can induct on a verified history. It does not approve the maintenance program, accept the aircraft onto the certificate, or make an airworthiness determination, all of which rest with the carrier and the authority.
What this review does not cover
- Approval of the receiving carrier's maintenance program
- Physical induction inspection or check accomplishment
- Any airworthiness or operational acceptance decision
Specific to this review
- Bridging is the hard part: two carriers run different programs, so task history is translated to the receiving intervals rather than copied across.
- A batch transfer multiplies each per-tail discrepancy against a schedule deadline, so induction readiness is tracked tail by tail.
- Status generated under the prior program does not by itself satisfy the receiving carrier's retention obligation.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
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). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
Frequently asked questions
Why can't we just carry the prior carrier's status over?
The receiving carrier operates under its own program and recordkeeping. The prior status has to bridge to those intervals and that retention, and gaps in the bridge are exactly what surface at the first check under the new certificate.
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.