AD/F2000/14 - State of Design Airworthiness Directives

The Directive builds on a small set of interlocking concepts and mechanics that determine who must act, what to check, and when to act.

• State of Design AD importation by reference: CASA identifies specific DGAC ADs (listed in Table 1) that it regards as potentially applicable to Australian-registered aircraft. The DGAC ADs are named by number, revision code where applicable, effective date and subject/title (Table 1). The text expressly directs the recipient to "Determine the applicability of the French ... ADs listed in Table 1" (Requirement 1) and to "perform the actions required by that AD" if applicable (Requirement 2). That is, CASA does not reproduce the technical content of the DGAC ADs in full; instead it requires operators/maintainers to consult the DGAC ADs themselves (the ADs are accessible at the URL provided).

• Applicability statement: The Directive’s applicability is narrowly specified: "Falcon 2000 and 2000EX aeroplanes" (Applicability). The Directive therefore targets only those specific airframe models as registered in Australia.

• One-time corrective action focus: The Background explains the DGAC ADs "require one time actions for which the compliance date and/or period has passed" (Background). That shapes the Directive’s purpose: to make sure aircraft recently registered in Australia have had those one-time mandated actions done even though the original DGAC compliance windows lapsed before the aircraft entered Australian registry.

• Two-step operational requirement: The Directive prescribes two discrete steps. First, determine whether each listed DGAC AD applies to a particular aircraft (Requirement 1). Second, where applicable and not already accomplished, carry out the DGAC-prescribed action (Requirement 2). The staging preserves the possibility that some aircraft will already be in compliance because the DGAC AD has previously been accomplished, and the Directive only mandates further work where the AD remains unaccomplished.

• Compliance timing: CASA sets an express compliance timeframe: both steps must be completed "Within 30 days after the effective date of this Directive" and the Directive "becomes effective on 8 June 2006" (Compliance; Effective Date). This creates a firm, short deadline for the determination and any remedial work.

• Reliance on State of Design documentation: The Directive explicitly points to the DGAC AD source (link provided) rather than reproducing full technical instructions. The CASA instrument therefore functions as a legal trigger to consult and act on foreign state-of-design airworthiness directives.

• Delegated issuance: The AD is issued by a CASA delegate, named in the document (James Coyne), showing administrative delegation for issuing such directives (signature block).

These concepts combine into a compliance architecture that places the operational work , records review, technical assessment and any required maintenance/modification , with the parties responsible for the affected aeroplanes, using foreign State of Design documentation as the technical standard and a short mandatory timeframe for action.

The Directive explicitly identifies the type of aircraft it affects: "Falcon 2000 and 2000EX aeroplanes" (Applicability). That description constrains affected aircraft by model; the document does not alter or expand the model list. The Background further frames the target population: CASA "has determined that these ADs may be applicable to recently registered Australian aircraft" and the Directive is "issued to ensure all State of Design ADs are complied with" (Background). Read together, the text points to the following categories of persons and entities who are materially affected:

• Registrants and operators of Australian-registered Dassault Falcon 2000 and 2000EX aeroplanes. The Directive requires that the listed DGAC ADs be checked for applicability to those aircraft and that required AD actions be carried out if not previously accomplished (Requirements 1 and 2). Although the Directive does not name the "registrant" or "operator" explicitly, the operative instructions are directed at the party with responsibility for the aircraft's continuing airworthiness, i.e., the party that must determine applicability and perform any AD-prescribed actions.

• Maintenance organisations or licensed maintenance personnel who perform continuing airworthiness and AD compliance work on the Falcon 2000 series. The Directive requires performance of the technical actions prescribed in the State of Design ADs where applicable; those are the typical tasks of maintenance suppliers and certificated engineers. Operators will need to engage such personnel if the work is not already recorded as accomplished.

• CASA, as the regulator and issuer, is affected in its enforcement and oversight role. The Directive is issued under CASA’s authority (issued by the Delegate) and establishes a compliance obligation that CASA can monitor, although the Directive text itself does not set out enforcement procedures or penalties (see Penalties and enforcement).

