FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15CA118 · Dayton A Babcock STORM

2 Jan 2015 · Eustis, FL, United States

Lake Hoppers Air Adventures Dayton A Babcock STORM · Accident: loss of control in flight during landing

From Mid Florida at Eustis Airport (X55) to Mid Florida at Eustis Airport (X55)

Report a problem

Event

NTSB case
ERA15CA118
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
0 · 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

Dayton A Babcock STORM

Category
Weight-Shift
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
N516VB
Onboard fatalities
Unknown
Route
From Mid Florida at Eustis Airport (X55), Eustis, FLTo Mid Florida at Eustis Airport (X55), Eustis, FL
Aircraft age
About 1 year (built 2014)
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
Landing · flare/touchdown
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
Loss of control in flight
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

  • Personnel issues › Action/decision

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

NTSB narrative

At the conclusion of a local formation flight, the flight of weight-shift-control aircraft returned to their home airport and entered the traffic pattern. During the landing flare, the accident pilot encountered the "prop wash" of the preceding aircraft, which resulted in his aircraft entering an uncommanded right bank. The pilot attempted to counteract the turn by applying a left banking control input, but the left main landing gear and nose landing gear impacted the ground, and further aggravated the turn. The nose landing gear then collapsed and dug into the soft turf runway, and the aircraft overturned to the right, where it came to rest on its right side. Examination of the wreckage by a Federal Aviation Administration inspector revealed that the airframe had been substantially damaged during the accident. The pilot reported that there were no mechanical malfunctions or failures or the aircraft that would have precluded normal operation, and when asked how the accident might have been prevented, the pilot stated, "…I could have performed (possibly) a go-around."

Probable cause

The pilot's failure to maintain adequate spacing from the preceding aircraft during a formation landing, resulting in an inadvertent "prop wash" encounter, loss of control, and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15CA118
Event ID
20150204X84810
Case number
ERA15CA118
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: 5cd46181ecff9b2629eadc74778c29b27ed53cfa1db23241991376283c531e23; retrieved 2026-09-16T02:04:16.236Z.