ERA24FA120 · Piper PA32 300
Piper PA32 300 · Accident: VFR encounter with IMC during takeoff
From an unrecorded airport to Winter Haven Regional Airport - Gilbert Field (KGIF)
Event
- NTSB case
- ERA24FA120
- 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
Piper PA32 300
- Aircraft type
- Piper PA32
- 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
- N8963N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Winter Haven Regional Airport - Gilbert Field (KGIF), Winter Haven, FL
- Aircraft age
- About 55 years (built 1969)
- 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
- Takeoff
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument-rated private pilot and two passengers departed on the cross-county flight under visual flight rules (VFR) during a period of heavy snow, as reported by witnesses of the accident flight. The airplane subsequently collided with terrain while maneuvering in the vicinity of the airport several minutes after takeoff. A postimpact fire consumed and destroyed most of the airplane, precluding determination of control position settings and instrument readings. Weather observations and satellite imagery indicated that instrument meteorological conditions (IMC) prevailed at the departure airport and its vicinity at the time of the accident, with surface visibilities ranging from 3/4 to 2 statute miles and ceilings around 1,200 ft above ground level (agl). Before the flight, the pilot received a weather briefing from ForeFlight that included an AIRMET warning of IMC in effect at the time of the accident for the departure airport and enroute. Witness accounts described even lower ceilings and visibilities than indicated in official weather reports, with one characterizing the snowfall as “very hard and windy” during the flight’s run-up and for 20 minutes afterward. Another witness stated that the airplane was only aloft for about 3 to 5 minutes; in that time, the airplane was maneuvering in the vicinity of the airport and departure runway. The airplane’s track was not captured by ADS-B data, and no onboard devices that capture digital data were recovered; therefore, the investigation could not determine how the airplane was maneuvering and whether the final impact was due to pilot spatial disorientation. A survey of the accident site revealed a linear debris path terminating in wreckage that was upright and relatively intact, suggesting that the airplane impacted the ground with relatively little energy, consistent with low-speed, controlled flight into terrain. While the airplane was exposed to the potential for airframe icing after removal from the hangar and through the end of the flight, the more imminent and pressing challenge the pilot faced would have been navigating and maintaining aircraft orientation under VFR given the restriction to visibility imposed by the period of heavy snow reported by witnesses. The postimpact fire precluded determination of whether airframe icing contributed to the accident. The pilot’s logbook was not available during the investigation. A flight instructor with whom the pilot had been working to obtain an instrument rating estimated that the pilot had logged 20 hours of instrument flight “under the hood.” Postaccident toxicology testing of specimens obtained from the pilot indicated he had used the sedating antihistamine diphenhydramine, which might have adversely affected his performance or increased his susceptibility to spatial disorientation. However, the diphenhydramine results in his postmortem tissues cannot be used to determine the details of his diphenhydramine use or whether he was significantly impaired by diphenhydramine effects at the time of the accident. The pilot’s decision to attempt a VFR flight in IMC with inadequate training and experience was inappropriate regardless of whether he was impaired and attributing that decision to diphenhydramine effects would be implausible.
Probable cause
The non-instrument-rated pilot’s decision to depart under visual flight rules into instrument meteorological conditions, which resulted in an inflight collision with terrain while maneuvering.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24FA120
- Event ID
- 20240224193833
- Case number
- ERA24FA120
- 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, 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: a1c770e662f2f2e1df4c871bf31733eeb896e3ce78f67a0793c08ab557df8e62; retrieved 2026-09-15T08:11:16.871Z.