Airworthiness Directives; Boeing Model 757-200 and -300 Series Airplanes and Model 767 Series Airplanes, 53053-53056 [05-17607]

Download as PDF Federal Register / Vol. 70, No. 172 / Wednesday, September 7, 2005 / Rules and Regulations Related Information (i) French airworthiness directive F–2005– 011, dated January 19, 2004, also addresses the subject of this AD. Material Incorporated by Reference (j) You must use Airbus Service Bulletin A340–54–4009, Revision 01, dated February 15, 2005, excluding Appendix 01, to perform the actions that are required by this AD, unless the AD specifies otherwise. The Director of the Federal Register approved the incorporation by reference of this document in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. Contact Airbus, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France, for a copy of this service information. You may review copies at the Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street SW., Room PL–401, Nassif Building, Washington, DC; on the Internet at http://dms.dot.gov; or at the National Archives and Records Administration (NARA). For information on the availability of this material at the NARA, call (202) 741–6030, or go to http://www. archives.gov/federal-register/cfr/ibrlocations.html. Issued in Renton, Washington, on August 29, 2005. Kalene C. Yanamura, Acting Manager, Transport Airplane Directorate, Aircraft Certification Service. [FR Doc. 05–17606 Filed 9–6–05; 8:45 am] BILLING CODE 4910–13–P AD to prevent display of ‘‘old’’ or expired ATC clearance messages on the CDU of subsequent flights, which could result in the airplane entering unauthorized airspace or following a flight path that does not provide minimum separation requirements between aircraft, and a consequent near miss or a mid-air collision. DATES: Effective October 12, 2005. The Director of the Federal Register approved the incorporation by reference of certain publications listed in the AD as of October 12, 2005. ADDRESSES: You may examine the AD docket on the Internet at http:// dms.dot.gov or in person at the Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL–401, Washington, DC. Contact Boeing Commercial Airplanes, P.O. Box 3707, Seattle, Washington 98124–2207, for service information identified in this AD. FOR FURTHER INFORMATION CONTACT: Samuel Slentz, Aerospace Engineer, Systems and Equipment Branch, ANM– 130S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue, SW., Renton, Washington 98055–4056; telephone (425) 917–6483; fax (425) 917–6590. SUPPLEMENTARY INFORMATION: DEPARTMENT OF TRANSPORTATION Examining the Docket Federal Aviation Administration You may examine the AD docket on the Internet at http://dms.dot.gov or in person at the Docket Management Facility office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The Docket Management Facility office (telephone (800) 647–5227) is located on the plaza level of the Nassif Building at the street address stated in the ADDRESSES section. 14 CFR Part 39 [Docket No. FAA–2005–20352; Directorate Identifier 2004–NM–214–AD; Amendment 39–14249; AD 2005–18–09] RIN 2120–AA64 Airworthiness Directives; Boeing Model 757–200 and –300 Series Airplanes and Model 767 Series Airplanes Discussion Federal Aviation Administration (FAA), Department of Transportation (DOT). ACTION: Final rule. AGENCY: SUMMARY: The FAA is adopting a new airworthiness directive (AD) for certain Boeing Model 757–200 and –300 series airplanes and Model 767 series airplanes. This AD requires replacing the existing operational software of the Pegasus flight management computer (FMC) system with new, improved operational software. This AD results from 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. We are issuing this VerDate Aug<18>2005 15:01 Sep 06, 2005 Jkt 205001 The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to include an AD that would apply to certain Boeing Model 757–200 and –300 series airplanes and Model 767 series airplanes. That NPRM was published in the Federal Register on February 15, 2005 (70 FR 7676). That NPRM proposed to require replacing the existing operational software of the Pegasus flight management computer (FMC) system with new, improved operational software. Comments We provided the public the opportunity to participate in the development of this AD. We have considered the comments that have been received on the NPRM. PO 00000 Frm 00011 Fmt 4700 Sfmt 4700 53053 Supportive or No Objection Comments for the NPRM One commenter supports the NPRM, and another commenter advises that it has no objection to the NPRM. Requests To Limit the Applicability of the NPRM Several commenters request that the applicability of the NPRM be limited to those airplanes that have the Air Traffic Services Data Link (ATS DL) enabled. The commenters advise that Flight Management Computer (FMC) systems that are not equipped with the optional operational program configuration (OPC) software to enable the ATS DL will never display Air Traffic Control (ATC) clearance messages (new, old, or expired) on the control display unit (CDU). The commenters point out that without the OPC, there is not the capability to get ATC clearance messages on the CDU. Therefore, the commenters contend that the NPRM should be applicable only to those airplanes that have the ATS DL FMC option enabled. Additionally, one commenter, an operator, contends that if airplanes not using ATS DL FMC are required to upgrade the Pegasus FMC software, the operators also will be forced to upgrade their older inertial reference units (IRU) due to differences in the magnetic variation models between Pegasus 2003 and the older IRU models. The commenter explains that upgrading the IRU would be a significant increase in its costs. The FAA agrees that the requirement to replace the OPS and FIDO software of the existing FMC with Pegasus 2003 OPS and FIDO software or Pegasus 2004 OPS and FIDO software should apply only to airplanes operating with an Air Traffice Services data link function enabled. We have revised paragraph (f) of this AD to clarify the applicability of that requirement. Requests To Add Service Information Several commenters, including the manufacturer, note that since the issuance of the NPRM, Boeing has issued new service bulletins that describe replacing the existing operational program software (OPS) and flight information and data output (FIDO) software of the FMC with Pegasus 2005 OPS and FIDO software. Accomplishment of the service bulletins is intended to correct certain problems that were experienced as a result of the installation of the Pegasus 2003 OPS and FIDO software, and to add other improvements on the map displays. The commenters request that the new service bulletins be added to the NPRM E:\FR\FM\07SER1.SGM 07SER1 53054 Federal Register / Vol. 70, No. 172 / Wednesday, September 7, 2005 / Rules and Regulations as an optional method of compliance with the proposed requirements of the NPRM. We agree with the commenters’ request. We have reviewed the new service bulletins and have added them to paragraph (f) of the AD and new Table 2, Pegasus 2005 OPS and FIDO— Applicable Service Bulletins, of this AD as an optional method of compliance with the requirements of this AD. Requests To Revise Paragraph (f) of the NPRM Two commenters request that we clarify that the use of the onboard software media binder (SMB) is optional. The commenters note that the accomplishment instructions of the service bulletins referenced in the NPRM could be construed to create a regulatory requirement for the existence of the onboard SMB. We agree with the commenters’ request for the reason specified and have revised paragraph (f) of the AD to specify that replacing the existing OPS and FIDO diskettes in the software media binder is not required by this AD. Requests To Approve Later Service Bulletins Several commenters request that we revise the NPRM to permit use of future FAA-approved service bulletins to comply with the proposed requirements of the NPRM. The commenters contend that future FAA-approved service bulletins provide assurance that the software described in future bulletins would meet the required level of safety specified in the NPRM. Specifically, the commenters would like us to add the words, ‘‘or later approved versions.’’ We do not agree with the commenters’ request. When referencing a specific service bulletin in an AD, using the phrase ‘‘or later FAA-approved revisions’’ in an AD would violate the Office of the Federal Register (OFR) regulations for approving materials that are incorporated by reference. In general terms, we are required by these OFR regulations to either publish the service document contents as part of the actual AD language, or submit the service document to the OFR for approval as ‘‘referenced’’ material, in which case we may only refer to such material in the text of an AD. The AD may refer to the service document only if the OFR has approved it for ‘‘incorporation by reference.’’ To allow operators to use later revisions of a referenced document, we must either revise the AD to reference the specific later revisions, or operators may request approval to use later revisions as an alternative method of compliance (AMOC) with this AD. VerDate Aug<18>2005 15:01 Sep 06, 2005 Jkt 205001 Operators may request approval of an AMOC for this AD under the provisions of paragraph (h) of this AD. Request To Revise the Costs of Compliance Section One commenter, the manufacturer, requests that we revise the estimated number of airplanes affected from 857 in the worldwide fleet and 547 on the U.S. registry to 310 airplanes estimated for the worldwide fleet and 247 airplanes estimated for airplanes of U.S. registry. We agree with the commenter. Based on our decision to clarify the applicability of the requirements of paragraph (f) of the AD, (reference the first comment discussion, ‘‘Request to Limit the Applicability of the NPRM’’), we have revised the ‘‘Costs of Compliance’’ section of this AD to reflect the numbers specified by the commenter above. rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the Agency’s authority. We are issuing this rulemaking under the authority described in subtitle VII, part A, subpart III, section 44701, ‘‘General requirements.’’ Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. Regulatory Findings Conclusion We have carefully reviewed the available data, including the comments that have been received, and determined that air safety and the public interest require adopting the AD with the changes described previously. We have determined that these changes will neither increase the economic burden on any operator nor increase the scope of the AD. We have determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. For the reasons discussed above, I certify that this AD: (1) Is not a ‘‘significant regulatory action’’ under Executive Order 12866; (2) Is not a ‘‘significant rule’’ under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. We prepared a regulatory evaluation of the estimated costs to comply with this AD and placed it in the AD docket. See the ADDRESSES section for a location to examine the regulatory evaluation. Costs of Compliance List of Subjects in 14 CFR Part 39 There are about 310 airplanes of the affected design in the worldwide fleet. This AD will affect about 247 airplanes of U.S. registry. The required actions will take about 3 work hours per airplane, at an average labor rate of $65 per work hour. The manufacturer will provide required parts to the operators at no cost. Based on these figures, the estimated cost of this AD for U.S. operators is $48,165, or $195 per airplane. Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety. Authority for This Rulemaking Title 49 of the United States Code specifies the FAA’s authority to issue I Clarification of Error in Certain Boeing Service Bulletins We noticed a typographical error in the effectivity of Boeing Service Bulletin 767–34–0472, dated March 17, 2005, and Boeing Alert Service Bulletin 767– 34A0390, dated February 19, 2004. We have verified with the manufacturer that the effectivity of these service bulletins is intended to be for Model 767–400ER series airplanes rather than for 747– 400ER series airplanes. Therefore, the applicability of this AD is correct and remains the same as the NPRM. PO 00000 Frm 00012 Fmt 4700 Sfmt 4700 Adoption of the Amendment Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows: I PART 39—AIRWORTHINESS DIRECTIVES 1. The authority citation for part 39 continues to read as follows: Authority: 49 U.S.C. 106(g), 40113, 44701. E:\FR\FM\07SER1.SGM 07SER1 Federal Register / Vol. 70, No. 172 / Wednesday, September 7, 2005 / Rules and Regulations § 39.13 767–200, –300, –300F, and –400ER series airplanes; certificated in any category; equipped with a Pegasus flight management computer (FMC) system. [Amended] 2. The Federal Aviation Administration (FAA) amends § 39.13 by adding the following new airworthiness directive (AD): I Affected ADs (b) None. Unsafe Condition (d) This AD was prompted by 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. We are issuing this AD to prevent the airplane from entering unauthorized airspace or following a flight path that does not provide minimum separation requirements between aircraft, and a consequent near miss or mid-air collision. Applicability (c) This AD applies to Boeing Model 757– 200 and –300 series airplanes and Model Compliance (e) You are responsible for having the actions required by this AD performed within 2005–18–09 Boeing: Amendment 39–14249. Docket No. FAA–2005–20352; Directorate Identifier 2004–NM–214–AD. Effective Date (a) This AD becomes effective October 12, 2005. 53055 the compliance times specified, unless the actions have already been done. Replacing the Operational Program Software (OPS) and Flight Information and Data Output (FIDO) Software (f) For all airplanes operating with an Air Traffic Services data link function enabled: With the exception of the work instruction to replace the existing OPS and FIDO diskettes in the software media binder, which is not required by this AD, within 18 months after the effective date of this AD, replace the OPS and 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 of this AD. TABLE 1.—PEGASUS 2003 OPS AND FIDO—APPLICABLE SERVICE BULLETINS Boeing Airplane Model Boeing Alert Service Bulletin Dated 757–200 series airplanes .................................................... 757–300 series airplanes .................................................... 767–200, –300, and –300F series airplanes ...................... 767–400ER series airplanes ............................................... 757–34A0258 ...................................................................... 757–34A0259 ...................................................................... 767–34A0389, Revision 2 ................................................... 767–34A0390 ...................................................................... February 12, 2004. February 12, 2004. December 16, 2004. February 19, 2004. TABLE 2.—PEGASUS 2005 OPS AND FIDO—APPLICABLE SERVICE BULLETINS Boeing Airplane Model Boeing Service Bulletin 757–200 series airplanes .......................................................................................................................... 757–300 series airplanes .......................................................................................................................... 767–200, –300, and –300F series airplanes ............................................................................................ 767–400ER series airplanes ..................................................................................................................... 757–34–0324 757–34–0325 767–34–0471 767–34–0472 Acceptable for Compliance (g) Accomplishment of Boeing Alert Service Bulletin 767–34A0389, dated February 19, 2004; or Revision 1, dated September 16, 2004, before the effective date of this AD, is an acceptable method of compliance with the requirements of this AD. Alternative Methods of Compliance (AMOCs) (h) The Manager, Seattle Aircraft Certification Office (ACO), FAA, has the authority to approve AMOCs for this AD, if requested in accordance with the procedures found in 14 CFR 39.19. Material Incorporated by Reference (i) You must use the applicable service bulletin in Table 3 of this AD to perform the actions that are required by this AD, unless the AD specifies otherwise. The Director of the Federal Register approved the incorporation by reference of these documents in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. Contact Boeing Commercial Airplanes, P.O. Box 3707, Dated March March March March 17, 17, 17, 17, 2005. 2005. 2005. 2005. Seattle, Washington 98124–2207, for a copy of this service information. You may review copies at the Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street SW., Room PL–401, Nassif Building, Washington, DC; on the internet at http://dms.dot.gov; or at the National Archives and Records Administration (NARA). For information on the availability of this material at the NARA, call (202) 741– 6030, or go to http://www.archives.gov/ federal_register/code_of_federal_regulations/ ibr_locations.html. TABLE 3.—MATERIAL INCORPORATED BY REFERENCE Service Bulletin Boeing Boeing Boeing Boeing Boeing Boeing Boeing Boeing Revision level Alert Service Bulletin 757–34A0258 ........................................................................................ Alert Service Bulletin 757–34A0259 ........................................................................................ Alert Service Bulletin 767–34A0389 ........................................................................................ Alert Service Bulletin 767–34A0390 ........................................................................................ Service Bulletin 757–34–0324 ................................................................................................. Service Bulletin 757–34–0325 ................................................................................................. Service Bulletin 767–34–0471 ................................................................................................. Service Bulletin 767–34–0472 ................................................................................................. VerDate Aug<18>2005 15:01 Sep 06, 2005 Jkt 205001 PO 00000 Frm 00013 Fmt 4700 Sfmt 4700 Original .............. Original .............. 2 ......................... Original .............. Original .............. Original .............. Original .............. Original .............. E:\FR\FM\07SER1.SGM 07SER1 Date February 12, 2004. February 12, 2004. December 16, 2004. February 19, 2004. March 17, 2005. March 17, 2005. March 17, 2005. March 17, 2005. 53056 Federal Register / Vol. 70, No. 172 / Wednesday, September 7, 2005 / Rules and Regulations Issued in Renton, Washington, on August 29, 2005. Kalene C. Yanamura, Acting Manager, Transport Airplane Directorate, Aircraft Certification Service. [FR Doc. 05–17607 Filed 9–6–05; 8:45 am] BILLING CODE 4910–13–P DEPARTMENT OF TRANSPORTATION Federal Aviation Administration 14 CFR Part 39 [Docket No. FAA–2005–22308; Directorate Identifier 2005–NM–160–AD; Amendment 39–14255; AD 2005–18–15] RIN 2120–AA64 Discussion Airworthiness Directives; Dassault Model Falcon 2000EX Airplanes Federal Aviation Administration (FAA), Department of Transportation (DOT). ACTION: Final rule; request for comments. AGENCY: SUMMARY: The FAA is adopting a new airworthiness directive (AD) for certain Dassault Model Falcon 2000EX airplanes. This AD requires revising the airplane flight manual (AFM) to extend runway length limits for takeoff and landing. This AD also provides for an optional terminating action for the AFM revision. This AD results from an event in which braking efficiency was temporarily lost during landing, but was recovered after the flightcrew fully released and then reapplied the brakes. We are issuing this AD to prevent a runway overrun in the event of loss of braking function, which could result in injury to passengers or flightcrew and damage to the airplane. DATES: This AD becomes effective September 22, 2005. The Director of the Federal Register approved the incorporation by reference of certain publications listed in the AD as of September 22, 2005. We must receive comments on this AD by November 7, 2005. ADDRESSES: Use one of the following addresses to submit comments on this AD. • DOT Docket Web site: Go to http://dms.dot.gov and follow the instructions for sending your comments electronically. • Government-wide rulemaking Web site: Go to http://www.regulations.gov and follow the instructions for sending your comments electronically. • Mail: Docket Management Facility; U.S. Department of Transportation, 400 Seventh Street SW., Nassif Building, Room PL–401, Washington, DC 20590. VerDate Aug<18>2005 15:01 Sep 06, 2005 Jkt 205001 • Fax: (202) 493–2251. • Hand Delivery: Room PL–401 on the plaza level of the Nassif Building, 400 Seventh Street SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. Contact Dassault Falcon Jet, P.O. Box 2000, South Hackensack, New Jersey 07606, for service information identified in this AD. FOR FURTHER INFORMATION CONTACT: Tom Rodriguez, Aerospace Engineer, International Branch, ANM–116, FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington 98055–4056; telephone (425) 227–1137; fax (425) 227–1149. SUPPLEMENTARY INFORMATION: ´ ´ The Direction Generale de l’Aviation Civile (DGAC), which is the airworthiness authority for France, notified us that an unsafe condition may exist on certain Dassault Model Falcon 2000EX airplanes. The DGAC advises us that an event occurred in which braking efficiency was temporarily lost during landing, but was recovered after the flightcrew fully released and then reapplied the brakes. This event has been attributed to improper communication of acceleration information between the inertial reference system (IRS) and the brake system control unit (BSCU). This condition, if not corrected, could result in a runway overrun in the event of loss of braking function, which could result in injury to passengers or flightcrew and damage to the airplane. Relevant Service Information Dassault has issued Temporary Change (TC) 17, dated July 26, 2005, to the Dassault Falcon 2000EX EASy Airplane Flight Manual, DGT88898. The TC describes procedures for revising the Limitations and Performance sections of the airplane flight manual (AFM) to extend runway length limits for takeoff and landing. The procedures include maximum allowable weights and field length limits for takeoff and landing. Dassault has also issued Service Bulletin F2000EX–80, dated May 11, 2005. The service bulletin describes procedures for modifying the wiring that links the IRS to the BCSU. The modification establishes a direct wiring link between the IRS and the BSCU, which makes the braking function fully independent of the enhanced avionics system. Accomplishing the modification terminates the AFM revision. We have determined that accomplishing the actions specified in the TC will adequately address the PO 00000 Frm 00014 Fmt 4700 Sfmt 4700 unsafe condition. The DGAC mandated the TC and issued French emergency airworthiness directive UF–2005–140, dated July 26, 2005, to ensure the continued airworthiness of these airplanes in France. FAA’s Determination and Requirements of This AD This airplane model is manufactured in France and is type certificated for operation in the United States under the provisions of section 21.29 of the Federal Aviation Regulations (14 CFR 21.29) and the applicable bilateral airworthiness agreement. Pursuant to this bilateral airworthiness agreement, the DGAC has kept the FAA informed of the situation described above. We have examined the DGAC’s findings, evaluated all pertinent information, and determined that we need to issue an AD for products of this type design that are certificated for operation in the United States. Therefore, we are issuing this AD to prevent a runway overrun in the event of loss of braking function, which could result in injury to passengers or flightcrew and damage to the airplane. This AD requires accomplishing the actions specified in the TC described previously, except as discussed under ‘‘Differences Among this AD, French Emergency Airworthiness Directive, and TC.’’ This AD also provides for an optional terminating action for the AFM revision. Differences Among This AD, French Emergency Airworthiness Directive, and TC Although the French emergency airworthiness directive specifies a compliance time of before the next flight after the effective date of the French emergency airworthiness directive for the AFM revision, we specify a compliance time of 10 days after the effective date of this AD. We find that this will prevent airplanes from being grounded unnecessarily without adversely affecting the safety of the airplanes. The French emergency airworthiness directive requires accomplishing the terminating action before December 31, 2006. This AD will provide for doing the terminating action as an option, and we may consider further rulemaking to require the terminating action. Interim Action We consider this AD interim action. We are currently considering requiring the modification of the wiring that links the IRS to the BSCU, which would terminate the AFM revision required by this AD. However, the planned E:\FR\FM\07SER1.SGM 07SER1

