AD/AMD 50/36 - Segregation of ADS/IRS Wiring

This AD is structured around a handful of technical and procedural concepts drawn from the aircraft avionics architecture and operator maintenance governance. The primary technical concepts in the text are:

• ADS and IRS: Air Data System (ADS) and Inertial Reference System (IRS) are distinct avionics systems that feed flight path information to cockpit displays. The AD explains that ADS and IRS inputs were not segregated in the GP Bus wiring, creating a risk that an ADS error could be propagated through the GP Bus to multiple display units.

• GP Bus and IRS primary inputs: The directive identifies the General Purpose Bus as the single conduit carrying multiple IRS primary inputs. The AD states “All IRS primary inputs are wired to the same General Purpose (GP) Bus,” and treats this wiring configuration as non‑compliant with the certified safety objectives for ADS segregation.

• Wiring segregation: The remedy is an electrical segregation change, effected by “IRS 2 wiring modification M5143.” The AD treats this as the primary mitigation to prevent a single unflagged ADS error from affecting both pilot and co‑pilot displays.

• Service Bulletin testing and EASA approval: The functional verification of the GP Bus IRS entry is to be performed “in accordance with the accomplishment instructions of Service Bulletin SB‑F900EX‑274 or later revisions approved by the European Aviation Safety Agency (EASA).” The AD thus links the physical modification to a documented test procedure and conditions the validity of later revisions on EASA approval.

• Maintenance Manual amendment and recurring test (MP 34‑209): To sustain the segregation posture over the aircraft lifecycle, the AD requires an insertion of Revision 2 of Chapter 5.40 into the Maintenance Manual to introduce a recurring functional test “test of general purpose bus IRS entry” at a 5 000 flight hour interval (MP 34‑209). That makes the recurring test part of the aircraft’s approved maintenance schedule.

• MEL/MMEL interaction: The AD requires amendment of the Minimum Equipment List to reflect revised dispatch conditions for “one IRS failure” as contained in the Dassault Aviation Master MMEL temporary change TC 3. This ties the airworthiness modification and test regime into operational dispatch rules.

The safety risk the AD documents is concrete and technical: “one single ADS unflagged air data error may lead to the computation and display on both pilot’s and co‑pilot’s display units of unnoticed and misleading flight information.” The AD identifies the operational phase of particular concern , “At take‑off or during go‑around this situation might considerably reduce flight safety.” The AD therefore combines a hardware modification, a verification test, and an update to operational dispatch criteria to address immediate and ongoing risk.

Conceptually, the AD imposes both a one‑off physical change (wiring mod) and an ongoing compliance obligation (5 000 FH test and updated MEL), and it links the acceptability of work instructions to EASA approvals and to the Dassault MMEL temporary change.

The AD explicitly identifies the affected fleet and the stakeholder roles that must act. The listed applicability is precise: “Falcon 900EX EASy S/N 97, 120 and subsequent (including S/N 601 & subsequent, also known as ‘DX’ aeroplanes).” That language captures three groups: the specific serial numbers named, later serial numbers in that production run, and a separate designation series (S/N 601 and subsequent) identified as “DX” aeroplanes. The AD thus applies to any operator, lessor, maintenance organisation, or owner whose registered or operated Falcon 900EX EASy aeroplane falls within those serial numbers.

Operationally, the AD allocates different duties depending on equipment status. Requirement 1 applies only to “aeroplanes in the applicability range and without modification M5143.” Therefore, operators that can demonstrate that their aeroplane already incorporates modification M5143 are outside that particular obligation but remain subject to Requirements 2 and 3. Requirements 2 and 3 apply to “all F900EX EASy aeroplanes in the applicability range,” so every operator of a listed aeroplane must amend the Maintenance Manual and the MEL per the AD.

The AD engages several roles and organisations:

• Aircraft operators and their technical management, who must plan and perform the wiring modification where required, schedule the SB‑based test, and insert Revision 2 of Chapter 5.40 into their Maintenance Manual, introducing MP 34‑209 at a 5 000 FH interval.

