Seymour SKYRANGER accident near Perris, California, September 13, 2012
On September 13, 2012 at about 8:20 pm local time, a 2004 Seymour SKYRANGER, registered N936LS, was substantially damaged in an accident during enroute (cruise) near Perris, California (Perris Valley airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of aircraft control during cruise flight for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 13, 2012 · about 8:20 pm local time · cases in 2012
- Place
- Perris, California · Perris Valley · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Seymour SKYRANGER, built 2004
- Registration
- N936LS · registry record · serial SKR0306325
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During cruise flight in the experimental amateur-built airplane, the pilot heard a "bang" sound, and the airplane immediately began to descend and roll to the left. He applied opposing aileron and right rudder control inputs and was able to regain partial control; however, as the descent progressed, the airplane's turn rate began to increase. The airplane struck the ground in a left-wing-low attitude, sustaining substantial damage. Examination of the airframe did not reveal any failures or anomalies that would have precluded normal operation. Although postaccident examination of the wreckage revealed two separated cables (a wing brace and an elevator trim tab cable), physical evidence indicated that the cable separations most likely occurred during the accident sequence. Additionally, if the elevator trim tab cable had separated in flight, the movement of the trim tab to the up position likely would not have resulted in the flight control difficulties experienced by the pilot. Thus, it was not possible to determine why the airplane departed controlled flight and why the pilot was unable to regain control.
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
- Unknown or undetermined during enroute (cruise) defining event
- Loss of control in flight during enroute (cruise)
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
Pilot
- Certificate: sport pilot
- Ratings: single-engine land
- Flight time: 1,533 hours in all; 1,050 in this make and model; 33.5 in the last 90 days; 7.9 in the last 30 days; 1,533 as pilot in command
- Last flight review: February 4, 2011
- Medical certificate: Sport Pilot
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 1,066 hours
- Last inspection: condition inspection, January 13, 2012; 68 hours since
- Maximum gross weight: 1,212 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912UL (piston); 1,056 hours total
The flight
- Departed from: AJO Corona CA at 7:40 pm
- Destination: L65 Perris CA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 99°F (37°C), dew point 45°F (7°C)
- Altimeter: 29.98 inHg
- Observation at 8:55 pm from RIV, 9 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
7 documents, released by the NTSB on December 9, 2013. 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 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Photo - 1 - Airplane at Accident Site | PDF, 1 page | View Download |
| 3 | Photo - 2 - Airplane at Accident Site | PDF, 1 page | View Download |
| 4 | Photo - 3 - Elevator Trim Tab | PDF, 1 page | View Download |
| 5 | Photo - 4 - Elevator Trim Tab Control Fitting | PDF, 1 page | View Download |
| 6 | Wing Brace Cable Examination Report | PDF, 2 pages | View Download |
| 7 | Evidence Control Form | PDF, 2 pages | View 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
- N936LS on the register today · the tail number may have moved to another aircraft since
- Engine: Rotax 912UL 135 aircraft carry this series today · as the NTSB recorded it
- Perris Valley Airport · nearest airport
- Corona Municipal · departed from
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,286 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR12LA417.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.
