FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Continental Airlines Bombardier Inc DHC-8-202 incident

26 Jun 2009 · Cleveland, OH, United States

Bombardier Inc DHC-8-202 and Embraer EMB-145XR · Incident: runway incursion (vehicle, aircraft or person) during takeoff

Report a problem

Event

NTSB case
OPS09IA009
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Bombardier Inc DHC-8-202

Aircraft type
Bombardier DHC-8
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N375PH
Onboard fatalities
Unknown
Route
From Cleveland Hopkins International Airport (CLE), Cleveland, OHTo John Glenn Columbus International Airport (CMH), Columbus, OH
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway incursion (vehicle, aircraft or person)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Aircraft 2 · Embraer EMB-145XR

Aircraft type
Embraer EMB-145
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N24103
Onboard fatalities
Unknown
Route
From Cleveland Hopkins International Airport (CLE), Cleveland, OHTo Kansas City International Airport (MCI), Kansas City, MO
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Taxi · into takeoff position
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway incursion (vehicle, aircraft or person)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

On Friday, June 26, 2009, a runway incursion occurred at Cleveland /Hopkins International Airport (CLE), Cleveland, Ohio involving Continental Express (BTA) flight 2426, call sign BTA2426, an Embraer 145 and Commutair (UCA) flight 8717, a De Havilland Canada Dash 8-200 (DH8). The incident occurred during daylight visual conditions. At the time of the incident there was a developmental controller being monitored by a certified controller at the local control position.

Continental Express (BTA) flight 2426, call sign BTA2426, an Embraer 145, aircraft number N24103 was on a scheduled part 121 flight from CLE to Kansas City International Airport (MCI), Kansas City, Missouri. BTA2426 had a crew of 3, which included the pilot, first officer, a flight attendant, and 40 passengers plus 1 lap child on board. Commutair (UCA) flight 8717, a De Havilland Canada Dash 8-200 (DH8), aircraft number N375PH was on a scheduled part 121 flight from CLE to Port Columbus International Airport (CMH) Columbus, Ohio. UCA8717 had a crew of 3 which included the pilot, first officer, a flight attendant and 19 passengers on board.

At 0856, the developmental controller directed UCA8717 to taxi into position and hold on the approach end of runway 24L at CLE. BTA2426, taxied from spot 5 to runway 24R via taxiways J and S and was directed to hold short of runway 24L by the ground controller before being directed to monitor the tower local controller on frequency 120.9. Nineteen seconds after directing UCA8717 to taxi into position and hold, the developmental trainee directed BTA2426 to cross runway 24L and advised BTA2426 that UCA8717 was in position for departure. Twenty seconds after directing BTA2426 to cross runway 24L, the local control developmental trainee directed UCA8717 to fly runway heading and issued a takeoff clearance. BTA2426 had not yet crossed runway 24L. UCA8717 acknowledged the takeoff clearance followed by the controller directing another aircraft to taxi into position and hold runway 24L. BTA2426 immediately called the tower with “BTA2426 we’re holding short of 24L you gave a clearance to cross though”. The local control developmental trainee did not respond. There were no other transmissions on the local control frequency until BTA2426 transmitted 10 seconds later “you copy for BTA2426”. The local control developmental trainee responded with “BTA2426 just hold there please”.

According to the pilots of UCA8717, the tower controller instructed them to taxi into position and hold on runway 24L. As the pilot was positioning his aircraft, he noticed that a Jetlink (BTA2426) aircraft was approaching the intersection of taxiway S and runway 24L when the pilot heard the tower direct BTA2426 to cross runway 24L. Shortly thereafter, the tower issued UCA8717 a takeoff clearance. Noticing that BTA2426 had not crossed the runway but was still able to do so, the pilot of UCA8717 planned to ask the local controller about BTA2426 when BTA2426 asked the tower, “I thought I was cleared to cross”. After a few seconds of silence, the pilot of UCA8717 heard BTA2426 state that he would hold short of the runway. After observing BTA2426 hold his position, the pilot of UCA8717 commenced his takeoff roll, after which BTA2426 crossed runway 24L at taxiway S.

Eighteen seconds later, BTA2426 was directed to taxi across runway 24L and advised that traffic was holding in position. BTA2426 crossed runway 24L without incident.

CLE was on a south flow configuration landing 24L departing runway 24L/R.

Reported weather at CLE at 0851 EDT/1251 UTC was wind 270 degrees at 8 knots, visibility 10 statute miles, scattered clouds at 1,200 feet. The temperature was 24 degrees Celsius, dew point 21 degrees Celsius. The altimeter was 2980.

ATCT staffing included 4 air traffic control specialist (ATCS); a controller-in-charge (CIC) combined at the flight data/clearance delivery position (FD/CD), 1 ground controller (GC), and a local controller (LC) combined on local control 1 and 2 positions as an on the job training instructor (OJTI) monitoring a LC developmental trainee.

Probable cause

The local controller did not visually scan the runways and ensure that the E145 had crossed runway 24L prior to issuing a takeoff clearance to the DH8, did not ensure separation between the two airplanes, and did not cancel takeoff clearance for the DH8 in a timely manner.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS09IA009
Event ID
20090806X31035
Case number
OPS09IA009
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 12139503fb844833de03322d859133f1b7a4164997e3740b8478140c4a1836ec; retrieved 2026-09-13T18:15:43.319Z.