Fleet induction
Airline fleet-induction records checklist
This checklist covers the records work of bringing an aircraft onto a receiving operator's maintenance program, from program bridging and AD reconciliation to loading component times and open task carry-over. Use it as a tail moves under a new operator's continuing-airworthiness management. You finish with a bridging matrix, a tracking-load reconciliation, and a list of items to resolve before the first scheduled check.
When this review is needed
- An aircraft is transferring to a receiving operator and its program has to be mapped to the new program.
- The receiving tracking system is about to be loaded with component times and check status.
- Open maintenance items from the outgoing operator have to be carried over and resolved on a schedule.
- The induction has a fixed entry-into-service date and the records work has to land before the first check.
The problem
The outgoing program and the receiving program rarely line up task for task. Intervals differ, repetitive inspections are written differently, and AD compliance was recorded against a method the new operator may not use. If the records team loads times straight from a status list, any error in that list lands in the new system on day one and surfaces at the worst moment during the first check.
What gets reviewed
- Outgoing maintenance program mapped to the receiving program intervals
- AD status reconciled to the receiving operator's compliance method
- Component and LLP times loaded against the source records
- Open task cards, deferrals, and repetitive items carried over
- Last check status and the next-due picture under the new program
- Repetitive inspections re-expressed in the receiving program's task structure
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 recurring task in the outgoing program maps to a task and interval in the receiving program
- AD compliance carries the method the receiving operator will use, not only the outgoing status
- Loaded component times match the source records they were taken from
- Each deferred item carries its category, basis, and resolution due point
- Repetitive inspection due points recompute correctly under the new program intervals
Evidence normally required
Common discrepancies
- A recurring task in the old program with no mapped equivalent in the new one
- Loaded times taken from a status list that disagrees with the source logbook
- A deferral carried over without its category or resolution basis
- AD compliance recorded against a method the receiving program does not accept
- A repetitive inspection whose next-due shifts once it is re-expressed in the new intervals
What is at stake
A mismapped recurring task or a wrongly loaded component time can put the aircraft out of compliance under its new program without anyone noticing until the next due calculation. Reconciling at induction, against source records, keeps the first scheduled check from turning into a discovery exercise.
How the work runs
Map the programs
Bridge each task and interval in the outgoing program to its equivalent in the receiving program and flag the unmatched.
Reconcile to source
Pull component and LLP times from the source records, not the status list, before they load into the new system.
Carry over open work
Capture deferrals and repetitive items with category, basis, and resolution point under the new program.
Build the pre-check list
Hand planning a list of items to resolve before the first scheduled check so it is not a discovery exercise.
What the buyer receives
- A program bridging matrix from outgoing to receiving tasks
- A tracking-load reconciliation against source records
- A pre-first-check action list for open and carry-over items
Who uses the output
- Continuing-airworthiness teams accepting the aircraft onto the program
- Records teams loading the receiving tracking system
- Planning teams building the first-check workscope
How the work fits into the transaction or program
The checklist sits between transfer and first scheduled check, feeding the receiving tracking load. Where the induction crosses authorities, the cross-jurisdiction transition evidence checklist handles the program-acceptance side.
Aircraft-specific considerations
Bridging effort scales with how the type's maintenance program is structured. A type with a detailed task card breakdown and many repetitive inspections takes more mapping than one with broad block intervals, so the matrix is sized to the program in hand.
Jurisdiction-specific considerations
Induction maps records and program tasks; it does not transfer one authority's acceptance of the prior program. Where the receiving operator sits under a different authority, the program has to be mapped to one that authority will accept.
Regulatory limits
The checklist reconciles records and program mapping. It does not grant operational approval, transfer an authority's acceptance, or by itself return the aircraft to service under the new program.
What this review does not cover
- Operational approval or air-operator certificate work
- Performing the first scheduled check itself
- Any airworthiness determination on the receiving operator's behalf
Specific to this review
- Induction reconciles records and program mapping; it does not by itself grant operational approval or transfer an authority's acceptance of the prior program.
- Loading times from a status list rather than the source record propagates any tracking error straight into the new operator's system.
- Re-expressing repetitive inspections in the new program's intervals can shift a next-due point, so each one is recomputed rather than copied across.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
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.
Frequently asked questions
Does loading the tracking system count as inducting the aircraft?
Loading is one step. The induction is complete only when the program is mapped, the loaded times trace to source, and the open items are carried over with a resolution position, which is what this checklist confirms.
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.