# NTSB NYC01FA040: Mooney M20K, N252MW, Rixford, PA, November 26, 2000 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: November 26, 2000, 11:20 local (16:20 UTC) - Place: Rixford, PA - Coordinates: 41.920333, -78.450813 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.9203&lon=-78.4508&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 3 fatal - Status: Completed, report November 14, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 51293 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC01FA040 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/51293/pdf - Page: https://openairdocs.org/ntsb/NYC01FA040 ## 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with terrain/water, maneuvering - miscellaneous,engine - surge - aircraft control - not maintained, pilot in command (cause) - lack of total experience in type operation, pilot in command (contributing factor) - weather condition - low ceiling (contributing factor) - terrain condition - rising ## Analysis 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. ## Factual narrative HISTORY OF FLIGHT On November 26, 2000, about 1120 eastern standard time, a Mooney M20K, N252MW, was destroyed when it impacted terrain, while maneuvering near Rixford, Pennsylvania. The certificated private pilot and two passengers were fatally injured. Instrument meteorological conditions prevailed at the time of the accident. An instrument flight rules flight plan was filed for the flight, between Bradford Regional Airport, Alton, Pennsylvania, and Yeager Airport (CRW), Charleston, West Virginia. The personal flight was conducted under 14 CFR Part 91. A review of the air traffic control audio transmissions revealed that at 1053, the pilot requested and received clearance to take off from Bradford Airport's runway 14. At 1056, the pilot reported that he wanted to return to the airport. He then made two additional calls, in which he stated that he wanted vectors back to the airport. After the third call, the controller from Cleveland Center asked if "five two mike whiskey" was calling. The pilot answered yes, and stated again that he'd like to get vectors back to the airport. He also stated that he had an engine emergency, but did not reveal the nature of the emergency. After the pilot stated he wanted vectors, the center controller responded that he did not have the airplane in radar contact. When the pilot did not respond, the controller called him again, and the pilot responded that he heard him "loud and clear." The controller reiterated that he did not have the airplane in radar contact, and that he could not give the pilot vectors. He then asked the pilot for his position, but the pilot did not respond. About a minute later, at 1058, the pilot of another airplane that was on the ground at Bradford Airport reported that he had seen the Mooney on his TCAS (Traffic Alert and Collision Avoidance System), and that it appeared to be on a short final for runway 32. The controller responded that he'd like to know when the airplane landed, and that hopefully, the Mooney pilot would then be able to talk to him about what occurred. About 1059, a voice similar to that of the accident pilot transmitted, "can you see the field or the runway? i'm trying to get down." For approximately the next 1 1/2 minutes, the controller talked to other airplanes. He then asked the accident pilot if he was on the ground at Bradford. The pilot responded that he was not, and asked if the controller had him on radar. The controller replied that he did not, and that the pilot's airplane was too low. The controller then asked the pilot if he was on final approach, and the pilot responded that he was not. At 1102, the controller advised the pilot that he had the airplane on radar, at 3,500 feet, and asked if the pilot had made a missed approach at Bradford. The pilot responded, "no sir, unable. i'm trying to get the engine here to [unintelligible]." He then asked the controller for a radar vector. The controller asked him if he wanted vectors for runway 32, and the pilot confirmed that he did. The controller then told the pilot that he would have to maintain 3,500 feet or greater, that the airplane was in radar contact, and to fly a heading of 170 degrees. The pilot acknowledged the heading. About 1/2 minute later, the controller asked the pilot if he could maintain 4,000 feet. The pilot stated that he thought he could, and controller then told him to climb to 4,000 feet, which the pilot acknowledged. About 1103, the controller stated that the airplane was about 2 miles northwest of Bradford Airport, and that he'd vector the airplane to the outer marker, at 4,000 feet. The pilot did not answer. A minute later, the controller asked the pilot if he were on a 170-degree heading, and the pilot responded that he was, but then said he was "one forty now." The controller then asked the pilot to verify his transponder code, but the pilot did not answer. The controller attempted to contact the pilot three more times, but the pilot still did not answer. At 1106, the controller stated that radar contact was lost again, and the airplane's last known position was over Bradford Airport. The pilot answered, "okay." The controller then confirmed with the pilot that he (the pilot) was unable to make a visual approach, and asked the pilot if he were on a 170-degree heading. The pilot first responded that he was on a 160-degree heading, and shortly thereafter, a 170-degree heading. The controller responded that the pilot's transmissions were "breaking up." He then informed the pilot that he was not on a 170-degree heading, but a 070-degree heading. The controller then twice repeated the 170-degree heading, for vectors for the "localizer three two approach." The controller then stated that the airplane was 2 miles north of Bradford Airport; however, the pilot did not respond. At 1109, the controller attempted to call the pilot again. About 15 seconds later, the pilot stated that he was on a 150-degree heading, at 4,000 feet. The controller told the pilot to maintain the 150-degree heading and 4,000 feet. He also stated that the airplane was about 3 miles north of the airport, and shortly thereafter, told the pilot that he had to make a right turn to 150 degrees, which the pilot acknowledged. At 1110, the pilot asked the controller if the airplane was in radar contact. The controller responded that he had contact occasionally, and that the last time he had contact, the airplane was 4 miles northeast of the airport. About 10 seconds later, the pilot stated that the airplane was at 4,400 feet. The controller acknowledged the call, and reported that he was not receiving the airplane's transponder. At 1111, the controller asked the pilot if he was on a 150-degree heading. The pilot confirmed that he was, and the controller stated that he was going to give the pilot a no-gyro turn to the right. He then told the pilot to turn right, but did not receive a response. The controller repeated his instructions, but again received no answer. The controller then told the pilot that if he received the last instruction, he should "ident." No additional transmissions were heard until 1112, when the controller told the pilot to stop the turn. The pilot responded that that he was stopping the turn, then said, "heading three five [unintelligible]." The controller replied, "no...you should be heading one seven zero, now turn right, heading one seven zero." Again, the pilot did not respond. Shortly afterwards, the controller asked the pilot to ident again. About 20 seconds later, at 1113, there was an unintelligible transmission. The controller stated that he received the pilot's ident, and then directed the pilot to make a right turn, for a "no-gyro vector for Bradford." There was no response from the pilot. At 1114, the controller told the pilot to stop his turn, and to ident if he received the transmission. Shortly thereafter, the controller asked the pilot of the airplane on the ground at Bradford Airport if he would be willing to launch, and lead the Mooney back toward the airport. The pilot agreed, and at 1117, was cleared for takeoff from runway 32. The pilot never made contact with the accident airplane, nor were any additional transmissions heard from it. A witness at Bradford Airport reported that the accident airplane departed at 1055, and that, at 1057, the pilot reported an emergency and that he was going to return to the airport. At 1103, the airplane flew over the airport from south to north, "with no contact." The airplane then made a 180-degree turn just north of the field, then flew over the airport, from north to south, "with the bottom of the aircraft in sight for just a very short time." The witness further stated, "at the time the aircraft went from north to south, it sounded like the prop was cycling." The nearest radar antenna to the accident site was about 60 n ## Aircraft - Registration: [N252MW](https://openairdocs.org/deregistered/N252MW-2013-07-02), registration cancelled 2013-07-02, S/N 25-1096 (OpenAirDocs) - Reported make and model: Mooney M20K - Registry model: [Mooney M20K](https://openairdocs.org/model/mooney-m20k) (registry code 5870220) (OpenAirDocs) - Registry engine: [Continental TSIO-360 series](https://openairdocs.org/engine/continental-tsio-360-series) (registry code 17019, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 25-1096 - Airframe hours: 1700 - Engines: Continental TSIO-360-GB 210 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Registered owner: Peter Sandek - Airworthiness certificate: Standard, Normal - Departed: BFD, MOUNT ALTON, PA - Destination: CRW, CHARLESTON, WV - Flight plan: IFR - Airport: BFD, Bradford Regional Airport, runway 14, 6,499 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--no waivers/lim.; seat: left; toxicology performed; flight hours: 200 total, 115 in this make and model, 15 in the last 30 days ## Weather - Conditions: Instrument (IMC), Day - Wind: 170° at 4 knots - Visibility: 5 statute miles - Lowest ceiling: 200 ft overcast - Temperature: 104 °F, dew point 104 °F - Altimeter: 29.00 inHg - Observed at: BFD, 10 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20001126038679A](https://openairdocs.org/incident/20001126038679A), Nov 26, 2000: Mooney M20K, Bradford, PA, No damage, 3 fatal. (-23) Aircraft had just departed Bradford, PA (bfd) destination charleston, WV (crw) when the pilot requested to return to Bradford because of an engine… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.