FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08FA043 · Cirrus Design Corp. SR22

30 Dec 2007 · Paso Robles, CA, United States

Cirrus Design Corp. SR22 · Accident: in flight encounter with weather while maneuvering

From San Carlos Airport (SQL) to Paso Robles Municipal Airport (PRB)

Report a problem

Event

NTSB case
LAX08FA043
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
Visual Meteorological Cond

Cirrus Design Corp. SR22

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
N254SR
Operator
Unknown
Onboard fatalities
Unknown
Route
From San Carlos Airport (SQL), San Carlos, CATo Paso Robles Municipal Airport (PRB), Paso Robles, 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
Maneuvering
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
Stall
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 › Airspeed, not maintained
  • Pilot in command › Maneuver to avoid obstructions, attempted
  • Pilot in command › Stall, inadvertent
  • Weather condition › Mountain wave
  • Weather condition › Turbulence, terrain induced

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

As the airplane was approaching a friend's residence, the pilot called the friend on a cellular telephone informing him that he was about to pass by. The pilot had done this on many occasions as a way of notifying the friend that he should leave to pick him up from the airport. The friend was speaking with the pilot on the telephone when he observed the airplane drop rapidly about 1,000 feet as it was flying toward his house. The airplane was maneuvering very low in a nose-high configuration with full power, flying fast through the slight valley about 75 feet above ground level (agl). He noted that the winds were from the east (providing a tailwind) and estimated they were about 40 miles per hour (mph). The friend heard the telephone drop, with the pilot making a few inaudible comments. The airplane than made a rapid ascent as it neared power lines, climbing in a near vertical nose-high maneuver to about 1,000 feet agl. It subsequently made a 90-degree pivot about the longitudinal axis and then continued to turn into a barrel roll, disappearing behind the tree line. Ground scar analysis, impact signatures, and wreckage fragmentation patterns disclosed that the airplane impacted terrain in a near level attitude, with high forward velocity. The impact geometry combined with the witness statements of observing the airplane roll immediately after a near-vertical climb, is consistent with the pilot recovering from an accelerated stall and subsequent roll just prior to impact. There was no evidence of a pre-mishap mechanical malfunction or failure observed during the examination of the engine or airframe. A pilot report in the immediate vicinity and prior to the accident reported continuous light to occasional moderate turbulence between 2,000 and 5,000 feet mean sea level (msl). The GOES-11 satellite imagery surrounding the period depicted orographic clouds over and downwind of the higher terrain and 5 minutes after the accident, showed a band of tubular or "arcus" clouds moving over the accident site, which were similar in appearance to roll clouds. The clouds were of short duration and had moved southeastward and became less distinct about 15 minutes thereafter. Additionally, the Vandenburg AFB soundings surrounding the accident time indicated a strong low-level temperature inversion with northerly winds favorable for mountain wave activity formation downstream from high terrain. Based on an analysis of the terrain, wind flow pattern, and potential arcus clouds over the area, it is likely the accident aircraft encountered moderate or greater turbulence and downdrafts during the flyby of the residence.

Probable cause

The pilot's encounter with isolated moderate (or greater) turbulence, updrafts, and downdrafts associated with localized mountain wave conditions at low altitude, and, his failure to maintain adequate airspeed during the encounter that resulted in an inadvertent accelerated stall. Contributing to the accident were the pilot's decision to conduct low altitude flight maneuver and the pilot's diverted attention while using a cell phone.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08FA043
Event ID
20080114X00045
Case number
LAX08FA043
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: 2047bb0770aef20d75a5f74be6e2d77f843f302061bc59591aaa802509ac313e; retrieved 2026-09-20T16:02:21.739Z.