|
| Title: | Takeoff from closed runway, Boeing 777-223ER, Chicago O'Hare, April 25, 2000 |
| Micro summary: | This Boeing 777-223ER took off from a closed runway. |
| Event Time: | 2000-04-25 at 0928 CDT |
| File Name: | 2000-04-25-US.pdf |
| Publishing Agency: | National Transportation Safety Board (NTSB) |
| Publishing Country: | USA |
| Report number: | CHI00IA125 |
| Pages: | 5 |
| Site of event: | Chicago, IL |
| Departure: | O'Hare International Airport, Chicago, Illinois, USA |
| Destination: | London Heathrow Airport, London, England, United Kingdom |
| Airplane Type(s): | Boeing 777-223ER |
| Flight Phase: | Takeoff |
| Registration(s): | N779AN |
| Operator(s): | American Airlines |
| Type of flight: | Revenue |
| Occupants: | 167 |
| Fatalities: | 0 |
| Serious Injuries: | 0 |
| Minor/Non-Injured: | 167 |
| Other Injuries: | 0 |
| Executive Summary: | NTSB short summary: 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. NTSB synopsis: 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." NTSB factual narrative text: 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.) |
| Learning Keywords: | Operations - Airspace - Air Traffic Control |
| Operations - Wrong Runway |
Accident Reports on DVD, Copyright © 2006 by Flight Simulation Systems, LLC. All Rights Reserved. All referenced trademarks are the property of their respective owners.www.fss.aero