Warbelows Air Ventures Piper PA31 accident
Piper PA31 · Accident: dragged wing/rotor/float/other during landing
From Coldfoot Airport (PACX) to Fairbanks International Airport (PAFA)
Event
- NTSB case
- ANC24LA074
- 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
- Event fatalities
- Unknown
- 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 PA31
- Aircraft type
- Piper PA31
- 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
- N9FW
- Operator
- Warbelows Air Ventures
- Onboard fatalities
- Unknown
- Route
- From Coldfoot Airport (PACX), Coldfoot, AKTo Fairbanks International Airport (PAFA), Fairbanks, AK
- Aircraft age
- About 50 years (built 1974)
- 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 · 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
- Dragged wing/rotor/float/other
- 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 › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that, after entering the traffic pattern before landing, the local tower controller asked him if he could accept a short approach to the arriving runway to accommodate other arriving traffic, and the pilot accepted. As the pilot maneuvered the airplane from the base leg to final approach, he allowed the airplane to descend below the intended glidepath, and he inadvertently allowed the airplanes airspeed to decay. As the airplane passed over the runway threshold, it rolled to the left, and the left wing struck the runway. The pilot momentarily aborted the landing but landed the airplane on a gravel covered airstrip, which was straight ahead and a short distance away. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's continuation of an unstabilized approach and his failure to monitor the aircraft's altitude and airspeed during the approach, resulting in a loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC24LA074
- Event ID
- 20240805194845
- Case number
- ANC24LA074
- 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, cause areas. 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: a6e7a3a3995381162bfc386a35a6db0d1f8aab3fa4952b17e5e170f3e0786b5b; retrieved 2026-09-16T19:07:55.815Z.