SEA00LA010 · Cessna 172M
Cessna 172M · Accident: overrun during landing
From Sandpoint Airport (SZT) to Friedman Memorial Airport (SUN)
Event
- NTSB case
- SEA00LA010
- 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 172M
- 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
- N12376
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sandpoint Airport (SZT), Sandpoint, IDTo Friedman Memorial Airport (SUN), Hailey, ID
- 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
- 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
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While making a precautionary landing at a remote grass airstrip, the aircraft did not touch down until after it had floated at least one-quarter of the way down the 5,000 foot long grass runway. After touchdown, and prior to the pilot applying brakes, a gust of wind lifted the aircraft back into the air. After touching down a second time, the pilot applied maximum braking, but he was unable to stop the aircraft before it departed the end of the runway and went over a 20 foot drop-off. At the bottom of the drop-off, the aircraft encountered rough/uneven terrain where it experienced a collapse of the nose gear and one main gear leg.
Probable cause
The pilot's failure to land at the proper touchdown point. Factors include a wind gust, a grass runway, and a drop-off into rough terrain at the end of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00LA010
- Event ID
- 20001212X20057
- Case number
- SEA00LA010
- 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 1999-10-28.
- API snapshot SHA-256: 97e826ab190f4235dd777883b3a4933b33b60cc016ab5f0e504a8b35b9fd2029; retrieved 2026-09-22T13:46:25.416Z.