• Maintenance organisations and licensed maintenance personnel, who will perform the wiring modification M5143 and the GP Bus IRS entry tests in accordance with SB‑F900EX‑274 or later EASA‑approved revisions.

• Document custodians within operator organisations, who must amend the operator Maintenance Manual and the operator MEL to reflect the new test and dispatch conditions, using the Dassault Aviation Master MMEL temporary change TC 3 as the source for the MEL dispatch condition changes.

• Regulators and certification authorities referenced in the AD: the document cites EASA AD 2006‑0157 and requires EASA approval for later revisions of the Service Bulletin. The AD is issued by the Civil Aviation Safety Authority (signature by James Coyne, Delegate), which signals that CASA is the issuing authority for Australian-registered operators.

Financially and operationally, the AD places obligations on operators: physical modification work if M5143 is not already present; testing to SB instructions; repetitive testing at a 5 000 FH interval; and amendments to the Maintenance Manual and MEL. The compliance period is short: “At the earliest opportunity but no later than three months after the effective date of this Directive.” That timeframe affects maintenance planning and may require prioritisation of these activities by operators whose aeroplanes are within the applicability list.

The AD does not name any other classes of affected parties such as passengers, insurers, or foreign authorities; however, because the directive references EASA‑approved SB revisions and an EASA AD, operators with aircraft that move between regulatory jurisdictions will need to ensure that the documentary and technical work meet both CASA and EASA expectations.

The AD creates a set of operator duties, differentiated by aeroplane status and documented as discrete requirements. These duties and the conditions attached to them are the operative legal expectations in this text.

Duties (explicitly stated in the AD):

1. Incorporation of IRS 2 wiring modification M5143: “For F900EX EASy aeroplanes in the applicability range and without modification M5143 - Incorporate IRS 2 wiring modification M5143 and test the GP bus IRS entry in accordance with the accomplishment instructions of Service Bulletin SB‑F900EX‑274 or later revisions approved by the European Aviation Safety Agency (EASA).” The duty is conditional: it binds only aeroplanes that do not already have M5143. The duty also includes the test requirement, tying hardware change to verification.

2. Maintenance Manual amendment: “For all F900EX EASy aeroplanes in the applicability range - Amend the Falcon 900EX EASy Maintenance Manual to introduce MP 34‑209 ‘test of general purpose bus IRS entry’ at 5000 FH intervals by inserting Revision 2 of Chapter 5.40 into the manual.” This is a documentation duty that converts a recurring functional test into an approved maintenance procedure.

3. MEL amendment: “For all F900EX EASy aeroplanes in the applicability range - Amend the Minimum Equipment List (MEL) to reflect the dispatch conditions for ‘one IRS failure’ contained in the Dassault Aviation Master Minimum Equipment List temporary change TC 3.” This duty alters operational dispatch rules by requiring MEL alignment with Dassault’s temporary MMEL change.

Compliance timing is explicit: “For Requirements 1, 2 and 3 - At the earliest opportunity but no later than three months after the effective date of this Directive.” The effective date is stated as 3 August 2006.

Rights and conditionalities implicit in the AD:

• Conditional applicability for Requirement 1: Operators who can demonstrate incorporation of M5143 are not obliged to re‑perform that wiring modification. The AD therefore recognises prior compliance as a right to exemption from the specific hardware change requirement, while still binding them to the recurring test and MEL amendment obligations.

• Use of later SB revisions is permitted only if EASA‑approved: the AD allows testing “in accordance with the accomplishment instructions of Service Bulletin SB‑F900EX‑274 or later revisions approved by the European Aviation Safety Agency (EASA).” That grants operators the right to rely on updated SB revisions, but only if they carry EASA approval.

• The AD cross‑references the Dassault Master MMEL temporary change TC 3 as the source of dispatch condition text to be adopted in the operator MEL. Operators have the right to use that temporary change as the authoritative text for amendment of their MELs.

