SEA06CA081 · Cessna 172 S
Air Center of Salt Lake Cessna 172 S · Accident: overrun during landing
From U42 · Salt Lake City, UT to Malad City Airport (MLD)
Event
- NTSB case
- SEA06CA081
- 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
- Unknown
- 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 172 S
- 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
- N679SP
- Operator
- Air Center of Salt Lake
- Onboard fatalities
- Unknown
- Route
- From U42 · Salt Lake City, UTTo Malad City Airport (MLD), Malad City, 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
- 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 obtained/maintained
- Pilot in command(cfi) › Remedial action, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
In a written statement the private pilot, who was at the controls during the accident, stated that after a high approach the airplane touched down at a point where it was "too late to execute a missed approach, because we had used so much of the runway. We both slammed on the brakes and started skidding off the end of the runway. We went through a barbed wire fence and hit a ditch. Hitting the ditch launched the aircraft over a road. We went through another fence and hit another ditch, flipping the aircraft upside down." The commercial pilot/certified flight instructor reported that the airplane was too high during the approach and just as he was going to instruct the pilot to go-around "...the wheels touched down and the tires started to lockup."
Probable cause
The private pilot's improper touchdown point during landing and the certified flight instructors delayed remedial action. Ditches and fences were factors in the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06CA081
- Event ID
- 20060525X00627
- Case number
- SEA06CA081
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-04-23.
- API snapshot SHA-256: 7701c607e0fea6c816dc7e8fea0b31b7db4f15d1fb712199c86c88bd2200bf60; retrieved 2026-09-22T04:58:09.486Z.