AD compliance
Dassault Falcon 7X Airworthiness Directive status records review
This review confirms that the AD status list for a Dassault Falcon 7X reflects what the records actually support, directive by directive. It is run by or for a party evaluating, transferring, or operating the aircraft, where an unsupported AD position carries real exposure. It checks applicability against the serial number and configuration, the accomplishment evidence behind each closed AD, the recorded method of compliance, and the recurring intervals still running. You receive an exception list of AD lines that outrun their evidence, a source map to the accomplishment records, and a plan to close the unsupported items for the tail.
When this review is needed
- A buyer is pricing the aircraft and the AD position drives both value and the work that lands after closing.
- A recurring AD is approaching its next threshold and the last accomplishment has to be confirmed.
- The status list was inherited from a prior operator and its applicability logic has never been rechecked.
- An AD is marked complied by an alternative method and the supporting basis is not on file.
The problem
An AD status list is easy to read and easy to overstate. A line marked complied looks settled, but the assurance lives in the accomplishment record behind it, and on a Falcon 7X that has changed operators the evidence can be missing while the status still reads green. Applicability is the other trap: an AD dispositioned as not applicable on a wrong configuration assumption leaves a live directive quietly unaddressed.
What gets reviewed
- AD applicability assessed against the serial number and installed configuration
- Accomplishment evidence located and matched for each AD marked complied
- Method of compliance recorded and consistent with the directive's requirement
- Recurring ADs checked for their next due threshold against current utilization
- Alternative methods of compliance supported by an approved basis where cited
- The status list reconciled to the underlying work packages and logbook entries
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 AD marked applicable or not applicable rests on the correct configuration for this serial number
- Every complied AD is supported by an accomplishment record, not the status list alone
- The recorded method of compliance matches what the directive actually requires
- Recurring AD intervals are current against the aircraft's time and cycles
- An alternative method of compliance cited on any AD carries its approval basis
Evidence normally required
- The current AD status list for the Falcon 7X
- Accomplishment records, work packages, and logbook entries for complied ADs
- Configuration and effectivity records for applicability decisions
- Current time-in-service and cycle figures for recurring intervals
- Approval basis for any alternative methods of compliance cited
Common discrepancies
- An AD marked complied with no accomplishment record behind the status line
- An applicability call resting on a configuration the aircraft does not actually have
- A recurring AD whose next interval was computed from a stale utilization figure
- An alternative method of compliance cited without its approval basis on file
What is at stake
An AD asserted complied without accomplishment evidence cannot be relied on, and at a transaction or an audit it reverts to open until the evidence is produced or the work is redone. A misjudged applicability call is worse, because it hides a directive that should have been actioned, and the correction can involve inspection or modification that the schedule never planned for.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix applicability
Confirm each AD's applicability against the serial number and installed configuration.
Find the evidence
Locate the accomplishment record behind every AD marked complied and check the method of compliance.
Clock the recurring ADs
Compute the next due threshold for each recurring AD against current time and cycles.
Flag and close
List the unsupported and mis-judged ADs and set a plan to close each one.
What the buyer receives
Who uses the output
- Asset managers pricing the AD work that will land after a transaction closes
- Continuing-airworthiness staff confirming recurring ADs are current before the next threshold
- Records teams assembling the accomplishment evidence a buyer or auditor will demand
How the work fits into the transaction or program
The AD review anchors the status work on a Falcon 7X because so many other records, from the redelivery binder to the export package, quote the AD position without re-testing it. Its closure plan feeds those downstream reviews with an AD line that is either backed by evidence or explicitly flagged as open.
Aircraft-specific considerations
The Falcon 7X is a three-engine long-range business jet with a fly-by-wire flight-control system, so directives touching the flight-control and avionics fit have to be assessed against the exact configuration and software standard on the tail. Its three-engine arrangement also means engine-related directives apply per position, and an AD status list that treats the engines as one entry can hide a per-position gap.
Jurisdiction-specific considerations
As a Dassault type, the Falcon 7X carries EASA directives that the FAA adopts through its own AD system, so the same underlying requirement can appear under two numbers and two effective dates. The review reconciles the FAA and EASA AD positions so a directive is not counted as closed under one authority while it is still open under the other.
Regulatory limits
The review reports whether each AD line is supported by the evidence the records hold. It does not accomplish an AD, approve an alternative method of compliance, or make an airworthiness determination on the directive status.
What this review does not cover
- Performing or signing off any AD accomplishment
- Developing or approving an alternative method of compliance
- Physical inspection tied to an AD requirement
Specific to this review
- A complied line on an AD status list is an assertion until the accomplishment record is found, so the evidence, not the list, sets the real position.
- Applicability errors are more dangerous than missing evidence, because they hide a directive rather than merely leaving one unproven.
- On a three-engine Falcon 7X, engine-related ADs apply per position, so a single combined status line can mask a gap on one engine.
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.
Frequently asked questions
The AD status list shows everything complied, so what is left to review?
A complied line is a claim that has to be matched to an accomplishment record. On an aircraft that has changed operators the record can be missing while the status still reads complied, and an applicability call can rest on the wrong configuration. The review tests each line against its evidence so the position holds up at a transaction or an audit.
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.