13 Sep 2012: SEYMOUR SKYRANGER

13 Sep 2012: SEYMOUR SKYRANGER (N936LS) — Unknown operator

No fatalities • Perris, CA, United States

Probable cause

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.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn September 13, 2012, about 1320 Pacific daylight time, an experimental light-sport Seymour Skyranger, N936LS, experienced an in-flight loss of control near Perris, California. The pilot/builder was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. The sport pilot sustained minor injuries, and the airplane sustained substantial damage. The personal flight departed Corona Municipal Airport, Corona, California, about 1240, with a planned destination of Perris Valley Airport, Perris. Visual meteorological conditions prevailed, and no flight plan had been filed.

The pilot reported that during cruise flight, he heard a "bang" sound, and the airplane immediately began to descend and roll to the left. He applied both right aileron and right rudder control inputs, and was able to regain partial control. He elected to land the airplane in a field rather than activate the ballistic recovery parachute; however, as the descent progressed, the airplane's turn rate began to increase. He became concerned that the airplane was too low to activate the parachute, and that it may become entangled in the rigging cords, so he braced for impact. The airplane struck the ground in a left-wing-low attitude, and the pilot was able to egress unaided. AIRCRAFT INFORMATIONThe airplane was built by the pilot, and issued its experimental light-sport certificate in December 2006. Since that time it had accrued a total of 1,066 flight hours. The last conditional inspection was completed on January 13, 2012, 68 flight hours prior to the accident. AIRPORT INFORMATIONThe airplane was built by the pilot, and issued its experimental light-sport certificate in December 2006. Since that time it had accrued a total of 1,066 flight hours. The last conditional inspection was completed on January 13, 2012, 68 flight hours prior to the accident. WRECKAGE AND IMPACT INFORMATIONThe airplane came to rest in a corral adjacent to a residence. The airplane remained in a nose-down attitude, sustaining crush damage to the forward fuselage. The nosegear had been separated, and the engine, firewall, and left main landing gear had become displaced aft. The left wing was bent upwards about 10 degrees at the lift strut, and sustained crush damage to the leading edge tip. The remaining structure was largely intact and examined by an FAA inspector who responded to the accident site. TESTS AND RESEARCHThe airplane was recovered to a hangar by friends of the owner, and subsequently examined by the NTSB investigator-in-charge.

Control continuity was established from the cockpit controls through to the respective control surfaces, with the exception of the elevator trim tab. The trim tab was positioned on the right elevator, and had been modified by the owner with the addition of a spring connecting the upper trim horn to the elevator spar. The trim control cable had pulled through its control fitting in the lower footwell, and as such, the spring had pulled the trim tab to the full-up position. The owner stated that he installed the spring to prevent the tab from fluttering in the event of a control cable failure.

All major structural members were intact, with damage limited to bending and crush damage centered around the forward fuselage.

The left wing internal brace cable, which connected the aft spar at the outboard trailing edge to the forward spar at the inboard leading edge, had separated where it entered its outboard crimp fitting. The cable was sent to the NTSB Office of Research and Engineering for analysis.

Examination revealed that the cable was a 7 x 7 wire rope type, composed of seven strands and seven wires per strand. Each fractured wire, 49 in total, was examined using a stereomicroscope. The fractured wire surfaces had either a cup and cone morphology or a slanted morphology approximately 45 degrees to the wire longitudinal axis. Both morphologies were consistent with an overstress fracture, with no indications of wear or rubbing of the wires inside the sleeve.

Examination by both the FAA inspector at the accident site, and NTSB investigator-in-charge at the follow up examination, did not reveal any mechanical anomalies with the airframe that would have precluded normal operation.

Contributing factors

  • Pilot
  • Directional control — Not attained/maintained

Conditions

Weather
VMC, wind 000/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.