Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

April 25, 2000 · Boeing 777-223ER · N779AN

Chicago, IL

Overview

Report Status
Final with probable cause
Event Type
Incident
Date
April 25, 2000
Injury Outcomes
No injuries (167 uninjured)
Location
Chicago, IL
Aircraft
Boeing 777-223ER
Tail Number
N779AN
Injuries
None
NTSB Number
CHI00IA125

The airplane departed from a closed runway. No injuries were reported. The first officer 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 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.

Full 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.)

Flight

Event TypeIncident
Event Time09:28 CDT
Nearest AirportO'Hare International (0nm)
Runway32R
Runway Length10003 ft
Runway Width150 ft
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBoeing 777-223ER
Tail NumberN779AN
Aircraft CategoryAir
Operating RulePart 121
Engines2
Engine TypeTurbofan
Engine DetailsRolls-Royce · TRENT/892-17 · Turbofan · 93400
Seats253

People & Injuries

Injury SummaryNo injuries (167 uninjured)
Fatal0
Serious0
Minor0
Uninjured167
Total167
Crew 1Age 59 · First Class

Conditions

ConditionsVMC
LightDaylight
Wind40° @ 10 kt, gusting 16 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point13 C
Altimeter30.00 inHg
Observation Time13:56
Weather SourceWFAC

Appendix: Source Data