{"id":"F2005L03149","name":"AD/B767/214 - Pegasus Flight Management Computer System","slug":"ad-b767-214-pegasus-flight-management-computer-system","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":134357,"registerId":"commonwealth-F2005L03149-current","compilationNumber":null,"startDate":"2026-04-03","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"Boeing 767 Series Aeroplanes","sectionType":"division","heading":"Boeing 767 Series Aeroplanes","content":"### Boeing 767 Series Aeroplanes\n\n| AD/B767/214 | Pegasus Flight Management Computer System | 12/2005 |\n| ----------- | ----------------------------------------- | ------- |\n\n```html\n

Applicability:

Model 767-200, -300, -300F and -400ER series aeroplanes, equipped with a Pegasus flight management computer (FMC) system operating with an Air Traffic Services data link function enabled.

Requirement:

Replace the Operational Programme Software (OPS) and Flight Information and Data Output (FIDO) software of the existing FMC with Pegasus 2003 OPS and FIDO software or Pegasus 2005 OPS and FIDO software, in accordance with the applicable service bulletin specified in either Table 1 or Table 2.

Table 1 - Pegasus 2003 OPS and FIDO - Applicable Service Bulletins

Aeroplane Model

767-200/-300/-300F series
767-400ER series

Boeing Alert Service Bulletin

767–34A0389, Revision 2
767-34A0390

Dated

16 December 2004
19 February 2004

Table 2 - Pegasus 2005 OPS and FIDO - Applicable Service Bulletins

Aeroplane Model

767-200/-300/-300F series
767-400ER series

Boeing Service Bulletin

767-34-0471
767-34-0472

Dated

17 March 2005
17 March 2005

Note: FAA AD 2005-18-09 Amdt 39-14249 refers.

Compliance:

Within 18 months after the effective date of this Directive.

This Airworthiness Directive becomes effective on 24 November 2005.

Background:

The United Sates Federal Aviation Administration (FAA) has advised that they have received reports of ‘old’ or expired air traffic control (ATC) clearance messages being displayed on the control display unit (CDU) of the FMC system during subsequent flights.

\n```\n\n| | This Directive is issued to prevent display of ‘old’ or expired ATC clearance messages on the CDU on subsequent flights, which could result in the aeroplane entering unauthorized airspace or following a flight path that does not provide minimum separation requirements between aircraft which could result in a near miss or mid-air collision. |\n| --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n\n![](image.001.png) \nJayaprakashan Ambali \nDelegate of the Civil Aviation Safety Authority\n\n4 October 2005","sortOrder":0},{"sectionNumber":"AD/B767/214","sectionType":"part","heading":"AD/B767/214","content":"## AD/B767/214","sortOrder":1},{"sectionNumber":"Pegasus Flight Management Computer Syste","sectionType":"part","heading":"Pegasus Flight Management Computer System","content":"## Pegasus Flight Management Computer System","sortOrder":2},{"sectionNumber":"12/2005","sectionType":"part","heading":"12/2005","content":"## 12/2005","sortOrder":3}],"analysis":{"kimi_summary":{"content_quality":"ok","complexity_score":3,"scope_assessment":{"changed":false,"description":"This is a standard, targeted airworthiness directive addressing a specific software defect. The scope remains tightly focused on the identified safety issue without expansion into broader operational matters."},"complexity_factors":["Technical aviation terminology throughout (FMC, CDU, OPS, FIDO, ATC, data link)","Two alternative compliance paths (Table 1 vs Table 2) with different software versions","Cross-reference to US FAA directive (AD 2005-18-09)","Specific model variants and equipment configurations in applicability","Tabular presentation of service bulletin references creates parsing complexity"],"plain_english_summary":"This CASA airworthiness directive requires operators of certain Boeing 767-200/300/300F/400ER aircraft with Pegasus flight management computers and datalink messaging to install updated flight‑computer software (approved 2003 or 2005 builds) within 18 months. The mandatory update prevents the display of stale ATC messages from previous flights, reducing the risk of pilots following outdated instructions and potential airspace conflicts."},"flash_summary":{"complexity_score":3,"scope_assessment":{"changed":false,"description":"The directive's scope remains consistent with its stated purpose: it targets Pegasus FMC-equipped Boeing 767s with ATS data‑link enabled and requires software replacement per specified Boeing service bulletins within 18 months to prevent display of expired ATC clearances. It does not broaden applicability beyond the identified models/configuration and continues to reference the related FAA AD without extending obligations to other systems."},"complexity_factors":["Targeted technical change: replaces OPS and FIDO software only (\"Requirement: Replace the Operational Programme Software (OPS) and Flight Information and Data Output (FIDO) software...\").","Narrow applicability: applies only to certain Boeing 767 models equipped with Pegasus FMC and ATS data‑link enabled (\"Applicability: Model 767-200, -300, -300F and -400ER series aeroplanes, equipped with a Pegasus flight management computer (FMC) system operating with an Air Traffic Services data link function enabled\").","Multiple acceptable fixes: permits either Pegasus 2003 or Pegasus 2005 software and refers to different Boeing service bulletins in Table 1 and Table 2 (requires operators to choose/install the correct bulletin for their model).","Compliance scheduling: fixed deadline ('Within 18 months after the effective date of this Directive') which imposes operational planning and potential downtime costs.","External cross-reference: note referring to FAA AD 2005-18-09 (\"Note: FAA AD 2005-18-09 Amdt 39-14249 refers\") creates an interjurisdictional reference point for technical conformity.","Cost and responsibility allocation: the operator/owner must carry out and pay for the software update and any associated maintenance or downtime (implied by the mandated replacement and compliance timeframe).","Safety-focused mandate with no listed alternatives or exemptions — the directive prescribes a single corrective action to mitigate the reported risk of expired ATC messages (Background: FAA reports of 'old' or expired ATC clearance messages...)."],"plain_english_summary":"Mandates replacing the Pegasus Flight Management Computer (FMC) Operational Programme Software (OPS) and Flight Information and Data Output (FIDO) with Pegasus 2003 or 2005 versions, using the Boeing service bulletins listed, for Boeing 767-200/-300/-300F and -400ER aeroplanes that have Pegasus FMC with Air Traffic Services data‑link enabled. Operators must install the specified software within 18 months; CASA issued the directive to prevent ‘‘old’’ or expired ATC clearances appearing on the CDU, which could lead to unauthorized airspace entry or loss of separation."},"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"}},"importantCases":[],"_links":{"self":"/api/acts/ad-b767-214-pegasus-flight-management-computer-system","history":"/api/acts/ad-b767-214-pegasus-flight-management-computer-system/history","analysis":"/api/acts/ad-b767-214-pegasus-flight-management-computer-system/analysis","conflicts":"/api/acts/ad-b767-214-pegasus-flight-management-computer-system/conflicts","importantCases":"/api/acts/ad-b767-214-pegasus-flight-management-computer-system/important-cases","documents":"/api/acts/ad-b767-214-pegasus-flight-management-computer-system/documents"}}