Agencies

[Federal Register Volume 70, Number 172 (Wednesday, September 7, 2005)]
[Rules and Regulations]
[Pages 53053-53056]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: 05-17607]


-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 39

[Docket No. FAA-2005-20352; Directorate Identifier 2004-NM-214-AD; 
Amendment 39-14249; AD 2005-18-09]
RIN 2120-AA64


Airworthiness Directives; Boeing Model 757-200 and -300 Series 
Airplanes and Model 767 Series Airplanes

AGENCY: Federal Aviation Administration (FAA), Department of 
Transportation (DOT).

ACTION: Final rule.

-----------------------------------------------------------------------

SUMMARY: The FAA is adopting a new airworthiness directive (AD) for 
certain Boeing Model 757-200 and -300 series airplanes and Model 767 
series airplanes. This AD requires replacing the existing operational 
software of the Pegasus flight management computer (FMC) system with 
new, improved operational software. This AD results from 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. We are issuing this AD to prevent display of 
``old'' or expired ATC clearance messages on the CDU of subsequent 
flights, which could result in the airplane entering unauthorized 
airspace or following a flight path that does not provide minimum 
separation requirements between aircraft, and a consequent near miss or 
a mid-air collision.

DATES: Effective October 12, 2005.
    The Director of the Federal Register approved the incorporation by 
