Cape Smythe Air Service Flight 350
Piper PA-31-T3 · Accident: in flight encounter with weather on approach
From Nome Airport (PAOM) to Iwakuni Kintaikyo Airport (IWK)
Event
- NTSB case
- ANC00LA027
- 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
- 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-31-T3
- 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
- N110JK
- Operator
- Cape Smythe Air Service
- Onboard fatalities
- Unknown
- Route
- From Nome Airport (PAOM), Nome, AKTo Iwakuni Kintaikyo Airport (IWK)
- 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
- Approach · VFR pattern base
- 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
- In flight encounter with weather
- 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 › Flight into adverse weather, inadvertent
- Pilot in command › Weather evaluation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport certificated pilot was landing a twin-engine turboprop airplane at a remote airport on a scheduled air taxi flight. Rising hilly terrain is located east of the airport. The pilot said that during the approach for landing, he noticed the airport wind sock indicating a wind from the east about 25 knots. When the pilot descended to 500 feet, about mid-base, the airplane encountered moderate turbulence and an increased rate of descent. He added engine power to arrest the descent. As he turned toward the runway, the airplane encountered 3 to 4 rolling oscillations with a bank angle up to 90 degrees while descending toward the runway. According to a company mechanic who traveled to the scene, it appeared that the airplane struck the runway about 1,200 feet from the approach end with the left wing and left elevator, while yawed about 45 degrees to the left of the runway centerline. The airplane then slid off the left side of the runway. After the collision, the pilot evacuated the passengers, and noticed the airport wind sock was indicating a tailwind. The Airport/Facility Directory contains the following in the airport remarks: 'Unattended. Easterly winds may cause severe turbulence in vicinity of runway.'
Probable cause
The pilot's inadequate evaluation of the weather conditions, and his inadvertent flight into adverse weather conditions. Factors in the accident were terrain induced turbulence and a tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC00LA027
- Event ID
- 20001212X20440
- Case number
- ANC00LA027
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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. 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: 720e679ead2c0efa35fc33b5a9dd6068466f5043e0b6470d11927d2eec45b870; retrieved 2026-09-18T16:49:23.817Z.
- The NTSB's operator name is blank for N110JK; the operator shown is the name the NTSB's other records give its FAA operator code, CSAA.