FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10CA281 · Cirrus Design Corp SR22

29 May 2010 · Avalon, CA, United States

Cirrus Design Corp SR22 · Accident: runway excursion during landing

From Corona Municipal Airport (KAJO) to Catalina Airport (KAVX)

Report a problem

Event

NTSB case
WPR10CA281
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
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
N314CP
Operator
Ilan Brand
Onboard fatalities
Unknown
Route
From Corona Municipal Airport (KAJO), Corona, CATo Catalina Airport (KAVX), Avalon, 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
Landing · landing roll
Defining eventThe 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
Runway excursion
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that he listened to the weather report at the airport prior to landing, which reported a slight tailwind on runway 22 that was in use by other airplanes in the traffic pattern. The pilot chose to land on runway 22 with a tailwind rather than changing runways to favor a headwind. In a phone conversation, the pilot stated that he landed "within the first couple hundred feet" of the runway at about 85 knots, using full flaps. He said that during the landing roll he overran the runway, resulting in the airplane exiting the end of the runway and coming to rest on a 45 degree downslope. The pilot stated that he "underestimated" the length of the runway due to the fact that the airplane was almost at max gross weight and there was a slight tailwind. The airplane sustained substantial damage to the right aft main wing spar. According to the Avalon aviation weather report, at the time of the accident the wind was from 020 degrees at 5 knots. According to the Southwest U.S. Airport/Facility Directory, the accident runway 04/22 is 3,000-feet-long. The first 2,000 feet of runway 22 is sloped up 1.8%, and the rest of the runway is level. At maximum gross weight in the weather conditions of the airport at the time of the accident, the airplane had a calculated ground roll of about 1,250 feet, with a total landing distance of about 2,500 feet. Taking into account the 5 knot tailwind and the 1.69% upslope, this airplane's final ground roll was calculated to be about 1,300 feet, and the total landing distance was about 2,650 feet.

Probable cause

The pilot's failure to achieve the proper touchdown point, which resulted in a runway overrun.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10CA281
Event ID
20100607X50851
Case number
WPR10CA281
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 6c6fec19eb7a913adb60364b8638df2dd1be89562ae9965ce1c319933fdcbe3d; retrieved 2026-09-15T14:22:46.742Z.