Casualties unknown

Aircraft Overshoots Final, Crashes Near Runway 31L Threshold (N38GF)

Seattle, WA, US

On April 11, 2000, a Cessna 172P (registration N38GF) was involved in an aviation accident near Seattle, WA. Investigators recorded the probable cause as: The pilot's failure to attain proper alignment with the landing runway, and her failure to maintain proper glide path for the landing runway, resulting in an encounter with vortex turbulence from a preceding heavy aircraft landing on a parallel runway and… This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

An aircraft in a right-hand traffic pattern for runway 31R overshot final, lined up behind a landing B-767 on runway 31L, and crashed with an extreme bank angle in the displaced threshold area of runway 31L.

Accident Overview

The accident occurred while the aircraft was conducting a touch-and-go landing in a right-hand traffic pattern for runway 31R. At the time, a Boeing 767 had just landed on the parallel runway 31L, which is spaced approximately 360 feet from runway 31R. The aircraft overshot the final approach for runway 31R and instead aligned with the final approach course for runway 31L, placing it behind the landing B-767.

Weather and Traffic Information

Wind conditions were from 290 degrees magnetic at 7 to 12 knots, resulting in a crosswind component of about 2 to 4 knots directed from runway 31L toward runway 31R during the accident time frame. Three on-duty tower controllers observed that the accident aircraft was low on its approach for runway 31R and noted its deviation from the correct approach path.

Sequence of Events

After lining up on the runway 31L final approach course behind the B-767, the aircraft subsequently rolled to an extreme bank attitude. It then crashed and came to rest in the displaced threshold area of runway 31L.

Pilot Experience

The pilot had accumulated 173.7 total flight hours, including 69.9 hours as pilot-in-command.

Frequently asked questions

What happened in the 11 Apr 2000 Cessna 172P accident near Seattle, WA?

An aircraft in a right-hand traffic pattern for runway 31R overshot final, lined up behind a landing B-767 on runway 31L, and crashed with an extreme bank angle in the displaced threshold area of runway 31L.

What aircraft was involved and where did it happen?

The accident on 11 Apr 2000 involved a Cessna 172P, registration N38GF, at Seattle, WA.

What was the probable cause of the accident?

The pilot's failure to attain proper alignment with the landing runway, and her failure to maintain proper glide path for the landing runway, resulting in an encounter with vortex turbulence from a preceding heavy aircraft landing on a parallel runway and subsequent loss of aircraft control. Factors included the…

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001212X20919. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.