FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11CA045 · Evolution Revo

10 Oct 2010 · Gransonville, MD, United States Narrative disagrees

DOJ/Sherrif's Association Evolution Revo · Accident: aerodynamic stall/spin on approach

From Bay Bridge Airport (W29) to Gransonville, MD

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location and departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA11CA045
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

Evolution Revo

Aircraft type
Evolution REVO
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
N611TX
Onboard fatalities
Unknown
Route Narrative disagrees
From Bay Bridge Airport (W29), Stevensville, MDTo Gransonville, MD
Aircraft age
Not recorded
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
Approach · VFR go-around
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
Aerodynamic stall/spin
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
  • Personnel issues › Task performance

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

NTSB narrative

According to the certificated flight instructor (CFI), he was giving instruction to another pilot who was not rated in special light sport weight-shift airplanes. During touchdown, the airplane bounced and the CFI instructed the pilot undergoing instruction (PUI) to perform a go-around. The PUI pushed the control bar and the airplane stalled. The airplane to roll to the left and the left wingtip contacted the ground, resulting in the airplane tumbling in a cartwheel-type movement. The CFI stated that the PUI was seated in the rear seat and therefore had more leverage than his controls. Postaccident examination by a Federal Aviation Administration inspector revealed damage was sustained to fuselage structure.

Probable cause

The pilot's improper recovery from a bounced landing and the certificated flight instructor's inadequate remedial action, which resulted in an aerodynamic stall during a go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11CA045
Event ID
20101101X13016
Case number
ERA11CA045
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: 869014e816fd9c4ba5fa03a5a74a14c9367e069f20ffa682ea25f9a8065d3548; retrieved 2026-09-15T15:31:41.841Z.