FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA055 · Mooney M20F

10 Nov 2010 · Copake, NY, United States

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

From Lorain County Regional Airport (LPR) to BGR · Great Barrington, MA

Report a problem

Event

NTSB case
ERA11FA055
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
2 · all aircraft and ground
Ground fatalities
Unknown
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
N6878V
Operator
John B Welch · private individual
Onboard fatalities
Unknown
Route
From Lorain County Regional Airport (LPR), Elyria, OHTo BGR · Great Barrington, MA
Aircraft age
Not recorded
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 · descent
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

  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The airplane was approaching the destination airport in night visual meteorological conditions, on an instrument flight rules (IFR) flight plan. The destination airport was at an elevation of 739 feet mean sea level (msl), located in the vicinity of mountainous terrain. About 10 miles from the destination airport, the pilot elected to cancel his IFR clearance. At that time, the airplane was at 3,900 feet msl and began a descent consistent with a 45-degree entry to a left downwind leg of the destination airport traffic pattern, which was 1700 feet msl. About 2 minutes later, the airplane had descended to 2,400 feet and was approximately 1/4 mile from the 2,000-foot summit of a mountain. About 10 seconds later, the airplane had descended to 2,100 feet, about 1,000 feet horizontally from the summit. The airplane impacted trees near the summit and came to rest about 500 feet beyond the initial impact. The summit was approximately 5 miles southwest from the destination airport. Examination of the wreckage did not reveal any preimpact mechanical malfunctions. The end of civil twilight occurred about 2 hours prior to the accident. Moonset occurred about 1 hour after the accident and the phase of the moon was waxing crescent with only 22 percent of the moon's visible disc illuminated.

Probable cause

The pilot's failure to monitor and maintain clearance from mountainous terrain during a visual descent to the destination airport at night, which resulted in controlled flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA055
Event ID
20101113X00616
Case number
ERA11FA055
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-11-11.
  • API snapshot SHA-256: 8ba6268417680432960dbbf0fde145287db3896381104b4826dc428f6f12b775; retrieved 2026-09-13T21:07:46.101Z.