Boeing 737-400 incident near Fort Lauderdale, Florida, November 9, 2005
On November 9, 2005 at about 11:26 pm local time, a Boeing 737-400, registered UNKNOWN, was involved in an incident near Fort Lauderdale, Florida (Fort Lauderdale-Hollywood Itl airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
the local controller's failure to monitor the operation and recognize a developing traffic conflict which resulted in a loss of separation between USA1251 and ComAir 5026. Contributing to the accident was the controller's incorrect prioritization of his workload.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 9, 2005 · about 11:26 pm local time
- Place
- Fort Lauderdale, Florida · Fort Lauderdale-Hollywood Itl · map
- Type
- Incident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Boeing 737-400 · all 737-400s on the register
- Registration
- UNKNOWN · no longer on the register
- Damage
- Not recorded
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative final · quoted from the NTSB record
The pilot of Comair flight 5026 (COM26), a Canadair Regional Jet, reported a near-collision with US Airways flight 1251 (USA1251), a Boeing 737-400. At the time of the incident, COM26 was holding in takeoff position on runway 9L, and USA1251 was on approach to runway 9L. USA1251 contacted the Fort Lauderdale (FLL) tower at 2342, and was cleared to land on runway 9L. The local controller advised that there would be several departures before USA1251's arrival, and the pilot acknowledged. At 2342:48, the controller cleared a Southwest flight for takeoff and instructed Comair 716 (COM716) to taxi into position and hold, advising the pilot that there was arrival traffic on 9-mile final. At 2343:52, the controller cleared COM716 for takeoff and instructed COM26 to taxi into position and hold on runway 9L, advising the pilot of COM26 that there was arrival traffic on 4-mile final. At 2344:46, COM716 was instructed to contact departure control. At 2344:52, the controller advised an arriving Gulfstream jet that they were number 2 for the runway, following a 737 on 2-mile final. At 2345:15, the controller began a series of exchanges with a helicopter that was 38 miles from FLL and trying to contact Miami approach control. At 2345:48, USA1251 asked if they were cleared to land; the controller responded, "USA1251 cleared to land runway 9L." Immediately, an unidentified voice on the frequency stated, "Traffic on 9 left." The controller transmitted, "USAir go around, USAir go around, USAir 1251 go around." USA1251 did go around, and, according to recorded radar data, passed about 100 feet above COM26. After USA1251 was given back to Miami approach for resequencing, the flight returned and landed uneventfully. The LCN controller notified the tower supervisor of the incident as soon as it occurred, and she initiated a quality assurance review (QAR) that was logged in the Daily Record of Facility Operation. According to the QAR summary, the supervisor interviewed both the local and ground controllers and reviewed the tape, concluding that there was no loss of separation between USA1251 and COM26 because USA1251 was instructed to go around when approximately one mile from the runway. The pilot of COM26 filed a near midair collision report with FLL tower on the day after the incident. At the time of the incident, the Local Control North (LCN) controller was responsible for both the LCN and Local Control South (LCS) positions, and was therefore required to monitor operations on all runways. The tower is located between runways 9L and 9R, so the LCN controller was therefore required to divide his attention in opposite directions while handling aircraft on both of those runways. Runway 9L is normally used for jet traffic, and runway 9R is normally used for general aviation traffic. While USA1251 was on approach there were multiple departures and arrivals operating on runway 9L, and a Seneca waiting to depart on runway 9R. Neither aircraft was damaged, and there were no reported injuries. Weather conditions at FLL at 2253 UTC were reported as wind 060 at 12 knots, visibility 10 miles, with scattered clouds at 3,500 feet.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
The aircraft
- Landing gear: retractable
- Operator: US Airways INC
The flight
- Departed from: PIT Pittsburgh PA
- Destination: FLL Fort Lauderdale FL
- Flight plan: IFR
- Runway 9L, 9,000 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 060° at 12 knots
- Visibility: 10 statute miles
- Sky: scat at 3,500 ft
- Temperature: 75°F (24°C), dew point 63°F (17°C)
- Altimeter: 30.06 inHg
- Observation at 10:53 pm from FLL
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under UNKNOWN the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
