FTW83FQA03 · Cessna T210M
Cessna T210M · Accident: in flight collision with object during initial climb
From Q16 · Reserve, NM to an unrecorded destination
Event
- NTSB case
- FTW83FQA03
- 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
- 1 · 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 T210M
- Aircraft type
- Cessna 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
- N732SK
- Operator
- E.H. Mullins & V.N. Mullins
- Onboard fatalities
- Unknown
- Route
- From Q16 · Reserve, NMTo not recorded
- 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
- In flight collision with object
- 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
- Tree(s)
- 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 › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT CRASHED SHORTLY AFTER TAKEOFF IN THE EARLY MORNING HOURS WHILE IT WAS STILL DARK. A CHECK AT THE AIRPORT REVEALED A PLANE WAS MISSING. A FURTHER CHECK WITH THE OWNER WAS MADE WHICH REVEALED THE AIRCRAFT HAD BEEN STOLEN. THE PLANE HAD BEEN SECURED WITH A WHEEL LOCK, BUT SOMEONE HAD CUT THE LOCK WITH A TORCH. ALL THE VEHICLES AND OTHER AIRCRAFT HAD HEAVY FROST ON THEIR WINDSHIELDS. THE TEMPERATURE WAS ABOUT 8 DEG. WITNESSES AGREED THAT THE PILOT HAD STARTED THE PLANE, TAXIED A SHORT DISTANCE AND TOOK OFF WITHOUT WARMING THE TURBOCHARGED ENGINE. REPORTEDLY, THE SURROUNDING HILLS WERE VIRTUALLY IMPOSSIBLE TO SEE. THE AIRCRAFT CRASHED AS IT PASSED OVER THE CREST OF A HILL ABOUT 2 MI FROM THE AIRPORT. DURING THE ACCIDENT, IT IMPACTED WITH TREES WHILE BANKED ABOUT 45 DEG TO THE LEFT. AFTER HITTING THE TREES, THE PLANE REMAINED AIRBORNE FOR SOME 474 FT BEFORE IMPACTING THE GROUND AND BURNING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83FQA03
- Event ID
- 20020917X04660
- Case number
- FTW83FQA03
- 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: investigation status. 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: 64177a65dce8f96e255eec3d25fc929c214440157749ee59a86a2866dbdd6b3b; retrieved 2026-09-21T07:19:51.853Z.