Aviation Accident Summaries

Aviation Accident Summary ERA16LA274

London, KY, USA

Aircraft #1

N602SL

ALISPORT SRL SILENT 2 TARGA

Analysis

Earlier on the day of the accident, the private pilot flew the motor glider in the airport traffic pattern and, after an uneventful landing, secured the glider. The pilot did not report any discrepancies with the canopy during that flight. Before starting another flight later the same day, the pilot noted that the right side of the canopy did not latch properly, which he corrected. The pilot reported that, while on the downwind leg of the traffic pattern, the right side of the canopy raised, followed by the left side and nose. He continued flying the glider and secured the engine, but did not retract the engine. After turning from the base to final leg of the traffic pattern, he realized that the glider was too far from the runway. The glider subsequently impacted trees short of the runway then impacted the ground. Postaccident examination of the canopy and canopy latch system revealed no evidence of preimpact failure or malfunction. Examination also revealed that the canopy could be offset from its normal position during the closing process and that the respective latch rod in that situation would be outside the airframe receiver hole, not allowing the canopy to secure properly. Additionally, there was no visual indication to indicate that the canopy was properly secured. It is likely that the pilot did not engage the latch rod into the airframe receiver hole when he closed the right side canopy latch before departure, which resulted in the in-flight canopy opening.

Factual Information

On July 24, 2016, about 1037 eastern daylight time, a privately owned and operated AliSport SRL Silent 2 Targa motor-glider, N602SL, collided with terrain during an attempted landing at London-Corbin Airport-Magee Field (LOZ), London, Kentucky. The private pilot sustained minor injuries and the motor-glider was substantially damaged. The flight was operating under the provisions of 14 Code of Federal Regulations Part 91, as a local, personal flight. Visual meteorological conditions prevailed and no flight plan was filed, for the flight that originated about 7 minutes earlier from LOZ.The pilot stated that earlier that day, he flew the motor-glider around the traffic pattern at LOZ, and landed uneventfully then secured the motor-glider. There were no discrepancies associated with the canopy during the first flight. When attempting to close the canopy in advance of the accident flight, he noted the right latch did not seat properly. He cycled the right canopy latch and noted it was then seated OK, and then started the engine. He taxied onto runway 24, and initiated takeoff. After becoming airborne he turned crosswind and then onto downwind leg where while flying at 700 feet above ground level (agl) and 50 mph, he heard a thump on his right knee. He reported the right canopy latch released allowing the right side of the canopy to raise about 1 inch along its full length, though the right canopy lever was full forward at the time (latched). He thought he could close the canopy, but the left side then released. While holding the rear of the canopy down with both hands as best he could, the canopy twisted which released the front latch. He thought about jettisoning the canopy but elected not to, making the decision to attempt to save the canopy. He secured the engine but he did not center the propeller nor retract the engine. He wrestled to keep the canopy closed and when he slowed the glider, the nose of the canopy came up. While wrestling to hold the canopy closed he turned base to final but realized he had drifted too far from the runway. While descending at 50 mph, he was forced to fly the glider into trees short of the runway. The left wing impacted a tree about 15 feet agl, then the motor-glider impacted the ground. He exited the motor-glider, walked to the airport, and was taken to a local hospital for treatment of his injury. He further indicated that at no point either in-flight or after coming to rest did he jettison the canopy. A Federal Aviation Administration (FAA) inspector examined the motor-glider at the accident site, and found the canopy in close proximity to the main wreckage. Some of the canopy acrylic material was missing but the canopy frame was intact. Further examination of the canopy revealed the left and right latch handles and rods, and also each rod receiver hole in the airframe were intact with no damage noted. Operational testing of the left and right canopy latches and the canopy emergency jettison system revealed no discrepancies. It was noted by the FAA inspector that the canopy could be offset from its normal position during the closing process and that the respective latch rod in that situation would be outside the airframe receiver hole not allowing the canopy to secure properly. It was also noted that there was no visual indication to indicate that the canopy was closed properly, and in the event that the canopy would raise in-flight due to being improperly secured, it would likely lift from the rear initially, but once the air pressure equalized with a forward airspeed, the canopy would stabilize in forward flight. The accident pilot purchased the motor-glider in June 2014, and since owning it he accrued 2.5 hours. During those flights excluding the accident flight, there were no reported problems with the canopy latch mechanism. A review of the maintenance records revealed the airplane's last condition inspection occurred on April 20, 2016. The entry associated with the inspection indicated the canopy eject system was functionally checked. The motor-glider had accrued about 2 hours since the inspection was performed.

Probable Cause and Findings

The pilot's failure to properly secure the right side of the canopy before takeoff, and an in-flight collision with trees while maneuvering with an open canopy. Contributing to the pilot's failure to properly secure the canopy was the lack of a visual indication that each side of the canopy was properly secured.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports