FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA464 · Fortuna Dave SONEX

5 Apr 2014 · Dunnellon, FL, United States

Fortuna Dave SONEX · Accident during initial climb

From Dunnellon Marion Co & Park of Commerce Airport (X35) to Zephyrhills Municipal Airport (ZPH)

Report a problem

Event

NTSB case
ERA14FA464
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
Unknown
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
Visual Meteorological Cond

Fortuna Dave SONEX

Aircraft type
Fortuna Dave SONEX
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
N229P
Onboard fatalities
Unknown
Route
From Dunnellon Marion Co & Park of Commerce Airport (X35), Dunnellon, FLTo Zephyrhills Municipal Airport (ZPH), Zephyrhills, FL
Aircraft age
About 13 years (built 2001)
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
Initial climb
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
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot was conducting a personal cross-country flight. Witnesses at the airport reported that they observed the airplane depart and climb out and that everything appeared to be normal. The airplane proceeded west of the departure end of the runway, made a left climbing turn, and then proceeded in a southerly direction. GPS data showed that the airplane then climbed to about 817 ft mean sea level, which was below the floor of available radar coverage. The airplane then continued in a southerly heading while descending with the ground speed increasing until about 2 minutes 30 seconds after takeoff, at which point the airplane made a right 270-degree turn for unknown reasons. The airplane continued to descend during controlled flight. The airplane subsequently impacted trees and the ground and then came to rest inverted about 1.7 nautical miles and 187 degrees from the departure end of the departure runway. No distress call was received from the pilot.

About 2 days later, an employee of the intended arrival airport called the departure airport and reported the airplane overdue. Subsequently that same day, the Civil Air Patrol, multiple local and state agencies, the pilot's son, and several privately operated aircraft began search operations; however, despite several weeks of ongoing search efforts, the airplane was not located. About 6 months later, the inverted wreckage was spotted by an individual in a heavily wooded area. No emergency locator transmitter (ELT) signal was ever received, and the ELT switch was found in the "off" position. The investigation determined that miscommunications, which led to delayed coordination, occurred between the Civil Air Patrol and the multiple local and state agencies during the initial search efforts. The delayed coordination between the response agencies, the nonactivation of the ELT, and the airplane's flight below radar coverage hampered the search efforts. However, the accident was not survivable; therefore, these issues did not contribute to the pilot's death.

Examination of the airframe revealed no evidence of fire. The engine, which had separated during the impact sequence, exhibited heat damage, which precluded testing of its operability. However, the No. 3 cylinder was found to have low compression, which likely existed when the flight departed. Full flight control continuity was confirmed, but the flap extension could not be determined. Although a hole was noted in a fuel supply line immediately adjacent to an engine control cable, extensive corrosion precluded a determination of whether the hole was preexisting or occurred postimpact.

Witnesses reported that the canopy opened while the pilot was taxiing to begin the flight, and it was found unlatched. However, the pilot was able to relatch it for taxi. Given that the fuel shutoff was found in the "off" position, it is likely that the pilot was preparing for a forced landing and unlatched the canopy at that time rather than it inadvertently becoming unlatched in flight. Based on the available evidence, the reason for the forced landing could not be determined.

Probable cause

The in-flight collision with a tree in a heavily wooded area during controlled flight while the pilot was attempting a forced landing for reasons that could not be determined based on the available evidence. Contributing to the delay in locating the wreckage were the nonactivation of the emergency locator transmitter and delayed coordination between the Civil Air Patrol and multiple local and state agencies.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA464
Event ID
20140410X75226
Case number
ERA14FA464
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. 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: 9a70f469419d8ead735b10f66605939839efe9ff60eb9479efa6a5fea0dcb71c; retrieved 2026-09-14T16:12:56.676Z.