FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA179 · Mooney M20M

4 Apr 2022 · Manville, NJ, United States

Guthrie Group Mooney M20M · Accident: controlled flight into terrain/object (CFIT) on approach

From Piedmont Triad International Airport (GSO) to an unrecorded destination

Report a problem

Event

NTSB case
ERA22LA179
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Mooney M20M

Aircraft type
Mooney M20
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N41XL
Onboard fatalities
Unknown
Route
From Piedmont Triad International Airport (GSO), Greensboro, NCTo not recorded
Aircraft age
About 16 years (built 2006)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR go-around
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, prior to landing, he obtained weather information as specified on the instrument approach procedure chart, which was from an airport about 18 nm from the landing airport. The wind was reported as being from 350° at 7 knots, which favored runway 07. During landing, the airplane floated longer than anticipated and bounced upon touchdown. The pilot added power and elected to do a go-around maneuver; however, the airplane was unable to attain a sufficient rate of climb and impacted trees at the departure end of the runway, which resulted in substantial damage to the fuselage and right wing. A witness stated that the weather obtained from the airport specified on the instrument approach plate did not match the conditions at the airport at the time of the accident, which included a 10-kt tailwind on runway 07. The nearest airport's weather observation system, about 7 miles from the accident airport, included wind at 310° at 11 kts gusting to 17 kts. The pilot reported that there were no preimpact mechanical failures or malfunctions of the airplane that would have precluded normal operation.

Probable cause

The pilot’s delayed go-around decision following an encounter with a tailwind during landing, which resulted in an inability to climb and subsequent impact with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA179
Event ID
20220405104893
Case number
ERA22LA179
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: f37e2f8c34ef7660a4cfc080a9252ced0a1b73e0fb8c1fead51bb1c22ca73a08; retrieved 2026-09-16T15:06:23.147Z.