• Potentially third-party records holders, such as previous registries, manufacturers, or maintenance organisations whose historical maintenance records may show whether the DGAC one-time actions were already accomplished. Because the listed DGAC ADs’ original compliance periods had passed, operators or maintainers will need to verify past maintenance to determine whether further action is required (Background; Requirements 1 and 2).

The Directive does not identify or impose obligations on other industry participants such as lessees, insurers, or foreign authorities by name. It does not alter ownership rights; it imposes an operational requirement tied to the aircraft's airworthiness status. The practical effect is to shift a task and potential expense to the party responsible for the Falcon 2000/2000EX in Australian registration: determine applicability of the five listed DGAC ADs and, where not already done, carry out the AD-mandated actions within the specified 30-day window following 8 June 2006.

The Directive sets out discrete duties in two operative requirements; it does not create a separate statutory right regime or specify appeal mechanisms in the text provided.

Duties

• Determine applicability (Requirement 1): The person responsible for the aircraft must "Determine the applicability of the French ... ADs listed in Table 1" (Requirement 1, Table 1). Practically, that requires consulting the named DGAC AD documents (the Directive provides the DGAC website URL) and comparing each AD's applicability criteria with the aircraft's configuration, serial number, modification status and maintenance history.

• Perform required AD actions (Requirement 2): Where a DGAC AD from Table 1 "is applicable and has not been previously accomplished, perform the actions required by that AD" (Requirement 2). The Directive thus obliges execution of the technical actions specified in the DGAC ADs , for example modifications, replacements, inspections or other one-time corrective measures as contained in the State of Design AD texts themselves.

• Comply within the timeframe (Compliance): Both Requirements 1 and 2 must be completed "Within 30 days after the effective date of this Directive" (Compliance). The Directive's effective date is 8 June 2006, so the explicit compliance window runs for 30 days thereafter (Compliance; Effective Date).

• Use DGAC source documents (Table 1 and URL): The Directive refers operators to the DGAC ADs by number and provides a URL where they "may be accessed" (link given), indicating the operative technical instructions are in the DGAC documents, not reproduced in full in the CASA Directive.

Rights and process signals in the text

• No explicit right of appeal or deferral is stated in the Directive text supplied. The document does not set out an administrative review or exemption mechanism, nor does it specify whom to contact at CASA for compliance questions in the body of the Directive that is reproduced (the signature block only identifies the delegate).

• Implicit discretion in applicability determination: Requirement 1 places the duty to "determine the applicability" on the responsible party, which implicitly allows technical judgment to be exercised by the determining party (for example, a certified maintenance engineer or an operator’s continuing airworthiness staff) when comparing the DGAC AD criteria with the individual aircraft. The Directive does not prescribe a method of determination, but the likely source documents for the technical criteria are the DGAC ADs themselves (Table 1 and URL).

• The Directive does not itself state record-keeping obligations or documentary proof standards for demonstrating compliance to CASA. It follows that any proof-of-compliance practices would come from general continuing airworthiness record obligations or from CASA’s broader regulatory framework, which are not reproduced here.

• The Directive is framed as ensuring "all State of Design ADs are complied with" (Background). That statement communicates CASA’s policy intent to impose the State of Design technical mandates on Australian-registered aircraft; the specific legal rights (for example, appeal, deferral or approval of alternative means of compliance) are not detailed within the text provided.

In short, the Directive creates two affirmative duties with a short, express deadline and relies on the DGAC AD texts as the technical prescriptions. The Directive does not set out an internal CASA process for challenge, deferral or record submission in the reproduced text.

The Directive sets a clear compliance obligation and a 30-day deadline, but the text reproduced does not include express penalty provisions or the enforcement mechanics by which CASA will verify or sanction non‑compliance.

What the Directive does state about enforcement and timing

