Fly 4 You Piper PA-31-350 accident
Piper PA-31-350 · Accident: collision with terrain/object (non-CFIT) en route
From Ted Stevens Anchorage International Airport (PANC) to Seward Airport (SWD)
Event
- NTSB case
- ANC20FA007
- 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
- 3 · 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
- N4087G
- Operator
- Fly 4 You
- Onboard fatalities
- Unknown
- Route
- From Ted Stevens Anchorage International Airport (PANC), Anchorage, AKTo Seward Airport (SWD), Seward, AK
- Aircraft age
- About 38 years (built 1981)
- 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
- En route · cruise
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Emergency clinic personnel contacted multiple air ambulance companies prior to contacting the accident operator, requesting air ambulance transportation of a patient. The first company contacted turned down the flight due to limited daylight hours. The second company declined the flight due to poor weather conditions. After accepting the flight, the pilot departed at night, destined for an airport about 75 nautical miles away. The route of flight would take the flight across a peninsula and a mountain range. The destination airport was at the north end of a fjord surrounded by mountains ranging from 4,000 ft to 6,000 ft elevation; for this reason, the destination airport prohibited instrument approaches at night. Radar data indicated the accident airplane departed and flew south about 3,000 ft mean sea level (msl) toward a highway. The airplane then descended to 2,200 ft msl while flying a right racetrack pattern before flying into a valley. The last data point indicated the airplane was over the west end of a lake at 2,100 ft msl, on a 127° course, and 122 kts groundspeed. Witnesses reported that they saw the lights of the airplane flying over the highway that night. One witness stated that he saw the airplane west of the mountains turn in a circle as it descended and then entered the valley. Another witness reported seeing the airplane flying low before it impacted the mountain and a post-crash fire ensued. The airplane impacted the mountain at an elevation of about 1,425 ft msl in an area of steep, heavily tree-covered terrain near the southeast end of a lake. The airplane was highly fragmented and burned; however, all major airplane components were accounted for at the accident site. Postaccident examination of the engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Weather simulations conducted after the accident indicated east to southeast winds above the accident site with wind speeds between 30 to 50 knots, downdrafts and updrafts with magnitudes of +/- 1,500 fpm, and relative humidity values above 90% at the mountain tops. Witness reports corroborated this information and also described precipitation and mountain obscuration. Airman's Meteorological Information (AIRMET) reports were active for the accident region that warned pilots of low-level wind shear (LLWS) conditions, moderate icing conditions between 6,000 and 15,000 ft, and occasional instrument flight rules (IFR) and mountain obscuration conditions due to precipitation and clouds. Weather graphics valid at the accident time and before the departure of the accident flight showed IFR conditions along the route of flight, isolated moderate turbulence conditions in LLWS, and moderate icing above 6,000 ft. It is likely the airplane encountered strong mountain wave conditions while traveling across the peninsula and through the end of the accident flight. Additionally, the terrain was likely obscured due to the reduced visibility, clouds, light rain or drizzle and the pilot likely did not see the rising terrain as he flew in the valley toward the destination. While sufficient weather information was available to predict the windy conditions and mountain obscuration for the flight, it is unknown what information the pilot had regarding the weather prior to departure.
Probable cause
The pilot’s failure to maintain clearance from terrain during gusty wind and reduced visibility night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC20FA007
- Event ID
- 20191130X55947
- Case number
- ANC20FA007
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-11-30.
- API snapshot SHA-256: 2af4e7994fcad3dd9e81a9b5e36b8125122fc47fb2c21be388317502e0616791; retrieved 2026-09-15T07:08:57.816Z.