The AD does not articulate an appeals process, discretionary waivers, or alternative means of compliance within its text. It does not specify recordkeeping formalities for showing compliance nor does it set out an inspector’s approval step. It does not itself define penalties or enforcement mechanisms. The AD therefore imposes affirmative duties, conditional exemptions for prior modification, and constrained rights to use later EASA‑approved SB revisions and the Dassault MMEL temporary change as the operative textual sources.

The text of the AD does not specify civil or criminal penalties, administrative fines, or the procedural steps for enforcement or escalation. The document sets out mandatory technical and documentary requirements, an effective date (3 August 2006), and a compliance timeframe (no later than three months after the effective date), but it does not include an express enforcement clause, penalty schedule or reference to civil aviation statutory sections that would prescribe sanctions for non‑compliance.

What the AD does specify and thereby creates an expectation of enforceable compliance are: concrete obligations tied to particular aeroplanes in a clear applicability list; specific technical standards and documents to be used (M5143, SB‑F900EX‑274 EASA‑approved revisions, Revision 2 of Chapter 5.40 of the Maintenance Manual, Dassault MMEL temporary change TC 3); and a discrete compliance deadline. In practice those elements are the basis on which a regulator or inspector would evaluate compliance, but the AD text itself does not elaborate that enforcement pathway.

The absence of stated penalties in the AD text means the directive relies on the issuing authority’s broader regulatory framework and enforcement powers, which are not included in this document. The AD is signed by a CASA delegate (James Coyne, 22 June 2006), indicating it is an authoritative AD issued under CASA processes, but the AD text does not reproduce or cross‑reference the enabling regulatory provisions, enforcement mechanisms, or inspection/remedial procedures.

Because the directive introduces changes to the Maintenance Manual and the MEL , documents that under standard airworthiness and operational oversight regimes are subject to regulator review and acceptance , operators should expect that regulatory oversight will verify execution of the AD’s requirements. The AD itself, however, contains no procedural instructions about monitoring, certification of compliance, or administrative penalties for non‑performance. The AD also does not state any follow‑up reporting obligations or documentation form to be provided to the regulator.

In short, the AD sets binding technical and documentary obligations with a firm deadline, but it does not include explicit penalty or enforcement provisions within the text. Any enforcement, monitoring or sanctions would therefore derive from the regulator’s general airworthiness and safety enforcement powers and processes, which are outside the explicit text of this AD.

Within the body of this AD the only external references to other regulatory instruments are to EASA AD 2006‑0157 and to procedural and documentary materials produced by Dassault Aviation. The AD states “Note: EASA AD 2006‑0157 refers,” and it conditions the acceptability of later revisions of the service bulletin on EASA approval: “or later revisions approved by the European Aviation Safety Agency (EASA).” The AD also requires MEL amendments “to reflect the dispatch conditions for ‘one IRS failure’ contained in the Dassault Aviation Master Minimum Equipment List temporary change TC 3.” Those are the only explicit cross‑references found in the document.

Operationally and administratively, the AD interacts with two kinds of operator documents that are typically governed by broader aviation rules:

• Maintenance Manual (MM): The AD requires insertion of Revision 2 of Chapter 5.40 and the introduction of MP 34‑209 at a 5 000 FH interval. Maintenance Manuals are operator‑held documents that set out the approved maintenance programme. The AD therefore creates a requirement to amend the operator’s MM, which will interact with any statutory or regulatory obligations operators have to keep their maintenance documentation current and to obtain necessary approvals for MM amendments. The AD does not itself cite those statutory approval processes, only the MM change to be made.

• Minimum Equipment List (MEL): The AD requires that an operator’s MEL be amended to reflect dispatch conditions for “one IRS failure” consistent with the Dassault Master MMEL temporary change TC 3. MELs are operational documents tied to national and international rules about dispatch with inoperative equipment. The AD requires MEL amendment but does not restate the national regulatory provisions that govern MEL approval or dispatch acceptance. The AD alters the content operators must adopt within their MELs, thereby interacting with the operator’s obligations under the broader MEL/MMEL approval framework.

