ANC09CA016 · Cessna 172S
U.S. Air Force Cessna 172S · Accident: landing area overshoot
From Elmendorf Air Force Base (PAED) to Elmendorf Air Force Base (PAED)
Event
- NTSB case
- ANC09CA016
- 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 172S
- 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
- N453SP
- Operator
- U.S. Air Force
- Onboard fatalities
- Unknown
- Route
- From Elmendorf Air Force Base (PAED), Elmendorf AFB, AKTo Elmendorf Air Force Base (PAED), Elmendorf AFB, AK
- 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 · flare/touchdown
- Defining eventThe 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
- Landing area overshoot
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot/student, seated in the left seat, and the certified flight instructor, seated in the right seat, departed on a visual flight rules flight for mountain flying instruction and an Aero Club airplane checkout. The instructor decided to have the pilot land at an airport that had a 2,088 foot long runway. The first approach to the airport was high and fast, and the landing approach was aborted. On the second approach, the airplane was again high and fast, and touched down about 600 to 800 feet beyond the runway threshold. The runway surface was compacted snow and ice, and the braking action was poor. The airplane collided with a snow berm at the end of the runway, and received substantial damage to the landing gear and fuselage. The flight instructor did not take control of the airplane at any time before or during the accident sequence.
Probable cause
The flight instructor's lack of action to correct a high and fast landing approach which resulted in a long landing, and subsequent collision with a snow berm at the end of the runway. Contributing to the accident was the student pilot's improper approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC09CA016
- Event ID
- 20081230X44507
- Case number
- ANC09CA016
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: ec20b45d2f3ae1a2a84fdcaa8a212c77d531704fa3d98d92730fb692c5d74e9d; retrieved 2026-09-15T10:38:59.920Z.