ERA12CA570 · FLY Hard Trike Inc SKYCYCLE STING RAY
FLY Hard Trike Inc SKYCYCLE STING RAY · Accident: loss of control in flight during landing
From Gulfport Biloxi International Airport (GPT) to Gulfport Biloxi International Airport (GPT)
Event
- NTSB case
- ERA12CA570
- 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
FLY Hard Trike Inc SKYCYCLE STING RAY
- Aircraft type
- FLY Hard Trike SKYCYCLE STING RAY
- 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
- N86862
- Operator
- Lindorfer John H
- Onboard fatalities
- Unknown
- Route
- From Gulfport Biloxi International Airport (GPT), Gulfport, MSTo Gulfport Biloxi International Airport (GPT), Gulfport, MS
- 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
- Landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the experimental weight-shift control aircraft stated that he was returning to the departure airport after an uneventful 90-minute test flight. During the landing approach, the aircraft encountered a gust of wind, then "violently" pitched up, rolled to the right, nosed over, and impacted the ground. Postaccident examination revealed substantial damage to the wings and nose. The pilot reported that there were no mechanical malfunctions or anomalies that would have precluded normal aircraft operation. The pilot stated that he believed that this was a “freak” accident caused by unanticipated turbulence over the runway at the time of touchdown.
Probable cause
The pilot’s failure to maintain aircraft control after an unexpected wind gust/turbulence encounter during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12CA570
- Event ID
- 20120921X23524
- Case number
- ERA12CA570
- 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: f0602770f740fef4e0c6b74f90c62a157d78495f8d6a267d3d7ac6dadb9e99fb; retrieved 2026-09-15T19:58:22.917Z.