Regional fleet assets
Regional jet records review
A regional jet records review is for lessors, operators, and acquisition teams moving a regional aircraft through a transition, sale, or end-of-lease event. The trigger is usually an asset that has passed through several operators, often across more than one maintenance program. We trace very high cycle accumulation, AD continuity across program changes, and component release evidence against the source documents that bridge each operator change. You receive a discrepancy register, a continuity view across operator and program changes, and the evidence each open item needs to close.
When this review is needed
- A regional jet has changed operators several times and the records span multiple maintenance programs.
- A high-cycle airframe is approaching a structural-inspection threshold tied to cycles.
- A buyer wants the records read before pricing an older regional asset.
- A transition is planned and the records must support the next operator's program.
The problem
Regional jets fly short, frequent sectors and pass through several operators across a long life. Each operator change can bring a different maintenance program, a different tracking system, and a different way of recording the same task. The accumulated history is dense and stitched together, and a logbook gap at a program handover is where traceability tends to break.
What gets reviewed
- AD accomplishment evidence on a high-cycle airframe, carried across each maintenance-program change
- Cycle-driven structural and life-limited part status with continuous traceability
- Maintenance-program changes across prior operators and the records that bridge them
- Service Bulletin and modification status with effectivity by serial number
- Authorized release certificates for components changed under successive operators
- Logbook continuity at each change of operator and program
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
- AD accomplishment carries forward consistently across each maintenance-program change
- Cycle-driven inspections and life limits trace with a consistent cycle history
- Logbook continuity is preserved at every change of operator and program
- Each component release uses a release document appropriate to the installation and the registry
- Items closed under a prior program were picked up rather than dropped by the next one
- Status lists reconcile against the underlying source documents
Evidence normally required
Common discrepancies
- A logbook gap at a change of operator or maintenance program
- Cycle-driven inspection status that does not carry forward consistently
- Release certificates missing for components changed under a prior operator
- AD compliance recorded under one program that the next program did not pick up
- Status lists that disagree with the source documents they summarize
What is at stake
Accepting a regional jet with a logbook gap across an operator change or an unsupported cycle-driven inspection can leave the next operator unable to show continuity at induction. On an older asset that gap is harder to reconstruct and can stall the next placement.
How the work runs
Reconstruct the operator timeline
Lay out the sequence of operators and maintenance programs and identify every handover point in the records.
Test continuity at each handover
Confirm AD, life-limit, and logbook continuity carried across each operator and program change.
Register discrepancies
Record each break with its source document, evidence trace, and the handover where it occurred.
Map closure
Recommend a reconstruction or closure path and responsible party for each break.
What the buyer receives
- A discrepancy register pairing each finding with its source document and evidence trace
- A continuity view that follows the asset across each operator and program change
- A closure recommendation for each item with the responsible party named
- A note on which continuity gaps are reconstructable and which are not
Who uses the output
- Asset managers deciding whether to accept the asset or adjust the price
- Records teams rebuilding continuity ahead of the next placement
- Operators inducting the aircraft against their own program
How the work fits into the transaction or program
The review runs ahead of the next placement so continuity gaps can be reconstructed while the records and the people who created them are still reachable. It feeds the induction package the receiving operator works from.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Regional jets typically move through several operators and programs over a long life, so the decisive checks center on continuity at each handover rather than on a single operator's records. Frequent short sectors push cycle-driven limits ahead of calendar limits, making cycle traceability the primary value driver.
Jurisdiction-specific considerations
A regional asset that crosses authorities during its life carries releases and program acceptance from more than one system, so the continuity view has to show documentation the receiving authority will accept at each crossing.
Regulatory limits
This review establishes records completeness, consistency, and continuity. It does not make an airworthiness determination, replace the operator or authority, or guarantee acceptance by the receiving program.
What this review does not cover
- Physical inspection of the aircraft or its engines
- Reconstruction of records the prior operators never created
- Issuance of any approval or airworthiness determination
Specific to this review
- Regional jets typically pass through several operators and maintenance programs in a long life, so continuity across program changes is the most common point of failure.
- Frequent short sectors push cycle-driven limits ahead of calendar limits, so cycle traceability is usually decisive on a regional asset.
- An item closed under one operator's program can be dropped at the next handover, so the review checks that compliance carried forward rather than restarting.
Sources
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Why are program changes the main risk on a regional jet?
Each operator change can switch the maintenance program and the tracking system. Compliance recorded under one program is sometimes not carried into the next, and logbook continuity breaks at the handover. The review focuses on whether the chain holds across those points.
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.