AD/F2000/25 - Oxygen - Incompatible Passenger Mask Boxes

Operators and owners of affected aeroplanes: The AD applies to Falcon 2000EX aeroplanes serial numbers 28-55 inclusive that have not implemented SB F2000EX‑61 or its Revision 1 (Applicability). Those operators or owners must ensure the replacement occurs by the compliance deadline. Determination of whether an aircraft “has implemented” the SB will be a records exercise, requiring review of maintenance logbooks and engineering records to confirm whether SB F2000EX‑61 (22 March 2006) or SB F2000EX‑61 Revision 1 (22 March 2007) has been carried out (Applicability).

Maintenance organisations and maintenance personnel: The required work is to be performed in accordance with the manufacturer’s SB; authorised maintenance organisations will be the parties that actually install the replacement mask boxes, certify the work, and record compliance in the aircraft maintenance logs (Requirement). The AD’s direction to follow the SB makes the SB the controlling technical procedure for maintenance staff.

Aircraft lessors and financiers: Where aircraft are leased, lessors will be interested in ensuring the lessee meets the AD’s requirement by the deadline to avoid airworthiness deficiencies that could affect asset value or lease obligations. The AD itself does not specify interested‑party rights, but the practical effect is that those with legal or economic interests in affected airframes must ensure compliance.

Regulatory authorities and inspectors: CASA (through its delegate who signed the AD) is the issuing authority. The AD references EASA approval for SB revisions and EASA AD 2007‑0073 (Requirement; Note). CASA and other civil aviation authorities will be the agencies that monitor compliance; the AD’s text is the instrument they will rely on to require and verify the work.

Manufacturer / supplier: Dassault Aviation is the source of the Service Bulletin (Requirement). The manufacturer provides the technical fix and replacement parts and is the originator of the corrective action identified in the AD (Applicability; Requirement).

Passengers indirectly: The AD’s stated safety aim is to prevent passenger incapacitation during oxygen‑dependent scenarios by ensuring minimum mass flow per certification requirements (Background). The directive does not create new passenger obligations but affects passenger safety indirectly through mandatory equipment replacement.

Other jurisdictions: The AD notes EASA AD 2007‑0073 and permits EASA‑approved revisions of the SB as compliant. Operators subject to EASA or other state regulators will need to coordinate compliance with both CASA’s AD and any equivalent EASA instrument referenced (Requirement; Note).

Primary duty to replace: The fundamental duty imposed by the AD is to replace passenger oxygen mask boxes “in accordance with SB F2000EX‑61 or later revision approved by the European Aviation Safety Agency (EASA)” (Requirement). The AD establishes no alternative corrective method within its text; compliance is to the SB text as approved by EASA.

Duty to meet the compliance deadline: Operators of affected aeroplanes must complete the replacement no later than 30 June 2008 (Compliance). The AD also states it becomes effective on 10 May 2007 (Compliance), so the AD creates an enforceable effective period between those dates.

Duty to determine applicability: Operators must determine whether their aeroplane is within serial numbers 28-55 inclusive and whether the SB has already been implemented (Applicability). This requires examination of serial‑number records and maintenance history to establish whether the AD’s obligation attaches.

Duty to use EASA‑approved SB revisions only: The AD allows later SB revisions to be used only if approved by EASA (Requirement). That conditions permitted technical procedures on a particular regulator’s approval, not solely on the manufacturer’s issuance.

Duty to follow the SB’s instructions: Because the AD prescribes compliance “in accordance with SB F2000EX‑61,” the SB’s procedural instructions, parts lists, and acceptance criteria become the operative method for compliance. Any deviation from the SB’s method would require an alternative approval route not contained within the AD text.

Recordkeeping implication: While the AD text does not explicitly command what records must be kept post‑modification, the nature of airworthiness directives means operators will need to document completion to demonstrate compliance with the AD. The AD itself names the SB and gives a compliance date, so a completed SB action will serve as the documentary proof.

Rights implicit in the text: The AD permits compliance by use of later SB revisions if and only if those revisions are approved by EASA (Requirement). That is a right to use an updated technical route to compliance, constrained by regulatory approval. The AD does not specify an appeals mechanism or alternative compliance routes in the text.

Delegated decision‑maker: The AD is issued by CASA’s delegate (signature block) and references EASA approval; these authorities determine the acceptability of any later SB revisions and interpret the AD’s requirements operationally (Requirement; Note; signature block).

No express compensation or cost allocation: The text does not allocate cost responsibility or compensation, nor does it provide funding. The mandate is technical: replace mask boxes per SB; the AD does not state who pays or reimbursements (Requirement; Compliance).

