Accident Pipistrel Virus SW N155CL,
ASN logo
ASN Wikibase Occurrence # 194552
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 4 April 2017
Time:09:08
Type:Silhouette image of generic PIVI model; specific model in this crash may look slightly different    
Pipistrel Virus SW
Owner/operator:Private
Registration: N155CL
MSN: 817 SWN 100
Year of manufacture:2016
Total airframe hrs:89 hours
Engine model:Rotax 912 ULS2
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:NW Marion County, Micanopy, FL -   United States of America
Phase: En route
Nature:Private
Departure airport:Sebring, FL (SEF)
Destination airport:Clemson, SC (CEU)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA17FA145
Status: Investigation completed
Duration: 2 years and 8 months
Download report: Final report

Sources:

NTSB

FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=155CL

Location

Media:

#

Revision history:

Date/timeContributorUpdates
04-Apr-2017 15:13 Geno Added
04-Apr-2017 22:12 Geno Updated [Aircraft type, Registration, Cn, Operator, Phase, Departure airport, Destination airport, Source, Damage, Narrative]
05-Apr-2017 05:36 harro Updated [Aircraft type, Embed code]
14-Apr-2017 14:28 Aerossurance Updated [Time, Nature, Source, Narrative]
22-Dec-2019 14:16 ASN Update Bot Updated [Time, Departure airport, Destination airport, Source, Embed code, Narrative, Plane category, Accident report, ]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org