NYC84LA251 · Cessna C172
Cessna C172 · Accident: loss of control in flight on approach
From Finger Lakes Regional Airport (0G7) to Bloomsburg Municipal Airport (N13)
Event
- NTSB case
- NYC84LA251
- 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 C172
- 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
- N2627L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Finger Lakes Regional Airport (0G7), Seneca Falls, NYTo Bloomsburg Municipal Airport (N13), Bloomsburg, PA
- 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
- Approach · VFR go-around
- 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 in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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 › Airspeed, not maintained
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS DITCHED IN A RIVER DURING AN ATTEMPTED GO-AROUND. THE PLT SAID HE APPROACHED THE ARPT WITH FULL FLAPS AT ABOUT 70 MPH. DURING THE ABORTED LANDING HE APPLIED FULL POWER AND THEN EXPERIENCED A SUDDEN LOW LEFT WING, A MUSHY CONTROL FEELING AND A LOSS OF AIRSPEED. THE PLT PUSHED THE NOSE DOWN SHARPLY. THE PLT SAID THAT DURING HIS ATTEMPTS TO REGAIN CONTROL THE ENGINE QUIT. THE PLT SAID HE CONCENTRATED ON KEEPING THE WINGS LEVEL AND RAISING THE NOSE FOR A WATERLANDING. THE ACFT NOSED UNDER AFTER TOUCHDOWN. THE PLT STATED THAT HE BELIEVES HIS MISHANDLING OF THE ACFT CAUSED THE STALL AND ENGINE FAILURE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC84LA251
- Event ID
- 20001214X40489
- Case number
- NYC84LA251
- 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: 644c47e0fa69d1ddd793ba67ba88357f12d0a64a3578669459e78f7ac7b80a21; retrieved 2026-09-22T02:11:26.425Z.