Promech de Havilland DHC-2 accident
de Havilland DHC-2 and de Havilland DHC-3 · Accident: midair collision en route
Event
- NTSB case
- ANC02LA098
- 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
Aircraft 1 · 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
- N64393
- Operator
- Promech
- Onboard fatalities
- Unknown
- Route
- From Ketchikan Harbor Seaplane Base (5KE), 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
- En route · cruise
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Aircraft 2 · de Havilland DHC-3
- Aircraft type
- de Havilland DHC-3
- 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
- N409PA
- Operator
- Promech
- Onboard fatalities
- Unknown
- Route
- From Ketchikan Harbor Seaplane Base (5KE), 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
- En route · climb to cruise
- 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
- Midair collision
- 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
- Pilot in command › Visual lookout, not maintained
- Pilot of other aircraft › Visual lookout, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Two airplanes operated by the same company, a float-equipped deHavilland DHC-2 Beaver, and a float-equipped deHavilland DHC-3 Turbine Otter, collided in midair as they were en route to the same remote destination. The Beaver sustained minor damage to the floats, and the Turbine Otter sustained substantial damage to the top portion of the wings, the fuselage, and vertical stabilizer. The collision occurred over an area of coastal channels and fjords. The pilot of the Beaver stated that his airplane was the first of three company airplanes to depart. Once airborne, and clear of the class E airspace, he changed radio frequencies to monitor a common traffic advisory frequency. He said that about 15 minutes after departure, while in level cruise flight, about 2,000 feet above the water, he felt a sudden thump, followed by a pronounced airframe shudder. He then observed the top of the left wing of the Turbine Otter to his left side, just under the floats of his airplane. He said that just after the two airplanes collided, the Turbine Otter made a left, descending turn, away from his airplane. He said that after determining that he still had full flight control, he elected to return to the operator's base of operation. The pilot of theTurbine Otter said that his airplane was the second of three airplanes. He said that he departed about 5 minutes after the Beaver, and proceeded on a northerly heading, while climbing the airplane to about 2,200 feet. He said that he changed radio frequencies to monitor a common traffic advisory frequency. He said that about 10 minutes after departure, he heard one of the passengers seated in the rear of the airplane yell "airplane." About two seconds later, the pilot heard a loud scrape on the top portion of the airplane. The pilot said that just after the impact, he experienced some difficulty in controlling the airplane, but was soon able to regain partial control, and subsequently made an emergency landing in the ocean waters in the channel. The pilot of theTurbine Otter reported that his airplane was about 10 knots faster than the Beaver.
Probable cause
The failure of the pilot of the other airplane to maintain an adequate visual lookout, which resulted in a midair collision between the two airplanes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC02LA098
- Event ID
- 20020904X01510
- Case number
- ANC02LA098
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 83fe3b4ab587fe061f5adba866284c39fc2b03d0d1382138f591e00e3066711a; retrieved 2026-09-18T15:59:09.098Z.
- The NTSB's operator name is blank for N64393; the operator shown is the name the NTSB's other records give its FAA operator code, PJMA.