Mooney M20J N201RF
27 November 2022 · Gaithersburg, Maryland, United States · Serious injuries
Summary
On 27 November 2022 at about 22:29 local time, a Mooney M20J registered N201RF was involved in an accident near Gaithersburg, Maryland, United States. 2 people were on board and 2 were seriously injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 22:29
- Classification
- Accident
- Location
- Gaithersburg, Maryland, United States
- Nearest airport
- Montgomery County Airpark (GAI)
- Coordinates
- 39.1844, -77.1886
- Aircraft
- Mooney M20J
- Registration
- N201RF
- Category
- Airplane
- Year built
- 1977
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- White Plains → Unknown
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Night
- NTSB number
- ERA23LA071
People
2 people were seriously injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 0 | 2 | 0 | 0 |
Probable cause
The pilot’s visual flight below published altitude minimums, which resulted in collision with a powerline tower structure.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The pilot was operating on an instrument flight rules (IFR) flight plan in dark night instrument meteorological conditions (IMC). As the pilot approached the destination airport, the air traffic controller attempted to vector him onto his requested GPS instrument approach procedure. The pilot was provided course corrections and heading changes from the controller, and was advised that the airplane before him had performed the missed approach procedure and diverted due to low cloud ceilings (200 ft above ground level [agl]). Flight track data revealed that the airplane was consistently below published minimum altitudes throughout the approach and was 500 ft below the minimum altitude prescribed at the final approach fix. The pilot continued the descent below the lowest minimums prescribed by the approach procedure, and about 1.25 miles from the runway and left of the runway centerline, the airplane impacted and became suspended in a power line tower at an elevation about 600 ft mean sea level (msl) and 100 ft above ground level. The airport was located at an elevation of 539 ft msl. Examination of the airplane revealed that there were no pre-impact mechanical anomalies that would have prevented normal operation. In an interview following the accident, the pilot stated that his course diversions during the flight were the result of a mis-programmed GPS. Throughout the interview, he could not articulate the features of his IFR-certified GPS, and stated that, in many situations, he used his handheld, VFR-only GPS to avoid the “complex keystrokes needed” to operate the IFR GPS. The pilot stated that he was not receiving vertical guidance on his GPS after intercepting the final approach course. He set an “alarm” to sound when the airplane had descended to 800 ft on the approach, but at 1,200 ft, he sighted the ground, and became focused on “keeping contact with the ground through the side window” and “pulling the airport out of the soup.” The pilot stated that he was familiar with the powerlines that he impacted and believed that he was beyond them. The lowest altitude allowed by the approach procedure was 789 ft msl, or 269 ft agl. However, this altitude was for an approach category that provided both lateral and vertical course guidance, and the pilot stated that he was not receiving vertical guidance. Whether the lack of vertical guidance was the result of the pilot’s mis-programming of the approach procedure or because he was referring to his VFR-only GPS for guidance was not determined. The lowest altitude allowed for an approach with only lateral guidance was 980 ft msl, or 460 ft agl. Based on the available information, the pilot became preoccupied with attempting to visually locate the runway and failed to maintain an effective scan of his instruments, which resulted in his descent below minimums, lateral deviation off the approach course, and collision with powerlines.
Quoted verbatim from the NTSB record.
Other Mooney M20J accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 9 Feb 2022 | Mooney M20J | Paradise, California, United States | Alfred W. Brown | Minor injuries | - |
| 25 Jun 2022 | Mooney M20J | Kerrville, Texas, United States | - | Fatal | 2 |
| 2 Dec 2022 | Mooney M20J | Falmouth, Massachusetts, United States | - | Fatal | 1 |
| 12 Jun 2022 | Mooney M20J | Charleston, South Carolina, United States | - | No injuries | - |
| 17 Oct 2022 | Mooney M20J | Luskintyre, Australia | - | Serious injuries | - |
| 12 Feb 2022 | Mooney M20J | Katy, Texas, United States | Aviation Partners SA LLC | Serious injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 1 Mar 2022 | Robinson R22 | Fallston, Maryland, United States | Fly For Fun Aircraft LLC | Minor injuries | - |
| 7 Mar 2022 | Cessna 525 | Middle River, Maryland, United States | Executive Flight Services LLC | No injuries | - |
| 22 Jul 2022 | Vulcanair V1 | Salisbury, Maryland, United States | Delaware State University | No injuries | - |
| 19 Aug 2022 | Mooney M20E | Hollywood, Maryland, United States | Walls of Time Inc | No injuries | - |
| 22 Apr 2022 | Cessna 172 | Westminster, Maryland, United States | Clearview Flying Club Inc | No injuries | - |
| 19 Jun 2022 | Piper PA-38-112 | Gaithersburg, Maryland, United States | - | No injuries | - |