{"id":"F2005L01952","name":"AD/B767/197 Amdt 3 - Air Data System","slug":"ad-b767-197-amdt-3-air-data-system","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":36165,"registerId":"commonwealth-F2005L01952-current","compilationNumber":null,"startDate":"2026-04-01","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/197 Amdt 3 | Air Data System | 9/2005 DM |\n| ------------------ | --------------- | --------- |\n\n| Applicability | Model 767-200, 767-300 and 767-300F series aeroplanes identified in Boeing Alert Service Bulletin (ASB) 767-34A0332, Revision 2, dated 30 September 2004. |\n| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Requirement: | 1. Either: |\n| | a. Modify the air data switching system and do a system functional test, according to the Accomplishment Instructions of ASB 767-34A0332, Revision 1 dated 24 April 2003 or Revision 2. |\n| | or, |\n| | b. Carry out the following: |\n| | (i) Change the termination of the wires and perform an operational test, according to the Accomplishment Instructions of Boeing Special Attention SB 767-31-0149, Revision 1, dated 7 November 2002 or Revision 2 dated 11 November 2004 and |\n| | (ii) Modify the air data switching system and do a system functional test, according to the Accomplishment Instructions of SB 767-34A0332, Revision 1 or Revision 2. |\n| | Note 1: Requirement 1 provides two alternate methods of compliance, if Requirement 1.b. is selected the compliance date for the modification of the air data switching system (ASB 767-34A0332 Revision 1 or Revision 2) is extended from 24 months to 72 months. |\n| | Modifications accomplished before the effective date of the original issue of this Directive in accordance with Boeing ASB 767-34A0332 dated 10 January 2002 are considered acceptable for compliance with Requirement 1.a. |\n| | Modifications accomplished in accordance with Requirement 2 of the original issue of this Directive are also considered acceptable for compliance with Requirement 1.a. |\n\n```html\n

2. For aeroplanes that are identified in ASB 767-34A0332, Revision 2 and also identified in any of the Boeing service bulletins listed below, unless previously accomplished, carry out all actions associated with replacing the existing Engine Indication and Crew Alerting System (EICAS) computers with improved EICAS computers, according to the Accomplishment Instructions of the applicable service bulletin specified below. This includes performing an EICAS readout comparison to ensure that the applicable software is used; replacing the existing EICAS computers with new, improved EICAS computers that can be upgraded with certain software together with making related wiring changes.

767-31-0091 Revision 3 dated 27 April 2000
767-31-0098 Revision 2 dated 21 October 1999
767-31-0099 Revision 3 dated 8 February 2001
767-31-0100 Revision 2 dated 29 July 1999
767-31-0101 dated 6 July 2000

Note 2: The Boeing service bulletins listed above all include Appendices A, B and C,

3. Parts listed in the “Existing Part Number” column under paragraph 2.E. of the following Boeing SBs shall not be installed on any aeroplane as a replacement part:

767-31-0091 Rev 3
767-31-0098 Rev 2

767-31-0099 Rev 3
767-31-0100 Rev 2

767-31-0101 Original

Note 3: FAA AD 2004-10-05 Amdt 39-13635 refers.

Compliance:

For Requirement 1.a. - Remains unchanged as ‘Within 24 months after the effective date of Amendment 1 to this Directive’.

For Requirement 1.b.(i) - Remains unchanged as ‘Within 18 months after the effective date of Amendment 1 to this Directive’.

For Requirement 1.b.(ii) - Remains unchanged as ‘Within 72 months after the effective date of Amendment 1 to this Directive’.

For Requirement 2 - Prior to, or concurrently with, SB 767-34A0332, Revision 1 or Revision 2.

For Requirement 3 - As of the effective date of the original issue of this Directive.

This Amendment becomes effective on 15 July 2005.

\n```\n\n| Background: | The original issue of this Directive required a modification of the ADC system, which involves installing certain new circuit breakers, relays, and related components, and making various wiring changes in and between the flight deck and main equipment centre. For certain aeroplanes, this amendment also required accomplishment of various other actions prior to, or concurrently with, the modification of the ADC system. For some aeroplanes, this Directive also contained an option that extended the compliance time to accomplish the modification of the ADC system. |\n| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| | These actions were considered necessary to ensure that the flight crew is able to silence an erroneous overspeed or stall aural warning. A persistent erroneous warning could confuse and distract the flight crew and lead to an increase in the flight crews workload. Such a situation could lead the flight crew to act on hazardously misleading information, which could result in loss of control of the aeroplane. |\n| | Amendment 1, whilst continuing the requirements of the original issue of the Directive, clarified the optional methods of complying with Requirement 1. |\n| | Amendment 2 introduced ASB 767-34A0332 Revision 2 as an alternate method of compliance and corrects a typographical error in Note 1. The Amendment also changed applicability of the Directive by the deletion of four aeroplanes and the inclusion of two additional aeroplanes. |\n| | This Amendment introduces SB 767-31-0149, Revision 2 as an alternate method of compliance for Requirement 1.b.(i). |\n| | The original issue of this Airworthiness Directive became effective on 5 August 2004. |\n| | Amendment 1 of this Airworthiness Directive became effective on 30 September 2004. |\n| | Amendment 2 of this Airworthiness Directive became effective on 17 February 2005 |\n\n![](image.001.png) \nJames Coyne \nDelegate of the Civil Aviation Safety Authority\n\n8 July 2005","sortOrder":0},{"sectionNumber":"AD/B767/197 Amdt 3","sectionType":"part","heading":"AD/B767/197 Amdt 3","content":"## AD/B767/197 Amdt 3","sortOrder":1},{"sectionNumber":"Air Data System","sectionType":"part","heading":"Air Data System","content":"## Air Data System","sortOrder":2},{"sectionNumber":"9/2005 DM","sectionType":"part","heading":"9/2005 DM","content":"## 9/2005 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":6,"scope_assessment":{"changed":true,"description":"The Directive's scope was modified across amendments: Amendment 2 introduced ASB 767-34A0332 Revision 2 as an alternate compliance method and changed the applicability by removing four aeroplanes and adding two; Amendment 3 adds Boeing SB 767-31-0149 Revision 2 as an alternate method for wire termination work and imposes EICAS computer replacement and software/readout verification for aeroplanes identified in ASB Rev 2 and listed SBs. Note 1 and related clauses also extend compliance time for the alternate route (from 24 to 72 months) and earlier-completed modifications are expressly accepted."},"complexity_factors":["Multiple alternative compliance paths (Requirement 1.a or 1.b with sub-steps) creating operator choices and sequencing effects","Cross-references to numerous Boeing service bulletins and specific revision numbers (ASB 767-34A0332 Rev 1/2; SBs 767-31-0149 Rev1/2; several 767-31-00xx SBs)","Different and staggered compliance deadlines (24 months, 18 months, 72 months, and ‘prior to or concurrently with’) depending on method and aircraft","Parts prohibition for specific existing part numbers listed in multiple SBs (prevents certain replacements as of effective date)","Requirement to perform functional tests and software/EICAS readout comparisons (operational verification burden and software-version control)","Acceptability clauses for prior accomplished modifications (creates conditional equivalence and record-keeping requirements)","Applicability limited to aircraft explicitly identified in the ASB revisions, and amendment-driven changes to the applicability list"],"plain_english_summary":"Requires operators of certain Boeing 767-200/300/300F aeroplanes identified in Boeing ASB 767-34A0332 Rev 2 to modify the air‑data switching system or, alternatively, change wire terminations and carry out tests, and—where identified—replace Engine Indication and Crew Alerting System (EICAS) computers with upgraded units and verify software/readouts. Operators (aircraft owners/operators and their maintenance providers) must pay for and perform the work within staggered compliance windows (18–72 months). The stated safety purpose is to prevent persistent erroneous overspeed or stall aural warnings that could distract flight crew."},"kimi_summary":{"content_quality":"ok","complexity_score":6,"scope_assessment":{"changed":true,"description":"The directive has grown significantly beyond its original purpose. What began as a straightforward air data system modification to address false stall/overspeed warnings has expanded through three amendments to include: (1) alternative compliance methods with extended timelines, (2) mandatory EICAS computer replacements for certain aircraft, and (3) a parts installation prohibition. The original scope was limited to ADC system modifications; Amendment 2 changed applicability by deleting four aircraft and adding two others; and Amendment 3 introduced additional service bulletin references and alternative methods. The directive now regulates not just the immediate safety fix but also equipment upgrades and parts supply chain restrictions."},"complexity_factors":["Multiple alternate methods of compliance (AMOCs) with different timelines (24 months vs 18+72 months)","Extensive cross-referencing to external Boeing documents (5 different Service Bulletins with multiple revisions each)","Nested conditional applicability — Requirement 2 only applies to aircraft identified in both ASB 767-34A0332 Rev 2 AND specific other service bulletins","Retroactive compliance recognition — modifications done before the directive's effective date under earlier Boeing bulletins are accepted","Amendment history tracking — references to Requirements from 'original issue', 'Amendment 1', and 'Amendment 2' creating temporal dependencies","Parts prohibition with reference to specific column ('Existing Part Number' under paragraph 2.E.) in external documents","Concurrent/compliance timing requirements ('prior to, or concurrently with') creating sequencing dependencies between Requirements 1 and 2"],"plain_english_summary":"This CASA Airworthiness Directive mandates fixes to the air data switching system on certain Boeing 767-200/300/300F aircraft to stop false overspeed or stall warnings that could distract crews and risk loss of control. Operators must choose either a direct modification within 24 months or a two-step rewire-and-test then later modification (shorter initial, longer final deadlines). Some aircraft also require upgraded EICAS computers, and specified old parts are banned. It affects all operators and maintainers of the listed 767s."}},"importantCases":[],"_links":{"self":"/api/acts/ad-b767-197-amdt-3-air-data-system","history":"/api/acts/ad-b767-197-amdt-3-air-data-system/history","analysis":"/api/acts/ad-b767-197-amdt-3-air-data-system/analysis","conflicts":"/api/acts/ad-b767-197-amdt-3-air-data-system/conflicts","importantCases":"/api/acts/ad-b767-197-amdt-3-air-data-system/important-cases","documents":"/api/acts/ad-b767-197-amdt-3-air-data-system/documents"}}