Light and midsize jet asset
Cessna Citation aircraft records review
A Citation records review checks the file of a light or midsize business jet against the program standing its seller claims. Lessors, owners, and acquisition teams run it before a purchase, a redelivery, or a re-lease. The work covers the inspection program and its revision, AD and SB accomplishment, engine-program enrollment and the maintenance evidence that keeps coverage in force, and the avionics modification history. You receive a discrepancy register, a program-status gap list spanning inspection and engine coverage, and the evidence each open item needs.
When this review is needed
- A light or midsize jet is changing hands and its engine-program enrollment status materially moves the price.
- The avionics suite has been upgraded and the buyer needs each change anchored to an approval.
- A redelivery requires the inspection program current and the records assembled against the correct revision.
- Program coverage is asserted in the listing and the maintenance evidence behind it has to be confirmed before closing.
The problem
On this class of jet, engine-program enrollment is often quoted as if it were proof of standing, but coverage stays in force only while the required maintenance is performed and recorded. A coverage statement can be presented while the maintenance evidence that keeps it valid is incomplete. Avionics upgrades create the same risk, where a flight-deck change is flying ahead of the STC paperwork that should accompany it.
What gets reviewed
- Inspection-program status and the revision and approval basis it runs under
- AD and SB accomplishment checked against the work evidence behind each item
- Engine-program enrollment and the maintenance evidence that supports continued coverage
- Avionics and flight-deck modifications and the STCs they depend on
- Powerplant time and cycle accumulation reconciled against the program records
- Status lists reconciled against logbooks and work-pack source documents
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
- Program enrollment is backed by maintenance evidence rather than a coverage statement alone
- Each avionics modification cites an STC whose document is on file and matches the installation
- AD closure is supported by accomplishment evidence that names the method of compliance
- Powerplant time and cycles reconcile between the program records and the airframe logbooks
- Inspection-program sign-offs correspond to the program revision that was in force
Evidence normally required
Common discrepancies
- Engine-program coverage asserted without the maintenance evidence that keeps it in good standing
- A flight-deck upgrade installed ahead of the STC paperwork that should support it
- AD status held in the tracking system but unsupported by source accomplishment evidence
- Powerplant time or cycles that disagree between the program records and the logbooks
- Inspection tasks recorded against a superseded program revision
What is at stake
Coverage that is not actually in good standing can collapse a value assumption the buyer paid for, and a flight-deck upgrade without its STC may have to be substantiated or removed. Both are far cheaper to identify before the sale closes than to dispute afterward.
How the work runs
Confirm the program
Establish the inspection program in force and the engine-program coverage the deal is being priced against.
Test the coverage evidence
Separate the engine-program coverage statement from the maintenance records that keep it valid and confirm the underlying evidence.
Anchor the avionics
Tie each flight-deck and avionics upgrade to its STC and check the installation against the document.
Register and assign
Record each finding with its source and a closure path, naming the responsible party.
What the buyer receives
- A discrepancy register listing each finding with its source and evidence trace
- A program-status gap list covering inspection currency and engine-program coverage
- An engine-coverage evidence note distinguishing the coverage statement from its supporting maintenance
- A closure path for each open item naming the responsible party
Who uses the output
- Acquisition teams pricing the engine-program standing into the deal
- Records teams assembling the program-evidence dossier before sale or re-lease
- Asset managers deciding whether the asserted coverage can be relied on
How the work fits into the transaction or program
The review runs before technical acceptance so engine-program and avionics findings can be priced or resolved while leverage holds. Its output supports the data room and the program baseline the next operator takes on.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
On light and midsize jets the engine-program standing is a value driver in its own right, so the review tests the maintenance evidence behind the coverage rather than treating an enrollment statement as proof, and it weighs avionics STC paperwork heavily because flight-deck upgrades on these aircraft often outrun their documentation.
Regulatory limits
The review confirms that the records are complete, consistent, and traceable. It does not validate an engine-program contract, approve a modification, determine airworthiness, or guarantee acceptance by any authority or buyer.
What this review does not cover
- Physical inspection of the aircraft, the avionics, or the engines
- Adjudication or negotiation of the engine-program contract terms
- Issuance of any STC or airworthiness determination
Specific to this review
- Engine-program enrollment is a price driver on this class of jet, and the coverage statement is treated as separate evidence from the maintenance that keeps coverage in force.
- Avionics and flight-deck upgrades on these aircraft frequently outrun their paperwork, so STC documentation is a primary focus of the configuration check.
- Recorded time and cycles are reconciled between the program records and the airframe logbooks, because a mismatch there can put the coverage assumption in question.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
Is an engine-program enrollment statement enough on its own?
No. Coverage stays in force only while the required maintenance is performed and recorded, so the review checks the maintenance evidence behind the statement rather than treating enrollment as proof of standing.
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.