Skip to content

Fleet induction & onboarding

Managed-aircraft onboarding records review

A managed-aircraft onboarding records review establishes the records baseline as an aircraft enters a management or continuing-airworthiness program. It is run by the incoming manager, the owner, or an airline taking the asset onto its certificate. It captures AD compliance status, life-limited part life remaining, the configuration baseline, open maintenance items, and any deferred defects carried in from the prior program. You receive a baseline status set, an open-item carry-in list, and the document gaps that must be closed before the asset is fully managed.

When this review is needed

  • An aircraft is moving onto a new manager's continuing-airworthiness program and the starting status has to be fixed.
  • An owner is placing a tail with a manager and wants the carry-in condition recorded before responsibility transfers.
  • An airline is adding a used aircraft to its certificate and the prior program's records must be mapped to its own.
  • A new management contract begins and the manager needs to know what it is inheriting before it signs off recurring tasks.

The problem

Onboarding usually starts from whatever the prior program handed over, and the handover is rarely complete on day one. The incoming manager builds its tracking from a status export, then discovers that deferred defects, repair approvals, and modification history were never reconciled to source. Whatever is not caught at induction becomes the new manager's problem the moment it assumes responsibility.

What gets reviewed

  • The prior maintenance program and how its tasks map to the incoming program
  • Airworthiness Directive status reconciled against accomplishment evidence at induction
  • Life-limited part life remaining established as the managed baseline
  • Configuration and modification baseline as the asset enters the program
  • Open and deferred maintenance items carried in from the prior operator
  • Component status and release evidence for the installed configuration

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 carried-in deferred defect has a category, raising date, and a defined disposition
  • AD status at induction is supported by accomplishment evidence rather than an export alone
  • Life-limited part life remaining at induction reconciles with shop and logbook history
  • The prior program's tasks map to the incoming program without unaccounted intervals
  • Modification and repair entries carry the approval basis the new program will rely on
  • Installed-component releases are present and match the recorded serial numbers at induction

Evidence normally required

  • The handover status export from the prior program
  • AD and modification status reports at the point of induction
  • Deferred defect and open-item registers from the outgoing operator
  • Logbooks or digital records covering the prior program period
  • The incoming maintenance program the asset is being placed onto

Common discrepancies

  • Deferred defects carried in without a category or a closure plan
  • AD status that an export claims closed but source evidence does not support
  • Modification history that does not map cleanly to the incoming program
  • Component releases absent for items installed under the prior operator
  • Task intervals that do not align between the prior and incoming programs

What is at stake

An induction that accepts the prior status without checking source documents carries forward errors that surface later as the manager's liability. A missed deferred defect or an unmapped modification can ground the aircraft or fail an audit after the program has already taken the asset on.

How the work runs

01

Fix the induction point

Define the date and configuration at which the baseline is taken and the record sets that apply to the specific aircraft.

02

Reconcile carry-in status

Compare the handover export against source AD, LLP, modification, and deferred-defect evidence.

03

Map the programs

Translate the prior program's tasks and intervals onto the incoming program and flag the unaccounted gaps.

04

Hand over the baseline

Deliver the fixed baseline, the carry-in open items, and the document gaps to close before full management begins.

What the buyer receives

  • A baseline status set fixing AD, LLP, and configuration at induction
  • An open-item carry-in list with category and disposition for each entry
  • A document-gap list to close before the asset is fully managed
  • A program-mapping note showing how prior tasks translate to the new program

Who uses the output

  • Continuing-airworthiness teams setting up the managed program
  • Owners confirming the carry-in condition before responsibility transfers
  • Records teams building the managed tracking from a verified baseline

How the work fits into the transaction or program

The review runs at induction, before the manager signs off recurring tasks on the new program, so the baseline it builds from is verified rather than assumed. It feeds the managed tracking setup and the carry-in register the manager works from.

Start with a single asset

Start with a single tail and expand once the workflow is proven.

Aircraft-specific considerations

Onboarding scope shifts with how the prior program was structured. A tail coming off a charter program carries different deferred-defect and interval conventions than one off a scheduled-carrier program, so the task mapping is built for the specific prior program rather than a generic template.

Jurisdiction-specific considerations

An aircraft moving onto a program under a different authority needs its prior compliance basis mapped before it is managed. The deferred-defect categories and the maintenance program acceptance that applied under the previous authority do not transfer automatically to the receiving one.

Regulatory limits

The review fixes a records baseline and identifies what is missing. It does not accept the aircraft onto a program on the operator's behalf, issue an airworthiness determination, or relieve the manager of the recurring obligations the program carries.

What this review does not cover

  • Setup or configuration of the maintenance-tracking software itself
  • Physical survey or inspection of the inducted aircraft
  • Acceptance of the aircraft onto the operating certificate

Specific to this review

  • The induction baseline is the reference everything the new manager does is measured against, so an unverified starting status propagates into every later status report.
  • Deferred defects are the most common carry-in surprise because the prior program's open items rarely transfer with their full category and disposition history.
  • Task-interval mapping between the prior and incoming programs is a distinct check from AD status, since two valid programs can hold the same task at different intervals.

Sources

Frequently asked questions

Is an onboarding review the same as accepting the aircraft onto our program?

No. Acceptance is the manager's decision. The review is the independent check that establishes what the records actually show at induction, so the manager accepts against a verified baseline rather than an export.

What if the prior program's records are incomplete at handover?

Incomplete handover is the usual case. The review records exactly which documents are missing at induction so the gaps can be pursued from the outgoing program while there is still a relationship to pursue them through.

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.