ASN Wikibase Occurrence # 150421
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: | Sunday 28 October 2012 |
| Time: | 14:34 |
| Type: |  Piper PA-32R-300 Cherokee Lance |
| Owner/operator: | Private |
| Registration: | N4478F |
| MSN: | 32R-7680450 |
| Year of manufacture: | 1976 |
| Total airframe hrs: | 3051 hours |
| Engine model: | Lycoming IO-540-K1G5D |
| Fatalities: | Fatalities: 0 / Occupants: 5 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | 4875 Top Road, Sevier County -
 United States of America
|
| Phase: | Take off |
| Nature: | Private |
| Departure airport: | Sevierville, TN (GKT) |
| Titusville, FL (TIX) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Probable Cause: 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.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 29-Oct-2012 04:39 | gerard57 | Added |
| 29-Oct-2012 12:43 | gerard57 | Updated [Aircraft type, Departure airport, Destination airport, Source] |
| 29-Oct-2012 16:02 | RobertMB | Updated [Time, Aircraft type, Registration, Cn, Operator, Departure airport, Destination airport, Source] |
| 29-Oct-2012 22:58 | Anon. | Updated [Time, Aircraft type, Registration, Cn, Operator, Departure airport, Destination airport] |
| 28-Nov-2017 20:15 | ASN Update Bot | Updated [Time, Operator, Other fatalities, Departure airport, Destination airport, Source, Damage, Narrative] |
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