SEA00LA125 · Cessna 172I
Cessna 172I · Accident: overrun during landing
From Page Airport (WA10) to Sandy River Airport (03S)
Event
- NTSB case
- SEA00LA125
- 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 172I
- Aircraft type
- Cessna 172
- 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
- N35359
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Page Airport (WA10), Camas, WATo Sandy River Airport (03S)
- 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
- Overrun
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that on final, he was higher than necessary. He subsequently touched down at the center of the field (the turf runway is 2,115 feet long.) He stated that he 'should have gone around but by the time I realized I wasn't going to make a successful landing it was [too] late.' The aircraft went off the end of the runway into soft dirt and blackberry vines. The pilot stated that he 'thought there was a pile of brush so [I] pushed the left rudder and ground looped rather than hit head on the brush.' The pilot indicated on his NTSB accident report that no mechanical malfunction or failure was involved in the accident.
Probable cause
The pilot's failure to attain the proper touchdown point for landing, and his failure to go around from the improperly executed approach. Factors included the pilot's failure to attain the proper glidepath on the approach, a short landing runway, and vegetation off the end of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00LA125
- Event ID
- 20001212X21605
- Case number
- SEA00LA125
- 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: 3a6382db680bc034e16092ece43cfb63b0e0e8b625e3fd4f147d9b3d3decc0f3; retrieved 2026-09-22T12:43:53.762Z.