• Effective date and compliance window: The Directive "becomes effective on 8 June 2006" and requires that Requirements 1 and 2 be completed "Within 30 days after the effective date of this Directive" (Compliance; Effective Date). This imposes a short, calculated window in which the determination and any remedial work must be completed.

• Issuer identity: The AD is issued by a CASA delegate, and the signature block shows James Coyne, Delegate of the Civil Aviation Safety Authority, dated 19 April 2006. That identifies CASA as the issuing authority and the delegated signatory as the officer who authorised the Directive.

What the Directive does not specify (silences in the source)

• No express penalties: The text does not state any monetary penalties, licence sanctions, grounding orders, or other specific enforcement actions that will be applied for non-compliance within the Directive text supplied. There is no section in the reproduced AD that sets out fines, suspension, or criminal offences.

• No stated verification process: The Directive does not specify how compliance will be demonstrated to CASA, what documentary evidence is required, or whether CASA will conduct audits, inspections, or require submission of compliance records for these specific ADs.

• No stated exemption, alternative means of compliance (AMOC) or appeal route: The text does not include provisions permitting an operator to apply for an exemption, implement an alternative means of compliance, or appeal the Directive’s application or content. The Directive likewise does not indicate a CASA contact for such matters within the reproduced text.

Implications that can be drawn from the document itself

• A short compliance window together with the Directive’s phrasing suggests CASA expects operators and maintainers to treat these ADs as immediately binding operational obligations for the specified aircraft type, and to show evidence of compliance if asked. Although explicit enforcement steps are not contained in the text, the issuance by CASA amounts to a regulatory requirement: the Directive mandates action within a defined timeframe.

• Absent explicit penalty language in the reproduced text, any sanctions, measures or procedural remedies would need to be sought in the broader CASA regulatory framework and enabling legislation, which are not reproduced here. The Directive does not itself create or list such enforcement tools.

Therefore, from the source text alone: the instrument creates a time‑bound compliance obligation under the authority of CASA, but the Directive as reproduced does not set out specific penalty regimes, verification procedures, or appeal/AMOC processes. Those items, if relevant, would be found in CASA’s enabling statutes, general AD policy or other CASA guidance not contained within this document.

The Directive explicitly engages with foreign State of Design airworthiness directives and CASA’s domestic regulatory authority. The reproduced text provides limited but clear pointers about that interaction.

Direct cross-reference to State of Design ADs

• The Directive identifies and imports the technical content of DGAC ADs by reference: it lists specific DGAC AD numbers and titles in Table 1 and directs recipients to determine applicability and comply with the actions required by those DGAC ADs (Requirement 1, Requirement 2, Table 1). The document also provides a URL for accessing the DGAC ADs. This is an example of CASA requiring Australian-registered aircraft to comply with State of Design airworthiness mandates by reference rather than reproducing the full technical prescriptions.

Interaction with domestic continuing airworthiness duties (backgrounded in the text)

• The Background states that the DGAC ADs "require one time actions for which the compliance date and/or period has passed" and that "CASA has determined that these ADs may be applicable to recently registered Australian aircraft. This Directive is issued to ensure all State of Design ADs are complied with" (Background). That shows the Directive’s role as a domestic enforcement mechanism that picks up State of Design obligations which might not have been met when aircraft transferred into Australian registry. It therefore operates as a corrective overlay to ensure that foreign-origin ADs are treated as operative obligations within the Australian context.

Absence of explicit cross-references to statutory provisions in the reproduced text

• The AD as reproduced does not cite the specific legislative provisions under which CASA issues ADs, nor does it cite or modify existing Australian aviation regulations. The Directive functions operationally to require action, but the text does not recite the enabling statutory provisions or reference penalties or enforcement measures drawn from other laws.

Reliance on external technical documents

• Because the Directive directs recipients to act based on the DGAC ADs themselves, it creates a dependency between Australian regulatory compliance and the State of Design’s technical determinations. The DGAC ADs listed include revision markers (for example 97-185-003(B)R1 and 2003-084(B) R1), indicating that the CASA requirement is to consult the specific version of the State of Design ADs identified in Table 1.

