LAX83FA090 · Beech 58
Beech 58 · Accident: in flight encounter with weather en route
From L-22 · Yucca Valley, CA to Bermuda Dunes Airport (UDD)
Event
- NTSB case
- LAX83FA090
- 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
- 2 · 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
- Instrument Meteorological Cond
Beech 58
- Aircraft type
- Beechcraft 58
- 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
- N1586W
- Operator
- J.R. Husham
- Onboard fatalities
- Unknown
- Route
- From L-22 · Yucca Valley, CATo Bermuda Dunes Airport (UDD), Bermuda Dunes, 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
- 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 › Flight into known adverse weather, continued
- Pilot in command › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT & PASSENGER HAD FLOWN FROM BERMUDA DUNES TO YUCCA VALLEY, CA ON A BUSINESS FLT. REPORTEDLY, THEY TERMINATED THEIR BUSINESS EARLY BECAUSE WX WAS BUILDING OVER THE MOUNTAINS BETWEEN YUCCA VALLEY & BERMUDA DUNES. WHILE ON THE RETURN TRIP, THE PLT REPORTED THAT HE HAD PROCEEDED TO A POINT WHERE HE HAD BERUMDA DUNES IN SIGHT, BUT ELECTED TO DIVERT BACK TO THE HIGH DESERT ARPT (NEAR YUCCA VALLEY) TO OBTAIN FUEL. AT APRX 1420 PST, THE PLT & PASSENGER TOOK OFF AGAIN FOR BERMUDA DUNES. SUBSEQUENTLY, THE ACFT IMPACTED RESING TERRAIN NEAR THE TOP OF A MOUNTAIN RIDGE ALONG THE EXPECTED ROUTE. SEVERAL SOURCES REPORTED THAT THE WX HAD DETERIORATED IN THE VICINITY OF THE CRASH SITE. THE OWNER OF THE HIGH DESERT ARPT STATED THAT WHEN THE ACFT DEPARTED AFTER REFUELING, THE WX TOWARDS PALM SPRINGS WAS IFR. THE OWNER OF A HELICOPTER AG OPERATION NEAR DESERT HOT SPRINGS, STATED THAT THE WX BUILD-UP OVER THE MOUNTAINS WAS NOT CONDUCIVE TO VFR FLT OPERATIONS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83FA090
- Event ID
- 20001214X42221
- Case number
- LAX83FA090
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 89c33e78613ec66fe94670d3661b9e35be7d9a399e92c707d714f49b591fdc14; retrieved 2026-09-21T07:12:57.774Z.