FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Paklook Air Piper PA32R 300 accident

6 Feb 2020 · Tuntutuliak, AK, United States

Piper PA32R 300 · Accident: controlled flight into terrain/object (CFIT) en route

From Bethel Airport (BET) to Kipnuk Airport (IIK)

Report a problem

Event

NTSB case
ANC20FA017
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
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
Instrument Meteorological Cond

Piper PA32R 300

Aircraft type
Piper PA32
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
N7632C
Operator
Paklook Air
Onboard fatalities
Unknown
Route
From Bethel Airport (BET), Bethel, AKTo Kipnuk Airport (IIK), Kipnuk, AK
Aircraft age
About 45 years (built 1975)
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
Controlled flight into terrain/object (CFIT)
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

  • Environmental issues › Conditions/weather/phenomena
  • Organizational issues › Support/oversight/monitoring
  • 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 departed under a special visual flight rules (VFR) clearance with four passengers on a VFR scheduled passenger flight. The airplane was reported overdue about an hour later when it had not reached its destination and was subsequently located about 35 nautical miles from the departure airport. There was no radar or other flight tracking information available for the accident flight, and the airplane’s flight track before the accident could not be determined; however, the wreckage was located along a direct course between the departure and destination and on a heading consistent with the intended direction of flight. The airplane was highly fragmented and the wreckage was distributed along a nearly 400-ft-long debris path. Examination of the airplane and engine did not reveal any evidence of mechanical malfunctions or anomalies that would have precluded normal operation. The weather about the time of departure included 1 ¼ miles visibility, a runway visual range of 2,200 ft to better than 6,000 ft, unknown precipitation and mist, and an overcast ceiling at 600 ft above ground level (agl). The observation closest to the accident time indicated 3 miles visibility, mist, and an overcast ceiling at 500 ft agl. Between the departure time and the accident time, instrument flight rules or low instrument flight rules conditions prevailed at the departure airport. In the hour after the accident, both the departure and intended destination airports reported low instrument flight conditions with visibility as low as ½ statute mile in light snow, mist, and freezing fog, and cloud ceilings as low as 400 ft agl. An atmospheric sounding depicted a stable atmosphere with cloud bases around 700 ft agl. A frontal inversion was collocated between the lifted condensation level, around 700 ft agl, and 3,000 ft mean sea level. The wind profile suggested the potential for low-level turbulence based on the low-level wind maximum and the strong vertical shear near the inversion and a 77% probability of moderate to severe turbulence at 700 ft due to the strong vertical wind shear. It is also likely that light to moderate rime icing conditions were present in clouds and precipitation. The pilot had been recently hired by the operator and had completed initial operating experience requirements the week before the accident. Interviews with the director of operations, general manager, and the flight follower who assigned the accident flight indicated that company policy required a minimum of 2 statute miles visibility and a cloud ceiling of at least 500 ft agl. Pilots were required to complete a flight risk assessment form before each flight, which was to be approved or disapproved by the director of operations or their delegate before the flight was released. No risk assessment form was located for the accident flight, and who approved the flight to depart could not be determined. Based on the available information, a lack of operational control permitted the pilot to depart into weather conditions that were below the minimums specified by company operating procedures. It is likely that, while en route, the pilot encountered adverse weather including low visibility, precipitation, and turbulence. Such conditions, in addition to the snow-covered terrain and overcast and/or low visibility likely present at the time of the accident, would have been conducive to flat light or white-out conditions. In these conditions pilots can experience illusions that can lead to unrecognized descents because of the difficulty discriminating between terrain and sky to identify a visible horizon. With the low ceilings likely en route, the pilot would have been flying at altitudes that would have precluded recognition and recovery from an inadvertent descent. The direction, distribution and fragmentation of the wreckage was consistent with a controlled flight into terrain event.

Probable cause

The pilot's continued visual flight rules flight into reduced visibility, including likely flat light and/or white out conditions, which resulted in a controlled flight into terrain. Contributing to the accident were the operator’s inadequate operational control procedures, which permitted the pilot to depart into conditions that were below the minimums specified by their operating procedures.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC20FA017
Event ID
20200206X34831
Case number
ANC20FA017
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: 3f4f1ebaeb32f7be36dba67a8fde4b07cec0d0e66885bd600f73054fdc893a7f; retrieved 2026-09-15T07:11:37.159Z.