FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN92FA064 · Mitsubishi MU-2B-30

24 Jun 1992 · ALAMAGORDO, NM, United States

Mitsubishi MU-2B-30 · Accident: in flight collision with terrain/water en route

From Alamogordo White Sands Regional Airport (ALM) to T27 · Burnet, TX

Report a problem

Event

NTSB case
DEN92FA064
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
6 · all aircraft and ground
Ground fatalities
0
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
Visual Meteorological Cond

Mitsubishi MU-2B-30

Aircraft type
Mitsubishi MU-2
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
N108SC
Operator
William G. Whitehead · private individual
Onboard fatalities
Unknown
Route
From Alamogordo White Sands Regional Airport (ALM)To T27 · Burnet, TX
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 · climb to 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 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

  • Atc personnel(dep/apch) › Safety advisory, not issued
  • Pilot in command › VFR procedures, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE FLT HAD DEPARTED THE ALAMAGORDO WHITE SANDS REGIONAL ARPT AFTER A FUEL STOP. THE PILOT HAD EARLIER INDICATED TO ATC THAT HE WAS UNFAMILIAR WITH THE AREA. PRIOR TO DEPARTURE AT 2321 THE PILOT WAS INFORMED THAT DEPARTURE RADAR WAS OUT OF SERVICE. THE FLT DEPARTED WITH A VFR DEPARTURE. AT 2324 THE PILOT WAS ADVISED THAT RADAR WAS BACK IN SERVICE, AND CONFIRMED THAT THE AIRCRAFT WAS CLIMBING THRU 5,300 FT. DISCUSSION ENSUED BETWEEN THE PILOT AND CONTROLLER CONCERNING TERRAIN CLEARANCE. AT 2324 THE PILOT INDICATED HE WAS TURNING LEFT DUE TO NOT BEING SURE IF A HILL WAS IN HIS PATH. THE AIRPLANE IMPACTED A MOUNTAIN AT 6,100 FT MSL, 1,500 FT BELOW THE SUMMIT. THE MINIMUM VECTORING ALTITUDE IN THE AREA WAS 11,000 FT.

Probable cause

THE FAILURE OF THE PILOT TO EXERCISE ADEQUATE VFR DEPARTURE TERRAIN AVOIDANCE PROCEDURES, AND THE FAILURE OF THE CONTROLLER TO ISSUE A SAFETY ALERT TO THE PILOT. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE: THE PILOT'S LACK OF FAMILIARITY WITH THE GEOGRAPHIC AREA, THE DARK NIGHT, AND THE MOUNTAINOUS TERRAIN.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN92FA064
Event ID
20001211X14834
Case number
DEN92FA064
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1992-06-25.
  • API snapshot SHA-256: a8d775d787d0c9d481c8f49796f4727c937aa3acb0dc9145216b5b88d117e3b0; retrieved 2026-09-21T01:05:23.353Z.