ASN Wikibase Occurrence # 218047
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: | Saturday 17 November 2018 |
| Time: | 19:35 LT |
| Type: |  Lancair Legacy RG |
| Owner/operator: | Private |
| Registration: | N8448J |
| MSN: | L2K-338 |
| Year of manufacture: | 2015 |
| Total airframe hrs: | 358 hours |
| Engine model: | Continental IO-550-N8B |
| Fatalities: | Fatalities: 1 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Lee Gilmer Memorial Airport (KGVL), Gainesville, GA -
 United States of America
|
| Phase: | Approach |
| Nature: | Training |
| Departure airport: | Charleston, SC (JZI) |
| Gainesville-Lee Gilmer Memorial Airport, GA (GVL/KGVL) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot/owner and flight instructor were returning from a cross-country flight and arrived in the vicinity of the airport after dark in visual meteorological conditions. The flight instructor requested (to the air traffic controller) and was cleared for a practice GPS approach to the runway, which was equipped with precision approach path indicator (PAPI) lighting. Flight data indicated the approach was flown using the autopilot. Just after the airplane passed the final approach fix, the flaps were partially extended, the pitch attitude decreased, and the airplane descended below the glidepath. The autopilot commanded nose up elevator and the airplane returned to slightly above the glidepath where it remained stable for about 16 seconds, before drifting to nearly a full-scale course deviation above the glidepath. The autopilot commanded the elevator to nose down, and the electric pitch trim to near the full nose-down position. The autopilot was then disconnected. Although the autopilot can automatically disengage in the event of a system failure, no failures were observed in the recorded data. Therefore, it was likely that the autopilot was manually disengaged. About 15 seconds later, the flaps were extended to full and then fully retracted. The descent rate increased, and the airplane descended below the glidepath, until the recorded data ended when the airplane was about 0.3 mile from the runway. The airplane then struck trees, crossed over a road, and impacted the left side of a localizer antenna platform before coming to rest in the grass short of the runway.
Examination of the wreckage and the recorded flight data did not reveal any preimpact electrical or mechanical anomalies that would have precluded normal operation. The pilot's guide for the autopilot system warned that with the autopilot engaged, a small amount of force on the pitch controls can result in the autopilot automatic trim entering an out-of-trim condition. As the airplane drifted above the glidepath, the autopilot attempted to command nose-down elevator, and the elevator servo met with some resistance, as evidenced by the increase in elevator servo torque, which was sufficient to activate the electric pitch trim. Given that there were no indications of a flight control malfunction, it is likely that one of the pilots was applying pressure to the elevator control in the cockpit, and the autopilot applied elevator trim to counteract that pressure, in its attempt to return to the glidepath.
At the time the autopilot was disengaged, the pitch trim was full nose down, which likely resulted in an unexpected increase in the (forward) force the pilot felt on the control stick, making it more difficult to control the airplane. The airplane's nose-down tendency would have increased further when the flaps were subsequently extended to full. This would have resulted in an even greater forward force on the control stick. It is likely that the pilot decided to then retract the flaps fully, due to the increased nose-down force on the control stick. However, the flap retraction resulted in an increased descent rate, and the airplane descended farther below the glidepath.
A witness and the flight instructor reported that the airplane rolled inverted before impact. The recorded flight data, which ended when the airplane was on the extended runway centerline about 0.3 mile from the runway and about 50 ft above the runway elevation, did not indicate that the airplane had rolled inverted. The struck trees were also located on the extended runway centerline, about 0.1 mile from the end of the runway. Therefore, it is unlikely that the airplane experienced any significant lateral course deviation or roll, between the end of the recorded data and the struck trees. It is likely that the roll occurred after the airplane struck the trees and before it impacted the localizer antenna platform.
The flight instructor had limited memory of the accident flight. He recalled that the pilot/owner was flying the airplane during the approach; however, the investigation was unable to determine which pilot was manipulating the controls at the time of the accident.
Probable Cause: The pilots' failure to execute a go-around when the nighttime autopilot-coupled approach became unstable, which resulted in a loss of control and subsequent impact with terrain. Also causal was the flight instructor's inadequate supervision of the pilot and his failure to perform remedial action. Contributing to the accident was the inadvertent application of pressure to the pitch control while the autopilot was engaged, which caused an out-of-trim condition that was not identified by either pilot and resulted in control difficulty when the autopilot was disengaged.
Accident investigation:
 |
|
Sources:
FAA register: https://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=8448J%20
NTSB ERA19FA049
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 18-Nov-2018 02:11 | Geno | Added |
| 18-Nov-2018 02:25 | Geno | Updated [Time, Phase, Departure airport, Source, Narrative] |
| 18-Nov-2018 02:34 | Geno | Updated [Source] |
| 18-Nov-2018 20:17 | Captain Adam | Updated [Aircraft type, Operator] |
| 19-Nov-2018 20:13 | Geno | Updated [Time, Registration, Cn, Departure airport, Destination airport, Source, Narrative] |
| 03-Jan-2019 09:48 | Russell | Updated [Narrative] |
| 03-Jan-2019 09:50 | harro | Updated [Time, Nature, Source, Narrative] |
| 31-Mar-2021 16:23 | ASN Update Bot | Updated [Time, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative, Category, Accident report] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation