NTSB CAROL · Event
Event ERA25FA201
Registry · N30689
FAA Aircraft Registry record.
Make / Model
PIPER PA-32RT-300
Year of manufacture
1978 · 47 years old at event
Engine
LYCOMING TI0-540 SER (310 hp)
Seats / Engines
7 seats · 1 engine
Last airworthiness date
19780930
ADS-B equipped
Yes — Mode-S A3392E
Registrant of record
PUNG LARRY J
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Factual narrative
On May 10, 2025, about 0935 eastern daylight time, a Piper PA-32RT-300, N30689, was destroyed when it was involved in an accident near Yulee, Florida. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot’s wife reported that the purpose of the flight was for the pilot to reposition the airplane from Nassau Airport (83FL), Yulee, Florida to Fernandina Beach Municipal Airport (FHB), Fernandina Beach, Florida, where they would wait for approaching thunderstorms to pass through the area before continuing on to Tennessee. She reported that earlier that morning, the pilot had dropped her and their dogs off at FHB before driving back to 83FL where he planned to finish loading the airplane for their trip and make the short flight to FHB. Review of video captured by a motion-activated surveillance camera mounted on a hangar near the end of runway 12 at 83FL showed that the airplane taxied toward runway 12 and began a back taxi down the runway and out of the video frame (figure 1). During the taxi the airplane’s nose baggage door was closed. As the video continued, the airplane re-entered the frame on a takeoff roll at 0934. The video showed that during the takeoff, the nose baggage door was open. The door stayed open until the airplane became airborne and exited the video frame. Following the accident, a sweep of the usable portion of runway 12 found a case of aviation oil about 100 ft from the beginning of the runway and to the right of centerline. A bag of dog food was also found about 440 ft from the beginning of the runway and to the right of centerline. Review of surveillance video from a residence that was located about 550 ft north of the departure end of the runway showed the airplane in a steep left wing low descent prior to impacting a tree and the ground about 10 seconds after departing 83FL. Figure 1. Still frames from the video showing the airplane during taxi and takeoff. Note the nose baggage door circled in read in each video frame. The wreckage was examined at the accident. The initial impact point was identified as a broken branch about 40 ft up a tree. A crater in the ground was identified about 24 feet away from the tree, and the wreckage came to rest upright about 15 ft from the crater, on a heading of 264° magnetic. The calculated angle of descent between the initial tree impact and the crater was about 50°. An 84-inch-long outboard portion of the left wing was impact-separated and remained near the crater with the left aileron attached. The cockpit and a majority of the fuselage were consumed by postimpact fire. The left flap, right wing, rudder, vertical stabilizer, and a majority of the stabilator and stabilator trim were also consumed by the postimpact fire. Aileron flight control continuity was confirmed from the aileron bellcranks to the flight control attachment points in the cockpit. Rudder flight control continuity was confirmed from the rudder control drum to the rudder pedals in the cockpit. Stabilator control continuity was confirmed from the stabilator control bellcrank to the lower portion of the cockpit control. The stabilator trim actuator was measured and equated to a trim setting halfway between full nose down and neutral. The three-blade propeller remained attached to the engine crankshaft flange. The propeller blades exhibited aft bending and chordwise scratching. Engine crankshaft and valvetrain continuity was established when the propeller was rotated 720°. Thumb suction and compression were observed on all cylinders. The vacuum pump remained attached to the engine accessory case; the drive gear and carbon veins all remained intact. The left standard magneto and right electronic magneto were removed and exhibited thermal damage. The fuel pump exhibited impact and thermal damage. The fuel injector assembly was impact separated and exhibited thermal damage. The sparkplugs were removed and exhibited normal wear and coloration consistent with normal engine operation when compared to the Champion Aviation Check-A-Plug AV-27 chart. The fuel injector nozzles were removed and were free of debris. The postimpact fire consumed most of the airplane’s fuel system. Both main wing fuel tanks were breached and exhibited thermal damage. The wreckage was retained for further examination. The pilot’s wife reported that several weeks before the accident, she and the pilot had flown from Clearwater Air Park (CLW), Clearwater, FL to 83FL, a flight that was about 1 hour long. She reported that they had fully fueled the airplane prior to that flight and that the accident flight was the first flight since. She also described that 83FL did not have fuel services and they did not add any fuel to the airplane after the flight from CLW to 83FL. Preliminary review of the Piper PA-32RT-300 Pilot Operating Handbook showed the airplane had an endurance between 5 and 7 hours depending on the power setting used. Preliminary review of weather radar data showed a line of intense precipitation echoes moving through the area at the time of the accident. A weather station at FHB, which was located about 3 nautical miles east of the accident site, reported at 0935 that the wind was from 180° true at 5 knots, 10 statute miles of visibility, and scattered clouds at 2,300 ft above ground level with thunderstorms in the vicinity and lightning distant southwest through north. The same station reported at 0955 wind from 320° at 13 knots gusting to 20 knots, 2 statute miles of visibility in heavy rain and thunderstorms, overcast clouds at 2,100 ft above ground level, and lightning in all quadrants. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Capability exceeded
- — Personnel issues-Psychological-Attention/monitoring-Monitoring environment-Pilot
- — Personnel issues-Psychological-Attention/monitoring-Attention-Pilot
- — Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
- — Environmental issues-Conditions/weather/phenomena-Convective weather-Thunderstorm-Contributed to outcome
- — Aircraft-Aircraft structures-Doors-Cargo/baggage doors-Unintentional use/operation
Verbatim from NTSB's published report. Source file
NTSB_2025_ERA25FA201.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (thunderstorm). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
The Impact of Thunderstorms on Take-off Data in South Africa
Aviation and meteorology are entwined disciplines, as aviation occurs in the atmosphere. Prevailing weather conditions at take-off are of utmost importance to aviation.
- NASA NTRS 2019 · Technical Memorandum (TM)
Thunderstorm hazards flight research: Storm hazards 1980 overview
A highly instrumented NASA F-106B aircraft, modified for the storm hazards mission and protected against direct lightning strikes, was used in conjunction with various ground based radar and lightning…
- NASA NTRS 2019 · Conference Proceedings
Operational evaluation of thunderstorm penetration test flights during project Storm Hazards '80
The National Aeronautics and Space Administration is conducting a research project called Storm Hazards '80 in order to study the prediction, detectability and avoidance of the hazards of severe storm…
- NASA NTRS 2019 · Preprint (Draft being sent to journal)
Nowcasting Thunderstorm Anvil Clouds Over KSC/CCAFS
Electrified thunderstorm anvil clouds extend the threat of natural and triggered lightning to space launch and landing operations far beyond the immediate vicinity of thunderstorm cells.
- NASA NTRS 2019 · Contractor Report (CR)
An Examination of Aviation Accidents Associated with Turbulence, Wind Shear and Thunderstorm
The focal point of the study reported here was the definition and examination of turbulence, wind shear and thunderstorm in relation to aviation accidents.
- NASA NTRS 2019 · Reprint (Version printed in journal)
Observations of severe turbulence near thunderstorm tops
Data derived from the flight tapes of two airliners that experienced severe turbulence near thunderstorm tops are used to produce quantitative descriptions of the turbulence and its environment.
Browse the full corpus — academia portal ↗