{"id":"F2009L01555","name":"AD/ERJ-170/22 - FADEC Software","slug":"ad-erj-170-22-fadec-software","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":78260,"registerId":"commonwealth-F2009L01555-current","compilationNumber":null,"startDate":"2026-04-02","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"Embraer ERJ-170 Series Aeroplanes","sectionType":"division","heading":"Embraer ERJ-170 Series Aeroplanes","content":"### Embraer ERJ-170 Series Aeroplanes\n\n| AD/ERJ-170/22 | FADEC Software | 5/2009 |\n| ------------- | -------------- | ------ |\n\n| Applicability: | Model ERJ 170-100 STD, ERJ 170-100 LR, ERJ 170-100 SU, ERJ 170-100 SE,ERJ 170-200 STD, ERJ 170-200 LR and ERJ 170-200 SU aeroplanes.                                                                                                                                                                                                                                                                                                                                                                             |\n| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Requirement:   | Replace the current engines full authority digital engine control (FADEC) software version by the new version V5.41 or any further FADEC software version approved by the Brazilian Agência Nacional de Aviação Civil (ANAC).                                                                                                                                                                                                                                                                                    |\n|                | The detailed instructions and procedures to accomplish this AD are described in the Embraer Service Bulletin 170-73-0006 original issue, or further revisions approved by the ANAC.                                                                                                                                                                                                                                                                                                                              |\n|                | Note: ANAC AD 2008-03-01R2 refers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |\n| Compliance:    | Within the next 1,200 hours time in service after the effective date of this Directive.                                                                                                                                                                                                                                                                                                                                                                                                                          |\n|                | This Airworthiness Directive becomes effective on 7 May 2009.                                                                                                                                                                                                                                                                                                                                                                                                                                                    |\n| Background:    | Initially, the ANAC had advised that instances have been reported of loss of thrust control due to problems in the Fuel Metering Valve (FMV) position feedback signal, which resulted in excessive thrust during some flight conditions. Such problems become critical during final approach flight phase. Since this condition affected flight safety, the AD/ERJ-170/16 required the FADEC software to be upgraded to version V5.40.                                                                           |\n|                | Since AD/ERJ-170/16 was issued the ANAC received reports of several instances of commanded in-flight shut down (IFSD) during use of FADEC with software version V5.40. Investigation has identified that these events linked to a logic error in software version V5.40. These IFSDs have a higher occurrence rate than the loss of thrust control events which resulted in the issue of AD/ERJ-170/16, therefore AD/ERJ-170/16 Amdt 1 was issued to require the FADEC software to be returned to version V5.30. |\n|                | FADEC software version V5.41 has now been issued with corrects the foregoing anomalies. This Directive requires the installation of software version V5.41.                                                                                                                                                                                                                                                                                                                                                      |\n\n|     | This Directive supersedes AD/ERJ-170/16 Amdt 1 which will be cancelled. |\n| --- | ----------------------------------------------------------------------- |\n\n![](image.001.png)  \nJames Coyne  \nDelegate of the Civil Aviation Safety Authority\n\n26 March 2009","sortOrder":0},{"sectionNumber":"AD/ERJ-170/22","sectionType":"part","heading":"AD/ERJ-170/22","content":"## AD/ERJ-170/22","sortOrder":1},{"sectionNumber":"FADEC Software","sectionType":"part","heading":"FADEC Software","content":"## FADEC Software","sortOrder":2},{"sectionNumber":"5/2009","sectionType":"part","heading":"5/2009","content":"## 5/2009","sortOrder":3}],"analysis":{"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"},"kimi_summary":{"content_quality":"ok","complexity_score":2,"scope_assessment":{"changed":false,"description":"This AD maintains its original narrow scope — addressing specific FADEC software defects in Embraer ERJ-170 aircraft. The document shows evolution through versions (V5.30 → V5.40 → V5.41) but this represents iterative safety refinement rather than scope creep. The directive remains tightly focused on engine control software for a specific aircraft family."},"complexity_factors":["Single, clear mechanical requirement (software replacement)","Only 7 aircraft models listed in applicability","One compliance timeframe (1,200 hours time in service)","No nested exceptions or conditional logic","Minimal cross-referencing (only references one Brazilian authority AD and one service bulletin)","Straightforward background narrative explaining the safety issue chain","No interpretation section with defined terms"],"plain_english_summary":"This Australian Airworthiness Directive requires owners/operators of specified Embraer ERJ-170 variants to install FADEC engine‑control software version V5.41 (or later ANAC‑approved) within 1,200 flight hours of 7 May 2009.  \n\nIt matters because earlier software caused loss of thrust control or introduced in‑flight shutdowns; V5.41 resolves both issues and replaces the prior unsafe fix."},"flash_summary":{"complexity_score":3,"scope_assessment":{"changed":false,"description":"The directive stays within the original safety-focused purpose (to correct unsafe FADEC behaviour). It does not expand to new regulatory domains or add unrelated obligations; it updates the required corrective action (mandating software V5.41 and ANAC‑approved later versions) in response to new technical findings, but this is an adjustment of remedy rather than a widening of scope."},"complexity_factors":["Single central technical requirement (install FADEC software V5.41)","Short compliance timeline metric: 1,200 hours time in service","Multiple aircraft models listed (7 variants)","Cross-reference to Embraer Service Bulletin 170-73-0006 for procedural detail","Conditional allowance for later FADEC versions only if ANAC approves them (regulatory gatekeeping)","Supersedes a prior AD and references ANAC ADs (historical cross-references)","Safety-critical technical history explained in Background (V5.40 → IFSD; earlier V5.30 reversion)"],"plain_english_summary":"**What this directive does (mechanics)**\n\n- Requires operators of specified Embraer ERJ-170 models to replace the engines' FADEC (Full Authority Digital Engine Control) software with version V5.41, or with any later FADEC software version if that later version has been approved by the Brazilian regulator (ANAC).\n- The update must be carried out following the procedures in Embraer Service Bulletin 170-73-0006 (original issue or later revisions approved by ANAC).\n- The software replacement must be completed within 1,200 hours time-in-service (TIS) from the directive’s effective date.\n- This directive cancels and supersedes a prior directive (AD/ERJ-170/16 Amdt 1) that required a different software state.\n\n**Which aeroplanes are affected**\n\n- All Embraer ERJ-170 variants listed: ERJ 170-100 STD, -100 LR, -100 SU, -100 SE, -200 STD, -200 LR, and -200 SU.\n\n**Why the rule exists (stated purpose) and the safety mechanism**\n\n- The regulator’s stated reason: earlier FADEC software versions produced two safety problems. One problem (incorrect Fuel Metering Valve feedback) could cause excessive thrust during critical phases such as final approach. A subsequent software version (V5.40) corrected that but introduced a logic error that caused an increased rate of in-flight engine shutdowns (IFSD). Version V5.41 was issued to correct those anomalies. The directive mandates installation of V5.41 to address those identified hazards (see Background).\n\n**Who pays, who decides, and what must operators change**\n\n- Aircraft operators (airlines, lessors, or maintenance organisations acting for them) are responsible for arranging and paying for the software update and any associated maintenance downtime; the directive places the compliance duty on operators (Requirement / Compliance sections).\n- The Brazilian regulator (ANAC) is the approval authority for the software version and for Service Bulletin revisions referenced by the directive; the Australian Civil Aviation Safety Authority issued this directive domestically (delegate signature appears on the directive).\n- Practically, operators must schedule the FADEC software installation within 1,200 flight hours and follow the Embraer Service Bulletin procedures approved by ANAC.\n\n**Practical costs, incentives and trade-offs (implementation lens)**\n\n- Direct costs: labour, tooling, possible increased AOG (aircraft on ground) time while software is installed and tested, and any certification paperwork costs. Those costs are concentrated on operators and maintenance providers.\n- Benefits are concentrated (reduced risk of IFSD or loss of thrust control for the updated fleet) and are safety-critical. The directive’s stated benefit is preventing two types of engine-control failures.\n- Implementation risk: the history in the Background shows software updates can fix one failure mode and introduce another (V5.40 → IFSDs). The directive requires a specific corrected version (V5.41) but leaves open the approval of later versions by ANAC; this shifts some decision-making to the regulator and the manufacturer’s validation processes.\n- Compliance burden: operators must track TIS hours to meet the 1,200-hour deadline, obtain and follow an ANAC‑approved Service Bulletin, and coordinate any testing required after installation.\n- Trade-offs: short-term maintenance cost and operational disruption versus reduced probability of engine-control failures in flight. The directive narrows operator choice of software to ANAC‑approved versions, which reduces option value but is standard for airworthiness enforcement.\n\n**Procedural and discretion points**\n\n- The directive delegates detailed procedures to an Embraer Service Bulletin; ANAC approval is required for any later revisions. This creates reliance on manufacturer documentation and the foreign regulator’s approval process for acceptable compliance methods.\n- The directive also cross-references earlier ADs (it supersedes AD/ERJ-170/16 Amdt 1), so operators must be aware of the historical sequence when assessing compliance history and records.\n\n**Where the key instructions appear in the text**\n\n- Requirement: description of the mandatory software version and the Service Bulletin to use.\n- Compliance: 1,200 hours TIS deadline and effective date information.\n- Background: explains the safety incidents that motivated prior directives and the revision to require V5.41.\n\n(Analysis above sticks to the directive’s mechanistic requirements and the observable implementation effects; it does not pass judgement on policy goals.)"}},"importantCases":[],"_links":{"self":"/api/acts/ad-erj-170-22-fadec-software","history":"/api/acts/ad-erj-170-22-fadec-software/history","analysis":"/api/acts/ad-erj-170-22-fadec-software/analysis","conflicts":"/api/acts/ad-erj-170-22-fadec-software/conflicts","importantCases":"/api/acts/ad-erj-170-22-fadec-software/important-cases","documents":"/api/acts/ad-erj-170-22-fadec-software/documents"}}