BFO88FA025 · Cessna 150E
Cessna 150E · Accident: in flight collision with object on approach
Event
- NTSB case
- BFO88FA025
- 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 150E
- Aircraft type
- Cessna 150
- 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
- N6202T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- In flight collision with object
- 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
- 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 › Aborted landing, delayed
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PLT ELECTED TO INITIATE THE FLT EVEN THOUGH THE FLAPS MALFUNCTIONED DURING THE PREVIOUS FLT. SHORTLY AFTER TAKEOFF THE PLT WAS UNABLE TO KEEP THE FLAPS IN THE EXTENDED POSITION. THE PLT HAD NOT BEEN FEELING WELL ON THE MORNING OF THE FLT AND FELT WORSE AS THE FLT PROGRESSED. BECAUSE HE WAS ILL, THE PLT DECIDED TO RETURN TO THE ARPT. PRIOR TO TAKEOFF HE HAD DECIDED HE WOULD LAND ON RWY 36 IF THE FLAPS WERE INOP. ON TAKEOFF WINDS WERE FROM 270 DEG BUT HAD SHIFTED TO THE SOUTH/SOUTHWEST DURING THE FLT. THE PLT WAS SO PREOCCUPIED WITH WANTING TO LAND THE ACFT BECAUSE HE WAS ILL THAT HE FAILED TO ADJUST HIS A/S FOR A NO-FLAP LANDING. THE ACFT FLOATED 3/4 OF THE WAY DOWN THE RWY BEFORE THE PLT INITIATED THE ABORTED LANDING. THE ACFT CONTACTED TREES OFF THE DEPARTURE END OF RWY AND COLLIDED WITH TERRAIN. A SPRING WAS FOUND ON THE FLAP HANDLE BTWN THE ROD AND RELEASE BUTTON. PERSONS INTERVIEWED DENIED KNOWLEDGE OF WHERE THE SPRING CAME FROM. THE FLAPS OPERATED PROPERLY DURING POST ACCIDENT TESTING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record BFO88FA025
- Event ID
- 20001213X25213
- Case number
- BFO88FA025
- 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: c880c397467bcff83f330742cd8014d63c0aea434eb532afdb792527e7564f93; retrieved 2026-09-23T10:54:31.733Z.