Avery Jack H GLASTAR GS-1 N103A

Summary

On 25 June 2013 at about 21:45 local time, a Avery Jack H GLASTAR GS-1 registered N103A was involved in an accident near Grand Rapids, Minnesota, United States. One person was on board and one was seriously injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

25 June 2013 at 21:45

Classification

Accident

Location

Grand Rapids, Minnesota, United States

Coordinates

47.2100, -93.5097

Aircraft

Avery Jack H GLASTAR GS-1

Registration

N103A

Category

Airplane

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

Grand Rapids → Grand Rapids

Aircraft damage

Substantial

Weather

VMC

Light

Day

NTSB number

CEN13LA376

1 person was seriously injured.

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

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.

Quoted verbatim from the NTSB record.