FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC01LA110 · Cessna 172K

22 Apr 2001 · Honesdale, PA, United States

Cessna 172K · Accident: loss of control on ground/water during landing

From Cherry Ridge Airport (N30) to an unrecorded destination

Report a problem

Event

NTSB case
NYC01LA110
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
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

Cessna 172K

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
N79210
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cherry Ridge Airport (N30), Honesdale, PATo 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 › Directional control, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, he entered the landing pattern for multiple landings on Runway 35. During the second landing, he encountered what he believed to be "variable cross/tail wind gusts" during landing rollout. The airplane veered off the runway, and onto an adjacent, water-saturated turf runway. The wheels furrowed into the turf, and the propeller and right wing struck the ground. There were no weather reporting facilities at the airport, and the nearest airport that had reporting facilities was approximately 25 nautical miles to the southwest, and separated by mountainous terrain. Weather, recorded at that airport about 25 minutes after the accident, included clear skies and winds from 230 degrees at 6 knots.

Probable cause

The pilot's loss of directional control during the landing roll. A factor was gusting winds.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC01LA110
Event ID
20010502X00848
Case number
NYC01LA110
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: b8c968d23d78a05ed2df00b1bd1658a6e71de41d8caa867fa76a954c7c515aa6; retrieved 2026-09-22T12:00:41.157Z.