The AD text does not specify criminal or civil penalties, fines, or a particular enforcement regime within its four labelled sections. It sets mandatory requirements,effective date, compliance date, and the specific corrective action,and relies on the issuing authority’s regulatory reach to give those requirements force. The document’s enforcement mechanics are implicit rather than described: the AD becomes effective on 10 May 2007 and requires completion by 30 June 2008 (Compliance). Non‑compliance with an AD is, in aviation regulatory practice, typically actionable by the issuing authority, but the AD text itself does not list sanctioning provisions or enforcement procedures.

The AD references EASA AD 2007‑0073 and requires SB revisions to be approved by EASA to be acceptable for compliance (Requirement; Note). That linkage suggests that enforcement and oversight may involve coordination with EASA decisions and that recorded compliance with an EASA‑approved SB revision will be the means of demonstrating conformity to the AD. The AD’s prescriptive direction to comply “in accordance with SB F2000EX‑61” makes the SB the technical standard; therefore, enforcement will effectively rest on verifying that the SB was carried out and documented.

Because the AD does not itself spell out penalty amounts, inspection powers, or administrative sanction processes, affected parties must look to the broader regulatory framework under which the Civil Aviation Safety Authority operates for enforcement mechanisms and remedies. The AD is explicit about the obligation and the timeline; it is silent about enforcement modalities and consequences for failure in this text alone.

Practical enforcement considerations drawn from the AD’s structure: inspectors and regulators will need to verify serial‑number applicability, confirm whether SB F2000EX‑61 (or Revision 1) has previously been implemented, and, for aircraft still non‑compliant, verify that replacement has been performed in accordance with the SB by the 30 June 2008 deadline (Applicability; Requirement; Compliance). Verification will necessarily rely on maintenance records and SB compliance documentation, because the AD’s instruction is execution of a specified SB rather than a device performance measure stated independently in the AD.

Reference to certification requirements: The Background states the oxygen flow in NORMAL mode fails to meet “the minimum mass flow of supplemental O2 for each passenger, as required by Certification Specifications” (Background). The AD therefore intersects with the airworthiness certification regime in that it seeks to restore equipment performance to the level required by those certification standards. The AD itself is a corrective instrument tied to meeting those certification requirements.

Interplay with manufacturer materials: The AD makes the manufacturer’s Service Bulletin F2000EX‑61 the operative technical document to achieve compliance, and allows later revisions only if EASA approves them (Requirement). This creates a direct interaction between regulatory obligation and manufacturer technical guidance; the SB is elevated from manufacturer guidance to mandatory corrective action by the AD.

Coordination with EASA: The AD explicitly refers to EASA AD 2007‑0073 and requires EASA approval for later SB revisions to be used for compliance (Requirement; Note). That reference creates a cross‑jurisdictional regulatory relationship: CASA’s AD synchronises with EASA’s oversight by recognising EASA’s approval as the controlling acceptance mechanism for revised SBs.

Relationship to state airworthiness regulations: The AD is a CASA instrument (signature block) and therefore sits within Australia’s state regulatory framework for airworthiness. While the AD text does not enumerate the relevant domestic statutory provisions that give CASA authority to issue ADs, the document functions as the national instrument requiring the specific corrective action; operators must comply with it as part of maintaining airworthiness under the applicable national regulatory regime.

No conflicting or superseding provisions stated: The AD does not state whether it supersedes or is superseded by any other domestic directives. It does, however, point to the EASA AD and to Dassault’s SBs as the technical bases for action; as drafted, compliance with an EASA‑approved SB revision will satisfy the AD (Requirement; Note).

No mention of international liability or compensation law: The text does not address liability allocation between operator and manufacturer, or state indemnities. The AD imposes an operational duty to replace equipment; any disputes about cost or liability for the corrective action are not addressed within the AD text.

The text supplies a concise timeline for the SBs and the AD itself:

• SB issuance dates: Dassault Aviation Service Bulletin F2000EX‑61 dated 22 March 2006, and SB F2000EX‑61 Revision 1 dated 22 March 2007 are expressly identified as the SB versions referenced in the AD (Applicability). The AD allows later revisions but only if approved by EASA (Requirement).

• AD signature and date: The AD is signed by the Delegate of the Civil Aviation Safety Authority, Charles Lenarcic, and dated 29 March 2007 (signature block).

• AD effective date: The AD “becomes effective on 10 May 2007” (Compliance).

