BFO93LA084 · Cessna A150M
Cessna A150M · Accident: in flight encounter with weather during landing
From Pittsburgh Northeast Airport (9G1) to Pittsburgh Northeast Airport (9G1)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- BFO93LA084
- 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 A150M Possible conflict
- 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
- N9891J
- Operator
- Aerobat V
- Onboard fatalities
- Unknown
- Route
- From Pittsburgh Northeast Airport (9G1)To Pittsburgh Northeast Airport (9G1)
- 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 · flare/touchdown
- 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 encounter with weather
- 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 › Directional control, not maintained
- Pilot in command › Proper alignment, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT ON HIS RETURN FROM A DEMONSTRATION FLIGHT HE ENCOUNTERED AN UPDRAFT AND DOWNDRAFT WHILE LANDING. HE STATED THAT AS HE NEARED HIS POSITION FOR LANDING, THE WIND CHANGED DIRECTION, AND AS HE WAS ABOUT TO APPLY POWER, THERE WAS AN UPDRAFT AND THE AIRPLANE ALMOST STALLED. HE REPORTED THAT HE PUSHED THE NOSE DOWN AND CONTINUED INTO THE FLARE/TOUCHDOWN BUT THE AIRPLANE WAS LEFT OF THE CENTERLINE AND VEERING TOWARDS AN UNOCCUPIED AIRCRAFT THAT WAS PARKED 22 FEET OFF THE SIDE OF THE RUNWAY ON A GRASSY AREA. DURING THE LANDING, THE LEFT WING STRUCK THE PARKED AIRPLANE. THE PILOT STATED THAT THERE WAS NO MECHANICAL MALFUNCTION AND THE ACCIDENT COULD HAVE BEEN PREVENTED, IF THE AIRPLANE HAD NOT BEEN PARKED CLOSE TO THE RUNWAY.
Probable cause
FAILURE OF THE PILOT TO MAINTAIN DIRECTIONAL CONTROL AND PROPER RUNWAY ALIGNMENT. THE ADVERSE WEATHER CONDITION AND PROXIMITY OF THE PARKED AIRCRAFT WERE RELATED FACTORS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA084
- Event ID
- 20001211X12314
- Case number
- BFO93LA084
- 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: c5991caaa8ccaa2638591c5dec668cb4f4205739cf62520e992c61a004f29704; retrieved 2026-09-23T02:06:48.015Z.