FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX98FA306 · Beech 95-B55

26 Sept 1998 · Hawthorne, NV, United States

Beech 95-B55 · Accident: in flight encounter with weather en route

From Red Bluff Municipal Airport (RBL) to St George Regional Airport (SGU)

Report a problem

Event

NTSB case
LAX98FA306
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
1 · 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 95-B55

Aircraft type
Beechcraft 55
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
N554MB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Red Bluff Municipal Airport (RBL), RED BLUFF MUNI, CATo St George Regional Airport (SGU), ST. GEORGE, UT
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
Stall/mush
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 › Airspeed, not maintained
  • Pilot in command › Flight into adverse weather, attempted
  • Pilot in command › Flight manuals, disregarded
  • Pilot in command › Weather forecast, disregarded

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

NTSB narrative

The pilot called the flight service station and obtained a weather briefing prior to the flight. He was told several times that VFR flight was not recommended due in part to IFR conditions along a portion of his route, mountain obscurment along the entire route, and moderate rime and mixed icing along the route between 8,000 and 18,000 feet. Additionally, he was told there were thunderstorms over the Sierra Nevada Mountains, Southern California, and throughout Utah and Nevada. The pilot picked up an IFR clearance moments before he told controllers that he had a "system's failure." The controller asked him what type of system's problem he had and he told the controller that he had lost control of the aircraft and was descending at 2,000 feet per minute. Ground units that were launched to locate the missing aircraft were hampered by inclimate weather, and an H-60 military helicopter that was conducting an airborne search entered clouds and crashed not far from the site of the downed aircraft. Teardown reports on both engines concluded that there were no mechanical malfunctions noted that would have caused an operational problem. The left propeller was found feathered prior to impact, with no preimpact discrepancies noted on either propeller that would have precluded normal operation. The right propeller had indications of rotation and power development on impact. The airplane was not equipped for flight into icing conditions and did not have any propeller or wing deicing boots. Analysis of meteorological data showed that the aircraft entered the clouds where significant light to moderate clear/mixed airframe icing was present, and, encountered a convective cell in the minutes prior to the accident.

Probable cause

The pilot's disregard of the weather briefing information and his decision to attempt flight into forecast adverse weather conditions, which led to an encounter with icing conditions beyond the performance capability of the aircraft. The pilot's disregard for the pilot operating handbook prohibition against flight into icing conditions is also causal.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX98FA306
Event ID
20001211X11089
Case number
LAX98FA306
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: e7b05f04507d674ed95029fd84d495402ff2e0c811e9a7b7cab663ed81db97e4; retrieved 2026-09-20T22:23:46.128Z.