FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20LA149 · Pipistrel Italia SRL Sinus 912 LSA

9 Apr 2020 · Marathon, FL, United States

Pipistrel Italia SRL Sinus 912 LSA · Accident: aerodynamic stall/spin while maneuvering

From Florida Keys Marathon International Airport (MTH) to Florida Keys Marathon International Airport (MTH)

Report a problem

Event

NTSB case
ERA20LA149
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
1 · 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

Pipistrel Italia SRL Sinus 912 LSA

Category
Airplane
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
N6263R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Florida Keys Marathon International Airport (MTH), Marathon, FLTo Florida Keys Marathon International Airport (MTH), Marathon, FL
Aircraft age
Built the same year (2020)
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
Maneuvering
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
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot of the motor glider performed a preflight inspection, departed the airport, and remained in the local area conducting maneuvers. Witnesses observed the glider about a mile from the airport and reported hearing unusually loud noises coming from it and, subsequently, a laboring engine. The glider had the appearance of wobbling; the engine surged and sputtered, and the glider then made a sharp left turn and the nose dropped. The glider's airframe ballistic parachute deployed shortly before the impact with a residential home and a postimpact fire ensued. It is likely that the glider entered an aerodynamic stall and an entry phase of a spin prior to impact. It is also likely that, despite the pilot’s attempt to pull the airframe parachute, it was not deployed at a sufficient altitude to arrest the descent. The airframe was destroyed by post-impact fire, which precluded an examination of the flight control system. Examination of the engine did not reveal any preimpact anomalies that would have precluded normal operation. Toxicology testing detected three potentially impairing substances in the pilot’s specimens. The sedating antihistamine diphenhydramine was detected in his blood and not quantified by one laboratory and not detected in iliac blood by another laboratory. While diphenhydramine is known to cause sedation, the level detected in the pilot’s blood appears to be well below therapeutic levels. Although no absolute threshold for impairment exists, any psychomotor effects from such a low diphenhydramine level would likely have been insignificant. The motion sickness medication meclizine was also detected but not quantified in the pilot’s blood. While meclizine can cause drowsiness, it’s also likely that any effects would have been minor at low concentrations detected. Duloxetine was detected at therapeutic levels in the pilot’s blood. The medication and conditions for which it is prescribed can impair the mental or physical ability to perform complex tasks. However, based on the operational evidence, the pilot appeared to have been intentionally testing the glider and took actions, although too late, to deploy the parachute. Thus, it is unlikely that effects from the pilot’s use of diphenhydramine, duloxetine, and meclizine were factors in the accident.

Probable cause

The pilot’s loss of control of the motorized glider, which resulted in an aerodynamic stall and collision with a residential home and postimpact fire. The reason for the loss of control could not be determined due to the condition of the wreckage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA149
Event ID
20200409X75658
Case number
ERA20LA149
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, coordinates, cause areas. 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: 7f0d83698b04eb3377703fb3eae154accaafc87c235b555d68463f298e05ff3c; retrieved 2026-09-15T07:13:32.785Z.