The AD’s requirement that Service Bulletin SB‑F900EX‑274 or later revisions must be “approved by the European Aviation Safety Agency (EASA)” links the domestic AD to EASA’s certification and approval processes. That creates a dependence on EASA action for the acceptability of later SB revisions, and it cross‑references EASA AD 2006‑0157 as relevant. The AD does not otherwise reference other domestic statutes, regulations, or civil aviation instruments.

Because the AD is signed by a CASA delegate, it sits within CASA’s administrative framework and will be implemented under CASA’s domestic regulatory oversight, but the AD itself does not reproduce CASA’s enabling or enforcement provisions. The AD therefore creates obligations that must be implemented by operators, while relying for test procedure approvals and some content authority upon EASA and upon Dassault Aviation documentation. Any interaction with other laws beyond those referenced in the AD would depend on general regulatory practice rather than on provisions contained in this document.

The document provided contains the AD as issued on 22 June 2006 with an effective date of 3 August 2006. It sets out three requirements and the compliance timeline. The AD text itself does not include any record of earlier or later amendments to this particular Directive. The only document revision language in the AD relates to operator documents that must be amended: the insertion of “Revision 2 of Chapter 5.40” into the Maintenance Manual, and the use of Dassault Aviation Master MMEL temporary change TC 3 for MEL amendment. Those references are to revisions of operator materials or manufacturer guidance rather than to amendments of the AD itself.

Specifically:

• The AD orders operators to “insert Revision 2 of Chapter 5.40 into the manual.” That is an instruction about the operator’s Maintenance Manual revision content, not a revision history entry for the AD. The AD does not indicate whether earlier revisions of the AD exist.

• The AD allows the test to be accomplished “in accordance with the accomplishment instructions of Service Bulletin SB‑F900EX‑274 or later revisions approved by the European Aviation Safety Agency (EASA).” This references potential future revisions to the Service Bulletin that would be acceptable if EASA approves them. It does not itself amend the AD.

• The AD contains a parenthetical: “Note: EASA AD 2006‑0157 refers.” That is a cross‑reference to an EASA AD but is not in itself an amendment note.

No successive or superseding ADs, no corrigenda, and no revocations are shown or noted in the provided text. If later changes to the AD had been made by CASA, those changes are not recorded in the text provided here. The AD as presented is therefore the single version in force as of the effective date included in the document.

For operators and maintainers, the relevant “revision history” items they must adopt are the Maintenance Manual Revision 2 insertion and any EASA‑approved later revisions of Service Bulletin SB‑F900EX‑274. The AD does not list any later amending instruments, nor does it contain a history log of amendments to the AD itself.

The AD document does not record any litigation history. It contains no mention of judicial or administrative appeals, no references to contested orders, and no recounting of legal proceedings arising from issuance of the Directive. The text is limited to the technical requirements, the safety background and the compliance timetable.

Because the AD does not include any litigation references, nothing in the provided text indicates whether the measure was litigated, challenged, stayed, or otherwise subjected to judicial or administrative review. The signatory is recorded as James Coyne, Delegate of CASA, and the date is 22 June 2006, but the AD does not supply post‑issue procedural or dispute information.

Accordingly, based solely on this document, there is no litigation history to report. Any litigation involving this AD, whether arising in Australia or elsewhere, would need to be sourced from external records or case reports not contained in the AD text provided.

The AD contains a number of features and technical cross‑references that may create practical pitfalls for operators, maintainers and document custodians. The following are source‑grounded implementation risks and areas where operators should exercise care.

Applicability nuance and serial number scope:

• The applicability language is specific but layered: “Falcon 900EX EASy S/N 97, 120 and subsequent (including S/N 601 & subsequent, also known as ‘DX’ aeroplanes).” Operators must parse that text correctly to determine whether a particular airframe is in scope. The phrase “and subsequent” and the parenthetical including S/N 601 & subsequent mean that later production aeroplanes in the specified series are included. Misreading this could lead to failure to act on aircraft within scope.

Conditional Requirement 1:

