FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC00LA120 · Piper PA-31-350

11 Sept 2000 · Anchorage, AK, United States

Piper PA-31-350 · Accident: vortex turbulence encountered en route

From SLEETMUTE, AK to Merrill Field (PAMR)

Report a problem

Event

NTSB case
ANC00LA120
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-31-350

Aircraft type
Piper PA-31
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N27179
Operator
Unknown
Onboard fatalities
Unknown
Route
From SLEETMUTE, AKTo Merrill Field (PAMR), Anchorage, AK
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Vortex turbulence encountered
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Atc personnel(dep/apch) › Safety advisory, not issued
  • Pilot in command › Wake turbulence, encountered

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

An airline transport pilot was returning from a charter flight in a twin-engine airplane and was in radio and radar contact with an FAA TRACON approach controller in Class C airspace. The pilot was given air traffic advisories for airplanes departing a satellite airport, but was not given an advisory about a McDonnell Douglas MD-11 airplane that was on final approach to land at the Ted Stevens Anchorage International Airport. The pilot said he did not specifically recall seeing the MD-11. The accident airplane encountered wake turbulence from the MD-11 that produced a violent vertical wind shear. The pilot then noticed the MD-11 airplane. After landing at a satellite airport, he notified the FAA of the wake turbulence event. Radar data revealed the MD-11 was on the glide path for landing at Anchorage, and the pilot of the MD-11 was in radio contact with the tower. The accident airplane crossed the flight path of the MD-11 at a 90 degree angle, about 900 feet msl, and about 55 seconds after the MD-11. When the accident airplane encountered the wake turbulence, it was 300 feet below the flight path of the MD-11 and separated by 2.47 miles. A postflight inspection of the airplane revealed substantial damage to the right wing. The Anchorage International Airport is within Class C airspace, which has a high volume mix of air carrier, general aviation, and military aircraft. Class D, Class E, and Class G airspace surround, and underlie the Class C area. In addition, the airspace is subject to Federal Aviation Regulation Part 93 (FAR 93). FAR 93 outlines geographic segments and special rules for operating at airports within the area. An air traffic controller is required to separate small aircraft operating behind heavy aircraft by 5 miles, and issue traffic advisories, and safety alerts including wake turbulence cautionary advisories. The TRACON utilizes certain prearranged coordination procedures to improve the traffic flow of aircraft through TRACON radar segments. Controllers are required to view a full data block on their radar screen when using prearranged coordination. The air traffic controller did not have a full data block displayed. The TRACON procedures manual does not contain a procedure for challenging, and verifying, the use or non-use of prearranged coordination between controllers. The air traffic controller did not notice that an aircraft designation symbol displayed on his screen indicated a heavy aircraft, and he did not issue a wake turbulence advisory. A heavy aircraft designator ('H' if assigned) is displayed on all radar data blocks (full or partial).

Probable cause

The failure of the TRACON air traffic controller to issue a wake turbulence advisory to the pilot, and a wake turbulence encounter by the pilot. Factors in the accident were the pilot's inadequate visual lookout, the failure of the TRACON controller to notice an aircraft as a heavy jet, and insufficiently defined TRACON procedures used to facilitate prearranged coordination of aircraft through radar segments.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC00LA120
Event ID
20001212X21890
Case number
ANC00LA120
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: c1ac4d00dfb5289932a8dd5ed38da56692512fe224c9cd2abf614afd5626abd8; retrieved 2026-09-22T12:27:33.978Z.