LAX08FA026 · Beech A100
RHB-JMJ Beech A100 · Accident: in flight encounter with weather during initial climb
From Chino Airport (KCNO) to Visalia Municipal Airport (KVIS)
Event
- NTSB case
- LAX08FA026
- 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
- 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
- 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 A100
- Aircraft type
- Beechcraft 100
- 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
- N30GC
- Operator
- RHB-JMJ
- Onboard fatalities
- Unknown
- Route
- From Chino Airport (KCNO), Chino, CATo Visalia Municipal Airport (KVIS), Visalia, 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
- Initial climb
- 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
- Tree(s)
- 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 › Climb, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The reported weather at the time of the accident was calm winds, a 1/4-mile visibility in fog and a vertical visibility of 100 feet. Shortly after takeoff for the instrument-flight-rules flight, the airplane made a slight turn to the left and impacted the tops of 25-foot trees about a 1/2 mile from the runway. An enhanced ground proximity warning system was installed on the airplane and data extraction from the system indicated that the airplane achieved an initial positive climb profile with a slight turn to the left and then a descent. A witness reported hearing the crash and observed the right wing impact the ground and burst into flames. The airplane then cartwheeled for several hundred feet before coming to rest inverted. The airframe, engines, and propeller assemblies were inspected with no mechanical anomalies noted that would have precluded normal flight.
Probable cause
The pilot's failure to maintain a positive climb rate during an instrument takeoff. Contributing to the accident was the low visibility.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08FA026
- Event ID
- 20071113X01788
- Case number
- LAX08FA026
- 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, coordinates. 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: e505f2929f0e53034eeea1406ac03c26f81e590106c4a2bad3cb65f1b638bca8; retrieved 2026-09-20T16:07:50.806Z.