ERA17FA145 · Pipistrel Virus SW
Pipistrel Virus SW · Accident: windshear or thunderstorm en route
From Sebring Regional Airport (SEF) to Oconee County Regional Airport (CEU)
Event
- NTSB case
- ERA17FA145
- 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
- 0
- 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
- Instrument Meteorological Cond
Pipistrel Virus SW
- Aircraft type
- Pipistrel VIRUS SW
- Category
- Glider
- 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
- N155CL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sebring Regional Airport (SEF), Sebring, FLTo Oconee County Regional Airport (CEU), Clemson, SC
- Aircraft age
- About 1 year (built 2016)
- 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
- En route · cruise
- 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
- Windshear or thunderstorm
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Although the airline transport pilot received preflight weather briefings that forecast a risk of severe thunderstorms along his route, he chose to depart on an instrument flight rules (IFR) cross-country flight in his motorglider. About 45 minutes after departure, he asked air traffic control for any pilot reports or other information about the line of weather, which was located to the north along his route. The controller advised that there were areas of heavy-to-extreme precipitation and offered to provide vectors through the area of least precipitation when the pilot arrived in the vicinity. The pilot acknowledged and advised the controller that he would divert to another airport south of the weather if the conditions deteriorated. The controller continued to provide vectors and inform the pilot of the location and severity of the precipitation as the airplane continued north. About 10 miles south of the line of weather, the controller issued a slight left turn to avoid an area of heavy to extreme precipitation. The pilot advised that he saw an area to his right that looked like a viable route, and after discussion with the controller, chose to navigate around the weather on his own. When the controller checked in with the pilot a few minutes later, the pilot said that his ride was smooth, and he could see some lightning to his right. He then indicated that he had entered the clouds and could no longer deviate around weather visually. No further transmissions were received from the pilot, and radar contact was lost about 2 minutes later.
The motorglider was highly fragmented at the accident site and was mostly confined to a small area about 75 ft in diameter. A large section of the left wing and the left flaperon were found in two separate locations about 4.5 and 3.5 miles away from the main wreckage, respectively, consistent with an in-flight breakup. Examination of the airframe and engine revealed no anomalies that would have precluded normal operation.
A review of available weather information revealed that the pilot likely encountered a severe rotating thunderstorm (supercell), with associated hazards such as severe wind shear, updrafts and downdrafts, hail, lightning, icing, and possible tornado activity.
The motorglider was not equipped for flight in instrument meteorological conditions (IMC) and the flight manual specifically prohibited flying according to instrument flight rules, in IMC, in heavy rainfall, or during thunderstorm activity. Despite the weather information provided to him before the flight, the pilot chose to depart toward and continue into the area of severe convective activity. The violent conditions associated with the supercell thunderstorm exceeded the motorglider's design stress limitations and resulted in an in-flight breakup.
Probable cause
The pilot's intentional flight into an area of known convective thunderstorm activity, which resulted in an in-flight breakup.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17FA145
- Event ID
- 20170404X04612
- Case number
- ERA17FA145
- 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: 45716c6ec7209f8e1425686c65530d17a73a12421643be55618d79fbef6ef2cd; retrieved 2026-09-15T06:00:46.555Z.