FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04FA076 · Agusta A109A

23 Dec 2003 · Redwood Valley, CA, United States

Agusta A109A · Accident: in flight encounter with weather en route

From Ukiah Municipal Airport (UKI) to Willits, CA

Report a problem

Event

NTSB case
LAX04FA076
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
3 · 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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Agusta A109A

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
N25RX
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ukiah Municipal Airport (UKI), Ukiah, CATo Willits, CA
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 91: General Aviation
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
In flight encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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 › In-flight planning/decision, improper
  • Pilot in command › VFR flight into imc, continued

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Following an encounter with night instrument meteorological conditions, the emergency medical services (EMS) helicopter collided with rising hilly terrain while attempting to reverse course in a narrow mountain valley near Redwood Valley, California. The purpose of the flight was to pickup a patient at a rural hospital in a mountainous area for transport to a larger medical facility. When weather conditions would not permit reaching the rural hospital, common practice for the operator's flight crews was to fly to an intermediate airport with an instrument approach where the helicopter could meet ground transport of the patient and continue the evacuation. Prior to departure from home base, the pilot received a weather briefing from DUATS, which indicated that areas along the route of flight would experience light rain showers, as well as cloud layers that ranged from 1,500 feet above ground level (agl) to 6,000 feet agl ,and visibilities between 3 to 5 statute miles (sm). The pilot filed an instrument flight rules flight plan from his home base to the intermediate airport. An employee of another EMS operator based at the intermediate airport said that there was rain and reduced visibilities at the airport, and that she told the accident medical crew by radio that they should come inside and wait for the ambulance to get to the airport because of the weather. Once the accident helicopter arrived at the intermediate airport, the helicopter was not shut down, the flight nurses got out and got back in, and helicopter departed the airport. Communications between a fire department dispatcher and the accident medical crew indicated that the accident flight was attempting to fly to the fire department's helipad located between the intermediate airport and the hospital. Recorded company communications indicated that a few minutes after the conversation with the fire department dispatcher, the accident flight was diverting back to the intermediate airport. There were no further communications with the accident crew. Witnesses in the area of the accident site all reported heavy rain and wind and poor visibilities due to a heavy fog in the area. Another witness about 2 miles south of the accident site reported hearing the helicopter flying very low over her house, just above the 100-foot tall treetops, about 12 minutes before the accident. The charge nurse at the rural hospital indicated that the weather was poor, and she had indicated to the operator's dispatch that the rural hospital would transport the patient to the intermediate airport. The accident area was located in a narrow valley with mountain peak elevations ranging up to 2,000 feet on either side of a major highway that ran in a north/south direction. The airframe and engines were inspected with no preimpact mechanical anomalies noted.

Probable cause

The pilot's improper in-flight planning and decision to continue flight under visual flight rules into deteriorating weather conditions, which resulted in an inadvertent in-flight encounter with instrument meteorological conditions and a collision with rising terrain while attempting to reverse course.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04FA076
Event ID
20040108X00032
Case number
LAX04FA076
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 2003-12-24.
  • API snapshot SHA-256: 0326af8b6f2d8ac44746eaeb707b59abedf894f0d700397c077b51c51d47d8c8; retrieved 2026-09-20T18:41:35.294Z.