AD/F2000/16 - Flight Controls - Trailing Edge Flaps Rotating Rods

The AD centralises three technical concepts: correct assembly, damage replacement, and labelling of the flap rotating rods and associated retaining brackets. Correct assembly is the primary preventive measure: the background to the AD explains that an in‑flight failure occurred because a rotating rod had been installed on the wrong side during maintenance, creating contact between the rotating rod and its retaining bracket. That incorrect installation led, after time in operation, to rod breakage and a flap asymmetry situation. The AD treats the resulting flap asymmetry combined with a latent failure of the asymmetry detection system as a catastrophic failure condition; this is the safety rationale the AD records in its Background paragraph.

The affected components are described in location terms rather than technical part numbers in the AD text: the left-hand and right-hand wing root compartments, and the left-hand and/or right-hand main landing gear compartments. The AD requires inspection of both wing root compartments and the main landing gear compartment(s) as instructed in the applicable Dassault Service Bulletin for the operator’s model (Falcon 2000 or 2000EX). The AD does not itself supply detailed drawings, torque values, part numbers, or labelling text; it delegates the technical particulars to the specified Dassault SBs (Table 1).

Table 1 is a document-reference concept: the AD does not vary or re‑state the SB content, but makes compliance conditional on performing the SB procedures or later DGAC‑approved revisions of those SBs. For Falcon 2000 the SB is F2000‑326; for Falcon 2000EX it is F2000EX‑83. The AD’s Note cross‑references EASA AD 2006‑0115 (10 May 2006), indicating harmonisation or relation with that European AD, but the AD text leaves the operational method to the Dassault SBs.

Time-based compliance concepts in this AD are twofold: a short time window for compelled replacement (prior to further flight if a rod is damaged) and a broader time window for the inspection and labelling tasks (within 330 flight hours or seven months from effective date, whichever first). These deadlines create both an urgency gradient (replacement is immediate if damage exists) and a planned compliance window (inspection and labelling within the specified flights/months).

Finally, the AD documents the administrative concept of effective date and authority: it becomes effective on 3 August 2006 and is issued by a CASA delegate, James Coyne, dated 21 June 2006. The AD does not itself include penalty provisions, alternative means of compliance, or continuing airworthiness recordkeeping obligations; instead it prescribes technical actions and timelines, and points the operator to the referenced SBs for procedural detail.

The AD applies specifically to Dassault Aviation Falcon 2000 and Falcon 2000EX aeroplanes, as stated in the Applicability section. That manifests as a concentrated set of affected parties: aircraft operators or owners of those models; the maintenance organisations or personnel performing maintenance and inspections on those aeroplanes; and any aviation engineering, procurement or logistical staff responsible for parts replacement and labelling. The AD identifies the compartments to be inspected , LH/RH wing root compartments and LH and/or RH main landing gear compartments , thereby identifying the maintenance tasks likely to be performed by licensed aircraft maintenance engineers or authorised maintenance organisations.

The AD also implicates the aircraft manufacturer’s technical data: Dassault Aviation Service Bulletins F2000‑326 (Falcon 2000) and F2000EX‑83 (Falcon 2000EX), or later DGAC‑approved revisions, are the procedural documents to be followed. Where the AD requires replacement "in accordance with the respective Dassault Aviation SB," the affected maintenance organisations must hold or obtain access to the specified SBs and any DGAC‑approved revisions. The DGAC reference implies interaction with that approving authority’s revisions for the SBs; the AD does not itself reproduce DGAC material but conditions compliance on DGAC‑approved SB revisions if they are later versions.

Regulatory actors are implicated to the extent the AD is issued by the Civil Aviation Safety Authority (CASA). The signatory on the document is James Coyne, Delegate of the Civil Aviation Safety Authority, dated 21 June 2006; the AD states it becomes effective on 3 August 2006. While the AD text does not set out enforcement procedures, it is a written directive from the regulator and therefore directly addresses regulated entities in the Australian civil aviation environment operating the specified aeroplane types.

Indirectly affected parties include operators’ scheduling and finance teams, since inspections, possible part replacements, and labelling require aircraft downtime, technician labour and replacement parts. Procurement must source correct replacement rods as specified by Dassault SBs. If maintenance discovers damage requiring replacement prior to further flight, that decision immediately affects flight planners and customers, as the aircraft cannot be dispatched until the replacement is completed in accordance with the AD.