Potential scope of interaction (from the document)

• The Directive’s goal, as stated, is to "ensure all State of Design ADs are complied with" (Background). That indicates CASA is using this instrument to align Australian continuing airworthiness obligations with those determined by the aircraft’s design authority. The Directive therefore represents an intersection between foreign airworthiness mandates and domestic operator obligations; the technical content that determines the precise compliance action resides in the DGAC ADs.

In sum, the Directive operationally imports State of Design ADs into Australian compliance duties for the listed aircraft type, but the text reproduced does not set out the precise legislative mechanism, penalty provisions or administrative processes whereby CASA would enforce or monitor performance beyond the 30-day deadline. Any further interplay with domestic statutes, enforcement powers or institutional processes would need to be referenced in CASA’s broader regulatory materials or enabling legislation, which are not part of the text supplied.

The text supplied records the Directive’s issuance and effective dates and includes revision identifiers for the DGAC ADs it references, but it does not contain any subsequent amendment entries to the CASA Directive itself.

What the document records

• Issuance date: The signature block shows "James Coyne, Delegate of the Civil Aviation Safety Authority" with the date 19 April 2006. That appears to be the date of signing or internal issuance (signature block).

• Effective date: The Directive states, "This Airworthiness Directive becomes effective on 8 June 2006" (Compliance; Effective Date). The compliance window is then set to "Within 30 days after the effective date of this Directive" for Requirements 1 and 2 (Compliance).

DGAC AD revision identifiers

• Table 1 lists DGAC AD numbers and some include revision markers in their identifiers, for example "97-185-003(B)R1" and "2003-084(B) R1". Those suffixes indicate that the particular DGAC ADs referenced include revision notes at the State of Design level. CASA’s Directive thus references specific versions of those DGAC ADs as identified in Table 1.

Absence of subsequent CASA amendments in the supplied text

• The supplied Directive text does not include any later amendments, supersessions or revocations of AD/F2000/14 itself. There is no "Amendment" section, no "Supersedes" clause, and no consolidated version showing later changes,in short, no amendment history for the CASA AD is recorded in the material provided.

How to treat the entity-level revision information

• The presence of DGAC AD revision codes in Table 1 means that, to follow the Directive as drafted, one must consult the specific State of Design AD versions identified in the Table. The CASA instrument does not say to treat later DGAC AD revisions as automatically applicable; rather, it requires determining applicability of the DGAC ADs "listed in Table 1", which references those specific DGAC AD numbers and dates.

If you require a definitive record of subsequent amendments to AD/F2000/14 after 8 June 2006, that information is not present in the reproduced text and would need to be obtained from CASA’s AD database or consolidated AD lists; the current document contains no such subsequent amendment entries.

The reproduced Directive does not refer to any litigation, court decisions, judicial review, or formal disputes concerning AD/F2000/14 or the DGAC ADs listed in Table 1. The text provides:

• no case citations;
• no references to legal challenges, reviews or appeals;
• no mention of contested enforcement actions or legal proceedings.

The absence of any litigation references in the Directive as reproduced means there is no litigation history recorded in this instrument itself. If litigation arose from the Directive’s operation (for example, a challenge to requirement, scope, or enforcement), those matters would be documented elsewhere,judicial records, administrative decisions or CASA enforcement files,which are not part of the text supplied here. The Directive is a short operational instrument setting a compliance obligation and does not include a discussion of legal disputes or jurisprudence.

If a practitioner needs to understand whether this CASA AD has been the subject of litigation or of administrative review, the relevant searches would be across court databases, tribunal records, and CASA enforcement archives. Nothing in the AD’s text provides commentary or history of such proceedings.

The Directive is compact but contains several points that can cause practical compliance risk or confusion if they are overlooked. These are concrete, source‑grounded issues drawn from the text.

1. Short compliance window tied to an effective date

