FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA036 · Piper PA-28-180

14 Nov 2023 · Micanopy, FL, United States

Piper PA-28-180 · Accident: VFR encounter with IMC en route

From Kissimmee Gateway Airport (ISM) to Keystone Heights Airport (42J)

Report a problem

Event

NTSB case
ERA24FA036
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

Piper PA-28-180

Aircraft type
Piper PA-28
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
N7806W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kissimmee Gateway Airport (ISM), Orlando, FLTo Keystone Heights Airport (42J), Keystone Heights, FL
Aircraft age
About 59 years (built 1964)
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
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
VFR encounter with IMC
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
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The non-instrument-rated private pilot was performing a visual flight rules (VFR) cross-country flight. ADS-B data revealed that when the pilot was about 20 nautical miles (nm) from his intended destination, the airplane began to fly erratically, with several 360° turns and multiple climbs and descents. During this time, the pilot contacted ATC, declared an emergency, and reported that he was “lost in weather.” The controller began to provide the pilot with radar vectors out of the weather and informed the pilot when he began to deviate in altitude or heading, to assist the pilot with maintaining control of the airplane. During these communications, the pilot reported that his vacuum-driven attitude indicator and his electrically driven turn and bank indicator had failed. The pilot reiterated that he couldn’t see anything and reported that he thought he was “upside down.” In the final minutes of flight, the airplane made two tight, left 360° turns with a steep descent in excess of 5,000 ft per minute. The last ADSB data point was about 650 ft from the wreckage location. Before departure, the ground controller at the departure airport reported that the weather conditions were “IFR” and indicated the ceiling was broken clouds at 800 ft above ground level (agl). About 1 minute later, the controller stated there were updated weather conditions, which were few clouds at 800 ft agl, then issued a taxi clearance to the pilot. VFR, marginal VFR (MVFR), and instrument flight rules (IFR) conditions were present along the pilot’s route of flight, with areas of low cloud coverage and low visibility due to rain. The closest weather reporting station to the accident location reported IFR conditions just before the accident with 2 miles visibility, rain and mist, and a broken cloud layer at 1,800 ft agl. A high-resolution atmospheric model for the accident site indicated stratus clouds with bases about 600 ft agl and an overcast cloud layer at 1,000 ft agl with tops near 16,200 ft. Aviation weather forecasts issued near the time of departure depicted general MVFR conditions along the route of flight, and a graphical AIRMET for IFR conditions was active for a portion of the route. There was no record that the pilot received a weather briefing prior to departing on the flight, which would have alerted him to the forecast inclement weather along his planned route of flight. Postaccident examination of the wreckage revealed no evidence of any preimpact anomalies or mechanical failures that would have precluded normal operation. The attitude indicator and the turn and bank indicator were examined; both instruments displayed rotational scoring on their gyroscopes, indicating that the gyroscopes were spinning at the time of impact. However, during a pre-buy inspection performed a few months before the accident, a mechanic determined that the attitude indicator was inoperative. The investigation was unable to determine the nature of the malfunction, but there was no evidence that the attitude indicator had been subsequently repaired or replaced. The detection of carboxy-delta-9-THC in samples of the pilot’s blood indicated that the pilot had used a cannabis product. However, the fact that no delta-9-THC was detected, and that carboxy-delta-9-THC was not detected in liver tissue, indicated that the time between the pilot’s last cannabis use and the accident likely was long enough that he was not experiencing acute psychoactive effects of cannabis at the time of the accident. In summary, it is likely that as the pilot neared the destination airport, the airplane entered a cloud layer, resulting in the pilot losing outside visual reference to his surroundings. As such, the pilot likely became spatially disoriented and subsequently lost control of the airplane.

Probable cause

The non-instrument-rated pilot’s improper inflight decision making and his flight into instrument meteorological conditions, which resulted in spatial disorientation and subsequent loss of airplane control. Contributing to the accident were the pilot’s inadequate preflight weather planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA036
Event ID
20231114193387
Case number
ERA24FA036
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: a7eeeb988e4c8937820590ccd6572c28ab1aba3c6c9d2d0036ba4de391ff4295; retrieved 2026-09-15T08:08:04.561Z.