Fayetteville Regional Airport
Aircraft Accident/Incident Report

Parkton, North Carolina 28371
Sunday, December 16, 2012 15:32 EST

NTSB Narrative Summary Released at Completion of Accident

The instrument-rated pilot departed with nearly full fuel tanks, obtained his instrument flight rules (IFR) clearance, and proceeded toward the destination airport, which, at the time of the accident, was IFR with a 500-foot ceiling. The pilot was vectored onto final approach for an instrument landing system approach. Radar data showed that the airplane performed s-type turns; the pilot then reported to the local controller that he had “...lost some gyros but I think we are getting it.” When the airplane was about 1 mile from the approach end of the runway at 1,300 feet, the local controller cancelled the approach clearance because the airplane was too high and advised the pilot to fly runway heading and climb to 2,000 feet. Radar data indicated that the pilot turned toward an easterly heading without clearance from the controller. The pilot was then instructed to maintain an easterly heading followed by a southwesterly heading (220 degrees) consistent with a downwind leg to fly parallel to runway 4. The pilot turned well past the southwesterly heading to a northwesterly heading, and was asked by the controller if he was having any problem with the airplane such that he was unable to fly assigned headings. The pilot advised the radar controller that he “...currently [had] no gyro I think the best thing for me to climb a little bit and go to my alternate of ah Columbus or some point south.” There was an adequate supply of fuel onboard to fly to his alternate airport, which at that time was under visual meteorological conditions with 10 miles visibility and a ceiling at 5,500 feet. As a result of the loss of gyros, the pilot was flying the airplane with a partial panel. The pilot was cleared to climb direct to his alternate airport; however, extensive heading and altitude deviations were noted during this portion of the flight, which was operating in IMC. The radar controller asked the pilot if he was ok to which he replied, “uh no im not okay right now.” This verbiage and the fact that extensive altitude and heading deviations occurred were clear indications that an emergency situation existed; however, the controller did not recognize this and did not request the necessary information needed to offer assistance, as outlined in FAA Order 7110.65, 10-2-1. The controller later reported that he believed the gyro comment would have affected only the pilot’s ability to maintain heading, thus, he did not believe the loss of gyros while in instrument conditions constituted an emergency. The controller then asked the pilot if he wanted to land at the airport, and he answered, “uh the best thing to”; however, the communication was not finished. It is likely that the pilot was intending to tell the controller again that he wanted to go to his alternate airport. However, because the controller did not recognize the emergency, he continued to vector the pilot to land using an ILS approach. While thbeing vectored, when the airplane was operating in IMC, major heading and altitude changes were noted; however, when the airplane was operating at higher altitudes in VFR conditions, the pilot was able to maintain the airplane’s assigned heading and altitude. The steady flight in VFR conditions should have been a cue to the controller that safe flight was possible in visual conditions; thus he should have encouraged the pilot to continue the flight to his alternate airport as the pilot had requested. Instead, the controller vectored the pilot to intercept the localizer, advised that the flight was about 4 miles from the final approach fix, and cleared the pilot to conduct an ILS approach. The pilot managed to fly onto final approach, but while in IMC conditions, rolled to the right and crashed inverted in a wooded area about 7.5 nautical miles from the approach end of the runway. Postaccident examination of the airframe and flights controls for roll, pitch, and yaw revealed no evidence of preimpact failure or malfunction. Examination of the power section of the engine revealed no evidence of preimpact failure or malfunction; one propeller blade exhibited “S”-bending consistent with the engine developing power at impact. No discrepancies were noted with the airport approach systems. Examination of the engine-driven vacuum pump, which operates the primary flight instruments consisting of the attitude indicator and directional gyro revealed fire damage to the shear shaft; however, no evidence of scoring of the interior surface of the housing was noted. Further, inspection of the gyroscopic flight instruments operated by the engine-driven vacuum pump revealed no evidence of rotational scoring; therefore, the engine-driven vacuum pump, which was about 3 years 4 months beyond the suggested replacement interval, was not operating at the moment of impact. This was consistent with the comment from the pilot that he had lost his gyro instruments. Although no determination could be made as to whether the pilot was instrument current, his inability to maintain control of the airplane while flying with a partial panel suggests he was not proficient in doing so; he failed this criteria in April 2002 during his first instrument rating checkride. In August 2004, in response to an NTSB recommendation, the FAA implemented national computer-based training to alert controllers of in-flight emergencies a pilot may encounter and the effect of the emergency. NTSB review of the current version of the CBI revealed it did not contain scenarios related to failures of the vacuum system or gyro flight instruments. Although the training provided to the controllers involved appeared to be inconsistent, it is unlikely that consistent training would have affected the outcome of the accident because specific mention of gyro malfunction was not a covered topic in the CBI training. Although the pilot had not declared an emergency, he had advised ATC personnel that he had lost his gyros, and that he was “not OK.” Further, extensive altitude and heading excursions of the aircraft were noted, all of which were clear indicators that an in-flight emergency existed. Had any of the FAA controller personnel understood either by experience or training that the pilot’s declarations or altitude and heading changes constituted an emergency, they could have declared an emergency for the pilot and obtained the necessary information required by section 10-2-1 of FAA Order 7110.65U, “Air Traffic Control.” Had that occurred, it is likely the pilot would have been vectored to an airport with VFR conditions for an uneventful landing.

NTSB Probable Cause Narrative

