BFO95LA070 · Piper PA-38-112
Piper PA-38-112 · Accident: loss of control in flight on approach
From NOO · Oswego, NY to 4B2
Event
- NTSB case
- BFO95LA070
- 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
Piper PA-38-112
- Aircraft type
- Piper PA-38
- 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
- N2423A
- Operator
- George e Barth · private individual
- Onboard fatalities
- Unknown
- Route
- From NOO · Oswego, NYTo 4B2
- 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; Tree(s)
- 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 › Raising of flaps, improper
Approximate · Estimated position: the centre of Utica, NY, the place the record names. Not the accident site.
NTSB narrative
THE PILOT REPORTED THAT UPON ARRIVING AT THE DESTINATION AIRPORT HE CHECKED FOR A WINDSOCK, BUT HE DID NOT SEE ONE SO HE DECIDED TO USE RUNWAY 32 AS HE HAD USED RUNWAY 33 AT HIS LAST DEPARTURE AIRPORT, ABOUT 50 MILES AWAY. DURING THE LANDING HE NOTICED THAT HE WAS LANDING WITH A TAILWIND, AND HE WAS UNABLE TO SLOW THE AIRPLANE FOR THE LANDING SO HE DECIDED TO EXECUTE A GO-AROUND. HE ATTEMPTED TO RETRACT 20 DEGREES OF FLAPS, BUT THE FLAP HANDLE WENT TO THE FULL UP (RETRACTED) POSITION. THE AIRPLANE BEGAN TO SINK AND THE TREES WERE GETTING CLOSER SO HE STALLED THE AIRPLANE. THE PILOT STATED THAT THERE WAS NO MECHANICAL MALFUNCTION, AND THE ACCIDENT COULD HAVE BEEN PREVENTED IF HE HAD 'BETTER PREPARATION OF PERFORMANCE ON A HOT HUMID DAY.'
Probable cause
The pilot's improper retraction of the flaps.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO95LA070
- Event ID
- 20001207X03641
- Case number
- BFO95LA070
- 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: 8ae3d470e19ae80995ab7051d80006485b82c90dc7be425930ddade8cb59c81a; retrieved 2026-09-21T22:15:04.140Z.