ASN Wikibase Occurrence # 151260
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 16 December 2012 |
| Time: | 15:32 |
| Type: |  Piper PA-28-160 Cherokee |
| Owner/operator: | Private |
| Registration: | N5714W |
| MSN: | 28-1215 |
| Year of manufacture: | 1963 |
| Total airframe hrs: | 6959 hours |
| Engine model: | Lycoming 0-320-D2A |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | 5 miles SW of Fayetteville Regional Airport/Grannis Field - KFAY, Faye -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Summerville, SC (DYB) |
| Fayetteville, NC (FAY) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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 prop
Probable Cause: 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.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N5714W
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=5714W
Location
Media:
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 16-Dec-2012 20:48 | Geno | Added |
| 17-Dec-2012 23:56 | gerard57 | Updated [Damage] |
| 18-Dec-2012 15:57 | Geno | Updated [Location, Source, Damage, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 28-Nov-2017 14:01 | ASN Update Bot | Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative] |
| 24-Dec-2018 17:40 | liamdaniel98 | Updated [Source, Embed code] |
| 24-Dec-2018 17:41 | harro | Updated [Embed code] |
| 03-Jul-2022 08:27 | rvargast17 | Updated [Source, Damage] |
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