FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC06LA044 · Aerospatiale AS-350BA

6 Apr 2006 · Haines, AK, United States

Aerospatiale AS-350BA · Accident: in flight collision with object during landing

From Haines, AK to an unrecorded destination

Report a problem

Event

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

Aerospatiale AS-350BA

Aircraft type
Aerospatiale AS-350
Category
Helicopter
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
N209CH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Haines, AKTo not recorded
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
Landing
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
In flight collision with object
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
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
Substantial

Cause areas

  • Pilot in command › Clearance, 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

The airline transport certificated pilot was landing a helicopter in an area of grass near the beach of an island on a CFR Part 135 air taxi flight. The pilot indicated that he was focused on a log as a reference point, when just before touchdown, the main rotor blades struck a tree. The operator's director of operations indicated that the rotor blades could not be repaired at his facility, and were being sent to the blade manufacturer's repair facility.

Probable cause

The pilot's failure to maintain adequate clearance from an object while landing a helicopter at a remote site, which resulted in the main rotor blades striking a tree.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC06LA044
Event ID
20060410X00415
Case number
ANC06LA044
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: 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: d74e804cf1e1696b74789d33a55f9d5e7fb70fb4b4a265398d1d17aff71b861d; retrieved 2026-09-18T14:54:09.630Z.