reference of certain publications listed in the AD as of October 12, 
2005.

ADDRESSES: You may examine the AD docket on the Internet at http://
dms.dot.gov or in person at the Docket Management Facility, U.S. 
Department of Transportation, 400 Seventh Street, SW., Nassif Building, 
Room PL-401, Washington, DC.
    Contact Boeing Commercial Airplanes, P.O. Box 3707, Seattle, 
Washington 98124-2207, for service information identified in this AD.

FOR FURTHER INFORMATION CONTACT: Samuel Slentz, Aerospace Engineer, 
Systems and Equipment Branch, ANM-130S, FAA, Seattle Aircraft 
Certification Office, 1601 Lind Avenue, SW., Renton, Washington 98055-
4056; telephone (425) 917-6483; fax (425) 917-6590.

SUPPLEMENTARY INFORMATION:

Examining the Docket

    You may examine the AD docket on the Internet at http://dms.dot.gov 
or in person at the Docket Management Facility office between 9 a.m. 
and 5 p.m., Monday through Friday, except Federal holidays. The Docket 
Management Facility office (telephone (800) 647-5227) is located on the 
plaza level of the Nassif Building at the street address stated in the 
ADDRESSES section.

Discussion

    The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 
CFR part 39 to include an AD that would apply to certain Boeing Model 
757-200 and -300 series airplanes and Model 767 series airplanes. That 
NPRM was published in the Federal Register on February 15, 2005 (70 FR 
7676). That NPRM proposed to require replacing the existing operational 
software of the Pegasus flight management computer (FMC) system with 
new, improved operational software.

