LAX82FA183 · Beech A24R
Beech A24R · Accident: in flight encounter with weather en route
From Redding Municipal Airport (RDD) to Grants Pass Airport (3S8)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX82FA183
- 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
- 4 · 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 A24R
- Aircraft type
- Beechcraft 24
- 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
- N9715L
- Operator
- Daniel L. Jackson · private individual
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Redding Municipal Airport (RDD), Redding, CATo Grants Pass Airport (3S8), Grants Pass, OR
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); 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 › Flight into known adverse weather, continued
- Pilot in command › VFR flight into imc, continued
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE FLIGHT ORIGINATED AT RENO, NV, BUT THE PILOT LANDED AT RED BLUFF, CA AFTER RECEIVING AN IN-FLIGHT WEATHER BRIEFING. AFTER LANDING, HE OBTAINED ANOTHER WEATHER BRIEFING AND WAS ADVISED THAT VFR FLIGHT WAS NOT RECOMMENDED. HE THEN FILED A VFR FLIGHT PLAN AFTER REPORTING THAT THE PASSENGERS WERE ANXIOUS TO GET HOME, OTHERWISE HE WOULD STAY. THE FLIGHT PLAN WAS FILED FOR 8500 FT. THERE WERE NO KNOWN COMMUNICATIONS WITH THE AIRCRAFT AFTER THE PILOT ACTIVATED HIS FLIGHT PLAN. THE PLANE COLLIDED WITH TREES AND CRASHED ON DOWNSLOPING TERRAIN ABOUT 12 MI NORTHEAST OF MT SHASTA. THE IMPACT OCCURRED ON A SOUTHERLY HEADING AT ABOUT 7000 FT MSL. ACCORDING TO A WEATHER STUDY, THERE WOULD HAVE BEEN EXTENSIVE CLOUDS BETWEEN 5500 AND 10,000 FT WITH SCATTERED RAIN SHOWERS. ALSO, THERE WOULD HAVE BEEN MIXED RIME AND CLEAR ICING IN CLOUDS AND RAIN SHOWERS ABOVE APPROXIMATELY 6300 FT AND TURBULENCE WAS FORECASTED BELOW 18,000 FT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82FA183
- Event ID
- 20020917X03652
- Case number
- LAX82FA183
- 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: 405df15d77c12c8ac535734ded242392ebdfe4777106c692cab84eb808bcbba8; retrieved 2026-09-21T08:22:10.561Z.