FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Med Evac Beech E90B accident

5 Aug 2007 · Ruidoso, NM, United States

Beech E90B · Accident: in flight collision with terrain/water while maneuvering

From Sierra Blanca Regional Airport (SRR) to Albuquerque International Sunport (ABQ)

Report a problem

Event

NTSB case
DEN07MA134
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
5 · 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

Beech E90B

Aircraft type
Beechcraft 90
Category
Airplane
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
N369CD
Onboard fatalities
Unknown
Route
From Sierra Blanca Regional Airport (SRR), Ruidoso, NMTo Albuquerque International Sunport (ABQ), Albuquerque, NM
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
Maneuvering
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 terrain/water
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 › Altitude/clearance, not maintained
  • Pilot in command › In-flight planning/decision, improper

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

NTSB narrative

The emergency medical services (EMS) airplane took off toward the east in dark night visual conditions. The purpose of the Part 135 commercial air ambulance flight was to transport a 15-month-old patient from one hospital to another. Immediately following the takeoff from an airport elevation of 6,814 feet above mean sea level (msl), witnesses observed the airplane initiate a left turn to the north and disappear. Satellite tracking detected the airplane a shortly after departure, when the airplane was flying at an altitude of 6,811 feet msl, an airspeed of 115 knots, and a course of 072 degrees. The airplane impacted terrain at an elevation of 6,860 msl feet shortly thereafter, about 4 miles southeast of the departure airport. The pilot, flight nurse, paramedic, patient, and patient's mother were fatally injured. When the airplane failed to arrive at its destination, authorities initiated a search and the wreckage was located the next morning. Documentation and analysis of the accident site by the NTSB revealed that debris path indicated a heading away from the destination airport. Initial impact with trees occurred at an elevation of 6,860 feet. Fragmented wreckage was strewn for 1,100 feet down a 4.5-degree graded hill on a magnetic heading of 141 degrees. The aircraft's descent angle was computed to be 13 degrees, and the angle of impact was computed to be 8.5 degrees. There was evidence of a post-impact flash fire. Both engine and propeller assemblies were recovered and examined; the assemblies bore signatures consistent with engine power in a mid to high power range. The flaps and landing gear were retracted, indicating that the pilot did not attempt to land the airplane at the time of the accident. Flight control continuity was established, and control cable and push rods breaks exhibited signatures consistent with overload failures. There was no evidence of any pre-impact mechanical malfunction found during examination of the available evidence. The pilot had logged 2,775 total flight hours, of which 23 hours were in the accident airplane. Toxicology testing detected chlorpheniramine (an over-the-counter antihistamine that results in impairment at typical doses) and acetaminophen (an over-the-counter pain reliever and fever reducer often known by the trade name Tylenol and frequently combined with chlorpheniramine). No blood was available for tox testing, so it is not possible to accurately estimate the time of last use, nor determine if the level of impairment that these substances would have incurred during the flight. The airplane was not equipped with either a flight data recorder or a cockpit voice recorder, nor were they required by Federal Aviation Regulation (FAR). The impact damage to the aircraft, presence of dark night conditions, experience level of the pilot, and anomalous flight path are consistent with spatial disorientation.

Probable cause

Failure to maintain clearance from terrain due to spatial disorientation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN07MA134
Event ID
20070815X01188
Case number
DEN07MA134
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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 2007-08-06.
  • API snapshot SHA-256: 79edfe7c0844559de3289cf39e2e11d939f4c5e51083238e8663b1cd5defdc28; retrieved 2026-09-18T12:54:48.997Z.
  • The NTSB's operator name is blank for N369CD; the operator shown is the name the NTSB records it doing business as.