FTW83FA271 · Cessna TU206F
Cessna TU206F · Accident: loss of control in flight on approach
From F29 · Oklahoma City, OK to an unrecorded destination
Event
- NTSB case
- FTW83FA271
- 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
- 3 · 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 TU206F
- Aircraft type
- Cessna 206
- 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
- N35925
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From F29 · Oklahoma City, OKTo 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
- Approach · VFR pattern base
- 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
- 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 › Physical impairment(cardiovascular)
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING ARRIVAL ON A DARK NIGHT, THE ACFT COLLIDED WITH LEVEL GROUND APRX 1 MI NORTHEAST OF THE ARPT. IT TOUCHED DOWN ON A WEST NORTHWESTERLY HEADING IN APRX A 45 DEG, LEFT BANK, SLIGHTLY NOSE DOWN, ATTITUDE. AN EXAM OF THE WRECKAGE WAS MADE, BUT NO EVIDENCE OF A PREIMPACT FAILURE OR MALFUNCTION OF THE ACFT WAS FOUND. ACCORDING TO LOCAL AUTHORITIES, THE PLT WAS HOLDING AN OXYGEN MASK IN HIS LEFT HAND WHEN THE WRECKAGE WAS LOCATED. THE OXYGEN SYS WAS FOUND IN THE 'ON' POSITION. THE OXYGEN PLUG IN COVER FOR THE PLT WAS OFF & BROKEN. ACCORDING TO PERSONS WHO FLEW WITH THE PLT ON A REGULAR BASIS, THE OXYGEN MASKS WERE NORMALLY CARRIED IN A CARDBOARD BOX IN THE BAGGAGE AREA. THEY REPORTED THAT EVEN THOUGH THE OXYGEN SYS WAS SERVICED, THE PLT HAD NEVER USED IT & NEVER FLEW AT ALTITUDES WHERE OXYGEN WAS REQUIRED. THE PATHOLOGIST, WHO PERFORMED THE AUTOPSY, BELIEVED THE PLT SUFFERED A CORONARY, CRIPPLING CONDITION. HOWEVER, HE REPORTED THE CAUSE OF DEATH WAS BLUNT FORCE TRAUMA WHICH WAS SUFFERED IN THE FATAL CRASH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83FA271
- Event ID
- 20001214X43323
- Case number
- FTW83FA271
- 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 1983-06-12.
- API snapshot SHA-256: cab15d751af878c234d27a5aac03f0b5b3cb6f57d6ee1ede39b382228c47817d; retrieved 2026-09-21T06:39:47.345Z.