SEA97LA134 · Cessna 172C
Cessna 172C · Accident: nose over during landing
From Fall City Airport (1WA6) to an unrecorded destination
Event
- NTSB case
- SEA97LA134
- 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 172C
- 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
- N1319Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fall City Airport (1WA6)To 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 · landing roll
- 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
- Nose over
- 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 › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Even though the pilot had 1,600 feet of paved runway available, he elected to land on the turf extension/overrun area. Because there had been extensive rains in the area during the week before the accident, the turf portion of the runway was wet and soft. According to the pilot, the aircraft touched down on the left side of the runway in a tire rut which contained standing water. The aircraft was then pulled further to the left, whereupon the nose gear dug into the soft ground and the aircraft nosed over.
Probable cause
the pilot's selection of unsuitable terrain for landing. The soft, wet terrain was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA97LA134
- Event ID
- 20001208X08250
- Case number
- SEA97LA134
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1997-06-11.
- API snapshot SHA-256: 139b433623e6bcb6b66d1869ce216aee9db64f0a9b6cf8cc623da9af63499dec; retrieved 2026-09-22T19:28:50.914Z.