FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC95LA003 · Cessna 172N

9 Oct 1994 · Center Harbor, NH, United States

Cessna 172N · Accident: dragged wing, rotor, pod, float or tail/skid during landing

Report a problem

Event

NTSB case
NYC95LA003
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 172N

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
N733MV
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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 · flare/touchdown
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
Dragged wing, rotor, pod, float or tail/skid
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 › Compensation for wind conditions, inadequate

Approximate · Estimated position: the centre of Center Harbor, NH, the place the record names. Not the accident site.

NTSB narrative

AFTER THE PILOT DEPARTED FROM THE SEAPLANE BASE IN THE RENTED FLOAT PLANE, HE MADE ONE EN ROUTE STOP AT ANOTHER LAKE, THEN LANDED AT HIS DESTINATION LAKE. AT THE DESTINATION LAKE HE GAVE LOCAL SCENIC RIDES TO FRIENDS. AT THE COMPLETION OF THE LAST FLIGHT, HE ESTABLISHED A SOUTHERLY FINAL APPROACH TO THE COVE. WHILE LANDING WITH A KNOWN GUSTING RIGHT CROSSWIND, THE LEFT WING CONTACTED THE WATER CAUSING THE AIRPLANE TO GROUND LOOP, AND THE SUBSEQUENT LEFT WING DAMAGE. WINDS REPORTED FROM AN AIRPORT 8 MILES SOUTH WERE FROM 210 DEGREES AT 12 KNOTS, WITH GUSTS TO 17. THE PILOT'S TOTAL FLIGHT TIME WAS REPORTED TO BE ABOUT 131 HOURS, WITH APPROXIMATELY 40 HOURS IN FLOAT PLANE OPERATION.

Probable cause

THE PILOT'S INADEQUATE COMPENSATION FOR A CROSSWIND CONDITION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC95LA003
Event ID
20001206X02504
Case number
NYC95LA003
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: 97bd8d0f31bf7ce850666dca76b9b01d12de9d4dcfa523800bc5c954eb41fe66; retrieved 2026-09-23T00:33:33.635Z.