FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC01LA210 · Cessna 172L

12 Aug 2001 · Brockport, NY, United States

Cessna 172L · Accident: in flight collision with terrain/water during landing

From Akron Fulton International Airport (AKR) to Ledgedale Airpark (7G0)

Report a problem

Event

NTSB case
NYC01LA210
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 172L

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
N7878G
Operator
James Beck
Onboard fatalities
Unknown
Route
From Akron Fulton International Airport (AKR), Akron, OHTo Ledgedale Airpark (7G0), Brockport, NY
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
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
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 › Go-around, delayed

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

NTSB narrative

At the completion of a night, cross-country flight, the pilot attempted to land at his home airpark under dark night conditions. The rotating beacon was operating, and per the NOTAM in effect, the runway and taxiway lights were inoperative. The pilot made an approach, then went around because he could not see the runway "soon enough." The pilot made another approach, and again attempted to go around. Shortly after commencing the go-around attempt, the airplane impacted the ground about 300 feet to the right of, and 700 feet from the approach end of the runway. The impact point was also 50 feet to the right of the parallel taxiway. There were no mechanical malfunctions noted.

Probable cause

The pilot's delayed go-around during the landing attempt. Factors included the dark night conditions and the pilot's inadequate preflight decision to fly to an airport with inoperative surface lighting.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC01LA210
Event ID
20010814X01681
Case number
NYC01LA210
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-08-13.
  • API snapshot SHA-256: f1c8ab0110d10b6724e079162b063d25c01330886c45adf3fad53a18d0f1e5e8; retrieved 2026-09-21T09:53:50.341Z.