Frontier Flying Service Piper PA-31-350 accident
Piper PA-31-350 · Accident: runway excursion during landing
From Ralph Wien Memorial Airport (OTZ) to Buckland Airport (PABL)
Event
- NTSB case
- ANC09LA025
- 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
- Charter & commuter
- 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
Piper PA-31-350
- Aircraft type
- Piper PA-31
- 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
- N4112K
- Operator
- Frontier Flying Service
- Onboard fatalities
- Unknown
- Route
- From Ralph Wien Memorial Airport (OTZ), Kotzebue, AKTo Buckland Airport (PABL), Buckland, 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 135: Air Taxi & Commuter
- 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
- 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
- Runway excursion
- 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
- 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 commercial pilot was on a cargo flight when he landed on the snow-covered runway and, upon touching down, he noticed the braking action was nil. He said that about 500 feet from the departure end of the runway he realized that stopping was going to be a problem, but he elected not to abort the landing. The airplane slid off the end of the runway and struck a snowbank, causing structural damage to the left wing. He said that he had not received any reports about braking action for the airport that day, but that he had landed there on the previous day and that the condition of the runway then was acceptable. According to the pilot, there were no known mechanical problems with the airplane prior to the accident. After the accident he examined the runway surface and determined that it was light snow over ice. The Federal Aviation Administration Flight Information Supplement, Alaska, Buckland Airport, under airport remarks, says, in part: "Unattended. Runway condition not monitored, recommend visual inspection prior to landing."
Probable cause
The pilot's failure to abort the landing while landing on a snow/ice-covered runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC09LA025
- Event ID
- 20090319X45005
- Case number
- ANC09LA025
- 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: 08c3be41fd0c2b1647b72b158cbef888ed1cb15e05cadea4c977230a657a86ba; retrieved 2026-09-15T10:51:17.745Z.