Super-midsize jet asset
Embraer Praetor aircraft records review
A Praetor records review checks the file of a midsize or super-midsize business jet against the configuration and compliance status its status lists assert. Lessors, owners, and acquisition teams use it before a purchase, a redelivery, or a re-lease. Because the type is relatively young, the work weighs service-campaign and SB incorporation, the flight-control and avionics configuration, the inspection program, and the engine life-limited part trace. You receive a discrepancy register, a configuration gap list covering flight-control and avionics systems, and the evidence each finding needs.
When this review is needed
- A relatively young super-midsize jet is changing hands and its service-campaign and modification status has to be reconciled rather than its aged structure.
- A redelivery requires the inspection program current against the right revision and the records assembled to match.
- The flight-control and avionics configuration has to be confirmed against the directives that are assessed on that basis.
- Rapid modification activity early in the type's life means the as-built and current standards need to be reconciled.
The problem
A young type concentrates its risk in churn rather than age. Service campaigns and modifications arrive quickly, and a campaign can be marked complete on a status list without the build evidence that ties it to the specific configuration. Where directives are assessed against the flight-control or avionics standard, a configuration record that lags the actual standard quietly invalidates the basis those directives were closed on.
What gets reviewed
- Inspection-program status and the revision and approval basis in force
- AD, SB, and service-campaign status against incorporation evidence tied to the configuration
- Flight-control and avionics configuration against the directives assessed on that basis
- As-built versus current configuration standard reconciliation
- Powerplant life-limited part status and the shop-visit history behind it
- 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
- Each service campaign and SB is supported by incorporation evidence tied to the specific configuration
- Flight-control and avionics configuration matches the standard the directives were assessed against
- The current configuration standard reconciles with the as-built record and the modifications since
- Engine LLP status resolves to release paperwork and a consistent cycle history
- Inspection-program sign-offs correspond to the program revision in force
Evidence normally required
Common discrepancies
- A service campaign recorded as complete without evidence tied to the specific configuration
- Flight-control or avionics configuration that does not match the basis a directive was assessed against
- A current configuration standard that does not reconcile with the as-built record
- Engine LLP cycle counts that disagree between the status list and the shop report
- Inspection tasks recorded against a superseded program revision
What is at stake
A service campaign recorded without configuration-specific evidence may have to be re-verified or re-accomplished, and a directive assessed against the wrong configuration basis can sit open while everyone believes it closed. On a young, high-residual asset those gaps move the price directly.
How the work runs
Set the configuration
Establish the as-built standard and the current configuration the inspection program and directives are assessed against.
Verify the campaigns
Tie each service campaign and SB to incorporation evidence that matches the specific configuration.
Check the directive basis
Confirm the flight-control and avionics configuration the directives were closed on and reconcile the engine LLP trace.
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 configuration gap list covering flight-control and avionics systems
- A service-campaign evidence note tying each campaign to the configuration it was accomplished on
- A closure path for each open item naming the responsible party
Who uses the output
- Acquisition teams pricing configuration and campaign risk into the deal
- Records teams assembling the campaign and configuration dossier before sale or re-lease
- Engineering reconciling the as-built and current configuration standards
How the work fits into the transaction or program
The review runs before technical acceptance so campaign and configuration findings can be priced or closed while leverage holds. Its output supports the data room and the configuration baseline the next operator inherits.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
A young super-midsize type concentrates risk in service campaigns and configuration churn rather than aged structure, so the review weighs SB and campaign incorporation evidence and the flight-control configuration more heavily than long-life structural repair history, and it reconciles the as-built standard against the current one.
Regulatory limits
The review confirms that the records are complete, consistent, and traceable. It does not approve a modification, make a directive-compliance finding for an authority, or guarantee acceptance by any authority or buyer.
What this review does not cover
- Physical inspection or functional testing of the flight-control systems or engines
- Accomplishment or re-verification of a service campaign in the field
- Issuance of any AD compliance finding or airworthiness determination
Specific to this review
- On a young type, service campaigns and configuration churn carry more diligence weight than aged structural repair history.
- The flight-control and avionics configuration is the basis several directives are assessed against, so it is verified before those directives are accepted as satisfied.
- The as-built configuration standard is reconciled against the current one, because rapid early-life modification can leave the two out of step.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
Why does a young jet still need a thorough records review?
Low airframe age does not remove risk. On a young type the risk shifts to service campaigns and configuration churn, where a campaign can be marked complete without configuration-specific evidence and a directive can be closed against a configuration that has since changed.
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.