FTW92LA206 · Cessna T-210N
King Aircraft Sales Cessna T-210N · Accident: loss of control in flight during initial climb
From Palestine Municipal Airport (PSN) to Palestine Municipal Airport (PSN)
Event
- NTSB case
- FTW92LA206
- 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
- 0
- 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
Cessna T-210N
- Aircraft type
- Cessna T-210
- 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
- N79MM
- Operator
- King Aircraft Sales
- Onboard fatalities
- Unknown
- Route
- From Palestine Municipal Airport (PSN)To Palestine Municipal Airport (PSN)
- 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
- First occurrenceThe 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Checklist, disregarded
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE TAXIED OUT FROM THE RAMP ONTO THE RUNWAY AND INITIATED A TAKEOFF WITHOUT CLEARING OR DOING A RUN UP, CAUSING ANOTHER AIRPLANE BACK TAXIING DOWN THE RUNWAY TO EXIT ONTO THE GRASS. THE DISPLACED PILOT STATED THAT THE ACCIDENT PILOT WAS PUTTING ON HIS SHOULDER HARNESS AS HE WENT BY. PILOT WITNESSES STATED THAT THE TAKEOFF WAS INITIATED WITH THE FLAPS EXTENDED IN EXCESS OF 20 DEGREES AND THAT AFTER LIFTOFF THE AIRPLANE MUSHED BACK INTO THE GROUND. THE AIRPLANE IMPACTED 78 FEET BEYOND THE END OF THE RUNWAY IN A TAIL LOW ATTITUDE WITH THE GEAR UP AND THE FLAPS RETRACTED TO ABOUT 7.5 DEGREES EXTENSION.
Probable cause
THE PILOT'S DISREGARD OF THE CHECKLIST AND THE RESULTING INADVERTENT STALL MUSH DURING TAKEOFF.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW92LA206
- Event ID
- 20001211X15412
- Case number
- FTW92LA206
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1992-08-11.
- API snapshot SHA-256: bc94ec7d05b4ef40789b2a411712e6bb764251ef92eb25a6adedf36a86229f9f; retrieved 2026-09-21T14:48:49.913Z.