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

Embraer EMB-145EP and Cessna 172P incident near Gulfport, Mississippi, June 19, 2011

On June 19, 2011 at about 5:43 pm local time, 2 aircraft, Embraer EMB-145EP (N13929) and Cessna 172P (N54120), were involved in the same incident near Gulfport, Mississippi (Gulfport-Biloxi Interntational airport). No one was hurt; 55 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the Gulfport control tower local controller cleared two aircraft for takeoff from runways with intersecting departure flight paths without ensuring the first aircraft had passed the flight path intersection prior to clearing the second aircraft for takeoff.
the Gulfport control tower local controller cleared two aircraft for takeoff from runways with intersecting departure flight paths without ensuring the first aircraft had passed the flight path intersection prior to clearing the second aircraft for takeoff.

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

What the record shows

Date
June 19, 2011 · about 5:43 pm local time
Place
Gulfport, Mississippi · Gulfport-Biloxi Interntational · map
Type
Incident
Injuries
No one was hurt; 55 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Embraer EMB-145EP · all EMB-145EPs on the register
Registration
N13929 · no longer on the register · serial 145009
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)
Aircraft 2
Cessna 172P · all 172Ps on the register
Registration
N54120 · registry record · serial 17274884
Damage
Not recorded
Flight
Flight of an unrecorded kind · general aviation rules (Part 91)

The NTSB's narrative for the Embraer EMB-145EP final · quoted from the NTSB record

N54120, a Cessna 172, called ready for takeoff on runway 18. The tower local controller (LC) cleared the Cessna for takeoff on runway 18. Sixteen seconds later, (Jet Link) BTA2555/Embraer ERJ145 called ready for takeoff for runway 14. The LC cleared the ERJ145 for takeoff. The departure flight path of runway 18 intersects runway 14. The local controller was working the LC position combined with Ground Control (GC), Clearance Delivery (CD)/Flight Data (FD) and Controller-In-Charge (CIC) positions. The Cessna was airborne crossing taxiway Charlie when the ERJ145 passed through the intersecting flight paths airborne in front of the Cessna. Both aircraft were estimated to be at 300 feet. No traffic was issued to either aircraft by the LC. Closest proximity was estimated to be 0 feet vertically and 300 feet laterally. According to FAA Order 7110.65, Air Traffic Control, paragraph 3-9-8, Intersecting Runway Separation: a. Issue traffic information to each aircraft operating on intersecting runways. b. Separate departing aircraft from an aircraft using an intersecting runway, or runways when the flight paths intersect, by ensuring that the departure does not begin takeoff roll until one of the following exists: 1. The preceding aircraft has departed and passed the intersection, has crossed the departure runway, or is turning to avert any conflict.

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 172P final · quoted from the NTSB record

N54120, a Cessna 172, called ready for takeoff on runway 18. The tower local controller (LC) cleared the Cessna for takeoff on runway 18. Sixteen seconds later, (Jet Link) BTA2555/Embraer ERJ145 called ready for takeoff for runway 14. The LC cleared the ERJ145 for takeoff. The departure flight path of runway 18 intersects runway 14. The local controller was working the LC position combined with Ground Control (GC), Clearance Delivery (CD)/Flight Data (FD) and Controller-In-Charge (CIC) positions. The Cessna was airborne crossing taxiway Charlie when the ERJ145 passed through the intersecting flight paths airborne in front of the Cessna. Both aircraft were estimated to be at 300 feet. No traffic was issued to either aircraft by the LC. Closest proximity was estimated to be 0 feet vertically and 300 feet laterally. According to FAA Order 7110.65, Air Traffic Control, paragraph 3-9-8, Intersecting Runway Separation: a. Issue traffic information to each aircraft operating on intersecting runways. b. Separate departing aircraft from an aircraft using an intersecting runway, or runways when the flight paths intersect, by ensuring that the departure does not begin takeoff roll until one of the following exists: 1. The preceding aircraft has departed and passed the intersection, has crossed the departure runway, or is turning to avert any conflict.

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 Embraer EMB-145EP 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 › Action › Incorrect action selection › ATC personnel

Crew member

No details recorded.

The aircraft

  • Seats: 55
  • Landing gear: retractable
  • Engine 1: Rolls-Royc AE3007 SER (turbofan); 0 hours total
  • Engine 2: Rolls-Royc AE3007 SER (turbofan); 0 hours total
  • Operator: Expressjet Airlines INC

The flight

  • Departed from: GPT Gulfport MS at 5:43 pm
  • Destination: IAH Houston TX
  • Flight plan: IFR
  • Runway 14, 9,002 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 210° at 10 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 2,600 ft
  • Temperature: 91°F (33°C), dew point 72°F (22°C)
  • Altimeter: 29.97 inHg
  • Observation at 4:53 pm from GPT

Injuries

FatalSeriousMinorNone
Cabi1
Flight crew2
Passengers50

The factual record for the Cessna 172P 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 › Action › Incorrect action selection › ATC personnel

The aircraft

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

The flight

  • Departed from: GPT Gulfport MS at 5:43 pm
  • Destination: GPT Gulfport MS
  • Flight plan: VFR
  • Runway 18, 4,953 ft by 150 ft
  • A second pilot was aboard

Injuries

FatalSeriousMinorNone
Flight crew2

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.