FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

S & S Aircraft Leasing de Havilland BEAVER DHC-2 accident

2 Jul 2012 · Ketchikan, AK, United States

de Havilland BEAVER DHC-2 · Accident: loss of control on ground during takeoff

From Ketchikan, AK to Ketchikan International Airport (PAKT)

Report a problem

Event

NTSB case
ANC12CA060
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 BEAVER DHC-2

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
N1018A
Onboard fatalities
Unknown
Route
From Ketchikan, AKTo Ketchikan International Airport (PAKT), Ketchikan, AK
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
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
Loss of control on ground
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot of the float-equipped airplane reported that he planned to step taxi while making a left turn and then takeoff. He applied takeoff power to get the airplane on step, then reduced power, and started a turn to the left. The airplane turned to the left sharper than he anticipated. He applied right rudder and reduced left aileron. As the turn started to straighten out, the airplane’s right wing struck the water and sustained substantial damage. There were no preaccident mechanical issues with the airplane.

Probable cause

The pilot’s failure to maintain directional control during a step turn on floats.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC12CA060
Event ID
20120703X12440
Case number
ANC12CA060
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. 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: 03adae0693033354a8e4cac3b4357fbad0f308468e76d8b2af217fc39c7ea917; retrieved 2026-09-15T18:43:30.595Z.