• The Directive requires both the determination of applicability and any unaccomplished AD actions to be completed "Within 30 days after the effective date of this Directive" and the stated effective date is "8 June 2006" (Compliance; Effective Date). That creates a deadline that must be met within a predictable but short timeframe (30 days). Failure to act within that window may leave aircraft noncompliant with CASA’s stated requirement.

2. The DGAC ADs are "one time actions" whose original compliance windows have passed

• Background states these DGAC ADs "require one time actions for which the compliance date and/or period has passed" (Background). That means a newly registered Australian aircraft could be non-compliant simply because the original DGAC compliance opportunity fell before the aircraft entered Australian registry. Operators cannot assume that the passage of the original DGAC dates relieves them from CASA’s present requirement.

3. Determination of applicability is an affirmative duty

• Requirement 1 requires the responsible party to "Determine the applicability" of each DGAC AD listed (Requirement 1). That determination typically requires inspection of aircraft configuration, serial numbers, modification records and prior maintenance records. If records are incomplete or unclear, operators must take steps to obtain or reconstruct evidence to support the applicability determination.

4. The Directive does not reproduce the DGAC AD texts

• The technical requirements are in the DGAC ADs themselves. The CASA document lists the DGAC ADs (Table 1) and provides a URL for accessing them. A potential pitfall is failing to consult the DGAC documents themselves or consulting a different version than the one listed by CASA. Table 1 lists specific DGAC AD numbers and effective dates; the particular DGAC AD versions listed must be the ones checked.

5. Some DGAC AD entries include revision markers

• Table 1 contains identifiers such as "97-185-003(B)R1" and "2003-084(B) R1". These suffixes indicate the State of Design ADs have revision history. Using the wrong revision could lead to an incorrect applicability determination or failure to carry out the precise technical action required by the referenced DGAC AD.

6. No express proof of compliance procedure in the Directive

• The Directive does not state how to evidence compliance to CASA nor list an AMOC or exemption route. Practitioners should not assume a particular submission or approval channel for evidence unless provided elsewhere by CASA. Keep contemporaneous documentary proof that the determination was made and that any required actions were performed.

7. Narrow applicability means scope errors are possible

• The Directive applies only to "Falcon 2000 and 2000EX aeroplanes" (Applicability). Operators should avoid overbroad assumptions (for example, applying the Directive to other Falcon models) and verify exact model and serial number matching before taking or withholding action.

8. Timing between issuance and effective date

• The signature block is dated 19 April 2006, while the Directive "becomes effective on 8 June 2006" (signature vs effective date). That gap could create confusion about when the 30-day compliance clock starts; the text is explicit that the clock starts from the effective date.

9. Potential reliance on historical records held offshore

• Because the DGAC ADs had past compliance dates, relevant evidence of prior accomplishment may be held with prior owners, foreign maintenance organisations or the manufacturer. Identifying and obtaining records in short order can be operationally challenging.

10. No penalties appear in the text

• The Directive does not set out penalties or enforcement measures in the reproduced text. That absence should not be taken to mean CASA will not enforce compliance; rather, enforcement mechanisms are not detailed in the instrument itself. Operators should treat the obligation as mandatory and prepare to demonstrate compliance if requested.

Those items are directly traceable to the Directive’s language (Applicability, Requirements 1 and 2, Table 1, Compliance, Background). Practitioners should plan compliance logistics with these exact constraints in mind: consult the specific DGAC AD versions listed, determine applicability, document the determination and any remedial actions, and complete all steps within the 30‑day window after 8 June 2006.

The Directive prescribes a tight, two-step compliance process. The following are concrete, source-grounded steps to implement the Directive as written.

Step 1 , Confirm aircraft fit the Directive’s applicability

• Verify the aircraft is a Dassault Falcon 2000 or 2000EX, because the Directive’s Applicability is limited to "Falcon 2000 and 2000EX aeroplanes" (Applicability). Confirm model designation and serial number to ensure the aircraft is within scope.

Step 2 , Access the DGAC ADs listed in Table 1

