Pipistrel VIRUS SW N155CL
4 April 2017 · Micanopy, Florida, United States · Fatal
Summary
On 4 April 2017 at about 13:08 local time, a Pipistrel VIRUS SW registered N155CL was involved in an accident near Micanopy, Florida, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 13:08
- Classification
- Accident
- Location
- Micanopy, Florida, United States
- Coordinates
- 29.4653, -82.3750
- Aircraft
- Pipistrel VIRUS SW
- Registration
- N155CL
- Category
- Glider
- Year built
- 2016
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Sebring → Clemson
- Aircraft damage
- Destroyed
- Weather
- IMC
- Light
- Day
- NTSB number
- ERA17FA145
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
Probable cause
The pilot's intentional flight into an area of known convective thunderstorm activity, which resulted in an in-flight breakup.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Pipistrel VIRUS accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 2 Dec 2015 | Pipistrel VIRUS | Englewood, Colorado, United States | - | No injuries | - |
| 4 Feb 2012 | Pipistrel VIRUS 912 | Ray, Michigan, United States | - | Fatal | 1 |
| 1 Jul 2008 | Pipistrel VIRUS 912 | Bend, Oregon, United States | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 1 Mar 2017 | Cessna 172S | St Petersburg, Florida, United States | - | No injuries | - |
| 24 Jun 2017 | Piper PA28 | Fort Myers, Florida, United States | - | Fatal | 1 |
| 3 Feb 2017 | Cessna 152 | Bonifay, Florida, United States | - | No injuries | - |
| 5 May 2017 | Cirrus SR22 | Clearwater, Florida, United States | - | Fatal | 1 |
| 24 Jun 2017 | Aero Commander 200D | Panama City, Florida, United States | - | Minor injuries | - |
| 4 Mar 2017 | Beechcraft B 60 | Duette, Florida, United States | - | Fatal | 2 |