Piper PA-32R-300 N4478F

Summary

On 28 October 2012 at about 18:34 local time, a Piper PA-32R-300 registered N4478F was involved in an accident near Sevierville, Tennessee, United States. 5 people were on board and 3 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

28 October 2012 at 18:34

Classification

Accident

Location

Sevierville, Tennessee, United States

Nearest airport

Gatlinburg-Pigeon Forge (GKT)

Coordinates

35.8092, -83.6522

Aircraft

Piper PA-32R-300

Registration

N4478F

Category

Airplane

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

Sevierville → Titusville

Aircraft damage

Substantial

Weather

IMC

Light

Day

NTSB number

ERA13LA042

3 people had minor injuries.

The air traffic controller’s failure to comply with the required vectoring and safety alert procedures, which resulted in the airplane’s flight into rising terrain. Contributing to the accident was the Federal Aviation Administration’s continued practice of using air traffic controllers who were performing required radar operational duties to supervise other controllers and the air traffic control facility’s culture of non-compliance with required procedures.

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

Read the full NTSB narrative

Before departure, the pilot had contacted the air traffic control (ATC) facility and received his instrument flight rules (IFR) clearance, which entailed flying direct to a navigational facility about 22 miles west of the departure airport. Shortly after departure, the pilot contacted ATC, and was given radar vectors toward that navigational facility and toward rising terrain. Because the airplane was in instrument conditions, the pilot was unable to see the surrounding terrain. When the airplane’s global position system's terrain feature alerted the pilot of a possible terrain issue, the pilot queried the air traffic controller. However, before the controller responded, the airplane impacted a pole and trees; a postimpact fire ensued and consumed the airplane. The Federal Aviation Administration (FAA) defines minimum vectoring altitude (MVA) as the lowest altitude at which an IFR aircraft will be vectored by a radar controller to ensure obstacle clearance. The FAA further states that air traffic controllers are to give first priority to separating aircraft, issuing safety alerts, and providing safety alerts regarding terrain or obstructions. Despite FAA requirements, a review of accident-related ATC radar and voice data revealed that ATC personnel issued a radar vector without first identifying the accident airplane on radar, provided radar vectors when the airplane was below the MVA, and did not provide safety alerts to the accident airplane or another airplane that had departed just before the accident flight. Interviews with the accident ATC personnel indicated that a facility-wide culture of providing vectors to aircraft below minimum altitudes existed, air traffic controllers supervised other controllers while performing operational duties, and the facility was non-compliant with safety alert requirements. The accident air traffic controller failed to adhere to the required procedures for vectoring and providing appropriate safety alerts, which negated the safety margins afforded by those procedures. This culture of disregard for standard operating procedures among the controller workforce at the ATC facility was indicative of a continuous failure of management at the facility.

Quoted verbatim from the NTSB record.