SEA06FA015 · Agusta A109E
Agusta A109E · Accident: in flight collision with object during takeoff
From Olympia, WA to Seattle, WA
Event
- NTSB case
- SEA06FA015
- 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
Agusta A109E
- Aircraft type
- Agusta A109
- 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
- N950AL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Olympia, WATo Seattle, WA
- 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
- 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
- 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 › Proper climb rate, not possible
- Pilot in command › Throttle/power control, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
In preparation for departure from the hospital's second story roof helipad, the pilot stated that once both engines were running he put both engine control switches to FLIGHT and verified that there were no caution lights. The aircraft's DO/VERIFY checklist was then verified after all pre-takeoff items had been completed. He then set the rotor rpm switch to the 102% position, pulled enough collective to bring the helicopter to a hover, and then verified 102% rpm before pulling collective for takeoff power and adding forward cyclic to start the climb-out. As the aircraft started its forward motion the pilot heard "ROTOR LOW" in his headset as the helicopter began to settle. The aircraft's tail rotor subsequently impacted the helipad's concrete barrier, resulting in the helicopter descending over a dirt filled courtyard, which was bordered on the east by a building approximately 40 feet away. The aircraft subsequently impacted the building, coming to rest on its right side after spinning around 180 degrees. There was no post-crash fire. The pilot then shut down both engines and aided in the evacuation of the helicopter's occupants. A post-accident examination conducted by an FAA inspector shortly after the accident revealed that both engine control switches were in the OFF position. Testing of various components and both engines failed to reveal any anomalies which would have precluded normal operation of the helicopter. Data from the Enhanced Ground Proximity Warning System (EGPWS) revealed that the number 1 engine was producing normal and abnormally high torque values during the takeoff sequence, while a zero torque value but proper Ng values were observed from data on the number 2 engine during takeoff; this is consistent with the number 2 engine control switch remaining in the IDLE position. The pilot's total time in all helicopters was 7,923 hours, with 15 hours in make and model. The pilot reported that during both his transition ground school training and flight training courses on the type accident helicopter, he had questioned the instructors about previous accidents involving the position of the engine control switches during the start sequence. A comparison of the Agusta Rotorcraft Flight Manual and the Agusta General Familiarization Training Manual revealed they provided inconsistent instructions about when to move the engine control switches from the IDLE to the FLIGHT position. The pilot also revealed that the operation of the limit override switch was never demonstrated during his training and remembered that it was in an awkward position. The limit override switch was not activated during the takeoff sequence, as the pilot was unsuccessful in locating it.
Probable cause
The pilot's improper positioning of the number 2 Power Flight Control switch and his inability to obtain the proper climb rate to clear a concrete wall barrier. Contributing factors included the checklist not being followed and the limit override switch not being activated.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06FA015
- Event ID
- 20051103X01776
- Case number
- SEA06FA015
- 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 2005-10-29.
- API snapshot SHA-256: 1980dc7bcfbcb486919ff6188357cb08c8fa960ff5ff4f090bf5562f69610d76; retrieved 2026-09-18T14:57:49.846Z.