NYC82DA213 · Mooney M20J
Aero Venture Mooney M20J · Accident: in flight collision with terrain/water on approach
From 87 · Robbinsville, NJ to DuBois, PA
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC82DA213
- 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 M20J
- 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
- N1156U
- Operator
- Aero Venture
- Onboard fatalities
- Unknown
- Route Possible conflict
- From 87 · Robbinsville, NJTo DuBois, PA
- 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
- In flight collision with terrain/water
- 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
- Stall/mush
- 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
- Pilot in command › Airspeed, misjudged
- Pilot in command › Distance, misjudged
- Pilot in command › Go-around, delayed
Approximate · Estimated position: the centre of Matawan, NJ, the place the record names. Not the accident site.
NTSB narrative
THE PILOT STATED THAT HE HAD NEVER BEEN AT THIS AIRPORT BEFORE. DURING ARRIVAL, HE LANDED ON RUNWAY 27 TOWARD THE SETTING SUN WITH A CROSSWIND FROM THE LEFT. HE STATED THAT HE TOUCHED DOWN FIRMLY ON THE FIRST 1/3 OF THE RUNWAY, THEN THE AIRCRAFT FLOATED BRIEFLY. HE REPORTED THAT HE GOT ALL WHEELS ON THE GROUND AND THE AIRSPEED BELOW VSO WITH ABOUT 1/3 OF THE RUNWAY REMAINING. FULL BRAKES WERE APPLIED, BUT DUE TO THE SUNGLARE, THE PILOT HAD DIFFICULTY JUDGING THE DISTANCE REMAINING. WHEN HE REALIZED HE COULD NOT STOP SAFELY ON THE RUNWAY, HE INITIATED A GO-AROUND AFTER LIFT-OFF AT THE END OF THE RUNWAY, THE AIRCRAFT MUSHED INTO BRUSH AND SMALL TREE STUMPS AND CAME TO REST ABOUT 200 FT FROM THE DEPARTURE END.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC82DA213
- Event ID
- 20020917X04008
- Case number
- NYC82DA213
- 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: e7946f9563a24e94c9af86a8c456c121aba71f4f3824d36def0f73ba221d12d2; retrieved 2026-09-24T01:18:35.143Z.