{"id":"F2006L00234","name":"AD/F2000/1 - Braking Function Anomalies","slug":"ad-f2000-1-braking-function-anomalies","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":58191,"registerId":"commonwealth-F2006L00234-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/1 | Braking Function Anomalies | 3/2006 TX |\n| ---------- | -------------------------- | --------- |\n\n| Applicability: | Falcon 2000EX aircraft with M1691 (EASy Aircraft) which have not incorporated Service Bulletin SB-F2000EX-80 (or modification M2675). |\n| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Requirement: | 1. Unless previously accomplished, add temporary change TC 17 to the AFM performance section (This can be achieved by inserting a copy of this AD in the AFM performance section).Adjacent to page 5-150-2: Take off Field length limitsField length determined from balanced field length charts has to be increased by 27%. Conversely, the field length limited take-off weight is reached when the field length determined from the charts is equal to the field length available multiplied by 0.78.Maximum take-off weight on wet runway must never be higher than maximum take-off weight on the same runway in dry conditions. Then in case of take-off weight limited by balanced field length on wet runway, this weight has to be compared to the maximum take-off weight on dry runway.Adjacent to page 5-150-3: Landing Field length limitLanding distance or landing field length as determined from the chart has to be increased by 25%. Conversely, the field length limited landing weight is reached when the field length or the landing distance, as required by operating regulations is equal to the runway length actually available multiplied by 0.80.The landing weight normally anticipated at the destination or alternate airport must not be greater than the maximum landing weight.2. Incorporate SB F2000EX-80 and cancel the TC-17 from the AFM.The incorporation of the SB F2000EX-80 is the terminating action for this AD which allows removal of the runway length penalties for take-off and landing from requirement 1.Note: DGAC AD UF-2005-140 EASA approval No. 2005-61 10 dated 26 July 2005 refers. |\n\n| Compliance: | 1. Before the next flight following the effective date of this AD.2. Before 31 December 2006. |\n| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| | This Airworthiness Directive becomes effective on 31 January 2006. |\n| Background: | Two types of events have been observed in service:Temporary loss of braking efficiency at landing which was recovered after fully releasing the brakes and reapplying braking force.Display shortly after take off of a red “BOTH BRAKE SYSTEM” CAS message associated with “BRAKE COMPTR#1 FAULT CODE” and “BRAKE COMPTR#2 FAULT CODE” CAS message.Both types of events have been linked to incorrect data being transmitted between the IRS and the Brake System Control Unit. This results in a failure of the BSCU to provide accurate use of the anti skid system and a reduction in braking efficiency.Loss of efficiency in braking may jeopardize the certificated take off and landing performances.This AD proposes to add runway length penalties at take off and landing to the AFM of the affected aircraft until a wiring modification is incorporated to directly link the IRS to the BSCU. |\n\n![](image.001.png) \nJames Coyne \nDelegate of the Civil Aviation Safety Authority\n\n24 January 2006","sortOrder":0},{"sectionNumber":"AD/F2000/1","sectionType":"part","heading":"AD/F2000/1","content":"## AD/F2000/1","sortOrder":1},{"sectionNumber":"Braking Function Anomalies","sectionType":"part","heading":"Braking Function Anomalies","content":"## Braking Function Anomalies","sortOrder":2},{"sectionNumber":"3/2006 TX","sectionType":"part","heading":"3/2006 TX","content":"## 3/2006 TX","sortOrder":3}],"analysis":{"kimi_summary":{"content_quality":"ok","complexity_score":3,"scope_assessment":{"changed":false,"description":"This AD maintains its original narrow scope — addressing a specific braking system anomaly in a specific aircraft variant. The temporary runway penalties and permanent wiring fix align precisely with the identified safety risk. No scope creep is evident."},"complexity_factors":["Single, specific technical issue with clear mechanical cause","Only two compliance actions required (temporary manual amendment + permanent modification)","Well-defined applicability criteria (specific aircraft model, specific avionics system, specific modification status)","Minimal cross-referencing (only one external reference to French DGAC and EASA approvals)","Straightforward conditional logic: if aircraft has X and not Y, then do Z","No nested exceptions or complex definitional sections","Technical but not legally convoluted — primarily operational/technical instructions rather than dense regulatory prose"],"plain_english_summary":"This AD mandates immediate, temporary AFM changes and a mandatory wiring modification for Dassault Falcon 2000EX jets with the EASy avionics after faulty IRS-to-BSCU data can degrade anti‑skid braking. Affected owners/operators and pilots must use specified runway distance penalties for wet takeoffs/landings until the permanent SB‑F2000EX‑80 fix is installed. The fix deadline was 31 Dec 2006; the AD became mandatory 31 Jan 2006 to prevent runway overruns and loss of life."},"flash_summary_failed":{"failed":true,"reason":"A positive credit balance is required for all requests, including BYOK, so fallback providers remain available. Add credits at https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%3Fmodal%3Dtop-up to continue.","source":"analysis-cron"},"flash_summary":{"complexity_score":5,"scope_assessment":{"changed":false,"description":"The AD confines measures to affected Falcon 2000EX (M1691 EASy) aircraft and prescribes temporary AFM runway-length penalties until the specified wiring modification/service bulletin is incorporated. It implements a corrective, time-limited operational restriction and a defined terminating action; it does not broaden applicability or add unrelated mandates (see Applicability; Requirement)."},"complexity_factors":["Technical root cause: avionics data link between IRS and Brake System Control Unit (BSCU) causing intermittent loss of braking efficiency (Background).","Operational performance adjustments: fixed percentage runway-length penalties (take-off +27%, landing +25%) require recalculating weights and dispatch decisions (Requirement 1).","Immediate compliance timeline: AFM change required before the next flight after effective date, creating urgent operational and administrative burden (Compliance).","Terminating action requires incorporation of Service Bulletin SB-F2000EX-80 (or mod M2675), involving wiring modification work and downtime (Requirement 2).","Narrow applicability: only Falcon 2000EX with M1691 (EASy) that haven't already incorporated the SB/mod, requiring operator record checks (Applicability).","Regulatory cross-reference: references DGAC/EASA approval, adding coordination/validation complexity for international operators (Note).","Two-step regulatory mechanic: temporary AFM penalties plus later hardware modification — creates transitional compliance management (Requirement 1–2).","Safety-critical impact on dispatch: changes affect certified take-off/landing performance and thus commercial payload/route choices (Background; Requirement)."],"plain_english_summary":"This AD requires operators of `Falcon 2000EX` aircraft with M1691 (EASy) that have not incorporated `SB-F2000EX-80` (or mod M2675) to insert temporary change TC‑17 into the Aircraft Flight Manual: increase balanced-field take-off distances by 27% and landing distances by 25% until the wiring modification in the service bulletin is installed (Requirement 1–2; Compliance). It responds to incorrect IRS→BSCU data that can reduce braking efficiency and trigger brake-fault messages; operators bear compliance costs, possible payload/runway limits and short-notice operational constraints (Background; Requirement; Compliance)."}},"importantCases":[],"_links":{"self":"/api/acts/ad-f2000-1-braking-function-anomalies","history":"/api/acts/ad-f2000-1-braking-function-anomalies/history","analysis":"/api/acts/ad-f2000-1-braking-function-anomalies/analysis","conflicts":"/api/acts/ad-f2000-1-braking-function-anomalies/conflicts","importantCases":"/api/acts/ad-f2000-1-braking-function-anomalies/important-cases","documents":"/api/acts/ad-f2000-1-braking-function-anomalies/documents"}}