LAX05FA088 · Cirrus Design Corp SR22 G2
Cirrus Design Corp SR22 G2 · Accident: in flight encounter with weather en route
From Reno Tahoe International Airport (RNO) to Oakland San Francisco Bay Airport (OAK)
Event
- NTSB case
- LAX05FA088
- 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
- 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 Design Corp SR22 G2
- Aircraft type
- Cirrus SR22
- 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
- N286CD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reno Tahoe International Airport (RNO), Reno, NVTo Oakland San Francisco Bay Airport (OAK), Oakland, 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
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
- Weather condition › Icing conditions
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane, while operating under an instrument flight rules (IFR) flight plan, departed from controlled flight after encountering icing conditions, entered an uncontrolled descent, and collided with the ground. The airplane was equipped with an Ice Protection System that when activated supplied deicing fluid to the wings, tail, and propeller. The aircraft was not certified for flight into known icing and the Pilot Operating Handbook reads that, "Flight into known icing conditions is prohibited." The pilot received a preflight weather briefing, which advised that there were no pilot weather reports (PIREP) for the intended route of flight, and that the freezing level in the Reno area was 6,000 feet with no precipitation. There were no valid SIGMET's or AIRMET's for icing conditions along the pilot's route. The pilot filed his IFR flight plan for 12,000 feet, but indicated he might request 14,000 feet once airborne. After takeoff, at 1807:46, the pilot contacted Oakland Air Route Traffic Control Center (ARTCC) and requested to climb to 16,000 feet to try to get above the clouds. At 1813:40, the pilot reported that he was still in the clouds and asked about going lower. At 1815:00, the pilot advised ARTCC that if he could go up another 200 to 300 feet, he could get above the clouds. ARTCC requested clarification if the pilot wanted to go up or down. The pilot responded that he would like to go up first to build up some airspeed. The pilot was cleared for a block altitude between 16,000 to 17,000 feet. About 2 minutes later, the pilot transmitted that he was "coming down" and that he was "icing up." The last transmission from the pilot was at 1817:42, again indicating that he was icing up and coming down. According to investigators from Ballistic Recovery Systems (BRS), following the examination of the ballistic parachute system, they determined the system was deployed outside of the operating envelope of the system, which is 133 knots indicated airspeed. An examination of the airplane wreckage did not reveal any evidence of preimpact mechanical failures or malfunctions. Analysis of the actual weather conditions encountered revealed the likelihood that the pilot encountered severe icing related to super-cooled large water droplets as the aircraft achieved 16,000 feet and above. Review of the weather forecast products available at the time of the pilot's briefing disclosed that the AFSS briefing fully conformed to Federal Aviation Administration standards and adequately covered the observed and forecast weather conditions. Although post accident analysis of the weather conditions showed the clear likelihood of severe icing conditions, the algorithms used by the NWS Aviation Weather Center to predict icing conditions showed only a low probability of icing in the area, and, in the absence of PIREPs to the contrary, an icing forecast was not triggered.
Probable cause
the pilot's in-flight loss of control following an inadvertent encounter with unforecast severe icing conditions. A factor in the accident was the inaccurate icing forecast developed by the NWS Aviation Weather Center.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05FA088
- Event ID
- 20050222X00211
- Case number
- LAX05FA088
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-02-07.
- API snapshot SHA-256: 83eee96ff3f265b8cac5cd5d613bc36c55540fb9b2f740f136b727c3b848313b; retrieved 2026-09-20T18:07:29.882Z.