2006 Mercy Air Bell 412 crash
Lifenet Bell 412SP · Crashed in fog
From Loma Linda University Medical Center Heliport (94CL) to Southern California Logistics Airport (VCV)
Event
- NTSB case
- LAX07FA056
- 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
- Unknown
- Event fatalities
- 3 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- Unknown
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- 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
Bell 412SP
- Aircraft type
- Bell 412
- 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
- N410MA
- Operator
- Lifenet
- Onboard fatalities
- Unknown
- Route
- From Loma Linda University Medical Center Heliport (94CL), Loma Linda, CATo Southern California Logistics Airport (VCV), Victorville, 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
- 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
- Controlled flight into terrain/object (CFIT)
- 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 › Clearance, not maintained
- Pilot in command › VFR flight into imc, encountered
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
The 2006 Mercy Air helicopter accident occurred on December 10, 2006, about 17:55 Pacific Standard Time, when a Bell 412SP helicopter, call sign "Mercy Air 2" impacted mountainous terrain near Hesperia, California and the Cajon Pass. The commercial helicopter pilot and two medical crew members were killed, and the helicopter was destroyed by impact forces and a postcrash fire.
On July 30, 2008, the National Transportation Safety Board (NTSB) released its probable-cause report on the accident. According to the NTSB, the probable cause of the crash was "the pilot's inadvertent encounter with instrument meteorological conditions and subsequent failure to maintain terrain clearance." The dark night conditions, fog, and mountainous terrain were ruled to be contributing factors.
Accident details
The Bell 412SP helicopter took off on a cross-country repositioning flight from Loma Linda University Medical Center (94CL), Loma Linda, California, at 17:42, with a planned destination of Southern California Logistics Airport (VCV), Victorville, California. Mercy Air 2 had transported a woman injured in a horse-riding accident in Phelan, California,
to Loma Linda, and was returning to its assigned base at the time of the accident, with only the pilot and two medical crew members on board. LifeNet, Inc., doing business as Mercy Air Service, Inc., was operating the helicopter under the provisions of 14 CFR Part 91. An FAA representative stated the helicopter was being operated under visual flight rules and was not being handled by air traffic control, a practice he called "perfectly normal."
At 18:00, the San Bernardino County Fire Department dispatch center started to receive numerous calls of an object falling from the sky, an explosion, and fire northeast of Interstate 15 in the area of Oak Hills. The first fire department responders to the accident site reported that the area was covered by intermittent waves of fog, which made locating the wreckage difficult.
The accident site was located on mountainous terrain on a 45° slope at an elevation of 4000 to 4300 ft above mean sea level, below a large electrical transmission tower, a little more than a mile east of I-15, and north of Highway 138. It is in a rural area with dirt roads, and no streetlights. The approximate global positioning system (GPS) coordinates of the primary wreckage were:.
First responders reported that upon their arrival, the scene was fully engulfed in fire. The postimpact fire consumed around 2 acre of mountainside, and made any reconstruction of the wreckage impossible. The first identified point of impact, a ground scar located next to the separated tail boom and the left skid, was near the base of the mountainous terrain, with the debris path emanating upslope. The debris path consisted of the tail boom, both skids, both engines, the main rotor assembly, and various other fuselage panels. The energy path was measured on a 155° bearing from the first identified impact point. No distress call was received from the aircraft. Initial speculation that the aircraft went down after hitting electrical wires was quickly eliminated as a cause. Examination of the maintenance and flight department records revealed no unresolved maintenance discrepancies against the helicopter prior to departure. The helicopter was built in 1987 and refurbished in May 2004, and had no previous accident history.
Text from the Wikipedia article “2006 Mercy Air Bell 412 crash” (revision 1352555685, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
The emergency medical services (EMS) helicopter was performing a cross-country repositioning flight from a hospital back to its base during dark night conditions back over a routing that the pilot had flown 5 times that day and also earlier in the evening when they had transported a patient to the hospital. Visual meteorological conditions predominantly prevailed along the route of flight; however, analysis of the weather reports disclosed conditions consistent with broken to overcast clouds having bases at 4,000 feet msl in the vicinity of the accident site. An AIRMET had been issued for the area for IFR conditions, with mountain obscuration, precipitation, mist, and fog. The helicopter was equipped with a satellite-based tracking system that reports the helicopter's GPS location to the operator's ground base while the system is in operation, and the data for the accident flight was reviewed. The route of flight proceeded toward the apex of a mountain pass, which is the main transition route from one side of a mountain range to the other, where the helicopter's base is located. The tracking data indicated that the helicopter appeared to follow a major highway in the lower portion of the pass. The highway makes a large "S" shaped path as it gains in elevation toward the top of the pass, which is about 4,200 feet mean sea level (msl). The route along the highway is away from a well-lit major city area that has a well-defined light horizon, toward rising and dark terrain with no ground reference lights other than vehicles on the highway. Once at the top of the pass as the highway turns toward the northeast, the upper desert communities on the other side of the mountain range once again provide a well-lit and clearly defined horizon. Near the upper end of the pass, the helicopter's satellite derived flight track showed that it inexplicably diverged toward the east, away from the highway, instead of continuing to follow the highway into the upper desert valley. The helicopter collided with terrain about 0.7 nautical miles east of the highway at 4,026 feet msl. The accident site was located in a small ravine, near the base of a 100-foot tall electrical transmission tower that was located along the ravine's east ridge. During subsequent examination of the airframe structures, flight control components, and engines, no pre-impact anomalies were found that would have precluded normal operation prior to impact. While the operator was in the process of equipping its helicopter fleet with night vision goggles, the accident helicopter had not as yet been equipped with any enhanced night vision devices. The helicopter was equipped for instrument flight, including a 3-axis autopilot. The first fire department responders to the accident site reported that the area was covered by what they described as "intermittent waves" of fog that would suddenly form and then dissipate, which made it difficult to locate the wreckage.
Probable cause
The pilot's inadvertent encounter with instrument meteorological conditions and subsequent failure to maintain terrain clearance. Contributing to the accident were the dark night conditions, fog, and mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: 2006 Mercy Air Bell 412 crash
- Revision
- 1352555685 · 2026-05-04 · retrieved 2026-09-18
- Wikidata
- Q4606594
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record LAX07FA056
- Event ID
- 20061220X01815
- Case number
- LAX07FA056
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
- Record
- Wikipedia article "2006 Mercy Air Bell 412 crash" (page 11842089, revision 1352555685); merged with NTSB case LAX07FA056 (events / aircraft)
- Date
- Wikipedia infobox: date (local date; NTSB record LAX07FA056 stores the UTC date 2006-12-11)
- Place and country
- Wikipedia infobox: site; country from NTSB record LAX07FA056
- Map position
- Wikipedia: Wikipedia article coordinates
- Aircraft, operator and route
- NTSB record LAX07FA056: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record LAX07FA056: operated under Part 91: General Aviation
- Fatalities
- Wikipedia: Wikipedia infobox: aircraft fatalities (the NTSB record states no total)
- Ground fatalities
- NTSB record LAX07FA056: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (2)
- One occurrence in two sources, merged: the Wikipedia article "2006 Mercy Air Bell 412 crash" and NTSB case LAX07FA056, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- The NTSB record dates it 2006-12-11, the UTC date it stores; the local date, 2006-12-10, is the Wikipedia article's and is used.