Business jet records
Phenom 300 pre-purchase records evidence review
The decision turns on the Phenom 100/300 runs staggered calendar inspection packages anchored to the delivery month plus heavy 60- and 120-month structural events, so a pre-buy must confirm the calendar packages were flown on the correct delivery-month cadence and that the heavy structural inspections were accomplished at threshold, alongside PW535E engine-program coverage. Read the calendar-package completion history against delivery month, 60/120-month structural status, engine-program coverage, and AD/SB status specific to the first. Resolve a calendar package computed off the wrong month, a 120-month structural event deferred near the sale, and an engine run off-program during a low-use ownership.
When this review is needed
- A transaction gate is coming up: pre-purchase inspection.
- The first evidence to test is the calendar-package completion history against delivery month.
- The open question is the Phenom 100/300 runs staggered calendar inspection packages anchored to the delivery month plus heavy 60- and 120-month structural events, so a pre-buy must confirm the calendar packages were flown on the correct delivery-month cadence and that the heavy structural inspections were accomplished at threshold, alongside PW535E engine-program coverage.
The problem
The difficult point is a calendar package computed off the wrong month, a 120-month structural event deferred near the sale, and an engine run off-program during a low-use ownership.
What gets reviewed
- Reconcile the claimed phenom 300 pre-purchase status to source documents by item, serial number, and date.
- Check that the latest status report agrees with logbook entries and task-card evidence.
- Review release paperwork for parts or assemblies that affect the stated configuration.
- Identify open items whose closure depends on outside records or revised statements.
- Map each discrepancy to the party best placed to answer it.
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
- Pass when the source page supports the same part, serial, date, and status shown in the summary.
- Fail when a spreadsheet line has no matching log entry or certificate in the delivered file.
- Pass when repetitive tasks show a traceable last-done and next-due basis.
- Fail when configuration claims rely on inherited wording without supporting embodiment evidence.
Evidence normally required
- pre-purchase records data room
- maintenance tracking export
- logbook entries with dates, times, and references
- release paperwork for affected parts
- task cards and non-routine records
- current status report from the operator or CAMO
Common discrepancies
- Status carried forward from a prior operator with no source-page reference.
- Cycle, hour, or calendar values that diverge between the tracking export and the log entry.
- Release paperwork filed under a related assembly rather than the affected serial.
- A closure note that describes work performed but omits the document needed to prove it.
What is at stake
If unresolved, a calendar package computed off the wrong month, a 120-month structural event deferred near the sale, and an engine run off-program during a low-use ownership changes the pre-purchase inspection position for Phenom 300 pre-purchase records.
How the work runs
Frame Phenom 300
Confirm the exact event, affected file set, buyer role, and decision standard before any pre-purchase records data room is treated as sufficient.
Trace Purchase Records
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Inspection Evidence
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Jet 100
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- Decision register for Phenom 300 pre-purchase records, split into supported, disputed, and missing evidence.
- Source map for the calendar-package completion history against delivery month tied to the controlling status records.
- Owner action list for document retrieval, data correction, technical disposition, or acceptance decision.
- Briefing note tying the open items to pre-purchase inspection.
Who uses the output
- buyer's technical rep uses the register to decide what can be accepted, reserved, or escalated.
- acquisition broker uses the register to decide what can be accepted, reserved, or escalated.
- owner-pilot uses the register to decide what can be accepted, reserved, or escalated.
How the work fits into the transaction or program
The Phenom 100/300 runs staggered calendar inspection packages anchored to the delivery month plus heavy 60- and 120-month structural events, so a pre-buy must confirm the calendar packages were flown on the correct delivery-month cadence and that the heavy structural inspections were accomplished at threshold, alongside PW535E engine-program coverage. The evidence set centers on the calendar-package completion history against delivery month, 60/120-month structural status, engine-program coverage, and AD/SB status specific to the. The likely weak points are a calendar package computed off the wrong month, a 120-month structural event deferred near the sale, and an engine run off-program during a low-use ownership. Handoff: buyer's technical rep, pre-purchase inspection, Phenom 300 pre-purchase records.
Start with a single asset
Organize records and a discrepancy register for diligence.
Aircraft-specific considerations
For Phenom 300 pre-purchase records, the records depend on the Phenom 100/300 runs staggered calendar inspection packages anchored to the delivery month plus heavy 60- and 120-month structural events, so a pre-buy must confirm the calendar packages were flown on the correct delivery-month cadence and that the heavy structural inspections were accomplished at threshold, alongside PW535E engine-program coverage.
Jurisdiction-specific considerations
For Phenom 300 pre-purchase records, FAA/EASA review starts with the calendar-package completion history against delivery month; the trigger is pre-purchase inspection.
Regulatory limits
The boundary is the calendar-package completion history against delivery month traceability, not an airworthiness release.
What this review does not cover
- Physical inspection findings outside the records package
- Negotiation of commercial credits or reserves
- Regulatory submissions made on behalf of the applicant
Specific to this review
- Phenom 300 calendar package structural prebuy changes which documents deserve first review because the highest-risk lines are seldom the newest pages.
- A clean index can still hide a weak position if the page reference points to a summary rather than primary evidence.
- Serial-number continuity matters as much as task completion for this review because assemblies move between assets.
- The most useful output is a decision register that separates accepted evidence, disputed evidence, and missing evidence.
- The scope uses the Phenom 300 Pre Purchase question as the control point, so the review stays tied to Pre-purchase inspection and the buyer decision behind it.
- The evidence starts with Pre-purchase records data room and follows Records Review Inspection Evidence references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for buyer's technical rep: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Business Jet 100 Staggered questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Page-referenced discrepancy register with affected assets and closure owner; it gives the next reviewer a precise map instead of another broad request for a better file.
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.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What makes this aircraft review different from a general file audit?
The scope is tied to phenom 300 pre purchase and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block pre-purchase inspection or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is pre-purchase records data room, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives buyer's technical rep a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.