Cessna 208B accident near Atqasuk, Alaska, April 11, 2018
On April 11, 2018 at about 4:18 pm local time, a 2002 Cessna 208B, registered N814GV, was substantially damaged in an accident during enroute (descent) near Atqasuk, Alaska (Atqasuk Edward Burnell SR Memo airport). It was flown under charter and air-taxi rules (Part 135). 1 person had minor injuries. The weather was conditions the NTSB did not record.
The NTSB's probable cause their words, unchanged
The pilot's decision to continue a visual flight rules flight into an area of instrument meteorological conditions and his subsequent failure to level the airplane after the autopilot disconnected, which resulted in a collision with terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 11, 2018 · about 4:18 pm local time
- Place
- Atqasuk, Alaska · Atqasuk Edward Burnell SR Memo · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- conditions the NTSB did not record
- Aircraft
- Cessna 208B, built 2002 · all 208Bs on the register
- Registration
- N814GV · registry record · serial 208B0958
- Damage
- Substantial damage
- Flight
- Flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
The pilot was on a visual flight rules flight transporting mail to a remote village. He reported that when he was about 15 minutes from the destination, he checked the automated weather observing system (AWOS) for updated weather information for the destination and recalled that the visibility was reported as 7 miles. However, the information he recalled was not consistent with what was actually reported by the AWOS; 18 minutes before the accident, the AWOS reported no more than 1 3/4 miles visibility. As he descended the airplane from 2,500 ft to 1,500 ft in the terminal area, he observed reduced visibility conditions that would require an instrument approach procedure. According to the pilot, while maneuvering toward the initial approach fix, he heard the autopilot disconnect, and the airplane began an uncommanded descent. He said that he remembered pulling on the control wheel and thought he had leveled off, but then the airplane impacted terrain, which resulted in substantial damage to the fuselage, vertical stabilizer, and rudder. He could not recall if he had heard terrain warnings or alerts before the impact. An airplane performance study indicated that the airplane was in a continuous descent from 2,500 ft until the final data point about 12 ft above the surface; the airplane was not leveled off at any time during the descent. In the final 15 seconds of recorded data, the rate of descent increased from about 500 fpm to about 2,300 fpm before decreasing to 1,460 fpm at the last recorded data point. Postaccident examinations of the airframe, engine, flight control, and autopilot components revealed no mechanical malfunctions or failures that would have precluded normal operation or affected flight controllability. It is likely that the unexpected instrument approach procedure increased the pilot's workload as he maneuvered to set up for the approach. Further, when the autopilot disconnected, the airplane continued to descend; although the pilot reported that he heard the autopilot disconnect, he did not arrest the airplane's descent rate. Given the low visibility conditions, it is likely that the pilot did not detect the airplane's descent, and the airplane descended into the terrain.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- VFR encounter with IMC during enroute (descent) defining event
- Controlled flight into terrain or object (CFIT) during enroute (descent)
The NTSB's findings
- cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Decision related to condition
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land
- Flight time: 7,713 hours in all; 230 in the last 90 days; 90 in the last 30 days; 7,628 as pilot in command
- Last flight review: November 12, 2017
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 9,778.2 hours
- Last inspection: condition inspection, February 25, 2018; 168 hours since
- Maximum gross weight: 9,062 lb
- Seats: 8
- Landing gear: fixed
- Engine: P&W Canada PT6A-114A (turboprop); 3,950 hours total
- Operator: Hageland Aviation Services INC
The flight
- Departed from: PABR Utqiagvik AK at 10:58 am
- Destination: ATK Atqasuk AK
Weather at the time
- Light: daylight
- Wind: from 030° at 9 knots
- Visibility: 9 statute miles
- Sky: clear
- Temperature: 7°F (-14°C), dew point 3°F (-16°C)
- Altimeter: 29.65 inHg
- Observation at 10:53 am from PABR, 58 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
21 documents, released by the NTSB on December 20, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
