FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

PSA Airlines Bombardier Inc CL-600-2B1 incident

29 May 2009 · Charlotte, NC, United States

Bombardier Inc CL-600-2B1 and Collett and Associates Pilatus PC12 · Incident: runway incursion (vehicle, aircraft or person) during takeoff

Report a problem

Event

NTSB case
OPS09IA005
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
Event fatalities
Unknown
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
Charter & commuter
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 CL-600-2B1

Aircraft type
Bombardier CL-600
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
N257PS
Operator
PSA Airlines
Onboard fatalities
Unknown
Route
From Charlotte Douglas International Airport (CLT), Charlotte, NCTo Charlotte Douglas International Airport (CLT), Charlotte, NC
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 135: Air Taxi & Commuter
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 · rejected 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 · Pilatus PC12

Aircraft type
Pilatus PC12
Category
Airplane · from aircraft type
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
N409DR
Onboard fatalities
Unknown
Route
From Charlotte Douglas International Airport (CLT), Charlotte, NCTo Coastal Carolina Regional Airport (KEWN), New Bern Craven, NC
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 91: General Aviation
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

The controller cleared PSA Airlines (JIA) flight 390, a CRJ-200, for takeoff on runway 18L. N409DR, Pilatus PC-12, was waiting to depart Runway 18L at intersection A. As required, the ground controller had written on the flight progress strip and verbally coordinated with the local controller that N409DR was requesting an intersection departure off Runway 18L at taxiway A; however; the local controller forgot about the intersection and instructed N409DR to taxi into position and hold on Runway 18L. JIA390 had already begun departure roll and had rolled approximately 1,600 feet as N409DR taxied onto the runway. The ASDE-X alerted, and as JIA390 began to slow the controller canceled the takeoff clearance. N409DR had pulled to the side of the runway when the pilot recognized what was happening. According to the Federal Aviation Administration, JIA390 stopped approximately 10 feet from N409DR. At the time of the incident the weather was visual flight rules with 9 miles visibility.

Probable cause

The Charlotte local control east controller's failure to ensure that the runway was clear prior to authorizing N409DR to enter the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS09IA005
Event ID
20090601X10341
Case number
OPS09IA005
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • 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: a915cde51ce5b99ef6d4c1a75731cb2a21b41ef6392e0e12f2607a2ba3a4e0e5; retrieved 2026-09-13T18:15:22.427Z.
  • The NTSB's operator name is blank for N257PS; the operator shown is the name the NTSB's other records give its FAA operator code, VNAA.