FTW83FPG02 · Cessna R172K
Cessna R172K · Accident: in flight encounter with weather en route
From AMA · HASKEL, OK to Bill & Hillary Clinton National Airport/Adams Field (LIT)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- FTW83FPG02
- 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
- 2 · 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
- Instrument Meteorological Cond
Cessna R172K
- Aircraft type
- Cessna 172
- 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
- N736QD
- Operator
- Clyde E. White · private individual
- Onboard fatalities
- Unknown
- Route Possible conflict
- From AMA · HASKEL, OKTo Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, AR
- 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
- En route · cruise
- 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 encounter with weather
- 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 › Flight into known adverse weather, continued
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT & PAX WERE ON A FLT FROM AMARILLO, TX TO LITTLE ROCK, AR. AN ENROUTE STOP WAS MADE AT HASKELL, OK AT APPR 1900 TO REFUEL. THE OWNER OF THE AFPT AT HASKELL STATED THAT THE PLANE ARRIVED IN A FAIRLY HEAVY RAINSTORM. AT THAT TIME, A WINTER TYPE COLD FRONT WAS MOVING EAST THRU TEXAS, OKLAHOMA & ARKANSAS. NUMEROUS THUNDERSTORMS & HEAVY RAINSTORMS WERE PRESENT & A TORNADO WATCH WAS IN EFFECT FROM 2130 TO 0100 FOR EASTERN OKLAHOMA AND WEST ARKANSAS. THE ARPT OWNER SUGGESTED WAITING OVER NIGHT & OFFERED ACCOMODATIONS, BUT SAID THE PLT & PAX WERE IN A HURRY. REPORTEDLY, RAIN WAS FALLING QUITE HEAVILY WHEN THEY WENT TO THE ACFT. THEY WAITED UNTIL THE STORM SUBSIDED THEN TKOF; HOWEVER, THEIR PLANNED ROUTE WOULD HAVE TAKEN THEM THRU THE SAME STORM. AT APPRX 2010 A WITNESS NEAR THE CRASH SITE HEARD VARIATIONS IN ENGINE PWR. HE WENT OUTSIDE & OBSERVED THE PLANE APPRX 10 TO 15 SEC BFR IT WENT OUT OF SIGHT THEN HEARD ON EXPLOSION & SAW A FIREBALL WHEN THE PLANE HIT A MTN SIDE AT NGT. NO PREIMPACT ENGINE FAILURE WAS FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83FPG02
- Event ID
- 20020917X04651
- Case number
- FTW83FPG02
- 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 1982-11-12.
- API snapshot SHA-256: 373b23a02ecebb2744ff4abe47646f21813ab6534a2421a8cd1bf044aa8697ee; retrieved 2026-09-21T07:32:25.691Z.