Finally, the AD’s Background notes that EASA AD 2006‑0115 dated 10 May 2006 is referred to, which means that European operators and authorities would have a related instrument; however, within this document the applicability is explicitly to Falcon 2000 and 2000EX aeroplanes and the specified SBs for those models, so the primary Australian‑jurisdiction impact is on operators and maintenance organisations responsible for those airframes.

Duties under this AD are explicit and narrowly framed. There are three core duties imposed on operators/maintenance providers:

1. Verification duty: Verify the correct assembly of flap rotating rods and associated retaining brackets installed in the left-hand and right-hand wing root compartments and in the left-hand and/or right-hand main landing gear compartment, as instructed in the respective Dassault Aviation Service Bulletins listed in Table 1. This is Requirement 1 of the AD.

2. Replacement duty: If any rotating rod is found to be damaged during inspection, the damaged rod must be replaced in accordance with the respective Dassault Aviation Service Bulletin for the aircraft model. This is Requirement 2 and the AD specifies that replacement must occur prior to further flight after the effective date (Compliance item 2).

3. Labelling duty: Label the rods and associated retaining brackets as instructed in the applicable Dassault Service Bulletin listed in Table 1. This is Requirement 3.

Each duty is accompanied by a compliance timeframe. For verification and labelling (Requirements 1 and 3), the operator must comply within 330 flight hours or within seven months from the effective date of the AD, whichever occurs first (Compliance items 1 and 3). For replacement (Requirement 2), the AD requires replacement prior to further flight after the effective date if damage is found (Compliance item 2). The AD’s effective date is 3 August 2006.

Rights in the AD are implicit rather than enumerated. The document does not set out an alternative means of compliance (AMOC) process, nor does it explicitly reserve rights to seek extensions or to apply different procedures. The AD points the operator to Dassault SBs and to DGAC‑approved revisions as the procedural mechanism; by specifying "or later DGAC approved revision" the AD permits the use of later DGAC‑approved revisions of the SBs listed in Table 1. That phrasing is a limited operative right: an operator may use a later DGAC‑approved SB rather than the specific version cited.

The AD does not state any recordkeeping duties, certification or signing requirements for the maintenance release after performing the tasks, nor does it include an express appeals or review mechanism in its text. The signature line shows the AD is issued by a CASA delegate (James Coyne), which establishes that the duties are regulatory in origin.

Practically, the duties require an operator to plan for inspection resource allocation, parts inventory or procurement to allow immediate replacement if damage is discovered, and application of the labelling procedure as specified by the SB. The replacement duty’s "prior to further flight" standard imposes an immediate operational constraint: any aeroplane found with a damaged rod cannot be flown again until it has been replaced in accordance with the Dassault SB.

The AD’s Note referencing EASA AD 2006‑0115 suggests harmonisation with an existing European AD; operators that also operate under European jurisdiction may need to align the Australian compliance with the EASA timeline and procedures, using the DGAC‑approved SBs as the focal compliance instruments.

The AD text does not set out civil or criminal penalties, fines, or specific enforcement procedures. It is an instruction issued by the Civil Aviation Safety Authority (CASA) and carries an effective date (3 August 2006) and a signatory delegate (James Coyne). The document’s Compliance section establishes explicit deadlines and the operative actions required, but it does not specify the administrative sanctions or legal consequences that will follow if an operator fails to comply. The AD therefore remains prescriptive about required actions and timing, while silent on concrete penalty instruments within the text.

Because the AD is an instrument issued by CASA, it functions as a regulatory direction. The record in the AD comprises three numbered Requirements and three numbered Compliance time points that mandate inspection, replacement where necessary, and labelling. The AD’s force is conveyed through those mandated actions and the AD’s effective date. The AD references specific Dassault Aviation Service Bulletins and qualifications for later DGAC‑approved revisions (Table 1), thereby creating a defined path to compliance.

Enforcement mechanisms, sanctions, or the procedure by which CASA monitors compliance are not included in the AD’s text supplied here. The AD contains no provisions on evidence of compliance, certification signatures, logbook entries, maintenance release declarations, or administrative reporting obligations. It likewise does not state whether compliance must be recorded in the aircraft’s maintenance log or notified to CASA.

