SEA01LA026 · Cessna 150C
Cessna 150C · Accident: loss of control on ground/water during landing
From Independence State Airport (7S5) to Pacific City State Airport (PFC)
Event
- NTSB case
- SEA01LA026
- 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 150C
- 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
- N7800Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Independence State Airport (7S5), Independence, ORTo Pacific City State Airport (PFC)
- 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
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated the aircraft's approach speed was higher than normal, and the aircraft subsequently touched down 200-300 feet beyond the landing threshold of runway 32. During the landing roll, the pilot intentionally steered the airplane right of runway centerline in an effort to stop the aircraft utilizing the run up area at the departure end of the runway. However, the aircraft departed the right side of the runway and subsequently collided with heavy vegetation adjacent to the runway. The aircraft's right wing and empennage sustained substantial damage. According to the Airport/Facility Directory, runway 32 is 1,875 feet in length and 30 feet in width. The pilot reported that there were no pre-existing mechanical anomalies with the aircraft that may have contributed to the accident.
Probable cause
The pilot's failure to maintain aircraft control during the landing roll. Factors include a higher than normal approach speed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA01LA026
- Event ID
- 20010114X00301
- Case number
- SEA01LA026
- 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: 9372e42a4764c1ef69e423cb3b6a80597d5ef7337b0898618ff6f5465b082e87; retrieved 2026-09-22T12:17:54.814Z.