The U.S. aircraft register, updated daily
Accidents · NTSB OPS10IA090 · Final report

Boeing 737-7H4 and Cessna 172M incident near Burbank, California, April 19, 2010

On April 19, 2010 at about 5:58 pm local time, 2 aircraft, Boeing 737-7H4 (N473WN) and Cessna 172M (N4415R), were involved in the same incident near Burbank, California (Bob Hope Airport). No one was hurt; 124 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The improper separation procedures by air traffic control.
The improper separation procedures by air traffic control.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 19, 2010 · about 5:58 pm local time
Place
Burbank, California · Bob Hope Airport · map
Type
Incident
Injuries
No one was hurt; 124 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Boeing 737-7H4 · all 737-7H4s on the register
Registration
N473WN · registry record · serial 33832
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)
Aircraft 2
Cessna 172M · all 172Ms on the register
Registration
N4415R · registry record · serial 17263163
Damage
Not recorded
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative for the Boeing 737-7H4 final · quoted from the NTSB record

A Boeing 737 (B737) was landing on runway 8 and a Cessna 172 (C172) was operating in the local touch-and-go traffic pattern when the C172, in the departure phase of a touch and go on runway 15, flew through the intersection of runway 8 in front of the B737, which was on landing rollout. According to the local controller and the controller-in-charge, they did not see the situation develop between the C172 and B737 because another aircraft, which had just departed, distracted them, and their attention was focused on the radar display, not out the tower window.

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 NTSB's narrative for the Cessna 172M final · quoted from the NTSB record

A Boeing 737 (B737) was landing on runway 8 and a Cessna 172 (C172) was operating in the local touch-and-go traffic pattern when the C172, in the departure phase of a touch and go on runway 15, flew through the intersection of runway 8 in front of the B737, which was on landing rollout. According to the local controller and the controller-in-charge, they did not see the situation develop between the C172 and B737 because another aircraft, which had just departed, distracted them, and their attention was focused on the radar display, not out the tower window.

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 for the Boeing 737-7H4 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Air traffic event during landing (landing roll) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Expectation/assumption › ATC personnel
  • cause Personnel issues › Action/decision › Action › Forgotten action/omission › ATC personnel

The aircraft

  • Seats: 140
  • Landing gear: fixed
  • Engine 1: Cfm Intl. CFM56 SERIES (turbofan); 0 hours total
  • Engine 2: Cfm Intl. CFM56 SERIES (turbofan); 0 hours total
  • Operator: Southwest Airlines

The flight

  • Departed from: KOAK Oakland CA at 5:08 pm
  • Destination: KBUR Burbank CA
  • Flight plan: not recorded
  • Runway 08, 5,802 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 130° at 7 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 68°F (20°C), dew point 48°F (9°C)
  • Observation at 5:53 pm from KBUR

Injuries

FatalSeriousMinorNone
Cabi3
Flight crew2
Passengers119

The factual record for the Cessna 172M from the NTSB's investigation tables, in plain English

What happened, in order

  1. Air traffic event during takeoff defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Expectation/assumption › ATC personnel
  • cause Personnel issues › Action/decision › Action › Forgotten action/omission › ATC personnel

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming 0-320 SERIES; 0 hours total

The flight

  • Departed from: KBUR Burbank CA
  • Destination: KVNY Van Nuys CA
  • Flight plan: not recorded
  • Runway 15, 6,885 ft by 150 ft

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.

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.