{"id":"F2008L02102","name":"AD/ERJ-190/3 Amdt 1 - Flight Guidance Control System","slug":"ad-erj-190-3-amdt-1-flight-guidance-control-system","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":74324,"registerId":"commonwealth-F2008L02102-current","compilationNumber":null,"startDate":"2026-04-02","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"Embraer ERJ-190 Series Aeroplanes","sectionType":"division","heading":"Embraer ERJ-190 Series Aeroplanes","content":"### Embraer ERJ-190 Series Aeroplanes\n\n| AD/ERJ-190/3 Amdt 1 | Flight Guidance Control System | 8/2008 DM |\n| ------------------- | ------------------------------ | --------- |\n\n| Applicability: | All ERJ-190 model aeroplanes equipped with Primus EPIC software load versions 4.3, 4.4, 4.5, 4.6 or 4.7.                                                                                                                                                                                                |\n| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Requirement:   | 1. Carry out a functional test to check the engagement of the Flight Guidance Control System (FGCS) channels in accordance with Embraer Service Bulletin (SB) 190-22-0002, original issue, dated 9 November 2006 or later revisions approved by the Brazilian Agência Nacional de Aviação Civil (ANAC). |\n|                | Note 1: For the purpose of this Directive, a functional check is defined as: \"A quantitative check to determine if one or more functions of an item perform within specified limits.”                                                                                                                   |\n|                | 2. Install primus EPIC software load 19.3 in accordance with Embraer SB190-31-0009, original issue, dated 4 May 2007 or later revisions approved by the ANAC; or a higher software load version in accordance with an Embraer SB approved by the ANAC.                                                  |\n|                | Note 2: For example version 19.4 may be installed in accordance with SB190-31-0014 dated 5 September 2007 or version 21.2 may be installed in accordance with SB 190-31-0015 dated 21 December 2007, other versions may be installed in accordance with an applicable approved SB.                      |\n|                | Note 3: The installation of the Primus EPIC software load version 19.3 or higher is considered a terminating action for the Requirement 1 repetitive functional check.                                                                                                                                  |\n|                | Note 2: ANAC AD 2006-11-03R3 refers.                                                                                                                                                                                                                                                                    |\n| Compliance:    | For Requirement 1 - Within the next 300 hours time in service (TIS) after the effective date of the original issue of this Directive and thereafter at intervals that do not exceed 600 hours TIS until Requirement 2 is accomplished.                                                                  |\n|                | For Requirement 2 - No later than 30 June 2009.                                                                                                                                                                                                                                                         |\n|                | This Amendment becomes effective on 18 June 2008.                                                                                                                                                                                                                                                       |\n\n| Background: | The ANAC has received reports that some “caution” messages issued by the FGCS are not displayed on aircraft equipped with EPIC software load 4.3, 4.4, 4.5, 4.6 or 4.7. Therefore, following a possible failure on one FGCS channel during a given flight, such a failure condition will remain undetected or latent in subsequent flights. If another failure occurs on the second FGCS channel, the result may be a command hard-over by the autopilot. |\n| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n|             | Since this condition may affect the safety of the aeroplane, the original issue of this Directive required the repetitive functional testing of the FGCS until the software load version 19.3 or higher is installed.                                                                                                                                                                                                                                     |\n|             | This Amendment continues the repetitive testing of the FGCS and extends the compliance time for Requirement 2 by one year. The Amendment also clarifies how higher versions of the software load may be installed.                                                                                                                                                                                                                                        |\n|             | The original issue of this Directive became effective on 27 March 2008.                                                                                                                                                                                                                                                                                                                                                                                   |\n\n![](image.001.png)  \nJames Coyne  \nDelegate of the Civil Aviation Safety Authority\n\n12 June 2008","sortOrder":0},{"sectionNumber":"AD/ERJ-190/3 Amdt 1","sectionType":"part","heading":"AD/ERJ-190/3 Amdt 1","content":"## AD/ERJ-190/3 Amdt 1","sortOrder":1},{"sectionNumber":"Flight Guidance Control System","sectionType":"part","heading":"Flight Guidance Control System","content":"## Flight Guidance Control System","sortOrder":2},{"sectionNumber":"8/2008 DM","sectionType":"part","heading":"8/2008 DM","content":"## 8/2008 DM","sortOrder":3}],"analysis":{"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"},"flash_summary":{"complexity_score":4,"scope_assessment":{"changed":false,"description":"The Amendment does not change which aeroplanes are covered or the core measures; it continues the repetitive FGCS testing, clarifies acceptable higher software‑load installations, and extends the compliance deadline for the software upgrade by one year (see `Requirement`, `Notes`, `Compliance`, `Background`)."},"complexity_factors":["Applicability limited to ERJ‑190 aeroplanes with specific EPIC software loads (`Applicability`): narrows affected population but requires software inventory checks.","Repetitive testing regime with specified intervals and a terminating action upon upgrade (`Requirement 1`; `Compliance`): operators must schedule tests every 600 hours TIS after an initial 300‑hour window until upgrade.","Mandatory software upgrade to load 19.3 or higher with multiple approved upgrade paths and SB cross‑references (`Requirement 2`; Notes): multiple service bulletins and example versions increase procedural choices.","Deadline and amended extension (install by 30 June 2009; amendment extends Requirement 2 by one year) (`Compliance`; `Background`): timing flexibility changed but creates administrative tracking.","Regulatory interdependence — Embraer service bulletins must be approved by ANAC (`Requirement 2`; Notes; ANAC AD reference): approvals constrain which SB revisions satisfy the AD.","Operational cost and logistics burden on operators (tests and software installation) (`Requirement`; `Compliance`): direct expenditure, downtime and scheduling impacts.","Document clarity issues (duplicate note numbering and multiple SB references in the text) (`Requirement` Notes): minor drafting ambiguities may cause procedural confusion for implementers.","Safety rationale ties to latent FGCS failures and autopilot hard‑over risk (`Background`): motivates strict compliance but requires accurate functional checks to be effective."],"plain_english_summary":"This Airworthiness Directive requires operators of Embraer ERJ‑190 aeroplanes fitted with Primus EPIC software `4.3–4.7` to run recurring functional tests of the Flight Guidance Control System (FGCS) channels and to install Primus EPIC software load 19.3 or a later approved load by a set deadline. It is driven by reports that some FGCS “caution” messages were not displayed, creating a latent‑failure risk that could lead to an autopilot command hard‑over; operators pay for testing and upgrades and must follow approved Embraer service bulletins."},"kimi_summary":{"content_quality":"ok","complexity_score":3,"scope_assessment":{"changed":false,"description":"This amendment maintains the original scope — addressing the same software defect in the same aircraft models. The amendment merely extends a compliance deadline and clarifies installation procedures for higher software versions, without expanding the regulatory reach beyond the original safety issue."},"complexity_factors":["Single, clearly defined applicability criterion (specific aircraft model + 5 specific software versions)","Two straightforward requirements with clear compliance deadlines","Minimal cross-referencing (only references to specific Embraer Service Bulletins and Brazilian ANAC approvals)","Simple conditional logic: testing continues until software upgrade is completed","Short document length (approximately 400 words of substantive content)","Only one defined term ('functional check' in Note 1)","No nested exceptions or complex procedural branching"],"plain_english_summary":"This CASA Airworthiness Directive requires Australian operators of Embraer ERJ-190s with Primus EPIC loads 4.3–4.7 to perform functional Flight Guidance Control System (FGCS) tests every 600 flight hours and to install software version 19.3 or later by 30 June 2009 (deadline extended from mid‑2008).\n\nIt addresses a bug that suppresses autopilot \"caution\" messages, risking undetected dual-channel failure and a possible autopilot \"hard‑over\" and loss of control; non‑compliance grounds the aircraft."}},"importantCases":[],"_links":{"self":"/api/acts/ad-erj-190-3-amdt-1-flight-guidance-control-system","history":"/api/acts/ad-erj-190-3-amdt-1-flight-guidance-control-system/history","analysis":"/api/acts/ad-erj-190-3-amdt-1-flight-guidance-control-system/analysis","conflicts":"/api/acts/ad-erj-190-3-amdt-1-flight-guidance-control-system/conflicts","importantCases":"/api/acts/ad-erj-190-3-amdt-1-flight-guidance-control-system/important-cases","documents":"/api/acts/ad-erj-190-3-amdt-1-flight-guidance-control-system/documents"}}