FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA037 · Cessna 150F

31 Oct 2024 · Wilder, TN, United States

Cessna 150F · Accident: controlled flight into terrain/object (CFIT) en route

From Crossville Memorial Airport Whitson Field (CSV) to Dupage Airport (DPA)

Report a problem

Event

NTSB case
ERA25FA037
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
Instrument Meteorological Cond

Cessna 150F

Aircraft type
Cessna 150
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
N8110S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Crossville Memorial Airport Whitson Field (CSV), Crossville, TNTo Dupage Airport (DPA), West Chicago, IL
Aircraft age
About 59 years (built 1965)
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
Defining eventThe 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
Controlled flight into terrain/object (CFIT)
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

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot was on the second leg of a long visual flight rules cross-country flight. The pilot departed shortly after the end of civil twilight and on a night where no lunar illumination was present. The pilot had not filed a flight plan and there was no evidence that he had obtained an official weather briefing from a source that would have logged that contact. After departure, the pilot flew over a town that contained significant cultural lighting and highway, flying parallel to a road for about 1 mile. He then turned away from the town and roughly toward the destination airport, over a sparsely populated area covered with dense forest and rising terrain. The dark night, in addition to the generally cloudy conditions and limited ground lighting along the flight path, would have made it difficult for the pilot to visually recognize the rising terrain. As the pilot continued toward this area of diminished visual reference, he encountered a band of light rain showers, which in addition to further restricting visibility, had the potential for updrafts and associated turbulence. Given these conditions, it is likely that the pilot was flying in instrument meteorological conditions (IMC) for the last 4 minutes of the flight. Postaccident examination of the wreckage at the accident site revealed no evidence of any preimpact mechanical malfunctions or failures of the airframe or engine. The relatively straight flight path for the final portion of the flight that was observed via ADS-B, the length of the wreckage path at the accident site, and the damage observed to trees along that wreckage path, were all consistent with controlled flight into terrain. The results of postaccident toxicological testing indicated that the pilot had used the prescription medication lamotrigine. While it is possible that his cognitive and psychomotor performance might have been impaired by the effects of the medication, no more-specific conclusion about pilot impairment can be drawn from the reviewed medical evidence alone. Based on the available information, the student pilot’s decision to continue the long cross-country flight at night, without obtaining a preflight weather briefing or having an apparent awareness of approaching precipitation, and without filing a flight plan, was indicative of poor judgement.

Probable cause

The student pilot’s decision to continue the visual flight rules flight into instrument meteorological conditions at night, which resulted in controlled flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25FA037
Event ID
20241101195426
Case number
ERA25FA037
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, cause areas. 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: c77b16699844ba3347ff56e9c91119686520f8ce4e6558be2442afe21de60e68; retrieved 2026-09-15T08:59:52.739Z.