FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Med-Trans Airbus Helicopters AS 350B3 accident

18 May 2022 · Christmas Valley, OR, United States

Airbus Helicopters AS 350B3 · Accident: loss of control in flight during landing

From St Charles Medical Center Heliport (54OR) to an unrecorded destination

Report a problem

Event

NTSB case
WPR22LA182
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
Event fatalities
Unknown
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

Airbus Helicopters AS 350B3

Aircraft type
Airbus 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
N851AL
Operator
Med-Trans
Onboard fatalities
Unknown
Route
From St Charles Medical Center Heliport (54OR), Bend, ORTo not recorded
Aircraft age
About 3 years (built 2019)
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
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 in flight
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the accident pilot, after transferring a patient from Klamath Falls, Oregon to Bend, Oregon, he received a request from his dispatch to collect a patient in Christmas Valley, Oregon. He reviewed weather information from stations surrounding the destination as there was no local weather reporting facility at the destination. The pilot recalled that the expected winds were from the northwest at 15-20 kts sustained, and gusting to 30 kts, but were acceptable for the flight. After a preflight inspection he departed on the accident flight with three flight crewmembers. They did not experience any significant weather while enroute to their destination and the helicopter was operating within its normal limitations. The pilot approached the airport by entering the airport traffic pattern from the north for a landing to the west as the winds were from the west/northwest. He recalled that the windspeeds at the time of arrival were approximately 15-20 kts and gusting between 25-30 kts.

After he became established on final approach he sidestepped and approached a parallel taxiway. He slowly taxied while looking for the air ambulance they were scheduled to meet. The pilot reported that he was monitoring the windsock during this time, but observed the helicopter handling well with no indication of winds that would exceed the helicopter’s limitations at the time. Once he identified the landing site he lined the helicopter with the landing pad and began a descent while noting several structures nearby that were providing protection from the wind. At this point he performed a right pedal turn from about 3 ft above ground level to position the left door towards the ambulance for the pickup, consistent with the operator’s protocol. The pedal turn went smoothly; however, as the helicopter touched down it was forced forward rapidly. The pilot reacted by increasing collective and applying aft cyclic to climb the helicopter and avoid surrounding hazards. He lowered collective when the helicopter was about 30 ft above ground level and held aft cyclic, but the helicopter began to spin to the left and he was unable to control the helicopter. The pilot then reduced power to IDLE using the throttle twist grip and could not recount anything further.

The pilot reported no preimpact mechanical anomalies or malfunctions with the helicopter that would have precluded normal operation. He opined that he encountered a hard wind from the rear. A witness estimated that the wind was about 50 mph (43 kts) at the time of the accident.

Probable cause

The pilot’s inability to maintain control in high wind conditions while repositioning during a landing attempt, which resulted in a loss of control and collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22LA182
Event ID
20220519105103
Case number
WPR22LA182
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2022-05-19.
  • API snapshot SHA-256: 55d442c87ea5e1958a0edb75922aae4a59ba4dc047106e44674b297b5160beca; retrieved 2026-09-16T15:14:21.547Z.