Business jet records
Legacy 600/650 pre-buy file evidence review for pre-purchase inspection
The decision turns on the Legacy 600/650 shares its airframe lineage with the ERJ-135 regional jet, so its heavy-check structure is more airline-like than a clean-sheet bizjet, and a pre-buy must confirm those airframe checks were flown on schedule plus AE3007 engine-program coverage. Read the airframe check completion history and structural task status, AE3007 program coverage, cabin/avionics mod approvals, and export-airworthiness readiness given many of these aircraft trade internationally first. Resolve an airline-style structural check deferred, an engine off-program during a low-use ownership, and export documentation gaps that surface late in the deal.
When this review is needed
- The records question has to close before pre-purchase inspection.
- The first evidence to test is the airframe check completion history.
- The open question is the Legacy 600/650 shares its airframe lineage with the ERJ-135 regional jet, so its heavy-check structure is more airline-like than a clean-sheet bizjet, and a pre-buy must confirm those airframe checks were flown on schedule plus AE3007 engine-program coverage.
The problem
The difficult point is an airline-style structural check deferred, an engine off-program during a low-use ownership, and export documentation gaps that surface late in the deal.
What gets reviewed
- Trace airframe check completion history against serial identity, date, cycle basis, configuration, and closure evidence.
- Compare structural task status against serial identity, date, cycle basis, configuration, and closure evidence.
- Verify AE3007 program coverage against serial identity, date, cycle basis, configuration, and closure evidence.
- Reconcile cabin/avionics mod approvals against serial identity, date, cycle basis, configuration, and closure evidence.
- Check export-airworthiness readiness given many of these aircraft trade internationally. against serial identity, date, cycle basis, configuration, and closure evidence.
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
- Accepted evidence carries the same serial, date, configuration, and status shown for Legacy 600/650 pre-buy file.
- A finding is raised if the spreadsheet line has no matching log entry, certificate, task card, or shop record.
- Repetitive or date-driven items need a clear last-done and next-due basis.
- Applicability claims must be backed by installed-configuration evidence.
- Open exceptions are grouped by blocker, reserve, cleanup, or monitor status.
Evidence normally required
- Airframe check completion history
- Structural task status
- AE3007 program coverage
- Cabin/avionics mod approvals
- Export-airworthiness readiness given many of these aircraft trade internationally.
- Current maintenance tracking export
Common discrepancies
- Airline-style structural check deferred, an engine off-program during a low-use ownership
- Export documentation gaps that surface late in the deal
What is at stake
If unresolved, an airline-style structural check deferred, an engine off-program during a low-use ownership, and export documentation gaps that surface late in the deal changes the pre-purchase inspection position for Legacy 600/650 pre-buy file.
How the work runs
Frame Legacy 600
Confirm the exact event, affected file set, buyer role, and decision standard before any airframe check completion history is treated as sufficient.
Trace Pre Purchase
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 Review Buy
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Evidence Inspection
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 Legacy 600/650 pre-buy file, split into supported, disputed, and missing evidence.
- Source map for the airframe check completion history 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 findings to decide which items block acceptance.
- acquisition broker uses the request list to chase specific pages or corrected statements.
- records reviewer uses the risk split for reserves, delivery conditions, or induction planning.
How the work fits into the transaction or program
The Legacy 600/650 shares its airframe lineage with the ERJ-135 regional jet, so its heavy-check structure is more airline-like than a clean-sheet bizjet, and a pre-buy must confirm those airframe checks were flown on schedule plus AE3007 engine-program coverage. The evidence set centers on the airframe check completion history and structural task status, AE3007 program coverage, cabin/avionics mod approvals, and export-airworthiness readiness given many of these aircraft trade internationally. The likely weak points are an airline-style structural check deferred, an engine off-program during a low-use ownership, and export documentation gaps that surface late in the deal. Handoff: buyer's technical rep, pre-purchase inspection, Legacy 600/650 pre-buy file.
Start with a single asset
Organize records and a discrepancy register for diligence.
Aircraft-specific considerations
For Legacy 600/650 pre-buy file, the records depend on the Legacy 600/650 shares its airframe lineage with the ERJ-135 regional jet, so its heavy-check structure is more airline-like than a clean-sheet bizjet, and a pre-buy must confirm those airframe checks were flown on schedule plus AE3007 engine-program coverage.
Jurisdiction-specific considerations
For Legacy 600/650 pre-buy file, FAA/EASA review starts with the airframe check completion history; the trigger is pre-purchase inspection.
Regulatory limits
The output supports records review for Legacy 600/650 pre-buy file; approval and acceptance calls remain outside it.
What this review does not cover
- Hands-on inspection outside the delivered file
- Negotiation of purchase credits or lease reserves
- Regulatory applications submitted for the buyer
Specific to this review
- Legacy 600/650 pre-buy file is evaluated around legacy 600 erj derived airframe export prebuy, rather than a generic asset checklist.
- The first review target is the record line most likely to move value, availability, or acceptance timing.
- Serial continuity is tested separately from task completion because evidence can follow a different asset.
- A useful register preserves accepted evidence, disputed evidence, and missing evidence as separate outcomes.
- The scope uses the Legacy 600 650 Pre question as the control point, so the review stays tied to Pre-purchase inspection and the buyer decision behind it.
- The evidence starts with Airframe check completion history and follows Purchase Records Review Buy 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 File Evidence Inspection Business questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Source-linked exception log for Legacy 600/650 pre-buy file; 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.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
What makes this aircraft review different from a general file audit?
The scope is tied to legacy 600 650 pre 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 airframe check completion history, 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.