Casualties unknown

2006-03-23: Boeing 737-300 (N309UA) — United Air Lines Inc — Chicago, IL

Chicago, IL, US

On March 23, 2006, a Boeing 737-300 (registration N309UA) operated by United Air Lines Inc was involved in an aviation accident near Chicago, IL. Investigators recorded the probable cause as: The probable cause of this incident was the ORD tower local controller's failure to provide sufficient separation between two aircraft departing intersecting runways. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 13 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 1781061362Data APIEditorial standards
Boeing 737-300
Photo: San Diego Air & Space Museum Archives / Public domain, via Wikimedia Commons

On March 23, 2006, a runway incursion occurred when UAL604 was cleared for takeoff while UAL1520 was crossing the runway. The UAL604 crew aborted the takeoff, avoiding collision with closest proximity of about 600 feet.

Incident Overview

On March 23, 2006, at 0907 Central Standard Time, a runway incursion took place at Chicago O'Hare International Airport (ORD) during daylight visual meteorological conditions. The incident involved United Airlines (UAL) flight 604, a Boeing 737-300, and UAL1520, an Airbus A-320.

Sequence of Events

The north local controller cleared UAL604 for takeoff from runway 4L. At the same time, UAL1520 was crossing that runway. The co-pilot of UAL604 observed the A-320 moving rapidly toward the runway and aborted the takeoff. The co-pilot then informed the controller that they were aborting the takeoff because of the crossing traffic. According to the co-pilot, the aircraft did not exceed taxi speed during the aborted departure.

Separation and System Status

Separation between the two aircraft was lost, with the closest proximity being approximately 600 feet—the distance from the approach end of runway 4L to taxiway H. The Airport Movement Area Safety System (AMASS) did not activate during the incident.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20060411X00417. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.