Comments

    We provided the public the opportunity to participate in the 
development of this AD. We have considered the comments that have been 
received on the NPRM.

Supportive or No Objection Comments for the NPRM

    One commenter supports the NPRM, and another commenter advises that 
it has no objection to the NPRM.

Requests To Limit the Applicability of the NPRM

    Several commenters request that the applicability of the NPRM be 
limited to those airplanes that have the Air Traffic Services Data Link 
(ATS DL) enabled. The commenters advise that Flight Management Computer 
(FMC) systems that are not equipped with the optional operational 
program configuration (OPC) software to enable the ATS DL will never 
display Air Traffic Control (ATC) clearance messages (new, old, or 
expired) on the control display unit (CDU). The commenters point out 
that without the OPC, there is not the capability to get ATC clearance 
messages on the CDU. Therefore, the commenters contend that the NPRM 
should be applicable only to those airplanes that have the ATS DL FMC 
option enabled. Additionally, one commenter, an operator, contends that 
if airplanes not using ATS DL FMC are required to upgrade the Pegasus 
FMC software, the operators also will be forced to upgrade their older 
inertial reference units (IRU) due to differences in the magnetic 
variation models between Pegasus 2003 and the older IRU models. The 
commenter explains that upgrading the IRU would be a significant 
increase in its costs.
    The FAA agrees that the requirement to replace the OPS and FIDO 
