Repair approval
Dassault Falcon 7X repair approval data records review
This review confirms that each repair and alteration on a Dassault Falcon 7X rests on approved data and closes with a return-to-service entry. It is run by or for a party evaluating, transferring, or maintaining the aircraft, where a repair without a traceable approval basis is a latent liability. It works from the repair map through the damage reports, the dispositions, the approved data cited, and the closing entries. You receive an exception list of repairs whose approval basis is missing or mismatched, a source map to the substantiation, and a plan to recover or re-substantiate each gap for the tail.
When this review is needed
- A buyer needs every structural repair on the aircraft to trace to an approval basis before pricing.
- A repair map shows a disposition but the approved data it relied on is not in the file.
- An alteration was embodied under an STC and the STC applicability to this serial number is unconfirmed.
- A repair may need re-substantiation before the aircraft can cross to a receiving register.
The problem
A repair is only as good as the data it was carried out against. On a Falcon 7X the repair map may list a disposition and a location, but the assurance lives in the approved data behind it, and a repair embodied against data that does not cover this configuration, or with no substantiation on file at all, leaves the structure supported only on paper. Those gaps are hardest to close long after the repair, when the approving source has moved on.
What gets reviewed
- The repair map reconciled to the damage reports and dispositions on file
- Approved data cited for each repair checked for coverage of this configuration
- Alterations traced to the STC or approval basis they were embodied under
- Return-to-service entries confirming each repair was closed
- Structural repairs assessed for interaction with recorded configuration and effectivity
- Repairs reconciled against the release evidence for any replacement parts installed
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 repair on the map carries approved data that covers the actual damage and location
- Every alteration traces to an STC or approval basis applicable to this serial number
- A return-to-service entry closes each repair against the data it relied on
- Damage reports and dispositions reconcile with the repair map
- Repairs that installed replacement parts tie to valid release evidence for those parts
Evidence normally required
- The repair map for the Falcon 7X
- Damage reports and repair dispositions
- Approved data and substantiation cited for each repair
- STC and alteration approval documentation
- Return-to-service entries and associated logbook records
Common discrepancies
- A repair on the map with no approved data locatable behind the disposition
- An alteration embodied under an STC that does not apply to this serial number
- A structural repair closed without a return-to-service entry tying it to its data
- A repair whose approved data does not cover the damage as actually reported
What is at stake
A repair without a traceable approval basis can force removal, re-work, or re-substantiation before the aircraft is accepted, which is far more expensive than confirming the basis when the repair was done. At a transaction the repair reverts to an open item, and an alteration whose STC does not apply to this serial number can require reversal or a fresh approval on the buyer's timeline.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the repair map
Reconcile the map to the damage reports and dispositions and list every repair and alteration.
Trace the approval basis
Confirm each repair cites approved data covering its damage and each alteration ties to an applicable STC.
Confirm closure
Match every repair to a return-to-service entry and to release evidence for any parts installed.
Plan the recovery
Flag the substantiation gaps and set a plan to recover data or re-substantiate where needed.
What the buyer receives
- An exception list of repairs with missing or mismatched approval data, ranked by structural significance
- A source map linking each repair to its approved data and closing entry
- A recovery plan for the substantiation gaps, with re-substitution options where recovery fails
Who uses the output
- Asset managers pricing the structural repair history against approvals that actually hold
- Engineering deciding how to treat a repair whose approval basis cannot be traced
- Records teams recovering substantiation before a transaction or a register change
How the work fits into the transaction or program
The repair review works alongside the configuration and release-document reviews on a Falcon 7X, because a structural repair often changes configuration and installs released parts. Its recovery plan closes the substantiation gaps before an export package or a redelivery binder cites the repair history as clean.
Aircraft-specific considerations
The Falcon 7X's composite and metallic structure and its fly-by-wire flight-control surfaces mean repairs to control surfaces and pressure structure carry substantiation that has to match the exact damage and location, so a generic repair reference is not sufficient. Repairs made during the aircraft's international operation may cite data approved under one authority, which raises a recognition question when the tail moves to another register.
Jurisdiction-specific considerations
Approved data recognized by the FAA is not automatically accepted by EASA and the reverse also holds, so a repair substantiated under one authority may need a recognized basis before the aircraft crosses registers. The review identifies repairs whose approval basis would need conversion or re-substantiation for the destination system.
Regulatory limits
The review confirms that each repair traces to approved data and a closing entry. It does not approve repair or alteration data, develop substantiation, or make an airworthiness determination on any repair.
What this review does not cover
- Developing or approving repair or alteration data
- Performing or re-performing any repair
- Physical inspection or assessment of the repaired structure
Specific to this review
- A repair is supported only by the data it was carried out against, so a disposition on the map with no approved data behind it is unsupported no matter how sound the workmanship.
- Alterations fail on applicability more than on quality: an STC can be genuine yet not apply to this serial number, which forces reversal or fresh approval.
- Substantiation is hardest to recover long after the repair, because the approving source and the shop records disperse over time.
Sources
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The repair looks sound and is on the map, so why chase the approval data?
Workmanship and approval are separate questions. A repair can be well made yet rest on data that does not cover this configuration, or on no traceable data at all, and at a transaction or a register change it reverts to an open item until the basis is produced. The review confirms each repair traces to approved data and a closing entry so the structural history holds up.
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.