2012-21-08: Auto Flight

Adoption of the Amendment \n\n\n\tAccordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows: \n\nPART 39--AIRWORTHINESS DIRECTIVES \n\n0 1. The authority citation for part 39 continues to read as follows: \n\n\n\tAuthority: 49 U.S.C. 106(g), 40113, 44701. \n\n\n\nSec. 39.13 (Amended) \n\n0 2. The FAA amends Sec. 39.13 by removing airworthiness directive (AD) 2005-07-20, Amendment 39-14045 (70 FR 17603, April 7, 2005), and adding the following new AD: \n\n2012-21-08 The Boeing Company: Amendment 39-17224; Docket No. FAA- 2010-0856; Directorate Identifier 2010-NM-117-AD. \n\n(a) Effective Date \n\n\n\tThis AD is effective November 27, 2012. \n\n(b) Affected ADs \n\n\n\tThis AD supersedes AD 2005-07-20, Amendment 39-14045 (70 FR 17603, April 7, 2005). \n\n(c) Applicability \n\n\n\tThis AD applies to The Boeing Company Model 737-600, -700, - 700C, -800, and -900 series airplanes, certificated in any category; delivered with the Rockwell Collins Enhanced Digital Flight Control System (EDFCS), as identified in the variable number table in Section 1.A.1., Effectivity, of Boeing Alert Service Bulletin 737- 22A1211, dated April 13, 2010. This AD is applicable to all airplanes listed in the variable number table, and is not defined by the ''Group 1'' description in Section 1.A. of Boeing Alert Service Bulletin 737-22A1211, dated April 13, 2010. \n\n(d) Subject \n\n\n\tJoint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 22, Auto Flight. \n\n(e) Unsafe Condition \n\n\n\tThis AD was prompted by reports of undetected erroneous output from a single radio altimeter channel, which resulted in premature autothrottle retard during approach. We are issuing this AD to detect and correct an unsafe condition associated with erroneous output from a radio altimeter channel, which could result in premature autothrottle landing flare retard and the loss of automatic speed control, and consequent loss of control of the airplane. \n\n(f) Compliance \n\n\n\tComply with this AD within the compliance times specified, unless already done. \n\n(g) Retained Software Installation and Test \n\n\n\tThis paragraph restates the requirements of paragraph (f) of AD 2005-07-20, Amendment 39-14045 (70 FR 17603, April 7, 2005). For airplanes identified in Boeing Alert Service Bulletin 737-22A1164, dated May 20, 2004: Within 12 months after May 12, 2005 (the effective date of AD 2005-07-20), install and test an updated version of the operational program software (OPS) of the EDFCS flight control computers (FCCs), in accordance with Boeing Alert Service Bulletin 737-22A1164, dated May 20, 2004. Installing software as required by paragraph (h)(1)(i) or (h)(1)(ii) of this AD, or verifying that the software is installed as specified by paragraph (h)(2) of this AD, or doing the actions specified in paragraph (i) of this AD, terminates the requirements of this paragraph. \n\n(h) New Requirements \n\n\n\tWithin 3 months after the effective date of this AD: Inspect to determine the part number of the OPS of the FCCs, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin 737-22A1211, dated April 13, 2010. Installing software as required by paragraph (h)(1)(i) or (h)(1)(ii) of this AD, or verifying that the software is installed as specified by paragraph (h)(2) of this AD, terminates the requirements of paragraph (g) of this AD. Doing the actions specified in paragraph (i) of this AD, terminates the requirements of this paragraph. \n\t(1) For any OPS having a part number identified in table 1 of the Accomplishment Instructions of Boeing Alert Service Bulletin 737-22A1211, dated April 13, 2010: Before further flight, do the actions specified in paragraph (h)(1)(i) or (h)(1)(ii), as applicable. \n\t(i) Install software identified in table 2 of the Accomplishment Instructions of Boeing Alert Service Bulletin 737-22A1211, dated April 13, 2010, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin 737-22A1211, dated April 13, 2010. \n\t(ii) Install software identified in table 2 of the Accomplishment Instructions of Boeing Alert Service Bulletin 737- 22A1224, dated May 18, 2012, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin 737-22A1224, dated May 18, 2012. \n\t(2) For any OPS having a part number identified in table 2 of the Accomplishment Instructions of Boeing Alert Service Bulletin 737-22A1211, dated April 13, 2010; or in table 2 of the Accomplishment Instructions of Boeing Alert Service Bulletin 737- 22A1224, dated May 18, 2012: No further action is required by this paragraph. \n\n(i) New Optional Software Installation \n\n\n\tInstalling a version of the FCC OPS approved after May 18, 2012 (the issue date of Boeing Alert Service Bulletin 737-22A1224) terminates the requirements of paragraphs (g) and (h) of this AD, provided that the conditions specified in paragraphs (i)(1) and (i)(2) of this AD are met. \n\t(1) The version of the FCC OPS must be approved by the Manager, Seattle Aircraft Certification Office (ACO), FAA; the Manager, Boeing Aviation Safety Oversight Office (BASOO), FAA; or the Boeing Commercial Airplanes Organization Designation Authorization (ODA). \n\t(2) The installation must be done in accordance with a method approved by the Manager, Seattle ACO, FAA; the Manager, BASOO, FAA; or the Boeing Commercial Airplanes ODA. \n\n(j) Alternative Methods of Compliance (AMOCs) \n\n\n\t(1) The Manager, Seattle Aircraft Certification Office (ACO), FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in the Related Information section of this AD. Information may be emailed to: [email protected]. \n\t(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office. \n\t(3) An AMOC that provides an acceptable level of safety may be used for any repair required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Seattle ACO, to make those findings. For a repair method to be approved, the repair must meet the certification basis of the airplane and the approval must specifically refer to this AD \n\t(4) AMOCs approved previously in accordance with AD 2005-07-20, Amendment 39-14045 (70 FR 17603, April 7, 2005), are approved as AMOCs for the corresponding provisions of this AD. \n\n(k) Related Information \n\n\n\tFor more information about this AD, contact Gregg Nesemeier, Senior Aerospace Engineer, Systems and Equipment Branch, ANM-130S, FAA, Seattle Aircraft Certification Office (ACO), 1601 Lind Avenue SW., Renton, Washington 98057-3356; \n\n((Page 64714)) \n\nphone: (425) 917-6479; fax: (425) 917-6590; email: [email protected]. \n\n(l) Material Incorporated by Reference \n\n\n\t(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51. \n\t(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise. \n\t(3) The following service information was approved for IBR on November 27, 2012. \n\t(i) Boeing Alert Service Bulletin 737-22A1211, dated April 13, 2010. \n\t(ii) Boeing Alert Service Bulletin 737-22A1224, dated May 18, 2012. \n\t(4) The following service information was approved for IBR on May 12, 2005 (70 FR 17603, April 7, 2005). \n\t(i) Boeing Alert Service Bulletin 737-22A1164, dated May 20,2004. \n\t(ii) Reserved. \n\t(5) For The Boeing Company service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data & Services Management, P.O. Box 3707, MC 2H-65, Seattle, WA 98124- 2207; telephone 206-544-5000, extension 1; fax 206-766-5680; Internet https://www.myboeingfleet.com. \n\t(6) You may view this service information at FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221. \n\t(7) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: http://www.archives.gov/federal-register/cfr/ibr-locations.html.