The AD’s silence on penalties or enforcement in its own text means that any sanctions or enforcement actions would arise from the broader regulatory framework of which this AD is a part, rather than from provisions inside the AD itself. The AD’s effectiveness date and the statement that the AD “becomes effective on 3 August 2006” establish an unambiguous temporal point at which the duties commence.

Operators and maintenance organisations must therefore treat the AD as a binding technical requirement to be complied with within the times specified by the AD and the underlying Service Bulletins. The AD’s replacement-when-damaged immediate requirement (“prior to further flight”) is operationally enforceable in that it prevents dispatch until the defective component is corrected in accordance with the AD; the AD text itself, however, does not enumerate the sanctions for non‑compliance.

The AD cross-references other regulatory or technical instruments within its text. Most directly, Table 1 incorporates Dassault Aviation Service Bulletins as the procedural means for verifying assembly, replacing damaged rods, and labelling. The listed SBs are F2000‑326 for Falcon 2000 models and F2000EX‑83 for Falcon 2000EX models, with the AD permitting the use of later "DGAC approved revision[s]" of those SBs. That connection means compliance with the AD requires following manufacturer service information, specifically the versions of those SBs approved by the DGAC where a later revision has been issued.

The AD includes a Note stating that "EASA AD 2006‑0115 dated 10 May 2006 refers." The inclusion of that reference indicates a purposive alignment or relation with an EASA airworthiness directive; however, the AD does not reproduce EASA AD provisions or adopt them verbatim. The AD’s operative compliance mechanism remains the Dassault SBs and the AD’s own compliance timeframes. The mention of EASA AD 2006‑0115 is an expressed cross‑reference in the AD text.

The AD is an instrument of the Civil Aviation Safety Authority and is signed by a CASA delegate. The AD thereby operates within the Australian civil aviation regulatory architecture. The AD itself does not mention or incorporate other Australian statutes or regulations within its text; nor does it set out how its requirements interact with maintenance release processes, logbook entries, or continued airworthiness obligations under other instruments. Those interactions are not articulated in the AD text supplied here.

Notably, the AD’s instruction to follow Dassault SBs "or later DGAC approved revision" creates an interaction between the manufacturer documentation and the DGAC’s approval process. Operators wishing to rely on a later revision must ensure that the revision is DGAC‑approved; the AD asserts that later DGAC approval is an acceptable method of satisfying the SB requirement. The AD does not reference approval by CASA for later revisions, nor does it state whether DGAC approval alone suffices for Australian regulatory compliance beyond the explicit phrasing used.

Beyond the direct tabled references, the AD’s background identifies a failure mode , a rotating rod installed on the wrong side during maintenance , that points to maintenance procedural interaction with manufacturer's instructions. The AD therefore links to the broader domain of maintenance quality assurance and human factors, but it does not specify or amend any other statutory maintenance obligations in its own text.

In short, the AD interacts with external instruments by directing compliance to specified manufacturer SBs and by cross‑referencing an EASA AD; it does not by itself set out relations to other Australian statutes or administrative enforcement procedures in its textual content.

The AD supplied contains no amendment history beyond its own date and effective date. The document is dated 21 June 2006 (signed by James Coyne, Delegate of the Civil Aviation Safety Authority) and states that the AD becomes effective on 3 August 2006. There are no later amendment entries, no revision dates, and no superseding notices included in the material provided.

Table 1 identifies Dassault Aviation Service Bulletins as the technical sources and explicitly permits "or later DGAC approved revision" of each listed SB to be used for compliance. That phrasing allows for later amendments to the manufacturer’s SBs (subject to DGAC approval) to serve as compliant methods, but it does not constitute an amendment to the AD itself. The AD’s text does not indicate that it will be automatically amended on issuance of a later SB revision; it simply authorises the use of a later DGAC‑approved SB as the procedural vehicle for compliance.

The Note in the AD refers to EASA AD 2006‑0115 dated 10 May 2006, which is an external instrument that predates this AD’s effective date. The AD contains neither references to earlier Australian ADs nor to any subsequent amendments. No revocation, supersession or further variation of this AD is recorded in the text provided.

