FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC93LA063 · Cessna 172M

4 Feb 1993 · VALLEY POINT, WV, United States

Cessna 172M · Accident: overrun during landing

From North Central West Virginia Airport (CKB) to Valley Point Airport (WV29)

Report a problem

Event

NTSB case
NYC93LA063
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 172M

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
N9839V
Operator
Carl E. Marsh · private individual
Onboard fatalities
Unknown
Route
From North Central West Virginia Airport (CKB), Clarksburg, WVTo Valley Point Airport (WV29)
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
Overrun
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 › Aborted landing, not performed
  • Pilot in command › Visual/aural detection

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

NTSB narrative

THE PILOT WAS LANDING ON A 2800 FT LONG RUNWAY. THE TERRAIN OFF THE DEPARTURE END OF THE RUNWAY SLOPED DOWN. THE PILOT SAID HE TOUCHED DOWN AT HIS NORMAL POINT; HOWEVER, THE AIRPLANE DID NOT DECELERATE NORMALLY AND RAN OFF THE DEPARTURE END OF THE RUNWAY. THE AIRPLANE BECAME AIRBORNE AGAIN AND THEN SETTLED INTO TREES. THE PILOT SAID THIS WAS HIS FIRST LANDING WEARING A HEADSET AND HE HAD FAILED TO CLOSE THE THROTTLE COMPLETELY UPON TOUCHDOWN. IN ADDITION, HE SAID, '...I DID NOT HEAR THE MOTOR OR OTHER SOUNDS OF SPEED. I DID NOT ADJUST TO JUDGING SPEED BY SIGHT....'

Probable cause

THE FAILURE OF THE PILOT TO MAKE A REJECTED LANDING WHEN THE AIRPLANE FAILED TO DECELERATE PROPERLY. A FACTOR RELATED TO THE ACCIDENT WAS THE FAILURE OF THE PILOT TO CLOSE THE THROTTLE UPON TOUCHDOWN.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC93LA063
Event ID
20001211X11885
Case number
NYC93LA063
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: de3e7e45d962df1d432591b605ff6ae65414537ae399bdf39d30e82181137aeb; retrieved 2026-09-23T02:20:37.255Z.