• Compliance deadline: Work must be completed “no later than 30 June 2008” (Compliance).

The AD text does not list prior or subsequent amendments to the AD itself. It names the two SB versions relevant at the time of issuance and contemplates future SB revisions, but only as a route to compliance if EASA approves them (Requirement). There is no later revision of the AD recorded in the provided document.

The AD also contains a cross‑reference: “Note: EASA AD 2007‑0073 refers.” This indicates contemporaneous or prior regulatory action by EASA and suggests coordination rather than an amendment history within the CASA AD text itself (Requirement; Note).

Absent from the text are any statements that this AD supersedes earlier directives or will be superseded on a particular date, and there is no listed amendment number for the AD. The document as provided is a single AD issued 29 March 2007 with the effective and compliance dates noted above.

The provided AD text contains no litigation history, case names, judicial decisions, or references to dispute resolution proceedings. It is a regulatory directive with provenance (CASA delegate signature dated 29 March 2007) and contains technical instructions, but it does not record any litigation related to the safety defect, the SB, or enforcement actions (signature block; Background; Requirement).

Because the text does not present any litigation record, readers seeking judicial interpretation, precedents about compliance obligations, or enforcement litigation must look beyond this AD to court or tribunal records, which are not part of the supplied document. The AD does, however, create a discrete regulatory obligation,replacement of mask boxes by a fixed date,such that any future litigation or administrative enforcement action would likely pivot on questions this document expressly frames: whether a given aircraft falls within the serial‑number range; whether SB F2000EX‑61 (or Revision 1) has already been implemented; whether the replacement was performed in accordance with the SB or an EASA‑approved later revision; and whether compliance occurred by the 30 June 2008 deadline (Applicability; Requirement; Compliance).

The AD does not foreclose civil claims that third parties might raise against manufacturers or operators for losses associated with the defect; the AD itself does not address product liability, contract remedies, or indemnities. The document is silent regarding dispute mechanisms, remedies, or prior litigation, and therefore provides no on‑its‑face litigation history or adjudicative interpretation to rely on for legal argument.

Narrow serial‑number applicability: The AD applies only to Falcon 2000EX aeroplanes serial numbers 28-55 inclusive (Applicability). Aircraft outside that SN range are not within the AD’s stated scope, even if they share similar equipment. Operators must verify serial numbers precisely; misidentifying an aircraft’s serial number could lead to unnecessary work or, conversely, non‑compliance.

SB implementation carve‑out: The AD exempts aircraft that have already implemented SB F2000EX‑61 (22 March 2006) or SB F2000EX‑61 Revision 1 (22 March 2007) from the replacement requirement (Applicability). Therefore, an aircraft that has had the SB work executed does not have to undergo the replacement again. The key operational gotcha here is that proof of prior SB compliance must be demonstrable in the aircraft’s maintenance records.

EASA approval gate for later SB revisions: The AD accepts later revisions of the SB only if those revisions are approved by EASA (Requirement). That means operators cannot simply follow any future manufacturer SB update; they must ensure the revision bears EASA approval before treating it as compliant under this AD. The practical consequence is a potential delay or administrative coordination when a later SB revision exists but has not yet received EASA approval.

Treatment of NORMAL vs OVERRIDE mode: The compatibility problem is mode‑specific: OVERRIDE yields nominal O2 flow while NORMAL mode yields half the required flow (Background). If operators or crew are unaware of the distinction or of any interim operational mitigations, there is a latent risk. The AD does not prescribe interim operational limitations or procedure changes; it prescribes hardware replacement. Operators should not assume an operational workaround exists unless separately promulgated by the authority or manufacturer.

Time window and scheduling pressure: The AD became effective on 10 May 2007 and set completion by 30 June 2008 (Compliance). The interval may appear long, but parts supply constraints, maintenance slot availability, or geographic considerations (aircraft outside primary service hubs) could compress effective scheduling time. Operators should not assume ample lead time without confirming parts and maintenance availability.

Documentation as proof of compliance: Because the AD mandates compliance “in accordance with SB F2000EX‑61,” the primary evidence of compliance will be maintenance records showing the SB’s steps were completed. A gotcha is failing to fully document the SB per its requirements; undocumented work may not be accepted as compliance.

Parts availability and SB‑specific parts: The AD mandates replacement with a new‑design mask box per the SB (Requirement). If the SB specifies proprietary part numbers, operators will need to obtain those parts. The AD does not address supply chain issues or alternative parts, so operators relying on non‑SB parts risk failing to meet the AD’s requirement.