For readers seeking to determine whether this AD has since been amended, revoked or superseded, the supplied document gives no such update. The only amendment‑type flexibility present in the AD is the explicit acceptance of later DGAC‑approved revisions of the cited Dassault SBs as allowable methods of compliance. Beyond that, there is no internal amendment history to report in the source material.

The AD document provided does not contain, cite or summarise any litigation history. There are no references to judicial or administrative appeals, disputes, enforcement proceedings or case law within the text. The document simply states the safety background, the required actions, the SBs to be used, compliance times, an effective date (3 August 2006), and the signature of a CASA delegate (James Coyne, 21 June 2006).

Because the supplied instrument does not include any mention of disputes, prosecutions, or litigation connected with the AD itself, no litigation history can be drawn from the source. The Background section describes an event , in‑flight rod failure caused by a maintenance assembly error , but it does not record any legal proceedings arising from that event. The Note refers to EASA AD 2006‑0115, which is another regulatory instrument; the AD does not report any litigation tied to that EASA AD either.

If a reader requires information on whether legal challenges, enforcement actions, or judicial determinations arose from this AD, that material is not present in the supplied source and therefore cannot be reported here. The AD text is silent on litigation and provides only the technical and compliance information summarised elsewhere in this deep dive.

Several operational and compliance pitfalls are implicit in the AD language and structure that are material for operators and maintenance organisations to note, all grounded in the AD text.

1. Location specificity and coverage: The AD requires verification in the LH/RH wing root compartments and in the LH and/or RH main landing gear compartments. The AD’s phrasing , "in the LH/RH wing root compartment and in the LH and / or RH main landing gear compartment" , suggests that inspections must cover both wing root compartments and at least the relevant main landing gear compartment(s). A misreading that inspects only one side, or only the wing root and not the landing gear compartments, would fail to meet the AD’s specified scope.

2. Urgency of replacement: If a damaged rod is found, the AD requires replacement "prior to further flight after the effective date of this AD." That operational constraint creates an immediate ground‑risk: a discovered damaged rod halts any further flight until the replacement is completed in accordance with the Dassault SB. Planning that does not allocate for prompt parts procurement and technician availability risks extended grounding of the aircraft.

3. Two compliance timelines: The AD imposes a short term window (330 flight hours or seven months, whichever first) for verification and labelling and an immediate replacement requirement if damage is found. Operators need to distinguish which action maps to which compliance deadline. The AD’s Compliance section lists three items that map to Requirements 1-3; those who conflate the timelines risk non‑compliance.

4. Dependence on Dassault SBs and DGAC approval status: The AD does not include procedural detail such as inspection criteria, torque values or labelling text, but delegates those procedural specifics to the Dassault SBs cited in Table 1, or later DGAC‑approved revisions. If an operator does not have access to the correct SB revision or to evidence that a later revision is DGAC‑approved, there is a compliance gap. The AD’s acceptance of later DGAC‑approved revisions does not state whether CASA approval is required for using those later revisions in Australia; the AD text itself references DGAC approval only.

5. Documentation gaps: The AD does not specify logbook entries, certification of work, or notification procedures. Operators must therefore be careful to follow applicable maintenance release and recordkeeping practices elsewhere in their regulatory environment when performing the AD tasks, because the AD itself does not specify those administrative steps. Failure to record compliance in accordance with broader maintenance documentation requirements could lead to regulatory friction even if the physical actions are performed.

6. Model differentiation: Table 1 lists separate SBs for Falcon 2000 and Falcon 2000EX. Applying the wrong SB (for the wrong model) would not meet the AD’s clear table instruction that the SB for the operator’s model must be used. Maintenance planners must confirm the aeroplane model before selecting the SB.

7. Labelling as a required action: The AD requires labelling of rods and associated retaining brackets per the SB. This is not merely an administrative recommendation: it is an express requirement (Requirement 3). Omitting the labelling step, or performing a labelling that does not match the SB instructions, would fall short of the AD’s mandates.

8. Background failure mode: The AD records that improper installation caused contact and eventual rod breakage, producing flap asymmetry. Flap asymmetry combined with a latent detection failure is classified in the AD’s Background as a catastrophic failure condition. This characterisation means that regulators and operators should treat the inspection and replacement requirements as addressing a high‑consequence risk; the AD’s operational timelines reflect that classification.

