# NTSB ERA16LA046: Mooney M20, N5512Q, Fort Meade, MD, November 22, 2015 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: November 22, 2015, 13:30 local (18:30 UTC) - Place: Fort Meade, MD - Coordinates: 39.085277, -76.759445 - Nearby events: https://openairdocs.org/map.md?lat=39.0853&lon=-76.7594&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report July 16, 2018 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA - NTSB case key (mKey): 92353 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA16LA046 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92353/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92353 - Page: https://openairdocs.org/ntsb/ERA16LA046 ## Probable cause A partial loss of engine power for reasons that could not be determined because postaccident examination of the engine revealed no mechanical malfunctions or failures that would have precluded normal operation. ## 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 M20E, 5 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=5870212), [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 (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [Mooney M20E, 9 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=5870212), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Mooney M20E, 9 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=5870212), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Mooney M20E, 28 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=5870212), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The commercial pilot reported that, during the initial climb after takeoff, the airplane's climb rate seemed "lethargic." The pilot elected to remain in the airport traffic pattern, and after turning onto the downwind leg, the engine experienced a partial loss of power. The pilot was unable to maintain adequate airspeed to reach the runway and landed adjacent to the runway. The right wing and engine firewall were damaged during the forced landing. A postaccident test run of the engine using the fuel onboard at the time of the accident did not reveal any anomalies that would have precluded normal operation, and the reason for the loss of power could not be determined. ## Factual narrative On November 22, 2015, at 1330 eastern standard time, a Mooney M20E, N5512Q, was substantially damaged following a collision with terrain during a forced landing at the Tipton Airport (FME), Fort Meade, Maryland. The commercial pilot was not injured. The airplane was registered to and operated by the pilot as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions were reported at the site about the time of the accident, and a VFR flight plan was filed for the flight destined for Thomasville Regional Airport (TVI), Thomasville, Georgia.According to the pilot, during climb out from runway 28, he noted that the airplane's climb rate seemed to be "lethargic". The pilot elected to remain the airport traffic pattern and return for landing on runway 28. After turning onto the downwind traffic pattern leg, while at an altitude of between 600 and 800 feet, the engine lost power. He then turned toward the runway to attempt a landing near midfield. As he made a turn for the final approach, he was unable to maintain the airplane's airspeed and landed adjacent to the runway. The right wing and engine firewall were damaged during the forced landing. According to two witnesses, they both watched the accident airplane attempt landing, overshoot the runway, and come to a landing in the grass just beyond the runway. An FAA inspector examined the airplane at the accident site and noted that the propeller appeared relatively undamaged, and examination of photographs revealed that the propeller did not display any leading-edge gouging, chordwise scratching, or s-bending. The outboard 1/4-span of one blade was bent aft about 45°. A visual cursory examination was conducted of the engine and it was determined that an engine test run could be performed. Because the ignition key could not be found, the ignition switch was bypassed in order to start the engine. During the test run the engine was operated normally utilizing fuel supplied from both fuel tanks. A review of copies of maintenance logbook records showed an annual inspection was completed on December 12, 2014, at a recorded airframe total time of 3,956 hours and an engine total time of 3,956 hours. Further review of the aircraft records revealed that the engine accumulated 1,043 hours since overhaul. The pilot stated that during a flight in September, the engine was running roughly. He reported the discrepancy to mechanics at FME, who examined the airplane. Review of maintenance records dated September 15, 2015, showed that they fabricated and replaced an air manifold line and returned the airplane to service. The accident flight was the airplane's first flight since being returned to service. ## Aircraft - Registration: [N5512Q](https://openairdocs.org/deregistered/N5512Q-2018-05-30), registration cancelled 2018-05-30, S/N 609, built 1965 (OpenAirDocs) - Reported make and model: MOONEY M20 (E) - Registry model: [Mooney M20E](https://openairdocs.org/model/mooney-m20e) (registry code 5870212) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 609 - Year built: 1965 - Airframe hours: 3956 - Engines: LYCOMING IO-360-A1A 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, December 12, 2014, 24 hours before - Departed: FME, Fort Meade, MD - Destination: TVI, Thomasville, GA - Flight plan: VFR - Airport: FME, Tipton, runway 28, 3,000 × 75 ft, asphalt - Equipment: Stall warning system, Auto-pilot, Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: none; commercial, private, flight instructor; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review November 21, 2015; seat: left; restraint: 3-point; flight hours: 1,270 total, 329 in this make and model, 1,208 as pilot in command, 8 in the last 90 days, 1 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 320° at 9 knots, gusting 18 - Lowest ceiling: none - Temperature: 45 °F, dew point 25 °F - Altimeter: 30.05 inHg - Observed at: FME ## 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 20151122022329A](https://openairdocs.org/incident/20151122022329A), Nov 22, 2015: Mooney M20E, Ft. Meade, MD, Substantial damage. On November 22, 2015 at tipton airport the pilot of Mooney N5512Q lost power during climb while turning down wind at approximately 800 feet altitude after… ## Other investigations on N5512Q (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 DEN66D0030](https://openairdocs.org/ntsb/DEN66D0030), Jun 20, 1965: Mooney M20E (N5512Q), Heber, AZ, substantial damage ## Docket (5 files) The files NTSB released with the investigation on April 19, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92353. 4.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 680 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462037&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot's Statement (item 2, .PDF, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462038&FileExtension=.PDF&FileName=Pilot%27s%20Statement-Master.PDF - FAA Inspector's Statement (item 3, .PDF, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462039&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.PDF - Maintenance Records (item 4, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462040&FileExtension=.PDF&FileName=Maintenance%20Records-Master.PDF - Photos (item 5, .PDF, 4 photos, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462041&FileExtension=.PDF&FileName=Photos-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.