• Requirement 1 applies only to aeroplanes “without modification M5143.” Operators must be able to demonstrate the modification status of IRS 2 wiring for each aeroplane. Inadequate records of historic modifications create risk: if an operator cannot show the aeroplane already incorporates M5143, the obligation to perform the wiring change and the GP Bus test will apply. Accurate review of maintenance records is therefore essential.

Dependence on EASA approval:

• The AD permits tests to follow “SB‑F900EX‑274 or later revisions approved by the European Aviation Safety Agency (EASA).” If an operator elects to use an updated SB, the AD conditions the acceptability of that later revision on EASA approval. Failure to verify that a later SB revision is indeed EASA‑approved could result in non‑compliant testing.

Documentation exactness:

• The AD requires insertion of “Revision 2 of Chapter 5.40” into the Maintenance Manual and the introduction of MP 34‑209 at 5 000 FH intervals. Operators must ensure the exact revision number and test text are used; ad hoc or trimmed entries could fail to satisfy the AD. Similarly, MEL updates must reflect the Dassault Master MMEL temporary change TC 3 for “one IRS failure.” Using an incorrect temporary change version or an unofficial adaptation risks non‑conformance.

Short compliance window:

• The compliance window is compressed: “At the earliest opportunity but no later than three months after the effective date of this Directive.” For an AD effective 3 August 2006, this is a tight window for planning wiring modifications, arranging maintenance slots, obtaining parts and approvals, performing tests, and updating MM and MEL documentation. Operators with limited maintenance capacity should prioritise affected aeroplanes to meet the deadline.

Operational dispatch implications:

• The AD’s background highlights that unflagged ADS errors could lead to identical incorrect displays on both pilot and co‑pilot PDUs, especially hazardous in take‑off or go‑around phases. Until the wiring mod and test are completed and the MEL updated, operators may face constrained dispatch options if an IRS or ADS anomaly occurs. The AD also notes that “Dispatch conditions under MMEL in case of an IRS2 failure are modified after implementation of the wiring change.” Operators should therefore expect changed dispatch rules post‑modification and ensure flight crew are briefed.

Record keeping and evidence:

• Because Requirement 1 is conditional on prior incorporation of M5143, and because the AD does not specify the form of compliance evidence, operators must maintain clear records showing either the prior existence of M5143 or the performance and completion of the wiring modification and the GP Bus test per SB. The AD does not prescribe a reporting form or submission process.

Interface with MEL approval processes:

• The AD requires MEL amendment to reflect Dassault’s temporary change TC 3, but it does not describe the MEL approval pathway. Operators should be careful to follow their regulatory MEL amendment processes when implementing the required change.

No stated penalties or enforcement steps:

• The AD does not specify enforcement mechanisms or penalties. That absence does not mean that regulators will not enforce the AD; it does mean operators must look to their regulator’s general enforcement framework. The lack of explicit enforcement steps in the AD could create uncertainty for operators about how compliance will be verified and by whom.

In sum, the main practical “gotchas” are correct determination of applicability and modification status, ensuring the Service Bulletin revision used is EASA‑approved, meeting the three month deadline, precise insertion of the Maintenance Manual revision and MP 34‑209 interval, correctly updating the MEL per Dassault TC 3, and maintaining unambiguous evidence of compliance.

The AD sets out three concrete actions and a compliance timetable. The following step‑by‑step compliance checklist reproduces and organises the AD’s requirements as actionable items, using only the authority and wording present in the AD text.

1. Determine applicability and modification status:

   • For each Falcon 900EX EASy aeroplane in your fleet, confirm whether the aeroplane is within the applicability list: “Falcon 900EX EASy S/N 97, 120 and subsequent (including S/N 601 & subsequent, also known as ‘DX’ aeroplanes).”
   • For aeroplanes in that scope, establish whether IRS 2 wiring modification M5143 is already incorporated. This determines whether Requirement 1 applies.