• Obtain the DGAC ADs identified in Table 1. The Directive provides a URL where the DGAC ADs "may be accessed" (DGAC ADs may be accessed at the following URL: http://www.gsac.fr/php/P_ConsignesNav.php). Use the specific DGAC AD numbers and effective dates listed in Table 1 to retrieve the correct AD versions, noting revision markers (for example "97-185-003(B)R1", "2003-084(B) R1" and so on).

Step 3 , Perform the applicability determination (Requirement 1)

• For each listed DGAC AD, compare the AD’s applicability criteria against the aircraft’s serial number, equipments list, modifications, and maintenance history to determine whether that DGAC AD applies to the aircraft (Requirement 1). Record the method and evidence used for the applicability determination (e.g., maintenance records, mod status, serial number checks).

Step 4 , Establish whether the DGAC AD action has already been accomplished

• The Directive requires action "if it is determined that a DGAC AD is applicable and has not been previously accomplished" (Requirement 2). For each applicable DGAC AD, check the aircraft’s historical maintenance records and any transfer documentation to confirm whether the one-time action has already been completed. If records are incomplete, make reasonable enquiries (for example, contact prior registrant/maintenance organisation or the manufacturer) before assuming compliance.

Step 5 , If unaccomplished, perform the DGAC‑specified actions (Requirement 2)

• Where the DGAC AD is applicable and not already accomplished, perform the actions required by that DGAC AD (Requirement 2). The CASA Directive relies on the technical prescriptions contained in the DGAC ADs themselves, so carry out the modification/inspection/repair strictly in accordance with the DGAC AD’s instructions and, where necessary, by appropriately certificated maintenance personnel.

Step 6 , Meet the timing requirement

• Complete Steps 3-5 "Within 30 days after the effective date of this Directive" (Compliance). The Directive's effective date is 8 June 2006, so the compliance period ends 30 days thereafter (Compliance; Effective Date). Plan resources and scheduling accordingly; if heavy maintenance is required, arranging slot time and parts within the 30-day window will be necessary.

Step 7 , Maintain documentary evidence

• Although the Directive does not itself prescribe the documentary format, it is practical and source-consistent to maintain records demonstrating: (a) the applicability determination for each DGAC AD; (b) proof of prior accomplishment where applicable; and (c) details of any remedial actions performed where the DGAC AD had not been accomplished. These records will be the primary evidence that the obligations under Requirements 1 and 2 have been met within the required timeframe.

Step 8 , Note the particular DGAC AD subjects in Table 1

• Table 1 lists the subjects of the DGAC ADs: Water Heater Overheat (97-185-003(B)R1), Passenger Oxygen Masks (1999-267-010(B)), Fire Protection (2003-084(B) R1), Navigation - Hybridated GPIRS Speed (2003-409(B)), and Indicating Recording Systems - NIC (Honeywell EPIC Network Interface Controllers) Timing Issues (F-2005-025). Use those subject headings to prioritise searches in maintenance records and to identify relevant aircraft systems requiring inspection or modification.

Step 9 , Consider contacting CASA if ambiguities arise

• The Directive itself does not set out an appeal or AMOC process. If there is uncertainty about scope, acceptable evidence of prior accomplishment, or the existence of an alternative means of compliance, an operator should engage with CASA through the standard regulatory contact channels (the Directive identifies CASA as issuer via the Delegate signature). The Directive’s text does not provide a direct CASA contact for queries; use CASA’s general communication channels if needed.

Step 10 , Treat this as a retroactive capture of State of Design obligations

• Remember the Background: these are "one time actions for which the compliance date and/or period has passed" and CASA issued the Directive "to ensure all State of Design ADs are complied with" (Background). Therefore do not assume that past dates relieve you; if the DGAC AD has not been accomplished on the particular airframe, the CASA Directive requires action now.

Perform these steps promptly, keep contemporaneous records and ensure the technical work follows the DGAC AD instructions listed in Table 1. The Directive’s narrow mechanics demand a factual applicability review first, then execution where necessary, all within the prescribed 30‑day window.