# NTSB CHI00IA125: Boeing 777-223ER, N779AN, Chicago, IL, April 25, 2000 - Type: NTSB incident investigation - Classification: Incident · No injuries · Incident investigation · Final report - Date: April 25, 2000, 09:28 local (14:28 UTC) - Place: Chicago, IL - Location: 41.9769° N, 87.9081° W: Placed by OpenAirDocs at CHICAGO O'HARE INTL (ORD), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=41.9769&lon=-87.9081&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 167 uninjured - Status: Completed, report September 6, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 49133 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI00IA125 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/49133/pdf - Page: https://openairdocs.org/ntsb/CHI00IA125 ## Probable cause the flightcrew not detecting the runway closure NOTAM and the Air Traffic Control personnel on the metering, ground, and local positions giving an improper clearance to taxi to a closed runway. Factors were the closed runway, ATIS information not issued by Air Traffic Control personnel, and insufficiently defined procedures of disseminating pertinent safety of flight information. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Miscellaneous/other, takeoff - airport/facilities - closed (contributing factor) - notams - not detected, flightcrew (cause) - condition(s)/step(s) insufficiently defined, atc personnel(lcl/gnd/clnc) (contributing factor) - atc clearance - improper, atc personnel(lcl/gnd/clnc) (cause) - information - not issued, atc personnel(lcl/gnd/clnc) (contributing factor) ## Analysis The airplane departed from a closed runway. No injuries were reported. The first officer's stated, "After normal preflight and gate departure. We advised metering that we were ready for taxi and would prefer 32R if available. Ground gave us clearance to taxi to 32R. Tower first had us hold short and then position and hold awaiting the departure of two aircraft from intersecting runways. We were then cleared for takeoff." The airport had issued a runway closure NOTAM. The flight's dispatch contained the NOTAM. The dispatch listed the runway status as open. ATIS did not list the runway closure. A FAA recommendation stated, "Add the suggestion to our list of good operating procedures that closure strips should not be used as departure strip runway separators. Closure strips should be placed and left in a prominent position on the podiums. ... In addition to Locals and Grounds receiving runway closure strips, both Flight Data and Ground Metering should have closure strips as well. ... Revise Flight Data, Clearance Delivery, and Ground Metering positions relief checklists to include runway closure information. Brief operational personnel that runway closures must be broadcast on the ATIS. Brief operational personnel that pilots must be informed that a runway is closed when it is requested for takeoff/landing. Brief operational supervisors of the requirement to ensure ATIS broadcasts are correct and contain pertinent information." ## Factual narrative On April 25, 2000, at 0928 central daylight time, a Boeing 777-223ER, N779AN, operated as American Airlines flight #90 to London, England, piloted by an airline transport rated captain and copilot, sustained no damage on departure from runway 32R, a closed runway, at O'Hare International Airport (ORD), Chicago, Illinois. The scheduled international 14 CFR Part 121 passenger flight was operating on an IFR flight plan. Visual meteorological conditions prevailed at the time of the incident. The 3 flight crewmembers, 12 cabin crewmembers, and 152 passengers were uninjured. The flight was originating at the time of the incident and landed at Heathrow Airport, near London, England, without further incident. O'Hare airport operations issued a Notice to Airmen (NOTAM) listed as number 0004206. The NOTAM stated "RWY [runway] 14L/32R CLSD [closed]" from 0830 to 1030 on April 25, 2000. The purpose of the runway closure was for "electrical maintenance." (See appended O'Hare airport NOTAM.) The flight's dispatch was reviewed. The dispatch's NOTAM section listed NOTAM "04/156 ORD 14L/32R CLSD WEF (ICAO contraction meaning with effect from, or effective from) 0004251330-0004251530" in it. The dispatch's ORD Field Report section indicated "14L/32R OPEN [status,] DRY [conditions, and] NORMAL [braking action]." (See appended flight dispatch.) The runway closure, advised in NOTAM 04/156, was not broadcast on ORD Automated Terminal Information Service (ATIS) Whiskey. Information Whiskey was current at the time of departure. The first officer's stated, "After normal preflight and gate departure. We advised metering that we were ready for taxi and would prefer 32R if available. Ground gave us clearance to taxi to 32R. Tower first had us hold short and then position and hold awaiting the departure of two aircraft from intersecting runways. We were then cleared for takeoff." Federal Aviation Administration (FAA) air traffic control personnel, as required by FAA Order 7110.65, did not inform the pilot that the runway was closed. The first officer stated, "Three days later we were advised that we may have taken off on a closed runway." The FAA convened an investigative team to explore the circumstances surrounding the operational error. The team developed recommendations. Excerpts of the recommendations stated, "Add the suggestion to our list of good operating procedures that closure strips should not be used as departure strip runway separators. Closure strips should be placed and left in a prominent position on the podiums. ... In addition to Locals and Grounds receiving runway closure strips, both Flight Data and Ground Metering should have closure strips as well. ... Revise Flight Data, Clearance Delivery, and Ground Metering positions relief checklists to include runway closure information. Brief operational personnel that runway closures must be broadcast on the ATIS. Brief operational personnel that pilots must be informed that a runway is closed when it is requested for takeoff/landing. Brief operational supervisors of the requirement to ensure ATIS broadcasts are correct and contain pertinent information." (See appended FAA reports.) ## Aircraft - Registration: [N779AN](https://openairdocs.org/aircraft/N779AN), registered now, S/N 29955, built 1999 (OpenAirDocs) - Reported make and model: Boeing 777-223ER - Registry model: [Boeing 777-223](https://openairdocs.org/model/boeing-777-223) (registry code 1385213) (OpenAirDocs) - Registry engine: [Rolls-Royce RB-211 series](https://openairdocs.org/engine/rolls-royce-rb-211-series) (registry code 54555, turbo-fan) (OpenAirDocs) - Category: Airplane - Serial number: 225 - Airframe hours: 4087 - Engines: Rolls-Royce TRENT/892-17 93400 lbs thrust turbo fan - Damage: No damage - Flight: Part 121 - Registered owner: American Airlines Inc. - Airworthiness certificate: Standard, Transport - Departed: ORD - Destination: LHR, LONDON, OF - Flight plan: IFR - Airport: ORD, O'Hare International, runway 32R, 10,003 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 59; airline transport; airplane ratings: multi-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; seat: left ## Weather - Conditions: Visual (VMC), Day - Wind: 40° at 10 knots, gusting 16 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 126 °F, dew point 82 °F - Altimeter: 30.00 inHg - Observed at: ORD ## Other investigations on N779AN (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CHI07LA078](https://openairdocs.org/ntsb/CHI07LA078), Feb 23, 2007: Boeing 777 (N779AN), Chicago, IL, no damage. Probable cause: An in-flight encounter with turbulence during cruise flight. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.