FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Cape Smythe Air Service Piper PA-31T3 accident

18 Sept 2000 · NUIQSUT, AK, United States

Piper PA-31T3 · Accident: dragged wing, rotor, pod, float or tail/skid during landing

From Deadhorse Airport (PASC) to Nuiqsut Airport (PAQT)

Report a problem

Event

NTSB case
ANC00MA125
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
5 · 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
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-31T3

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
N220CS
Onboard fatalities
Unknown
Route
From Deadhorse Airport (PASC), DEADHORSE, AKTo Nuiqsut Airport (PAQT), NUIQSUT, 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 · flare/touchdown
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
Dragged wing, rotor, pod, float or tail/skid
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aborted landing, improper
  • Pilot in command › Gear extension, not performed
  • Pilot in command › Stall/mush, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airline transport certificated pilot was landing at a remote village on a scheduled domestic commuter flight with nine passengers. The accident airplane, a twin-engine turboprop certified for single-pilot operations, was equipped with a fuselage-mounted belly cargo pod. Witnesses saw the airplane touch down on the gravel runway with the landing gear retracted. The belly pod lightly scraped the runway for about 40 feet before the airplane transitioned to a climb. The propeller tips did not contact the runway. As the airplane began climbing away from the runway, the landing gear was extended. The airplane climbed to about 100 to 150 feet above the ground, and then began a descending left turn, colliding with tundra-covered terrain. A postcrash fire destroyed the fuselage, right wing, and the right engine. The flaps were found extended to 40 degrees. The balked landing procedure for the airplane states, in part: "power levers to maximum, flaps to 15 degrees, landing gear up, and then retract the flaps." Five passengers seated in the rear of the airplane survived the crash. The survivors did not recall hearing a gear warning horn before ground contact. The airplane was landed gear-up eight months before the accident. The airplane was nearly landed gear-up four months before the accident. Each time, a landing gear warning horn was not heard by the pilot or passengers. A postcrash examination of the airplane and engines did not locate any preimpact mechanical malfunction. The FAA's Fairbanks, Alaska, FSDO conducted an inspection of the operator six months before the accident, and recommended the operator utilize two pilots in the accident airplane. Following the accident, the Fairbanks FSDO required the operator to utilize two pilots for passenger flights in the accident airplane make and model.

Probable cause

The pilot's failure to extend the landing gear, his improper aborted landing procedure, and inadvertent stall/mush. Factors in the accident were an improper adjustment of the landing gear warning horn system by company maintenance personnel, and the failure of the pilot to utilize the prelanding checklist.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC00MA125
Event ID
20001212X21902
Case number
ANC00MA125
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: 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: 9ff54a9d2d463ef56753d2ef8612857189a50e1bc59a4cf8fdbed47b79ad96c3; retrieved 2026-09-18T13:11:36.548Z.