{"id":"F2007L00512","name":"AD/F2000/24 - Software Integrity Check and Enhanced Avionics System Upgrade","slug":"ad-f2000-24-software-integrity-check-and-enhanced-avionics-system-upgrade","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":63762,"registerId":"commonwealth-F2007L00512-current","compilationNumber":null,"startDate":"2026-04-02","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"Dassault Aviation Falcon 2000 Series Aer","sectionType":"division","heading":"Dassault Aviation Falcon 2000 Series Aeroplanes","content":"### Dassault Aviation Falcon 2000 Series Aeroplanes\n\n| AD/F2000/24 | Software Integrity Check and Enhanced Avionics System Upgrade | 4/2007 DM |\n| ----------- | ------------------------------------------------------------- | --------- |\n\n| Applicability: | Falcon 2000EX aeroplanes, serial numbers 06, 28 to 86 inclusive, and 88; without Dassault Aviation Falcon Service Bulletin (SB) F2000EX-100 dated 30 August 2006 or later Revision approved by the European Aviation Safety Agency (EASA) implemented (ie still in EASy Step 2 configuration). |\n| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Requirement:   | 1. Perform a software check using a dedicated software tool named “Flash Integrity Check” (FLICK) in accordance with the accomplishment instructions of Dassault Aviation Falcon SB F2000EX-120 dated 7 September 2006 or later Revision approved by the EASA.                                 |\n|                | 2. Make a temporary amendment to Chapter 5-40 of the Aircraft Maintenance Manual (AMM) to indicate that the MP 45-403 \"Software modules integrity check\" is to be accomplished at 40 day intervals.                                                                                            |\n|                | Note 1: To record the temporary inspection schedule, a copy of this Directive may be included in of the AMM as a temporary change.                                                                                                                                                             |\n|                | 3. Modify the aircraft in accordance with the accomplishment instructions of SB F2000EX-100 (modification M2656) or later Revision approved by the EASA.                                                                                                                                       |\n|                | This is considered to be a terminating action for the temporary repetitive inspection requirements introduced by the Requirement 2 AMM amendment and the temporary amendment to the AMM may be removed.                                                                                        |\n|                | 4. For aircraft with advanced graphics module (AGM) and enhanced ground proximity warning module (EGPWM) modules with a part number (P/N) prior to 7026545-1904 (AGM) and 7028419-1904 (EGPWM), perform a check with the FLICK tool in accordance with the AMM MP 45-401.                      |\n|                | Note 2: EASA AD 2007-0032 refers.                                                                                                                                                                                                                                                              |\n| Compliance:    | For Requirement 1and 2 - No later than 40 days after the effective date of this Directive.                                                                                                                                                                                                     |\n|                | For Requirement 3- Within 12 months after the effective date of this Directive.                                                                                                                                                                                                                |\n|                | For Requirement 4 - After each operational software loading.                                                                                                                                                                                                                                   |\n\n|             | This Airworthiness Directive becomes effective on 28 February 2007.                                                                                                                                                                                                                                                                                              |\n| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Background: | EASA has advised that during an internal review, it was discovered that some software integrity checks were not fully implemented in modules of the Honeywell EPIC avionics, as used in Falcon EASy aircraft.                                                                                                                                                    |\n|             | Consequently, the continuing integrity of the modules’ software cannot be demonstrated, as required by software requirements. Software corruption may then potentially occur during any upload of the operational software and also as random effects under normal conditions.                                                                                   |\n|             | This Directive mandates the use of the FLICK tool on a regular basis pending a software correction. The software load implementing the terminating actions also include a software correction for the untimely inhibition of the \"flap asymmetry” detection below 200ft. This is mandated to correct a situation that may not conform to EASA CS 25.671 (c) (1). |\n\n![](image.001.png)  \nDavid Punshon  \nDelegate of the Civil Aviation Safety Authority\n\n23 February 2007","sortOrder":0},{"sectionNumber":"AD/F2000/24","sectionType":"part","heading":"AD/F2000/24","content":"## AD/F2000/24","sortOrder":1},{"sectionNumber":"Software Integrity Check and Enhanced Av","sectionType":"part","heading":"Software Integrity Check and Enhanced Avionics System Upgrade","content":"## Software Integrity Check and Enhanced Avionics System Upgrade","sortOrder":2},{"sectionNumber":"4/2007 DM","sectionType":"part","heading":"4/2007 DM","content":"## 4/2007 DM","sortOrder":3}],"analysis":{"flash_summary":{"complexity_score":3,"scope_assessment":{"changed":false,"description":"This AD remains within the original, narrow safety-focused purpose: to detect and mitigate software integrity weaknesses in specific Honeywell EPIC avionics on Falcon 2000EX aeroplanes pending a software correction, and to mandate the corrective SB that terminates the interim checks. The measures (temporary recurring checks plus a terminating modification) are standard regulatory responses to a discovered avionics software deficiency and do not expand the AD beyond that remedial scope."},"complexity_factors":["Single-aircraft type and narrow serial-number applicability (serials 06, 28–86, 88)","Four numbered substantive requirements (software check, AMM temporary amendment, terminating SB modification, targeted AGM/EGPWM check)","Three distinct compliance timeframes (40 days; 12 months; after each software loading)","References to external documents: two Dassault Service Bulletins (F2000EX-120 and F2000EX-100) and EASA AD 2007-0032","Conditional clause that the SB modification is a terminating action for the temporary inspection requirement","One equipment-specific conditional (AGM and EGPWM part-number thresholds) adding per-software-load checks"],"plain_english_summary":"**What this directive does and who it affects**\n\n- This Airworthiness Directive (AD) applies to Dassault Falcon 2000EX aeroplanes with serial numbers 06, 28–86 and 88 that have not had Dassault Service Bulletin (SB) F2000EX-100 (30 Aug 2006 or later EASA-approved revision) installed — i.e. aircraft still at EASy Step 2 configuration. (Applicability)\n\n- It requires operators to run a dedicated software integrity check tool called \"Flash Integrity Check\" (FLICK) and to temporarily add a recurring inspection item to the Aircraft Maintenance Manual (AMM). Those interim measures stay in place until the aircraft are modified by installing the SB F2000EX-100 upgrade. (Requirement 1–3)\n\n- For aircraft with older part-numbered advanced graphics modules (AGM) or enhanced ground proximity warning modules (EGPWM), it requires a further FLICK check after each operational software load. (Requirement 4)\n\n- Deadlines: the software check and AMM temporary amendment must be done within 40 days of the AD becoming effective; the SB modification that removes the temporary inspection requirement must be done within 12 months. The special AGM/EGPWM check is required after every software loading. (Compliance)\n\n**Why the regulator required this**\n\n- The European Aviation Safety Agency (EASA) found during an internal review that some Honeywell EPIC avionics modules installed on Falcon EASy aircraft did not have fully implemented software integrity checks. The regulator is concerned that this could permit software corruption during uploads or randomly in service, and that at least one software issue may affect compliance with certification standard CS 25.671(c)(1) (flap asymmetry detection below 200 ft). (Background)\n\n**How it works mechanically**\n\n- Short-term (interim) action: Operators must use the FLICK tool to validate software integrity and add MP 45-403 \"Software modules integrity check\" to Chapter 5-40 of the AMM as a 40-day recurring task. A copy of the AD may be inserted into the AMM as the temporary change. (Requirement 1–2)\n\n- Long-term (terminating) action: Install SB F2000EX-100 (modification M2656) within 12 months. Once that SB is installed, the temporary 40-day inspection requirement may be removed — the SB is the terminating action for the interim checks. (Requirement 3)\n\n- Targeted extra checks: If the AGM or EGPWM have part numbers prior to 7026545-1904 (AGM) or 7028419-1904 (EGPWM), perform FLICK checks according to AMM MP 45-401 each time operational software is loaded. (Requirement 4)\n\n**Who pays and what changes for operators and maintainers**\n\n- Aircraft operators and their maintenance organisations bear the direct costs: running FLICK, recording the temporary AMM amendment, and scheduling the 40-day checks (labour, possible aircraft downtime). (Requirement 1–2, Compliance)\n\n- Installing SB F2000EX-100 within 12 months will incur the modification cost and any associated downtime; once done, the repeat inspection burden ends. (Requirement 3)\n\n- For affected AGM/EGPWM part numbers there is an ongoing cost whenever software is reloaded. (Requirement 4)\n\n**Incentives, trade-offs and implementation risks**\n\n- The AD raises the marginal cost of operating affected aircraft until the terminating SB is fitted (recurrent inspection effort vs one-off modification). Operators must decide whether to absorb repeated 40‑day inspections or prioritise scheduling the SB modification within 12 months. (Requirement 2–3)\n\n- The FLICK tool is a dedicated (proprietary) check method specified by the manufacturer/AMM. That concentrates the technical method of compliance on a particular tool and on maintenance organisations authorised to use it; this can increase demand for Dassault-authorised or EASA‑approved service providers. (Requirement 1, Requirement 4)\n\n- The AD trades short-term inspection burden for increased assurance of software integrity, with the SB modification intended to remove the need for continued repetitive checks. If operators delay the terminating action, cumulative inspection costs grow. (Requirement 2–3)\n\n- Implementation risk: if operators fail to run FLICK correctly or do not follow the AMM amendment, software corruption may remain undetected. The AD mitigates that by specifying the tool and AMM references and by setting firm compliance windows. (Requirement 1–2, Compliance)\n\n**Concentrated benefits and diffuse costs**\n\n- The principal safety benefit accrues to each aircraft operator that avoids software corruption and to crews/passengers via reduced failure risk. The maintenance work (benefit to businesses) is concentrated: authorised MROs and the manufacturer are likely to capture most modification and tooling work since the AD references specific SBs and AMM procedures. (Requirement 1–4)\n\n**Administrative notes**\n\n- The AD cites EASA AD 2007-0032 and EASA‑approved SB revisions; compliance must follow EASA‑approved revisions of the SBs and AMM instructions. (Note 2, Requirement references)\n\n- The AD became effective on 28 February 2007.\n\n(References in parentheses indicate where the requirement appears in the AD: Applicability; Requirement 1–4; Compliance; Background.)"},"flash_summary_failed":{"failed":true,"reason":"Unauthenticated. Configure AI_GATEWAY_API_KEY or use a provider module. Learn more: https://ai-sdk.dev/unauthenticated-ai-gateway","source":"analysis-cron"},"kimi_summary":{"content_quality":"ok","complexity_score":4,"scope_assessment":{"changed":false,"description":"This is a standard Airworthiness Directive with a focused, specific scope. It addresses a discrete safety issue (software integrity in specific avionics modules) for a defined aircraft population. The requirements remain tightly bounded to the original safety concern identified by EASA."},"complexity_factors":["Multiple conditional applicability criteria (specific serial numbers, specific configuration status, specific part numbers for Requirement 4)","Interdependent requirements where Requirement 3 terminates Requirement 2, creating a temporal dependency","Cross-reference to external documents (EASA AD 2007-0032, Dassault Service Bulletins with specific dates and revision protocols)","Technical aviation terminology requiring domain knowledge (EASy Step 2, EPIC avionics, AGM, EGPWM, FLICK tool, AMM Chapter 5-40)","Mixed compliance timelines (40 days, 12 months, and recurring 'after each operational software loading')","Nested conditions in Requirement 4 (only applies to aircraft with specific modules AND specific part numbers)"],"plain_english_summary":"This AD orders owners/operators of certain Dassault Falcon 2000EX jets (specific serial numbers on EASy Step 2) to address a software‑integrity risk: perform an immediate FLICK diagnostic and repeat it every 40 days until a mandated hardware/software Service Bulletin upgrade is installed within 12 months, after which checks can stop. The rule stems from findings that improper integrity verification can let critical flight software become corrupted, risking system malfunctions during flight or landing."}},"importantCases":[],"_links":{"self":"/api/acts/ad-f2000-24-software-integrity-check-and-enhanced-avionics-system-upgrade","history":"/api/acts/ad-f2000-24-software-integrity-check-and-enhanced-avionics-system-upgrade/history","analysis":"/api/acts/ad-f2000-24-software-integrity-check-and-enhanced-avionics-system-upgrade/analysis","conflicts":"/api/acts/ad-f2000-24-software-integrity-check-and-enhanced-avionics-system-upgrade/conflicts","importantCases":"/api/acts/ad-f2000-24-software-integrity-check-and-enhanced-avionics-system-upgrade/important-cases","documents":"/api/acts/ad-f2000-24-software-integrity-check-and-enhanced-avionics-system-upgrade/documents"}}