The U.S. aircraft register, updated daily
Accidents · NTSB ERA26FA034 · Preliminary: the investigation is not finished

Extra Flugzeugproduktions EA 300/SC accident near Keystone Heights, Florida, November 8, 2025

On November 8, 2025 at about 3:15 pm local time, a 2014 Extra Flugzeugproduktions EA 300/SC, registered N330SL, was destroyed in an accident during maneuvering (aerobatics) near Keystone Heights, Florida (Keystone Heights airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 8, 2025 · about 3:15 pm local time · cases in 2025
Place
Keystone Heights, Florida · Keystone Heights · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Extra Flugzeugproduktions EA 300/SC, built 2014 · all EA 300/SCs on the register
Registration
N330SL · registry record · serial SC050
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative preliminary · quoted from the NTSB record

On November 8, 2025, at 1038 eastern standard time, an Extra 330/SC, N330SL, was destroyed when it was involved in an accident near Keystone Heights, Florida. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 flight. The owner of the airplane flew the airplane from St. Augustine, Florida, to Keystone Heights Airport (42J), Keystone Heights, Florida, on the morning of the accident to use the aerobatic box located at 42J. The airplane owner stated that he, along with a few other pilots, planned to practice their aerobatic routines for an upcoming competition. The owner said he flew his practice routine first and reported no issues with the airplane. After he landed, the airplane was refueled, and another pilot boarded the airplane and departed for his practice flight. The airplane owner said he watched the pilot’s entire routine and witnessed the accident. He said the pilot entered the aerobatic box and performed a “warm up figure” which was a lay down figure eight. He then climbed to approximately 3, 500 ft. mean sea level (msl) and re-entered the aerobatic box and executed the first three maneuvers “very precisely.” The third figure ended with a vertical climb with two quarter rolls in the middle of the climb and ended by laying out inverted in preparation for the next maneuver which began with a 1 ¼ inverted spin. The airplane entered the inverted spin; however, it did not stop at the 1 ¼ position as expected. The owner said the airplane spun another ½ -turn, before the pilot was able to stop the turn with the nose of the airplane pointed nose down about 30 degrees; however, the airplane rapidly accelerated into a flat inverted spin to the left. The airplane owner said the pilot appeared to regain control after six rotations and attempted to “fly out” inverted but had insufficient altitude to do so. The airplane re-entered the spin and impacted the ground inverted. A preliminary review of airport surveillance video revealed the airplane’s engine could be heard being advanced to full power prior to the airplane coming into view. When the airplane came into view it was in an inverted flat spin to the left. The airplane made three rotations before it rolled upright about 100 ft. above the ground. The airplane then nosed over and impacted the ground inverted. A postimpact fire consumed the airplane. The wreckage was retained for further investigation.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Aerodynamic stall/spin during maneuvering (aerobatics) defining event

The aircraft

  • Seats: 1
  • Landing gear: fixed
  • Fire on the ground

The flight

  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 190° at 6 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 10,000 ft
  • Temperature: 77°F (25°C), dew point 64°F (18°C)
  • Altimeter: 29.97 inHg
  • Observation at 10:53 am from GNV, 15 miles away

Weather report (METAR): METAR KGNV 081553Z 19006KT 10SM BKN100 25/18 A2997 RMK AO2 SLP146 T02500183

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Other NTSB records under N330SL the same tail number, which may have belonged to a different aircraft at the time

2011-11-13CEN12CA078 · accident near Carbondale, IL · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/ERA26FA034.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.