# NTSB ERA15CA157: Mooney M20K, N231KA, Laurel, MD, March 16, 2015 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 16, 2015, 19:55 local (23:55 UTC) - Place: Laurel, MD - Coordinates: 39.076946, -76.828056 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.0769&lon=-76.8281&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 11, 2015 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA FSDO - NTSB case key (mKey): 90880 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA15CA157 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/90880/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=90880 - Page: https://openairdocs.org/ntsb/ERA15CA157 ## Probable cause The pilot's improper decision to attempt a nighttime landing at an unsuitable airport, which resulted in a collision with the precision approach path indicator. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Mooney M20K, 11 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=5870220), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Mooney M20K, 4 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=5870220), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Mooney M20K, 2 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=5870220), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Mooney M20K, 28 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=5870220), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot stated that he was aware that the Low Intensity Runway Lights (LIRL) at his departure airport were not operational when he departed on a local flight. When the pilot returned to the departure airport later that night, he attempted to operate the LIRL, but only one side of the runway edge lights activated. The pilot conducted a low approach to see which lights were working and then executed a go-around. On the second approach, the pilot planned to conduct another low approach to see if he could identify the runway paint markings. If the pilot saw the paint markings, he planned to continue the low approach into a landing. During the second low approach, the airplane collided with a structure that was used as a precision approach path indicator. The airplane sustained substantial damage to the fuselage and both wings. The pilot did not report any anomalies that would have precluded normal operation. A review of the airport facility directory revealed that the LIRL lights were listed as inoperative indefinitely but also listed to activate LIRL with common traffic advisory frequency. ## Factual narrative The pilot stated that he was aware that the Low Intensity Runway Lights (LIRL) at his departure airport were not operational when he departed on a local flight. When the pilot returned to the departure airport later that night, he attempted to operate the LIRL, but only one side of the runway edge lights activated. The pilot conducted a low approach to see which lights were working and then executed a go-around. On the second approach, the pilot planned to conduct another low approach to see if he could identify the runway paint markings. If the pilot saw the paint markings, he planned to continue the low approach into a landing. During the second low approach, the airplane collided with a structure that was used as a precision approach path indicator. The airplane sustained substantial damage to the fuselage and both wings. The pilot did not report any anomalies that would have precluded normal operation. A review of the airport facility directory revealed that the LIRL lights were listed as inoperative indefinitely but also listed to activate LIRL with common traffic advisory frequency. ## Aircraft - Registration: [N231KA](https://openairdocs.org/deregistered/N231KA-2015-06-02), registration cancelled 2015-06-02, S/N 25-0005, built 1978 (OpenAirDocs) - Reported make and model: MOONEY AIRCRAFT CORP. 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-0005 - Year built: 1978 - Airframe hours: 3562 - Engines: CONT MOTOR TSIO-360 SER 210 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Pridgen Michael E - Registered owner: Pridgen Michael E - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 2, 2014 - Departed: ESN, EASTON, MD - Destination: W18, Laurel, MD - Flight plan: VFR - Airport: W18, Suburban, runway 21, 2,324 × 40 ft, asphalt - Equipment: Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 53; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 1,302 total, 200 in this make and model, 1,217 as pilot in command, 3 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night/dark - Wind: calm - Visibility: 5 statute miles - Lowest ceiling: none - Temperature: 30 °F, dew point 28 °F - Altimeter: 30.10 inHg - Observed at: FME, 3 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 20150316002479A](https://openairdocs.org/incident/20150316002479A), Mar 16, 2015: Mooney Aircraft Corp. M20K, Laurel, MD, Substantial damage. The pilot attempted to activate the runway lights of runway 21 but only the left lights came on. He did a flyby to try and determine on which side of the… ## Docket (8 files) The files NTSB released with the investigation on July 27, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=90880. 15.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 9.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429800&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Pilot statement (item 2, .PDF, 27 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429801&FileExtension=.PDF&FileName=Pilot%20statement-Redacted.PDF - Record of conversation-Pilot (item 3, .PDF, 50 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429802&FileExtension=.PDF&FileName=Record%20of%20conversation-Pilot-Master.PDF - NOTAMS (item 4, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429803&FileExtension=.PDF&FileName=NOTAMS-Master.PDF - Afd W18 (item 5, .PDF, 45 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429804&FileExtension=.PDF&FileName=AFD%20W18-Master.PDF - Photo 1 – View of broken PAPI and skid marks from airplane (Photo Courtesy of FAA) (item 6, .PDF, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429805&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20View%20of%20broken%20PAPI%20and%20skid%20marks%20from%20airplane%20(Photo%20Courtesy%20of%20FAA)-Master.PDF - Photo 2 – View of damaged left wing (Photo Courtesy of FAA) (item 7, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429806&FileExtension=.PDF&FileName=Photo%202%20%E2%80%93%20View%20of%20damaged%20left%20wing%20(Photo%20Courtesy%20of%20FAA)%0D%0A-Master.PDF - Photo 3- Close up view of damaged left wing spar (Photo Courtesy of FAA) (item 8, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40429807&FileExtension=.PDF&FileName=Photo%203-%20Close%20up%20view%20of%20damaged%20left%20wing%20spar%20(Photo%20Courtesy%20of%20FAA)-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.