# NTSB ERA18LA172: Mooney M20J, N201FD, Monroe, NC, June 19, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 19, 2018, 13:50 local (17:50 UTC) - Place: Monroe, NC - Coordinates: 35.017501, -80.621948 - Nearby events: https://openairdocs.org/map.md?lat=35.0175&lon=-80.6219&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report June 3, 2020 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 97543 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA18LA172 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97543/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=97543 - Page: https://openairdocs.org/ntsb/ERA18LA172 ## Probable cause A loss of engine power for reasons that could not be determined based on the available information. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Mooney M20J, 12 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=5870219), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Mooney M20J, 13 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=5870219), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241); cases with it: [Mooney M20J, 11 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=5870219), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Mooney M20J, 6 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=5870219), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis According to the pilot, the purpose of the flight was to conduct instrument approaches; a pilot-rated passenger was on board. The pilot had completed the instrument landing system instrument approach procedure to near decision altitude in visual conditions and initiated the missed approach with a climbing right turn. He indicated that when the airplane was about 600 ft above ground level, "the engine suddenly started to falter." The pilot initiated a course reversal to conduct a forced landing on the opposite runway, but the airplane stalled just above the runway and landed hard about 45° off the runway heading. The landing gear separated, the fuselage was substantially damaged, and the airplane slid into the grass infield where it came to rest. Examination of engine and GPS track data revealed the airplane had entered a full-power climb near the approach end of the 7,001-ft runway when fuel flow and engine rpm rapidly decreased. The climb was arrested, and instead of continuing straight ahead, the airplane entered a descending right turn. About 30 seconds into the descent, the last GPS position was recorded about 3,200 ft down the runway, 1,100 ft right of centerline, at an altitude of 1,023 ft. An engine start attempted at the airport shortly after the accident was unsuccessful; however, after the airplane was recovered to a recovery facility, the engine was successfully started and run on the airframe using the airplane's own fuel system. The reason for the loss of engine power could not be determined. ## Factual narrative On June 19, 2018, at 1350 eastern daylight time, a Mooney M20J, N201FD, was substantially damaged during a forced landing following a missed approach to runway 5 at Charlotte-Monroe Executive Airport (EQY), Monroe, North Carolina. The private pilot was not injured, and the pilot-rated passenger sustained minor injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight which departed Jim Hamilton L. B. Owens Airport (CUB), Columbia, South Carolina about 1245, and was conducted under the provisions of 14 Code of Federal Regulations Part 91.In a written statement, the pilot said the purpose of the flight was to practice instrument approaches at three different airports, and then return to CUB; his home airport. The pilot-rated passenger, who was not instrument rated, accompanied him as a "safety pilot." According to the pilot, he had completed the ILS RWY 5 instrument approach procedure at EQY (682 feet elevation) to near decision altitude and initiated the missed approach with a climbing right turn, when about 600 feet above ground level (agl), "the engine suddenly started to falter." The pilot visually checked the mixture, throttle, propeller, and fuel pump settings and turned left for a forced landing on runway 23. The pilot maneuvered the airplane over trees and buildings on the airport perimeter towards the runway "just above" stall speed. As the airplane neared the landing surface heading about 270 degrees and about 8 feet agl, the airplane stalled, landed hard on the paved surface, and continued into the grass between the runway and parallel taxiway. In a telephone interview, the pilot-rated passenger provided an account consistent with the pilot's. Prior to the approach, he said the pilot consulted his approach checklist. At the end of the approach segment, he estimated the airplane was 200 feet above the runway, but not less than 100 feet. The pilot applied full power, and initiated a climbing right turn about 45-degress off the runway heading. The airplane climbed at 85-90 knots at 1,000 ft per minute for about 10 seconds when the "engine went to idle." The pilot declared an emergency over the radio and pushed the throttle and mixture controls full forward, "even though they were already there." "We had just enough energy – altitude and airspeed – to nearly complete a 180 degree turn in the opposite direction from the point where we lost power which would have required about 600 to 800 feet AGL. I did not look at the altimeter." "The airplane stalled about 6-8 feet above the ground and hit the edge of the runway at about a 45-degree angle, wings level, and skidded into the grass with pieces of the airplane and landing gear passing us as we slid." The pilot-rated passenger believed the airplane was over the runway when the missed approach was initiated and stated that because they had completed a 45-degree right turn and were about 10 seconds into the climb, there was "no way" the airplanecould have landed on the remaining runway. The runway was behind them, and they were headed away from it. He added that the few seconds of the climb were what allowed the pilot just enough altitude to reverse course, clear obstacles, and land in the direction of the opposite runway. A JPI Engine Data Monitor was recovered from the airplane and downloaded. The unit recorded engine parameters at 6 second intervals, and GPS position and altitude parameters at varying intervals, typically 18 to 24 seconds. Some airplane positions referenced in this report were estimated by interpolation of GPS groundspeed and elapsed time. GPS track data recovered from the engine monitor depicted a track consistent with the approach described by the pilot. According to that data, the airplane was at 965 ft, about 0.8 miles prior to the threshold of the 7,001-ft runway, aligned with the runway centerline, when a full-power climb along the right side of the runway was initiated. About 25 seconds later, over the paved surface about 0.2 miles prior to the displaced threshold at an altitude of 1370 ft, the fuel flow and engine RPM decreased rapidly (16 GPH to 6 GPH, 2,600 RPM to 2,000 RPM). The airplane's climb was arrested and approximately abeam the displaced threshold, the airplane entered a descending right turn. About30 seconds into the descent, the last GPS position was recorded about 3,200 feet down the runway, 1,100 feet right of centerline, at an altitude of 1,023 ft. The recorded data ended about 36 seconds later and did not depict the course reversal likely due to the GPS data update rate. According to the ILS or LOC RWY 5 approach at EQY, the published missed approach procedure was, "Climb to 1500 then climbing right turn to 3000 on heading 200°…" The pilot held a private pilot certificate with ratings for airplane single-engine land and instrument airplane. His most recent Federal Aviation Administration (FAA) 3rd class medical was issued March 20, 2017. The pilot reported 772 total hours of flight experience, of which 137 were in the accident airplane make and model. The airplane's most recent annual inspection was completed April 4, 2018 at 5,391 total aircraft hours. According to the Owner's Manual, the published stall speed for the airplane with flaps retracted was 63 knots. The best glide airspeed at 2,500 pounds was 88 knots. At 1353, the weather recorded at EQY included scattered clouds at 7,000 feet and variable winds at 4 knots. The temperature was 36°C, and the dew point was 19°C. The altimeter setting was 29.96 inches of mercury. Examination of photographs revealed substantial damage to the wings and fuselage. Following the accident, and under the supervision of an FAA aviation safety inspector, electrical power was applied, and an engine start was attempted at EQY. The engine rotated when the starter was actuated, but the start attempt was unsuccessful. While troubleshooting, compression was confirmed on each cylinder using the thumb method, fueldelivery was confirmed, and spark was confirmed at the top spark plugs for cylinders 1 and 3, and the bottom spark plugs for cylinders 2 and 4. Subsequent start attempts were also unsuccessful. The engine exam was suspended, and the airplane was scheduled for recovery from the site and further examination. An NTSB investigator examined the airplane and attempted an engine start on the airframe utilizing the airplane's own battery and fuel system. Both wing tanks were "full" of fuel, and the electric fuel boost pump was used to prime the engine. An engine start was attempted using a "flooded engine procedure" as described by a Lycoming representative. With the mixture off, and the throttle full forward, "the engine turned over 7-10 times before it started. Mixture was then placed in full forward position and the engine was run at idle for several minutes to warm up. The engine RPM was then increased to about 2000 RPM and [the engine] ran well." The engine was stopped and restarted several times using the same procedure. The engine ran smoothly and continuously each time without interruption. ## Aircraft - Registration: [N201FD](https://openairdocs.org/deregistered/N201FD-2019-05-01), registration cancelled 2019-05-01, S/N 24-0168, built 1977 (OpenAirDocs) - Reported make and model: MOONEY M20J (NO SERIES) - Registry model: [Mooney M20J](https://openairdocs.org/model/mooney-m20j) (registry code 5870219) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 24-0168 - Year built: 1977 - Airframe hours: 5391 - Engines: LYCOMING IO360 SER 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 4, 2018, 6 hours before - Departed: CUB, COLUMBIA, SC - Destination: EQY, Monroe, NC - Airport: EQY, Charlotte-Monroe Executive, runway 23, 7,001 × 100 ft, asphalt - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 67; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review June 4, 2017; seat: left; restraint: 3-point; flight hours: 772 total, 137 in this make and model, 661 as pilot in command, 7 in the last 90 days, 2 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Temperature: 97 °F, dew point 66 °F - Altimeter: 29.95 inHg - Observed at: KEQY ## 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 20180619008239A](https://openairdocs.org/incident/20180619008239A), Jun 19, 2018: Mooney M20J, Monroe, NC, Substantial damage. According to the pilot. He had completed the ILS rwy 5 instrument approach procedure at eqy to near decision altitude and initiated the missed approach. With a… ## Other investigations on N201FD (1) 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. - [NTSB CEN09IA416](https://openairdocs.org/ntsb/CEN09IA416), Jul 6, 2009: Mooney M20J (N201FD), Midland, TX, incident, minor damage. Probable cause: The pilot’s failure to ensure the airplane was properly configured, which resulted in a wheels-up landing. ## Docket (7 files) The files NTSB released with the investigation on March 25, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=97543. 3.2 MB in all. - NTSB Form 6120.1 - Pilot/Operator Aircraft Accident/Incident Report (item 1, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481532&FileExtension=.PDF&FileName=NTSB%20Form%206120.1%20-%20Pilot%2FOperator%20Aircraft%20Accident%2FIncident%20Report-Master.PDF - Photos (item 2, .PDF, 940 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481533&FileExtension=.PDF&FileName=Photos-Master.PDF - Engine Data Monitor - Factual Report (item 3, .PDF, 733 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481534&FileExtension=.PDF&FileName=Engine%20Data%20Monitor%20-%20Factual%20Report-Master.PDF - Engine Data Monitor - Tabular Data (item 4, .CSV, 74 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481535&FileExtension=.csv&FileName=Engine%20Data%20Monitor%20-%20Tabular%20Data-Master.csv - Memorandum For Record - Engine Run (item 5, .PDF, 53 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481536&FileExtension=.PDF&FileName=Memorandum%20For%20Record%20-%20Engine%20Run-Master.PDF - Memorandum For Record - Safety Pilot (item 6, .PDF, 61 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481537&FileExtension=.PDF&FileName=Memorandum%20For%20Record%20-%20Safety%20Pilot-Master.PDF - ILS/LOC RWY 5 Instrument Approach Procedure (item 7, .PDF, 298 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481538&FileExtension=.PDF&FileName=ILS%2FLOC%20RWY%205%20Instrument%20Approach%20Procedure-Master.PDF 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.