No explicit interim measures: The AD does not state any interim operational restrictions, crew procedures, or mitigations to be taken pending replacement (Background; Requirement). Operators who are aware of the fault but have not yet completed replacement cannot rely on the AD for prescriptive interim measures, so they must use prudential judgment consistent with national safety rules and any separate guidance from CASA or the manufacturer.

Cross‑reference to EASA AD: The AD’s note,“EASA AD 2007‑0073 refers”,is a pointer that operators governed by EASA or operating into EASA jurisdictions should check corresponding EASA paperwork; failing to reconcile CASA and EASA requirements could cause compliance gaps for international operations (Requirement; Note).

No penalties detailed within the AD: The AD’s text does not list enforcement or penalty provisions (Penalties and enforcement). Operators must therefore be aware that enforcement comes from the broader regulatory framework and that the AD alone does not specify the enforcement route.

Step 1 , Identify affected aeroplanes: Confirm whether each airframe is a Falcon 2000EX with serial number between 28 and 55 inclusive and whether SB F2000EX‑61 (22 March 2006) or SB F2000EX‑61 Revision 1 (22 March 2007) has already been implemented. This requires a review of the aircraft’s serial‑number plate and maintenance records to verify historic SB compliance (Applicability).

Step 2 , If not already done, obtain the SB and EASA approvals: Obtain Dassault Aviation Service Bulletin F2000EX‑61 (22 March 2006) or SB F2000EX‑61 Revision 1 (22 March 2007) as applicable. If a later SB revision is to be followed, confirm that the revision is approved by EASA before proceeding, because the AD requires compliance with the SB “or later revision approved by the European Aviation Safety Agency (EASA)” (Requirement; Note).

Step 3 , Schedule the work within the AD window: The AD became effective 10 May 2007 and requires completion by 30 June 2008 (Compliance). Plan maintenance availability, parts procurement, and downtime accordingly to ensure the replacement is completed prior to the deadline.

Step 4 , Use authorised maintenance organisations and follow the SB: Execute the replacement of passenger oxygen mask boxes strictly “in accordance with SB F2000EX‑61” or the approved later revision (Requirement). The SB will contain parts lists, removal and installation procedures, inspection steps, and acceptance criteria. Ensure personnel performing the work are qualified to carry out the SB tasks and that any required associated tasks or tests specified by the SB are completed.

Step 5 , Parts and technical coordination with Dassault: Coordinate procurement of the new‑design passenger oxygen mask boxes and any SB‑specified hardware or software changes with Dassault Aviation or authorised parts suppliers. The AD names Dassault as the SB originator, so Dassault will supply the SB‑specified parts and technical information (Applicability; Requirement).

Step 6 , Documentation and record entry: After completing the SB tasks, enter the completion details in the aircraft maintenance records and logbooks in the manner required by national maintenance regulations so there is demonstrable evidence that the AD requirement has been satisfied prior to 30 June 2008 (Requirement; Compliance). Record the SB number, revision, parts used, certifying mechanic or organisation, date of completion, and any test results required by the SB.

Step 7 , Verify compliance to the regulator: While the AD does not specify a formal notification process in its text, be prepared to present the maintenance records showing SB compliance to CASA or other relevant inspectors if requested. Operators whose aircraft operate internationally should confirm whether EASA or another authority requires separate notification.

Step 8 , If a later SB revision is used, secure EASA approval evidence: If relying upon a later revision to SB F2000EX‑61, retain explicit documentation of EASA’s approval of that revision, because the AD limits acceptable alternative SBs to those that are EASA‑approved (Requirement).

Step 9 , Operational prudence pending replacement: The AD does not set interim operational measures. If replacement cannot be completed immediately, operators should consider their own risk assessments and any separate manufacturer or regulator advisories to determine whether operational restrictions, additional crew procedures, or passenger limits are necessary until the mandated replacement is carried out (Background). Any interim measures should be documented and justifiable under the operator’s safety management system.

Step 10 , Liaise with legal and insurance advisers if there are disputes: Because the AD imposes a mandatory technical duty without addressing cost allocation, operators with questions about liability for parts, time, or workmanship should consult contractual documentation (leases, purchase agreements, maintenance contracts) and, where necessary, legal counsel or insurers to clarify responsibilities.

In sum, compliance is: (1) establish airframe applicability and prior SB compliance, (2) procure and implement the SB (or an EASA‑approved later revision), (3) complete and document the work by 30 June 2008, and (4) retain the documentation that demonstrates compliance for regulatory inspection (Applicability; Requirement; Compliance).