The failure of the instrument-rated pilot to maintain control of the airplane while in instrument meteorological conditions after reporting a gyro malfunction. Contributing to the accident was the loss of primary gyro flight instruments due to the failure of the vacuum pump, the inadequate assistance provided by FAA ATC personnel, and the inadequate recurrent training of FAA ATC personnel in recognizing and responding to in-flight emergency situations.

Event Information

Type of Event Accident
Event Date 12/16/2012
Event Day of the Week Sunday
Time of Event 1532
Event Time Zone Eastern Standard Time
Event City Parkton
Event State NORTH CAROLINA
Event Country --
Zipcode of the event site 28371
Event Date Year 2012
Event Date Month 12
MidAir Collision Indicator No
On Ground Collision occurred ? No
Event Location Latitude 345222N
Event Location Longitude 0785708W
Event Location Airport Fayetteville Regional
Event Location Nearest Airport ID FAY
Indicates whether the acc/inc occurred off or on an airport Off Airport/Airstrip
Distance from airport in statute miles 8
Degrees magnetic from airport 206
Airport Elevation 189
Weather Briefing Completeness --
Investigator's weather source Weather Observation Facility
Time of the weather observation 1543 Eastern Standard Time
Direction of event from weather observation facility (degrees) 27
Weather Observation Facility ID FAY
Elevation of weather observation facility 189
Distance of event from weather observation facility (units?) 8
Time Zone of the weather observation EST
Lighting Conditions Day
Lowest Ceiling Height 1300
Lowest Non-Ceiling Height 700
Sky/Lowest/Cloud Conditions Scattered
Sky Condition for Lowest Ceiling Overcast
Visibility Runway Visual Range (Feet) --
Visibility Runway Visual Value (Statute Miles) --
Visibility (Statute Miles) 3
Air Temperature at event time (in degrees celsius) 14
Dew Point at event time (in degress fahrenheit) 14
Wind Direction (degrees magnetic) 210
Variable Wind Indicator Wind direction could be determined
Wind Speed (knots) 3
Wind Velocity Indicator --
Wind Gust Indicator Not Gusting
Wind Gust (knots) --
Altimeter Setting at event time (in. Hg) 29.99
Density Altitude (feet) --
Intensity of Precipitation --
METAR weather report --
Event Highest Injury Fatal
On Ground, Fatal Injuries --
On Ground, Minor Injuries --
On Ground, Serious Injuries --
Injury Total Fatal 1
Injury Total Minor --
Injury Total None --
Injury Total Serious --
Injury Total All 1
Investigating Agency NTSB
NTSB Docket Number (internal use) 32475
NTSB Notification Source FAA Southern C-ROC
NTSB Notification Date --
NTSB Notification Time --
Fiche Number and/or location -used to find docket information --
Date of most recent change to record Mar 11 2014 11:18AM
User who most recently changed record kenj
Basic weather conditions Instrument Meteorological Cond
FAA District Office --

Aircraft Involved

Aircraft #1

Aircraft Registration Number N5714W
NTSB Number ERA13FA088
Missing Aircraft Indicator --
Federal Aviation Reg. Part Part 91: General Aviation
Type of Flight Plan filed IFR
Flight plan Was Activated? Yes
Damage Substantial
Aircraft Fire Ground
Aircraft Explosion None
Aircraft Manufacturer's Full Name PIPER
Aircraft Model PA-28-160
Aircraft Series Identifier --
Aircraft Serial Number 28-1215
Certified Max Gross Weight 2200
Aircraft Category Airplane
Aircraft Registration Class --
Aircraft is a homebuilt? No
Flight Crew Seats --
Cabin Crew Seats --
Passenger Seats --
Total number of seats on the aircraft 4
Number of Engines 1
Fixed gear or retractable gear Fixed
Aircraft, Type of Last Inspection Annual
Date of Last Inspection Jan 27 2012 12:00AM
Airframe hours since last inspection --
Airframe Hours 6959
ELT Installed Yes
ELT Activated Unknown
ELT Aided Location of Event Site No
ELT Type Unknown
Aircraft Owner Name Virgil T. Deal
Aircraft Owner Street Address --
Aircraft Owner City Fayetteville
Aircraft Owner State NC
Aircraft Owner Country USA
Aircraft Owner Zipcode 28312-7037
Operator is an individual? No
Operator Name Virgil T. Deal
Operator Same as Owner? Yes
Operator Is Doing Business As --
Operator Address Same as Owner? Yes
Operator Street Address --
Operator City Fayetteville
Operator State NC
Operator Country USA
Operator Zip code 28312-7037
Operator Code --
Owner has at least one certificate None
Other Operator of large aircraft? --
Certified for Part 133 or 137 Operation --
Operator Certificate Number --
Indicates whether an air carrier operation was scheduled or not --
Indicates Domestic or International Flight --
Operator carrying Pax/Cargo/Mail --
Type of Flying (Per_Bus / Primary) Personal
Second Pilot on Board No
Departure Point Same as Event No
Departure Airport Code DYB
Departure City Summerville
Departure State SC
Departure Country USA
Departure Time 1400
Departure Time Zone EST
Destination Same as Local Flt --
Destination Airport Code FAY
Destination City Fayetteville
Destination State NC
Destination Country USA
Specific Phase of Flight --
Report sent to ICAO? --
Evacuation occurred --
Date of most recent change to record Mar 11 2014 11:19AM
User who most recently changed record kenj
Since inspection or accident Last Inspection
Event Location Runway Number and Location 04
Runway Length 7709
Runway Width 150
Sight Seeing flight No
Air Medical Flight No
Medical Flight --