FTW95FA393 · Cessna 172M
Cessna 172M · Accident: in flight collision with object en route
From Memorial Field Airport (HOT) to Springdale Municipal Airport (ASG)
Event
- NTSB case
- FTW95FA393
- 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
- Instrument Meteorological Cond
Cessna 172M
- 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
- N61899
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Memorial Field Airport (HOT), Hot Springs, ARTo Springdale Municipal Airport (ASG), FAYETTVILLE, 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 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 › Altitude/clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight originated during early morning hours, and the airplane was reported missing at 0930; it was found atop a heavily wooded mountain ridge. A ground witness who lived near the accident site reported that there was heavy fog in the vicinity during the early morning hours. Investigation revealed that the airplane had collided with trees. It then descended through the trees for approximately 420 feet until it struck the ground and came to rest inverted. Examination of the airplane and engine revealed no evidence of a malfunction that would have contributed to the accident. Toxicology tests of the pilot's blood showed a low level (0.365 mcg/ml) of Methamphetamine and 25 mg/dl Ethanol. There was evidence that the Ethanol was due to post-mortem production. A test of the pilot's urine showed 0.059 mcg/ml Tetrahydrocannabinol Carboxylic Acid (inactive metabolite of marijuana), but none was detected in his blood. According to an FAA regional flight surgeon, the level of an inactive metabolite in the pilot's urine indicated that he had been under the influence of marijuana sometime in the past. Methamphetamine is a stimulant that is not approved by the FAA for use while operating an aircraft.
Probable cause
failure of the pilot to maintain sufficient altitude/clearance from high/wooded terrain. Factors relating to the accident were: darkness, high terrain, and foggy weather conditions. Also, the pilot's use of Methamphetamine (not approved by the FAA) was a possible factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95FA393
- Event ID
- 20001207X04479
- Case number
- FTW95FA393
- 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: a909a49e72486be9c8dd2cd0fe930312091703b3084a6eb592b8f28a2b5d4fdb; retrieved 2026-09-20T23:37:21.374Z.