NYC97LA044 · Mooney 20F
Mooney 20F · Accident: loss of control in flight on approach
From Dillant Hopkins Airport (EEN) to an unrecorded destination
Event
- NTSB case
- NYC97LA044
- 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 20F
- Aircraft type
- Mooney 20
- 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
- N7112V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dillant Hopkins Airport (EEN), Keene, NHTo not recorded
- 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
- Approach · VFR go-around
- First occurrenceThe 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
Approximate · Estimated position: the centre of Jaffrey, NH, the place the record names. Not the accident site.
NTSB narrative
The airplane struck trees as the pilot tried to do a go-around. The pilot said that when he attempted the landing, '...the left side of the runway had a quartering wind. I'm making a perfect landing - all the numbers are right, airspeed, etc. - when all of a sudden everything goes bad. I gave power to go around and the plane balloons up twenty feet in the air. I'm pushing the nose down to get back to the runway but the plane keeps going to the left. I believe the nose struck the ground first.' The passenger said, '. It seemed like we were landing and taking off at the same time. We hit nose first and cartwheeled into the woods. We went backwards into the woods. One wing tore off. There was gasoline everywhere.' The pilot reported no mechanical malfunction. Examination of the airplane did not disclose evidence of mechanical malfunction.
Probable cause
The pilot's failure to maintain aircraft control during a go around attempt, which resulted in a loss of control and collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA044
- Event ID
- 20001208X07350
- Case number
- NYC97LA044
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: ddfb1a60dec3c282e9884a065129509d99e3d0474735fcfd8397dc7b554d572a; retrieved 2026-09-21T12:14:36.479Z.