FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO89LA030 · Cessna 150F

19 Apr 1989 · New Cumberland, WV, United States

Cessna 150F · Accident: loss of control in flight on approach

Report a problem

Event

NTSB case
BFO89LA030
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 150F

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
N3570L
Operator
Alex Wright
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
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

  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained
  • Pilot in command › Go-around, delayed

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

NTSB narrative

THE PLT STATED THAT THE LANDING APCH WAS FAST AND HIGH SO HE ELECTED TO GO-AROUND. DURING THE GO-AROUND THE ACFT SETTLED ONTO THE RUNWAY AND TRAVELED OFF THE LEFT SIDE OF THE RUNWAY. IT CONTINUED INTO A GRASS AREA BEFORE STRIKING A WOODEN TEE HANGAR STRUCTURE. INSPECTION FAILED TO REVEAL ANY FAILURE/MALFUNCTION OF THE ACFT; HOWEVER, THE CARB HEAT CONTROL WAS FOUND IN THE ON POSITION AND THE SPARK PLUGS WERE SOOTED. THE PLT REPORTED WINDS FROM 270 DEGS AT 10 KTS. THE LANDING WAS BEING MADE ON RWY 22.

Probable cause

THE PILOT'S FAILURE TO COMPENSATE FOR CROSSWIND CONDITIONS DURING AN ATTEMPTED GO-AROUND. CONTRIBUTING FACTORS WERE THE CROSSWIND CONDITION AND THE PILOT'S LOW LEVEL OF EXPERIENCE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO89LA030
Event ID
20001213X28047
Case number
BFO89LA030
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: 7880701da33864578d73efa5c82f89999fc69209bbcd3ba234498b931d967ef4; retrieved 2026-09-23T07:41:29.610Z.