Integrated-flight-deck light jet asset
Embraer Phenom aircraft records review
A Phenom records review checks the file of an entry-level or light business jet against the configuration and compliance status its status lists assert. Lessors, owners, and acquisition teams commission it before a purchase, a redelivery, or a re-lease. The work covers the inspection program, AD and SB status including software-related directives, the integrated-avionics software and database loads, and the engine life-limited part trace. You receive a discrepancy register, a configuration gap list covering avionics software currency, and the evidence each finding needs to close.
When this review is needed
- A light jet with an integrated flight deck is changing hands and the loaded software standard has to be confirmed against the directives that depend on it.
- A redelivery requires the inspection program current and the records assembled against the correct revision.
- The engine LLP trace drives value and has to be reconciled against the shop-visit history.
- A software-related directive is open and the actual loaded standard, not just the airframe serial, has to be established.
The problem
An integrated flight deck makes the loaded software and navigation database part of the airworthiness configuration, yet the configuration record can drift from what is actually loaded after a service-center visit. A directive may be assessed against the airframe serial when it really turns on the software standard fitted, and a database can lapse out of currency without anything flagging it in the status list.
What gets reviewed
- Inspection-program status and the revision and approval basis in force
- AD and SB accomplishment, including software-related directives, against the work evidence
- Integrated-avionics software part numbers and navigation-database currency
- Configuration records matched to the standard actually loaded on the aircraft
- 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
- Loaded avionics software and database parts match the numbers the configuration record claims
- Software-related ADs are assessed against the loaded standard, not the airframe serial alone
- Navigation-database currency is supported by evidence rather than assumed from the status list
- 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
- Loaded avionics software that does not match the standard the configuration record claims
- A software-related AD assessed against the airframe serial but not the loaded standard
- A navigation database lapsed out of currency without a flag in the status list
- 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 software-related directive assessed against the wrong basis can be recorded as satisfied while the actual loaded standard leaves it open, and a configuration record that disagrees with what is loaded undermines every directive that depends on it. Catching the mismatch in diligence avoids inheriting an unverified avionics baseline.
How the work runs
Capture the baseline
Establish the inspection program in force and the avionics software and database standard the configuration record claims.
Verify the load
Confirm the loaded software and database part numbers against the configuration record and the service-center load history.
Reconcile the directives
Assess software-related directives against the loaded standard and reconcile the engine LLP trace against the shop history.
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 avionics software and database currency
- A software-baseline note reconciling the loaded standard against the directives that depend on it
- A closure path for each open item naming the responsible party
Who uses the output
- Acquisition teams pricing the avionics baseline into the deal
- Records teams assembling the configuration dossier before sale or re-lease
- Engineering deciding how to reconcile the loaded standard with open directives
How the work fits into the transaction or program
The review runs before technical acceptance so avionics and configuration findings can be priced or resolved while leverage holds. Its output supports the data room and the avionics 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
An integrated flight deck folds the avionics software standard into the airworthiness configuration, so the review verifies loaded software and database part numbers against the configuration record and the directives that turn on them, which is where the file most often drifts after a service-center visit.
Regulatory limits
The review confirms that the records are complete, consistent, and traceable. It does not approve a software standard, make a directive-compliance finding on an authority's behalf, or guarantee acceptance by any authority or buyer.
What this review does not cover
- Physical inspection or functional testing of the avionics or the engines
- Loading, updating, or certifying avionics software or databases
- Issuance of any AD compliance finding or airworthiness determination
Specific to this review
- On an integrated flight deck, software-related ADs apply against the loaded standard rather than the airframe serial alone, which is a frequent reconciliation point.
- Navigation-database currency and software part numbers are part of the configuration baseline on these aircraft, not a separate operational detail.
- The configuration record can drift from what is actually loaded after a service-center visit, so the loaded standard is verified against the record rather than assumed from it.
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.
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
Frequently asked questions
Why check software against the loaded standard rather than the airframe serial?
On an integrated flight deck a directive often turns on the software fitted, not the airframe alone. Assessing against the loaded standard catches directives that were closed against the wrong basis and databases that have lapsed.
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.