LAX91FA040 · Beech S-35
Beech S-35 · Accident: in flight collision with terrain/water en route
From Grand Junction Regional Airport (GJT) to Jacqueline Cochran Regional Airport (TRM)
Event
- NTSB case
- LAX91FA040
- 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
- Visual Meteorological Cond
Beech S-35
- Aircraft type
- Beechcraft S-35
- 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
- N5748K
- Operator
- Crimmins, William H. · private individual
- Onboard fatalities
- Unknown
- Route
- From Grand Junction Regional Airport (GJT), Grand Junction, COTo Jacqueline Cochran Regional Airport (TRM), Thermal, 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 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 › Proper altitude, not identified
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE 57 YEAR OLD PILOT DEPARTED LATE IN THE DAY FOR A 7 TO 8 HOUR CROSS COUNTRY FLIGHT TO BEAT SOME INCOMING WEATHER. HE HAD BEEN PHEASANT HUNTING FOR TWO DAYS PRIOR. THE SECOND LEG OF HIS TRIP WAS A DARK NIGHT DEPARTURE FOR WHICH HE FILED A VFR FLIGHT PLAN AND INDICATED 12500 FEET MSL AS HIS CRUISING ALTITUDE. RADAR DATA DISCLOSED THAT HE CLIMBED TO 13100 FEET AT ONE POINT, HOWEVER, HIS OVERALL ROUTE OF FLIGHT FOR NEARLY 3 HOURS WAS ONE OF A MEANDERING AND UNDULATING TRACK. THE APPROXIMATE LAST 10 MINUTES OF FLIGHT WAS A GRADUAL ON TRACT DESCENT TO IMPACT AT ABOUT 5700 FEET, ABOUT AN HOUR SHORT OF HIS DESTINATION. HE CARRIED NO SUPPLEMENTAL OXYGEN. FRIENDS INDICATED HE FREQUENTLY TOOK 'CAT NAPS' ON LONG CROSS COUNTRY TRIPS WHILE LETTING THE AUTO PILOT FLY THE AIRCRAFT. HIS AUTOPILOT WAS OPERATIONAL EXCEPT FOR THE ALTITUDE HOLD.
Probable cause
PROPER ALTITUDE NOT MAINTAINED. CONTRIBUTING TO THE ACCIDENT WAS: THE LACK OF SUPPLEMENTAL OXYGEN ON BOARD THE AIRCRAFT, PILOT FATIGUE, IMPROPER USE OF THE AUTO PILOT, AND PILOT COMPLACENCY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91FA040
- Event ID
- 20001212X24625
- Case number
- LAX91FA040
- 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 1990-11-20.
- API snapshot SHA-256: 7083c2c05bdc531ddc67b503501e7e91a17ab31bb3e852810d2a1e66dd015ee5; retrieved 2026-09-21T02:04:45.274Z.