Operators and maintenance providers should therefore read the AD together with the correct Dassault SB for their model, ensure prompt availability of replacement parts and qualified personnel, ensure inspections cover the specified compartments bilaterally, apply labelling per SB instructions, and document the work according to applicable maintenance records practices even though the AD does not itself prescribe the recordkeeping steps.

The AD prescribes a clear compliance pathway; the steps below restate the AD’s obligations and map them to operational actions, using only the text and references in the AD.

1. Identify affected aeroplanes: Confirm the aeroplane is a Dassault Falcon 2000 or Falcon 2000EX (Applicability section). Only those models are subject to the AD as written.

2. Obtain the correct Dassault Service Bulletin: For Falcon 2000 obtain Dassault Aviation SB F2000‑326 (or a later DGAC‑approved revision). For Falcon 2000EX obtain Dassault Aviation SB F2000EX‑83 (or a later DGAC‑approved revision). The AD’s Table 1 makes compliance contingent on following the procedures in the relevant SB.

3. Plan inspection within the stated deadline: For verification and labelling tasks, schedule the inspection within 330 flight hours or within seven months from the AD’s effective date (3 August 2006), whichever occurs first. This is Compliance items 1 and 3 mapped to Requirements 1 and 3. Ensure planning covers both LH and RH wing root compartments and LH and/or RH main landing gear compartment(s) as the SB instructs and as the AD requires.

4. Perform verification: Carry out the verification of correct assembly of the flap rotating rods and associated retaining brackets in the left-hand and right-hand wing root compartments and in the main landing gear compartment(s) as per the instructions in the applicable Dassault SB. The AD’s Requirement 1 mandates this verification.

5. If damage is found, replace immediately: If the inspection reveals a damaged rotating rod, replace that rod in accordance with the respective Dassault SB. The AD’s Requirement 2 requires replacement "in accordance with the respective Dassault Aviation SB," and Compliance item 2 requires that replacement occur prior to further flight after the effective date. That creates an immediate non‑dispatch condition until the replacement is complete and performed in accordance with the SB.

6. Apply labelling as required: After verification and any necessary replacement, label the rods and associated retaining brackets exactly as instructed in the applicable Dassault SB (Requirement 3). Do this within the same 330 flight hours / seven months window unless the SB specifies otherwise; the AD’s Compliance items tie labelling to the same timeframe as verification.

7. Use the correct SB revision: If a later Dassault SB revision exists and is DGAC‑approved, that later DGAC‑approved revision is acceptable under the AD’s Table 1 wording ("or later DGAC approved revision"). Ensure the revision used is DGAC‑approved as required by the AD text.

8. Preserve evidence of compliance: Although the AD text does not set out recordkeeping requirements, good compliance practice is to maintain contemporaneous maintenance records showing the SB revision used, the inspection findings, any replaced part numbers, date/time/cycles/flight hours at which the work was performed, and the name, licence/certification of the person who performed and authorised the work. The AD itself is silent on recordkeeping, but operators should reconcile AD completion with their established maintenance release and airworthiness record procedures.

9. Coordinate parts availability and technician resources: Because replacement, if needed, must occur prior to further flight, ensure procurement and stocking approaches account for potential immediate replacement. The AD does not specify spare part nomenclature beyond referring to the SBs; follow the SBs for part identification and replacement procedures.

10. Consider cross‑jurisdictional references: The AD’s Note refers to EASA AD 2006‑0115 dated 10 May 2006. If the operator is subject to multiple jurisdictions’ continuing airworthiness rules, confirm that the chosen SB revision and timing satisfy both the AD and any parallel foreign authority ADs referenced.

11. Respect effective date: The AD becomes effective on 3 August 2006. Compliance timeframes in the AD are measured from that effective date where specified.

12. Retain the AD and SB documentation: Keep a copy of the AD and the SB used for compliance with the maintenance records so that evidence of compliance can be produced in an audit or inspection. While the AD does not mandate a particular form of documentation, operators should ensure their maintenance release and records reflect the AD work performed.

Following these steps will align maintenance actions with the AD’s explicit requirements: verify correct assembly, replace damaged rods per the SB prior to further flight, and label rods/brackets per SB instructions, using the Dassault SB appropriate to the aeroplane model or a later DGAC‑approved revision, within the timeframes the AD specifies.