The U.S. aircraft register, updated daily
Accidents · NTSB ERA13LA042 · Final report

Piper PA-32R-300 accident near Sevierville, Tennessee, October 28, 2012

On October 28, 2012 at about 6:34 pm local time, a Piper PA-32R-300, registered N4478F, was substantially damaged in an accident during enroute (climb to cruise) near Sevierville, Tennessee (Gatlinburg-Pigeon Forge airport). It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries; 2 others were unhurt. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 28, 2012 · about 6:34 pm local time
Place
Sevierville, Tennessee · Gatlinburg-Pigeon Forge · map
Type
Accident
Injuries
3 people had minor injuries; 2 others were unhurt.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-32R-300 · all PA-32R-300s on the register
Registration
N4478F · no longer on the register · serial 32R-7680450
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Air traffic event during enroute (climb to cruise) defining event
  2. Terrain avoidance alert during enroute (climb to cruise)
  3. Controlled flight into terrain or object (CFIT) during enroute (climb to cruise)
  4. Fire/smoke (post-impact) during post (impact)

The NTSB's findings

  • cause Environmental issues › Operating environment › Air traffic/operating proc › ATC clearance procedure › Compliance w/ procedure
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › ATC personnel
  • factor Organizational issues › Management › Culture › Safety › ATC
  • factor Organizational issues › Support/oversight/monitoring › Oversight › Oversight of personnel › ATC
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Contributed to outcome
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 502 hours in all; 242 in this make and model
  • Last flight review: January 7, 2011
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 3,051 hours
  • Last inspection: annual inspection, July 31, 2012
  • Maximum gross weight: 3,600 lb
  • Seats: 7
  • Landing gear: retractable
  • Engine: Lycoming IO-540-K1G5D (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: GKT Sevierville TN at 6:30 pm
  • Destination: TIX Titusville FL
  • Flight plan: IFR
  • Runway 28, 5,506 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: at 5 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 4,000 ft; a few clouds at 1,400 ft
  • Temperature: 48°F (9°C), dew point 43°F (6°C)
  • Altimeter: 29.89 inHg
  • Observation at 6:56 pm from GKT, 6 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers31

Documents from the investigation the NTSB's docket: the evidence folder behind the report

18 documents, released by the NTSB on June 26, 2013. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - Pilot PDF, 12 pages View Download
2 ATC 3 - Factual Report of Group Chairman PDF, 14 pages View Download
3 FAA Air Traffic Control Transcript PDF, 5 pages View Download
4 ATC 3 - Attachment 1 - Flight Progress Strip of N4478F PDF, 1 page View Download
5 ATC 3 - Attachment 2 - Sevierville Tn Departure Procedure - Terminal Procedures Publication (Tpp) PDF, 2 pages View Download
6 Minimum Vectoring Altitude Depiction with Flight Overlay PDF, 4 pages View Download
7 Memorandum of Record - Phone Interview with Pilot PDF, 2 pages View Download
8 Memorandum of Record - FAA Inspector Telephone Conversation PDF, 1 page View Download
9 Aircraft Filed IFR Flightplan PDF, 1 page View Download
10 Memorandum of Record - Gatlinburg Weather (2 Embedded Photos) PDF, 3 pages View Download
11 Fuel Receipt PDF, 1 page View Download
12 Fuel Sample Report PDF, 4 pages View Download
13 Memorandum of Record - NTSB Transcript of ATC Audio Recordings PDF, 8 pages View Download
14 Reports from Local Agencies - Sheriff's Department Report PDF, 3 pages View Download
15 Statement of Party Representatives to NTSB Investigation - ATC Group (Natca) PDF, 1 page View Download
16 Photo 1: Airplane at Rest (Courtesy of the FAA) PDF, 1 page View Download
17 Photo 2: Tree Strikes with 45 Degree Cuts (Courtesy of the FAA) PDF, 1 page View Download
18 Photo 3: Initial Pole Strike with Cloud Cover (Courtesy of the Sevier County Sheriff's Office) PDF, 1 page View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.