software of the existing FMC with Pegasus 2003 OPS and FIDO software or 
Pegasus 2004 OPS and FIDO software should apply only to airplanes 
operating with an Air Traffice Services data link function enabled. We 
have revised paragraph (f) of this AD to clarify the applicability of 
that requirement.

Requests To Add Service Information

    Several commenters, including the manufacturer, note that since the 
issuance of the NPRM, Boeing has issued new service bulletins that 
describe replacing the existing operational program software (OPS) and 
flight information and data output (FIDO) software of the FMC with 
Pegasus 2005 OPS and FIDO software. Accomplishment of the service 
bulletins is intended to correct certain problems that were experienced 
as a result of the installation of the Pegasus 2003 OPS and FIDO 
software, and to add other improvements on the map displays. The 
commenters request that the new service bulletins be added to the NPRM

[[Page 53054]]

as an optional method of compliance with the proposed requirements of 
the NPRM.
    We agree with the commenters' request. We have reviewed the new 
service bulletins and have added them to paragraph (f) of the AD and 
new Table 2, Pegasus 2005 OPS and FIDO--Applicable Service Bulletins, 
of this AD as an optional method of compliance with the requirements of 
this AD.

Requests To Revise Paragraph (f) of the NPRM

    Two commenters request that we clarify that the use of the onboard 
