ERA11CA331 · Cessna 172
Cessna 172 · Accident: loss of control in flight during landing
From Pittsfield Municipal Airport (PSF) to Finger Lakes Regional Airport (0G7)
Event
- NTSB case
- ERA11CA331
- 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 172
- 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
- N8895B
- Operator
- Meranda Seth
- Onboard fatalities
- Unknown
- Route
- From Pittsfield Municipal Airport (PSF), Pittsfield, MATo Finger Lakes Regional Airport (0G7), Seneca Falls, 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
- Defining eventThe 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
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, several minutes after takeoff the weather began to deteriorate and the sky turned black with convective activity reported in the area. He decided to divert to a nearby airport which had a 4,000-foot long by 75-foot wide turf runway. As the pilot approached the runway he could not determine where the approach end was located. The airplane approached the runway high and fast. The pilot did not think he would be able to stop the airplane before reaching the end of the runway, so he aborted the landing. One witness reported that the airplane aborted the landing with less than 1/4 of the runway's total length remaining. During the attempted climb out, the pilot thought that the engine felt less powerful but could not recall any specific abnormal indications. Without sufficient airspeed to climb above approaching trees, the pilot stalled the airplane into a pond, resulting in substantial damage to the left wing and empennage. A postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunctions or failures.
Probable cause
The pilot's delayed decision to abort the landing and execute a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA331
- Event ID
- 20110609X25931
- Case number
- ERA11CA331
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 23cfb1b477fff0b1f3f8e5da7a5a4ab6b6e2cea45729ee3556ae1d1bf1cf16ea; retrieved 2026-09-15T16:15:48.041Z.