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

Embraer EMB-135KL and Beech 300 incident near Chicago, Illinois, April 22, 2010

On April 22, 2010 at about 2:53 am local time, 2 aircraft, Embraer EMB-135KL (N806AE) and Beech 300 (N71), were involved in the same incident near Chicago, Illinois. The NTSB record does not give the injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The air traffic controller's issuance of an improper takeoff clearance to the pilot of the Embraer. Contributing to the incident was the instructor’s inadequate monitoring of the trainee local controller.
The air traffic controller's issuance of an improper takeoff clearance to the pilot of the Embraer. Contributing to the incident was the instructor’s inadequate monitoring of the trainee local controller.

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

What the record shows

Date
April 22, 2010 · about 2:53 am local time · cases in 2010
Place
Chicago, Illinois · map
Type
Incident
Injuries
The NTSB record does not give the injuries.
Weather
visual conditions (good weather)
Aircraft 1
Embraer EMB-135KL · all EMB-135KLs on the register
Registration
N806AE · registry record · serial 145503
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)
Aircraft 2
Beech 300 · all 300s on the register
Registration
N71 · registry record · serial FF-6
Damage
Not recorded
Flight
Public-use flight (federal) · public-use (government) rules

The NTSB's narrative for the Embraer EMB-135KL final · quoted from the NTSB record

An operational error occurred when an Embraer regional jet departing from runway 9R conflicted with a Raytheon-Beech King Air conducting a navigational flight check of equipment associated with runway 32. Both airplanes were receiving air traffic control services and were operating in Class B airspace. The control position handling the two airplanes was being operated by a trainee controller and an instructor. The trainee issued an improper takeoff clearance and departure heading to the regional jet that caused it to conflict with the King Air. The instructor did not notice the error and failed to intervene to prevent the loss of separation.

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 Beech 300 final · quoted from the NTSB record

An operational error occurred when an Embraer regional jet departing from runway 9R conflicted with a Raytheon-Beech King Air conducting a navigational flight check of equipment associated with runway 32. Both airplanes were receiving air traffic control services and were operating in Class B airspace. The control position handling the two airplanes was being operated by a trainee controller and an instructor. The trainee issued an improper takeoff clearance and departure heading to the regional jet that caused it to conflict with the King Air. The instructor did not notice the error and failed to intervene to prevent the loss of separation.

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-135KL from the NTSB's investigation tables, in plain English

What happened, in order

  1. Near midair/TCAS alert/loss of separation during initial climb defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action performance › ATC personnel
  • factor Organizational issues › Support/oversight/monitoring › Oversight › Oversight of personnel › ATC

The aircraft

  • Seats: 37
  • Landing gear: fixed
  • Engine 1: Rolls-Royc AE3007 SER (turbojet); 0 hours total
  • Engine 2: Rolls-Royc AE3007 SER (turbojet); 0 hours total
  • Operator: American Eagle Airlines INC

The flight

  • Departed from: Chicago IL
  • Destination: KLIT Little Rock AR
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Visibility: 10 statute miles
  • Sky: overcast at 9,000 ft
  • Temperature: 43°F (6°C), dew point 34°F (1°C)
  • Altimeter: 29.87 inHg
  • Observation at 2:53 am from KORD

The factual record for the Beech 300 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Near midair/TCAS alert/loss of separation during approach (VFR go-around) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action performance › ATC personnel
  • factor Organizational issues › Support/oversight/monitoring › Oversight › Oversight of personnel › ATC

The aircraft

  • Seats: 19
  • Landing gear: fixed
  • Engine 1: P&W PT6A SER (turboprop); 0 hours total
  • Engine 2: P&W PT6A SER (turboprop); 0 hours total

The flight

  • Departed from: Chicago IL
  • Destination: Chicago IL
  • Flight plan: not recorded
  • A second pilot was aboard

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/OPS10IA155.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.