CEN09CA505 · Fairchild PT-19A
Fairchild PT-19A · Accident: aerodynamic stall/spin during initial climb
From 00V · Colorado Springs, CO to 00V · Colorado Springs, CO
Event
- NTSB case
- CEN09CA505
- 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
- Accident
- 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
- General aviation
- 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
Fairchild PT-19A
- Aircraft type
- Fairchild PT-19
- 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
- N54804
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 00V · Colorado Springs, COTo 00V · Colorado Springs, CO
- 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
- Initial climb
- 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
- Aerodynamic stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane departed Runway 33 (6,000 feet by 60 feet, asphalt, with a slight upslope). Witnesses reported that the airplane "never got more than about 50 feet in the air". The airplane then impacted terrain and came to rest just beyond the departure end of the runway. Fuel was present at the site and the airplane's engine and right wing had been torn from the fuselage during the accident, resulting in substantial damage. The Federal Aviation Administration inspector who responded to the accident site stated that the airplane's wooden propeller was in "splinters" and that there "didn’t appear to be any control problems". The density altitude was calculated to be 9,590 feet. The pilot failed to submit the requested NTSB form 6120.1, Pilot/Operator Accident/Incident Report.
Probable cause
The pilot's failure to maintain adequate airspeed to avoid an aerodynamic stall during a high-density altitude takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA505
- Event ID
- 20090810X01932
- Case number
- CEN09CA505
- 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, coordinates. 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: aa86e4d16f720c39f41d09b301b330b79264c94a267379d1c0fc768c1ebdef35; retrieved 2026-09-15T12:46:22.711Z.