FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Bald Mountain Air Service de Havilland DHC 6 TWIN OTTER accident

21 Mar 2018 · Arctic Ocean, United States

de Havilland DHC 6 TWIN OTTER · Accident: collision during takeoff/landing

From Deadhorse, AK to Deadhorse Airport (PASC)

Report a problem

Event

NTSB case
ANC18LA027
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
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

de Havilland DHC 6 TWIN OTTER

Aircraft type
de Havilland DHC-6
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
N716JP
Onboard fatalities
Unknown
Route
From Deadhorse, AKTo Deadhorse Airport (PASC), Deadhorse, AK
Aircraft age
About 41 years (built 1977)
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
Takeoff
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 during takeoff/landing
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 › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The captain and first officer were conducting a flight to provide ongoing logistical support to a remote research camp located on frozen water. The captain reported that departing and arriving flights used an airstrip built on the ice that was lined with snow berms on both sides. He added that, just before the takeoff roll, he and the first officer saw a pedestrian standing near the left side of the departure end of the airstrip. As the takeoff roll continued, the airplane became airborne, so the captain lowered the nose to remain within ground effect and gain airspeed before initiating a climb. The captain added that, as the airspeed increased, he started to climb the airplane and then initiated a left turn. Both pilots reported that, during the turn, they heard a loud thump, which was immediately followed by an aileron control anomaly. The captain initiated a left turn back toward the airstrip and subsequently made an emergency landing. After landing, both pilots saw the pedestrian lying near a snow berm on the left side of the airstrip. The captain reported that he did not remember if it had been prearranged to have the pedestrian stand near the departure end of the airstrip during the departure.

The pedestrian reported that, just before the two pilots boarded the airplane, he told the captain that he would position himself alongside the airstrip so that he could photograph the airplane at departure. As the airplane back-taxied before takeoff, the pedestrian positioned himself clear of the airstrip and behind a 3- to 4-ft-tall snow berm. He said that, as the airplane's takeoff progressed, it did not climb as quickly as it had during previous departures and that the last thing he remembered before the collision was seeing the left wing getting lower to the ground as the airplane began a left turn and flew toward him while continuing to accelerate.

A security video camera recorded the accident sequence, and the recording supported the pedestrian's account of the sequence of events. Although the captain reported that he climbed the airplane before initiating a left turn, the review of the video revealed that the flight crew operated the airplane at a low altitude and along a flightpath that placed it in dangerous proximity to the pedestrian (which was inconsistent with federal regulations) and left no margin to avoid the collision with him.

Probable cause

The flight crew's improper decision to deliberately operate the airplane at low altitude and along a flightpath that resulted in a collision with a pedestrian after takeoff. Contributing to the accident was the pedestrian's proximity to the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC18LA027
Event ID
20180322X70555
Case number
ANC18LA027
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. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 8491d1df8fb26f95d36c34f31b0a09eb8a28e683ecce5725c8e99bacd0e555a7; retrieved 2026-09-16T06:41:53.785Z.