FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA307 · Mooney M20F

10 Jul 2022 · Cragsmoor, NY, United States

Mooney M20F · Accident: controlled flight into terrain/object (CFIT) en route

From Joseph Y Resnick Airport (N89) to Brookhaven Calabro Airport (HWV)

Report a problem

Event

NTSB case
ERA22LA307
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 M20F

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
N600FS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Joseph Y Resnick Airport (N89), Ellenville, NYTo Brookhaven Calabro Airport (HWV), Shirley, NY
Aircraft age
About 48 years (built 1974)
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
En route · climb to cruise
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that he departed with the airplane’s fuel tanks full and proceeded along a route recommended by local pilots to clear the surrounding terrain. The pilot noted that the airplane’s climb performance was “less than normal” and that the airplane was “struggling” to maintain a climb rate of 500 ft per minute. As the airplane approached terrain, the pilot considered a “hard turn,” but was concerned about losing airspeed and the proximity of the terrain and chose to continue at the airplane’s best rate of climb. The airplane subsequently began to scrape across trees in a level attitude, then settled into the trees.

The airplane came to rest in heavily-wooded terrain at an elevation about 2,230 ft mean sea level (msl) southeast of the departure airport. Examination of the engine revealed that the induction air boot from the airbox to the fuel injector unit was severely degraded. No other anomalies were observed that would have precluded normal operation.

Performance information from the airplane’s pilot operating handbook indicated that the expected rate of climb given the airplane’s gross weight and the atmospheric conditions present at the time of the accident was about 1,300 ft per minute at a best rate of climb speed of 113 mph indicated airspeed. Based on this information, the airplane would travel a horizontal distance of about 2.8 statute miles (sm) to reach an altitude of 2,500 ft msl. The accident site was located about 3 sm straight-line distance from the departure airport.

The departure airport was located in a valley adjacent to a ridgeline that ran northeast/southwest. Another airport was located in the valley about 9 nautical miles south of the departure airport. Review of the sectional chart revealed that the accident site was located just north of a peak with a charted elevation of 2,289 ft msl, the highest terrain in the immediate vicinity of the departure airport.

It is possible that the condition of the fuel injector airbox boot could have affected airflow over the fuel injector impact tubes and the performance of the fuel injectors. Although this effect could not be quantified based on the available information, it may have contributed to the pilot’s perception of decreased climb performance. If the pilot had concerns about the airplane’s climb performance after takeoff, the options available included returning to the departure airport, continuing south along the valley and gaining altitude before turning on course, or diverting to the airport to the south. However, the available evidence suggests that, after takeoff, the pilot turned the airplane toward the destination airport and the area of highest terrain surrounding the departure airport, where the airplane subsequently impacted trees and rising terrain.

Probable cause

The pilot’s decision to continue toward rising terrain despite observing the airplane’s decreased climb performance after takeoff, which resulted in flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA307
Event ID
20220712105455
Case number
ERA22LA307
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, coordinates, 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: 837dc1ed83921190b5c6ee373fc88fc8cdda3cfb3ed229a49328bedfc63ae352; retrieved 2026-09-16T15:26:45.823Z.