NYC91LA106 · Cessna 172P
Interstate Aviation Cessna 172P · Accident: loss of control on ground/water during landing
From Martha's Vineyard Airport (MVY) to an unrecorded destination
Event
- NTSB case
- NYC91LA106
- 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
Cessna 172P
- Aircraft type
- Cessna 172
- 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
- N64182
- Operator
- Interstate Aviation
- Onboard fatalities
- Unknown
- Route
- From Martha's Vineyard Airport (MVY), MARTHAS VINEYD, MATo 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
- Landing · landing roll
- 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 on ground/water
- 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 › Aircraft control, not maintained
- Pilot in command › Compensation for wind conditions, not maintained
- Pilot in command › Flight controls, improper use of
Approximate · Estimated position: the centre of Burlington, CT, the place the record names. Not the accident site.
NTSB narrative
THE PILOT WAS RETURNING FROM A SHORT X C FLIGHT. HE MADE A GO-AROUND ON HIS FIRST APPROACH TO RUNWAY 01 BECAUSE HE 'TURNED IN TOO CLOSE.' ON HIS SECOND APPROACH HE TOUCHED DOWN ON THE APPROACH END AND THEN VEERED OFF THE RUNWAY TO THE RIGHT. HE APPLIED POWER FOR A GO AROUND AND THEN CLOSED THE THROTTLE. THE AIRPLANE STRUCK A ROCK WITH THE RIGHT LANDING GEAR WHICH COLLAPSED AND THE AIRPLANE CAME TO A STOP ON ITS RIGHT WING. THE PILOT HAD A TOTAL TIME OF 113 HOURS WITH 20 HOURS IN THE PRECEDING 6 MONTHS. PRIOR TO THAT HE HAD GONE 4 YEARS WITH NO FLYING. THE WINDS WERE REPORTED TO BE FROM THE WEST AT 5 TO 10 KNOTS WITH GUSTS TO 15 KNOTS.
Probable cause
THE FAILURE OF THE PILOT TO MAINTAIN DIRECTIONAL CONTROL DURING THE LANDING. FACTORS RELATED TO THE ACCIDENT WERE: IMPROPER USE OF THE FLIGHT CONTROLS BY THE PILOT, HIS LACK OF RECENT EXPERIENCE AND TOTAL TIME, AND THE CROSSWIND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC91LA106
- Event ID
- 20001212X16863
- Case number
- NYC91LA106
- 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: 20c09dccf93fbd2071717f1a71f5115888a59f1fe05f32a191b0819bf6d5ae1b; retrieved 2026-09-23T04:25:51.820Z.