software media binder (SMB) is optional. The commenters note that the 
accomplishment instructions of the service bulletins referenced in the 
NPRM could be construed to create a regulatory requirement for the 
existence of the onboard SMB.
    We agree with the commenters' request for the reason specified and 
have revised paragraph (f) of the AD to specify that replacing the 
existing OPS and FIDO diskettes in the software media binder is not 
required by this AD.

Requests To Approve Later Service Bulletins

    Several commenters request that we revise the NPRM to permit use of 
future FAA-approved service bulletins to comply with the proposed 
requirements of the NPRM. The commenters contend that future FAA-
approved service bulletins provide assurance that the software 
described in future bulletins would meet the required level of safety 
specified in the NPRM. Specifically, the commenters would like us to 
add the words, ``or later approved versions.''
    We do not agree with the commenters' request. When referencing a 
specific service bulletin in an AD, using the phrase ``or later FAA-
approved revisions'' in an AD would violate the Office of the Federal 
Register (OFR) regulations for approving materials that are 
incorporated by reference. In general terms, we are required by these 
OFR regulations to either publish the service document contents as part 
of the actual AD language, or submit the service document to the OFR 
for approval as ``referenced'' material, in which case we may only 
refer to such material in the text of an AD. The AD may refer to the 
service document only if the OFR has approved it for ``incorporation by 
reference.'' To allow operators to use later revisions of a referenced 
document, we must either revise the AD to reference the specific later 
revisions, or operators may request approval to use later revisions as 
an alternative method of compliance (AMOC) with this AD. Operators may 
request approval of an AMOC for this AD under the provisions of 
paragraph (h) of this AD.