2. Wiring modification and functional test (Requirement 1):

   • For aeroplanes in the applicability range that do not already have M5143, schedule and carry out incorporation of “IRS 2 wiring modification M5143.”
   • After incorporation, test the GP Bus IRS entry “in accordance with the accomplishment instructions of Service Bulletin SB‑F900EX‑274 or later revisions approved by the European Aviation Safety Agency (EASA).” Ensure the Service Bulletin revision used has EASA approval where applicable.
   • Record the modification and the completion of the SB‑based test in the aircraft maintenance records, noting the SB revision and any EASA approval references.

3. Maintenance Manual amendment and MP 34‑209 insertion (Requirement 2):

   • For all aeroplanes in the applicability range, implement the Maintenance Manual amendment required by the AD. Insert “Revision 2 of Chapter 5.40” into the Falcon 900EX EASy Maintenance Manual.
   • Confirm that the insertion introduces MP 34‑209 described as “test of general purpose bus IRS entry” and that the MP is to be performed “at 5000 FH intervals.”
   • Update maintenance planning and scheduling systems to include MP 34‑209 at the 5 000 flight hour recurrence. Ensure maintenance personnel are trained on the MP procedure and that the MP references the appropriate Service Bulletin or test instructions mandated by the AD.

4. MEL amendment (Requirement 3):

   • Amend the operator’s Minimum Equipment List to reflect the dispatch conditions for “one IRS failure” as contained in the Dassault Aviation Master MMEL temporary change TC 3.
   • Align the MEL text exactly with Dassault’s temporary change TC 3 language where the AD requires it, and follow the operator’s standard MEL approval process to implement the change.
   • Brief flight crews and dispatchers on the revised dispatch conditions for ‘one IRS failure’ and any interim operational restrictions that apply prior to modification completion.

5. Timing and scheduling:

   • Perform Requirements 1-3 “At the earliest opportunity but no later than three months after the effective date of this Directive.” The AD effective date is 3 August 2006. Plan maintenance windows, parts procurement, and document amendments to meet this deadline.
   • Prioritise aircraft that are commercially active or scheduled for near‑term missions, given the AD’s safety rationale citing take‑off and go‑around phases.

6. Documentation and evidence:

   • Maintain explicit records of (a) the aircraft serial number and applicability determination; (b) whether M5143 was present prior to the AD and documentation proving that; (c) the wiring modification work order and certification for M5143 where performed; (d) the GP Bus IRS entry test report, including the Service Bulletin revision used and any EASA approval reference; (e) copies of the amended Maintenance Manual with Revision 2 of Chapter 5.40 inserted and the added MP 34‑209; and (f) the amended MEL showing Dassault TC 3 content and the MEL approval record.
   • Because Requirement 1 is conditional on prior incorporation of M5143, include documentary evidence in maintenance records to substantiate the aircraft’s modification status.

7. Coordination and approvals:

   • If you intend to use a later revision of SB‑F900EX‑274, confirm EASA approval of that later revision before proceeding with the test, as the AD conditions acceptability on EASA approval.
   • When amending the MEL per Dassault TC 3, follow any required operator MEL submission and approval processes with your regulator.

8. Operations during compliance window:

   • Until the wiring modification and required MEL changes are in place, assess dispatch risk if an IRS or ADS anomaly occurs, noting the AD’s background observation that an unflagged ADS error “may lead to the computation and display on both pilot’s and co‑pilot’s display units of unnoticed and misleading flight information,” particularly at take‑off or during go‑around.
   • Implement interim operational mitigations consistent with the operator’s safety management system while final compliance measures are accomplished.

9. Ongoing compliance:

   • After insertion of MP 34‑209 into the Maintenance Manual, incorporate the 5 000 FH recurring test into standard maintenance cycles and ensure test results are recorded and reviewed.
   • Ensure that MELs remain aligned with Dassault MMEL updates and any regulatory guidance that supersedes the temporary change TC 3.

This compliance plan follows the AD’s three numbered requirements and the prescribed compliance deadline verbatim. The AD does not require additional reporting within the text, nor does it specify forms or a submission process for compliance evidence; operators should therefore retain the records listed above and be prepared to present them to the regulator upon request.