LAX04LA324 · Cirrus SR-22
Cirrus SR-22 · Accident: in flight encounter with weather en route
From Redding Municipal Airport (KRDD) to Gillespie Field (KSEE)
Event
- NTSB case
- LAX04LA324
- 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
- 0 · 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
Cirrus SR-22
- Aircraft type
- Cirrus SR-22
- 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
- N931CD
- Operator
- William K. Graham · private individual
- Onboard fatalities
- Unknown
- Route
- From Redding Municipal Airport (KRDD), Redding, CATo Gillespie Field (KSEE), El Cajon, 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 · climb to 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
- Substantial
Cause areas
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Flight into adverse weather, continued
- Weather condition › Thunderstorm
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During climbing flight at 16,000 feet, the single engine airplane encountered the outer boundaries of severe convective weather; the airplane departed controlled flight, the pilot deployed the Cirrus Airframe Parachute System (CAPS), and the airplane was substantially damaged during the parachute landing in a walnut grove. The pilot did receive a standard weather briefing, checked radar, and satellite imagery prior to departing on the 600-mile cross-country flight. Throughout the flight the pilot recognized cloud build-ups and steered west to avoid the weather. About an hour into the flight he climbed from 13,500 to 16,000 in an attempt to stay clear of clouds; the autopilot was in heading mode and the vertical speed knob was set to maintain 100 knot climb. About this time radar depicted the airplane descending 1,100 feet in 23 seconds then climbing 1,300 feet in 14 seconds. The pilot heard a "whirring" noise in his headset, prompting him to disconnect the autopilot. The nose pitched up and the left wing dropped. It was at this time that the pilot transmitted that he was out of control and he deployed the CAPS. The airplane then descended by parachute to a landing in a walnut orchard. The radar track of the airplane combined with the weather surveillance radar imagery depicted the airplane encountering a level 5 (intense) area of convective activity moments prior to the final descent (CAPS deployment). Radar derived cloud tops indicated that the tops of the thunderstorms in the accident area were between 15,000 and 20,000 feet. Convective SIGMETs 44W and 47W, had been issued during the hour before departure, and warned of thunderstorms in the vicinity of the pilots' planned route of flight. SIGMET 49W, which covered the area in which the airplane was flying, was issued approximately 10 minutes prior to the airplane departing controlled flight. Examination of the airplane revealed no evidence of a preimpact malfunction or failure of the control system, autopilot, or power plant.
Probable cause
The pilot's decision to continue flight into adverse weather and the subsequent encounter with the outer boundaries of a level 5 thunderstorm, which resulted in his loss of control of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04LA324
- Event ID
- 20041007X01591
- Case number
- LAX04LA324
- 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: 056067dacc6d7c0f6e55885acad7ff9dd3395e543ed9213a7a5d1c442b13ec22; retrieved 2026-09-22T06:42:20.290Z.