ASN Wikibase Occurrence # 37727
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 26 November 2000 |
Time: | 11:20 |
Type: | Mooney M20K |
Owner/operator: | Private |
Registration: | N252MW |
MSN: | 25-1096 |
Total airframe hrs: | 1700 hours |
Engine model: | Continental TSIO-360-GB |
Fatalities: | Fatalities: 3 / Occupants: 3 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Rixford, PA -
United States of America
|
Phase: | Manoeuvring (airshow, firefighting, ag.ops.) |
Nature: | Private |
Departure airport: | Mount Alton, PA (BFD) |
Destination airport: | Charleston, WV (CRW) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The pilot received clearance for an IFR departure. Three minutes later, in IMC conditions, the pilot transmitted that he wanted vectors back to the airport. He later stated that he had an engine emergency, but did not reveal its nature. The controller advised him that he did not have radar contact and asked the pilot for his position, but the pilot did not respond. About a minute later, the pilot of an airplane on the ground reported that he had seen the accident airplane on TCAS, and that it appeared to be on a short final for runway 32. Shortly thereafter, the accident pilot transmitted, "can you see the field or the runway? i'm trying to get down." The airplane flew over the airport from south to north, made a 180-degree turn, and flew over it from north to south. The bottom of the airplane became briefly visible to a witness on the ground. About 8 minutes after departure, radar contact was established at 3,500 feet, and the pilot was asked if he had just made a missed approach. The pilot responded, no sir, unable. i'm trying to get the engine here to [unintelligible]." During the next 17 minutes, the controller gave the pilot numerous headings and no-gyro turns for an ILS approach, but the pilot had difficulty in complying with them. The airplane's altitude during the last part of the flight generally ranged between 4,500 feet and 3,800 feet. The airplane was equipped with an autopilot. The wreckage site was in rising mountainous terrain about 10 miles northeast the airport, about 2,120 feet msl. The airport elevation was 2,143 feet msl. Accident site tree strikes descended in a straight line at an 8-degree angle, and were consistent with an approximately wings-level attitude. The engine had been overhauled after a propeller strike by the pilot, and he subsequently complained of "surging". When the airplane flew over the airport from north to south, the propeller sounded like it was "cycling". Previously, leaning the engine had eliminated the surging. One propeller blade showed no leading edge damage, while the other exhibited leading edge gouging, chordwise scoring, and minor "s-bending." The spark plug electrodes were gray in color. The interior walls of the vacuum pump housing exhibited rotational scoring. Engine disassembly revealed no mechanical malfunctions, and total flight duration was about 25 minutes. The pilot received his instrument rating 10 days before the accident flight. Weather at the departure airport included an overcast cloud layer at 200 feet, visibility 5 statute miles in light rain and mist, and cloud tops at 5,700 feet.
Probable Cause: The pilot's loss of control of the airplane while maneuvering. Factors included low ceilings and the pilot's lack of instrument flight experience.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | NYC01FA040 |
Status: | Investigation completed |
Duration: | |
Download report: | Final report |
|
Sources:
NTSB:
https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20001215X45423&key=1 Revision history:
Date/time | Contributor | Updates |
24-Oct-2008 10:30 |
ASN archive |
Added |
21-Dec-2016 19:23 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
12-Dec-2017 19:29 |
ASN Update Bot |
Updated [Source, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation