ANC07MA083 · de Havilland DHC-2
de Havilland DHC-2 · Accident: loss of control in flight while maneuvering
From Ketchikan, AK to Ketchikan Harbor Seaplane Base (5KE)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ANC07MA083
- 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
- Visual Meteorological Cond
de Havilland DHC-2
- Aircraft type
- de Havilland 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
- N345KA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Ketchikan, AKTo Ketchikan Harbor Seaplane Base (5KE), 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
- Maneuvering
- First occurrenceThe 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 in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall; Tree(s)
- 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
- Pilot in command › Airspeed(vs), not maintained
- Pilot in command › Weather evaluation, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The float-equipped airplane was departing from a remote bay 20 miles north of Ketchikan, Alaska, to return air taxi passengers to Ketchikan after a ground tour. The accident pilot, who reported that he had 17,000 flight hours and 7,000 hours in the make and model of the accident airplane, said that southeasterly winds had begun to increase while he was waiting at the bay for the passengers to return from the tour. He said that, unlike when he had landed about 2.5 hours earlier, it was no longer "nice and calm" when the passengers returned. The pilot noticed choppy waves in parts of a nearby cove.
To avoid some of the wind and waves, the pilot elected to take off toward the interior of the bay, in the direction of rising terrain. The pilot said that he had never taken off in that direction before. The pilot also said that he had intended to make a shallow, right-climbing turn toward the mouth of the bay and away from the terrain, but shortly after takeoff, he saw numerous choppy waves concentrated along his proposed departure flightpath, which he said indicated to him that strong winds were likely along that path. The pilot decided to change his plan and continue flying straight temporarily, away from the waves, and to make a left, 180-degree turn inside the bay, which was surrounded by high terrain. The pilot indicated that when the turn was initiated, the airplane was about 400 feet above the water, and he did not recall the indicated airspeed. The attempted 180-degree turn was within the airplane’s performance capabilities but placed it closer to rising terrain.
While attempting this turn, the pilot encountered a downdraft, was unable to climb above the terrain, and stalled the airplane about 60 feet above the ground. The downdraft likely made it more difficult to avoid descending into the rising terrain. A weather study by the National Transportation Safety Board confirmed that there was a gust front in the area and an abrupt wind change about the time of the accident. Pilots flying nearby also reported low-level windshear, strong winds, and turbulence.
No mechanical anomalies were discovered during postaccident inspections by the Safety Board.
Probable cause
An inadvertent aerodynamic stall resulting from the pilot's poor decision-making and inadequate planning and execution when he took off toward nearby rising terrain, in strong winds, under circumstances where his options for maneuvering were severely limited and where his safety margin was, thus, insufficient.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC07MA083
- Event ID
- 20070823X01233
- Case number
- ANC07MA083
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-08-17.
- API snapshot SHA-256: afc476a84a5019814aa0f191dad05ffb14a0aa86cdffc2bfc4ae6b148578cd6f; retrieved 2026-09-18T12:54:43.480Z.