BFO94LA029 · Cessna 152
Cessna 152 · Accident: loss of control on ground/water during landing
Event
- NTSB case
- BFO94LA029
- 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 152
- Aircraft type
- Cessna 152
- 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
- N94963
- 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
- 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
- Loss of control on ground/water
- 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
Approximate · Estimated position: the centre of Plymouth, MA, the place the record names. Not the accident site.
NTSB narrative
The student pilot reported that during the flare/touchdown a gust of wind raised the airplane's left wing and the right gear contacted the ground. The pilot stated that the airplane started to pivot to the right so he added full aileron and left rudder to get the airplane back on the runway's centerline. The airplane veered to the left and contacted a snow bank located along the left side of the runway. The right wing was substantially damaged. The pilot reported that the wind was coming from a magnetic heading of 330 degrees at a velocity of 15 knots. The pilot wrote under the Recommendations Section (How could this accident been prevented) on the Pilot/Operator Aircraft Accident Report Form, 'AMOS (Automated Service Observing System) at the [airport], [reporting] wind speed [and direction] have been INOP at least since May [1993], two of the most important items [needed] by pilots. [There is] no radio [frequency] available for in-[flight] AMOS.'
Probable cause
the pilot's failure to maintain directional control during the flare/touchdown.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO94LA029
- Event ID
- 20001206X00595
- Case number
- BFO94LA029
- 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: c99b1149b9f2bbf47eb5e2314fab1d43d45aaeb51b6ac5242584e137e74a4833; retrieved 2026-09-23T01:22:40.456Z.