Yakovlev YAK 52 accident near Redlands, California, February 8, 2010
On February 8, 2010 at about 8:50 pm local time, a Yakovlev YAK 52, registered N52VY, was substantially damaged in an accident during maneuvering (aerobatics) near Redlands, California (Redlands Municipal Airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain aircraft control and altitude sufficient to recover from a low-level aerobatic maneuver.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 8, 2010 · about 8:50 pm local time · cases in 2010
- Place
- Redlands, California · Redlands Municipal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Yakovlev YAK 52 · all YAK 52s on the register
- Registration
- N52VY · no longer on the register · serial 855608
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Witnesses reported that the pilot completed several loops and other aerobatic maneuvers over the course of about 10 minutes. The airplane then began a spin from a low altitude and continued in a "corkscrew" path until colliding with the ground. Ground scar analysis and wreckage fragmentation disclosed that the airplane impacted in a slight nose-low attitude at a relatively low airspeed, an indication that the pilot was likely recovering from the spin at the time of impact. An examination of the wreckage revealed that all major components were accounted for at the accident site; flight control continuity could not be established due to the extensive fragmentation of the wreckage. The pilot had amassed 21.1 hours flight time in the make/model airplane, which included 7.7 hours of dual aerobatic training and 5.2 hours of solo aerobatic time.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Low altitude operation/event during maneuvering (aerobatics) defining event
- Loss of control in flight during maneuvering (aerobatics)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not specified
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
- Flight time: 250 hours in all
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: fatal
Crew member
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 200 hours in all
- Medical certificate: None (without waivers/limitations)
- Seat: rear
- Injury: fatal
The aircraft
- Airframe total time: 963 hours
- Last inspection: condition inspection, September 1, 2009
- Maximum gross weight: 2,340 lb
- Seats: 2
- Landing gear: fixed
- Engine: Vedenev M-14P (piston); 0 hours total
The flight
- Departed from: REI Redlands CA at 8:30 pm
- Destination: REI Redlands CA
- Flight plan: none
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: scat at 3,500 ft
- Temperature: 57°F (14°C), dew point 41°F (5°C)
- Altimeter: 29.94 inHg
- Observation at 8:53 pm from SBD, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
9 documents, released by the NTSB on October 13, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Yak Industry Experts: Video Critique | PDF, 4 pages | View Download |
| 2 | UAS Comments | PDF, 3 pages | View Download |
| 3 | Toxicological Report | PDF, 1 page | View Download |
| 4 | Aerobatic Scoresheet (First Page Found in Wreckage) | PDF, 5 pages | View Download |
| 5 | Maintenance Records | PDF, 15 pages | View Download |
| 6 | Tests and Research (11 Pictures Embedded) | PDF, 4 pages | View Download |
| 7 | Main Wreckage (4 Pictures Embedded) | PDF, 2 pages | View Download |
| 8 | Photo of Video Footage | PDF, 1 page | View Download |
| 9 | Video Footage of Accident | MPG file | Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N52VY: not on the register today · the record of its deregistration
- Yakovlev YAK 52 117 registered today · the model family and its accident history
- Yakovlev 229 aircraft on the register
- Engine: Vedenev M-14P · as the NTSB recorded it
- Redlands Municipal · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,500 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR10FA131.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
