Accident Glasair GlaStar N103A,
ASN logo
ASN Wikibase Occurrence # 157257
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 25 June 2013
Type:Silhouette image of generic GLST model; specific model in this crash may look slightly different    
Glasair GlaStar
Registration: N103A
MSN: 5328
Total airframe hrs:453 hours
Engine model:Lycoming O-360 SERIES
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Location:Shoal Lake, NW of Grand Rapids, MN -   United States of America
Phase: Landing
Departure airport:Grand Rapids, MN (GPZ)
Destination airport:Grand Rapids, MN
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Prior to takeoff from the airport pond, the pilot performed a few high-speed taxi and on-the-step maneuvers with no anomalies noted. After the flight and during the short flight to the intended landing area, the pilot heard two to three aural “autopilot disconnect” voice messages. Because the pilot believed he did not engage the autopilot during the flight, he was uncertain why he was hearing the autopilot disconnect messages and was not overly concerned. During the landing, after the floats contacted the water, the airplane's right wing immediately lifted up, and the left wing tip contacted the water. Subsequently, the airplane nosed over. The pilot reported the weather at the time of the accident as ideal for flying; sky clear and a steady 5-knot wind. Data extracted from the avionics units showed 9 autopilot engagements during the flight; however, the data did not show what caused the inadvertent engagements. It is likely the autopilot engaged during the attempted landing and caused the loss of directional control, but the reason for the autopilot engagement was not determined due to damage to the avionics system caused by water exposure and recovery damage.
Probable Cause: The loss of directional control during landing because the autopilot engaged for undetermined reasons because water and recovery damage precluded detailed examination of system components.

Accident investigation:
Investigating agency: NTSB
Report number: CEN13LA376
Status: Investigation completed
Download report: Final report




Revision history:

26-Jun-2013 21:03 Geno Added
03-Jul-2013 07:35 Geno Updated [Time, Aircraft type, Registration, Cn, Phase, Departure airport, Destination airport, Source, Damage, Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
29-Nov-2017 08:46 ASN Update Bot Updated [Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]

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