Request To Revise the Costs of Compliance Section

    One commenter, the manufacturer, requests that we revise the 
estimated number of airplanes affected from 857 in the worldwide fleet 
and 547 on the U.S. registry to 310 airplanes estimated for the 
worldwide fleet and 247 airplanes estimated for airplanes of U.S. 
registry.
    We agree with the commenter. Based on our decision to clarify the 
applicability of the requirements of paragraph (f) of the AD, 
(reference the first comment discussion, ``Request to Limit the 
Applicability of the NPRM''), we have revised the ``Costs of 
Compliance'' section of this AD to reflect the numbers specified by the 
commenter above.

Clarification of Error in Certain Boeing Service Bulletins

    We noticed a typographical error in the effectivity of Boeing 
Service Bulletin 767-34-0472, dated March 17, 2005, and Boeing Alert 
Service Bulletin 767-34A0390, dated February 19, 2004. We have verified 
with the manufacturer that the effectivity of these service bulletins 
is intended to be for Model 767-400ER series airplanes rather than for 
747-400ER series airplanes. Therefore, the applicability of this AD is 
correct and remains the same as the NPRM.

Conclusion

    We have carefully reviewed the available data, including the 
comments that have been received, and determined that air safety and 
the public interest require adopting the AD with the changes described 
previously. We have determined that these changes will neither increase 
the economic burden on any operator nor increase the scope of the AD.

Costs of Compliance

    There are about 310 airplanes of the affected design in the 
worldwide fleet. This AD will affect about 247 airplanes of U.S. 
registry. The required actions will take about 3 work hours per 
airplane, at an average labor rate of $65 per work hour. The 
manufacturer will provide required parts to the operators at no cost. 
Based on these figures, the estimated cost of this AD for U.S. 
operators is $48,165, or $195 per airplane.

Authority for This Rulemaking

    Title 49 of the United States Code specifies the FAA's authority to 
issue rules on aviation safety. Subtitle I, section 106, describes the 
authority of the FAA Administrator. Subtitle VII, Aviation Programs, 
describes in more detail the scope of the Agency's authority.
    We are issuing this rulemaking under the authority described in 
subtitle VII, part A, subpart III, section 44701, ``General 
requirements.'' Under that section, Congress charges the FAA with 
promoting safe flight of civil aircraft in air commerce by prescribing 
regulations for practices, methods, and procedures the Administrator 
finds necessary for safety in air commerce. This regulation is within 
the scope of that authority because it addresses an unsafe condition 
that is likely to exist or develop on products identified in this 
rulemaking action.

Regulatory Findings

    We have determined that this AD will not have federalism 
implications under Executive Order 13132. This AD will not have a 
substantial direct effect on the States, on the relationship between 
the national government and the States, or on the distribution of power 
and responsibilities among the various levels of government.
    For the reasons discussed above, I certify that this AD:
    (1) Is not a ``significant regulatory action'' under Executive 
Order 12866;
    (2) Is not a ``significant rule'' under DOT Regulatory Policies and 
Procedures (44 FR 11034, February 26, 1979); and
    (3) Will not have a significant economic impact, positive or 
negative, on a substantial number of small entities under the criteria 
of the Regulatory Flexibility Act.
    We prepared a regulatory evaluation of the estimated costs to 
comply with this AD and placed it in the AD docket. See the ADDRESSES 
section for a location to examine the regulatory evaluation.

List of Subjects in 14 CFR Part 39

    Air transportation, Aircraft, Aviation safety, Incorporation by 
reference, Safety.

Adoption of the Amendment

0
Accordingly, under the authority delegated to me by the Administrator, 
the FAA amends 14 CFR part 39 as follows:

PART 39--AIRWORTHINESS DIRECTIVES

0
1. The authority citation for part 39 continues to read as follows:

    Authority: 49 U.S.C. 106(g), 40113, 44701.

[[Page 53055]]

Sec.  39.13  [Amended]

0
2. The Federal Aviation Administration (FAA) amends Sec.  39.13 by 
adding the following new airworthiness directive (AD):

2005-18-09 Boeing: Amendment 39-14249. Docket No. FAA-2005-20352; 
Directorate Identifier 2004-NM-214-AD.

Effective Date

    (a) This AD becomes effective October 12, 2005.

Affected ADs

    (b) None.

Applicability

    (c) This AD applies to Boeing Model 757-200 and -300 series 
airplanes and Model 767-200, -300, -300F, and -400ER series 
airplanes; certificated in any category; equipped with a Pegasus 
flight management computer (FMC) system.

Unsafe Condition

    (d) This AD was prompted by 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. We are issuing this AD to prevent the airplane from 
entering unauthorized airspace or following a flight path that does 
not provide minimum separation requirements between aircraft, and a 
consequent near miss or mid-air collision.

Compliance

    (e) You are responsible for having the actions required by this 
AD performed within the compliance times specified, unless the 
actions have already been done.

Replacing the Operational Program Software (OPS) and Flight Information 
and Data Output (FIDO) Software

    (f) For all airplanes operating with an Air Traffic Services 
data link function enabled: With the exception of the work 
instruction to replace the existing OPS and FIDO diskettes in the 
software media binder, which is not required by this AD, within 18 
months after the effective date of this AD, replace the OPS and 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 
of this AD.

                        Table 1.--Pegasus 2003 OPS and FIDO--Applicable Service Bulletins
----------------------------------------------------------------------------------------------------------------
                                               Boeing Alert Service
          Boeing Airplane Model                      Bulletin                             Dated
----------------------------------------------------------------------------------------------------------------
757-200 series airplanes.................  757-34A0258................  February 12, 2004.
757-300 series airplanes.................  757-34A0259................  February 12, 2004.
767-200, -300, and -300F series airplanes  767-34A0389, Revision 2....  December 16, 2004.
767-400ER series airplanes...............  767-34A0390................  February 19, 2004.
----------------------------------------------------------------------------------------------------------------


                        Table 2.--Pegasus 2005 OPS and FIDO--Applicable Service Bulletins
----------------------------------------------------------------------------------------------------------------
                                                     Boeing
             Boeing Airplane Model                   Service                          Dated
                                                    Bulletin
----------------------------------------------------------------------------------------------------------------
757-200 series airplanes.......................     757-34-0324  March 17, 2005.
757-300 series airplanes.......................     757-34-0325  March 17, 2005.
767-200, -300, and -300F series airplanes......     767-34-0471  March 17, 2005.
767-400ER series airplanes.....................     767-34-0472  March 17, 2005.
----------------------------------------------------------------------------------------------------------------

Acceptable for Compliance

    (g) Accomplishment of Boeing Alert Service Bulletin 767-34A0389, 
dated February 19, 2004; or Revision 1, dated September 16, 2004, 
before the effective date of this AD, is an acceptable method of 
compliance with the requirements of this AD.

Alternative Methods of Compliance (AMOCs)

    (h) The Manager, Seattle Aircraft Certification Office (ACO), 
FAA, has the authority to approve AMOCs for this AD, if requested in 
accordance with the procedures found in 14 CFR 39.19.

Material Incorporated by Reference

    (i) You must use the applicable service bulletin in Table 3 of 
this AD to perform the actions that are required by this AD, unless 
the AD specifies otherwise. The Director of the Federal Register 
approved the incorporation by reference of these documents in 
accordance with 5 U.S.C. 552(a) and 1 CFR part 51. Contact Boeing 
Commercial Airplanes, P.O. Box 3707, Seattle, Washington 98124-2207, 
for a copy of this service information. You may review copies at the 
Docket Management Facility, U.S. Department of Transportation, 400 
Seventh Street SW., Room PL-401, Nassif Building, Washington, DC; on 
the internet at http://dms.dot.gov; or at the National Archives and 
Records Administration (NARA). For information on the availability 
of this material at the NARA, call (202) 741-6030, or go to http://
www.archives.gov/federal_register/code_of_federal_regulations/
ibr_locations.html.

                                  Table 3.--Material Incorporated by Reference
----------------------------------------------------------------------------------------------------------------
            Service Bulletin                      Revision level                           Date
----------------------------------------------------------------------------------------------------------------
Boeing Alert Service Bulletin 757-       Original.......................  February 12, 2004.
 34A0258.
Boeing Alert Service Bulletin 757-       Original.......................  February 12, 2004.
 34A0259.
Boeing Alert Service Bulletin 767-       2..............................  December 16, 2004.
 34A0389.
Boeing Alert Service Bulletin 767-       Original.......................  February 19, 2004.
 34A0390.
Boeing Service Bulletin 757-34-0324....  Original.......................  March 17, 2005.
Boeing Service Bulletin 757-34-0325....  Original.......................  March 17, 2005.
Boeing Service Bulletin 767-34-0471....  Original.......................  March 17, 2005.
Boeing Service Bulletin 767-34-0472....  Original.......................  March 17, 2005.
----------------------------------------------------------------------------------------------------------------



[[Page 53056]]

    Issued in Renton, Washington, on August 29, 2005.
Kalene C. Yanamura,
Acting Manager, Transport Airplane Directorate, Aircraft Certification 
Service.
[FR Doc. 05-17607 Filed 9-6-05; 8:45 am]
BILLING CODE 4910-13-P