21 Apr 2019: Rans S7 S

21 Apr 2019: Rans S7 S (N25TX) — Unknown operator

2 fatalities • Kingsland, TX, United States

Probable cause

The exceedance of the airplane's critical angle of attack during a steep climb after takeoff, which resulted in an aerodynamic stall and spin into terrain.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn April 21, 2019, at 1443 central daylight time, a Rans S-7S airplane, N25TX, was destroyed when it was involved in an accident near Kingsland, Texas. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

A witness reported that the pilot had just completed a few touch-and-go landings at Shirley Williams Airport before the passenger boarded the airplane. He saw the airplane taxi back to the runway, then heard it impact the ground shortly thereafter.

Another witness reported observing what he considered a "normal" takeoff, followed by a steep 15 to 20 second climb. At the top of the climb, the nose and left wing suddenly dropped, and the airplane entered a left-turning spiral, completing 3 to 4 slow rotations before impact with the ground. He stated that the engine sounded normal the whole time and he did not notice anything wrong. AIRCRAFT INFORMATIONAccording to the second witness who observed the accident, in March 2019, the pilot and passenger (who was also a mechanic) had completed maintenance work on the carburetors and synchronized them so that the engine ran smooth. The week before the accident, the pilot and passenger had dinner with the witness and told him that they were troubleshooting an issue where the engine would sputter during steep climbs. They told the witness that they cleaned the gascolator, checked the fuel lines, and verified that the propeller was adjusted correctly. The witness stated that, 1 day before the accident, the pilot flew the airplane with another passenger, but they just flew to get lunch and did not attempt any steep climbs. The pilot reported to him that the engine operated with no issues. The witness further stated that, on the day of the accident, the pilot's plan was to perform steep climbs and try to figure out why the engine was sputtering. The witness did not know if the accident flight was the first troubleshooting flight.   AIRPORT INFORMATIONAccording to the second witness who observed the accident, in March 2019, the pilot and passenger (who was also a mechanic) had completed maintenance work on the carburetors and synchronized them so that the engine ran smooth. The week before the accident, the pilot and passenger had dinner with the witness and told him that they were troubleshooting an issue where the engine would sputter during steep climbs. They told the witness that they cleaned the gascolator, checked the fuel lines, and verified that the propeller was adjusted correctly. The witness stated that, 1 day before the accident, the pilot flew the airplane with another passenger, but they just flew to get lunch and did not attempt any steep climbs. The pilot reported to him that the engine operated with no issues. The witness further stated that, on the day of the accident, the pilot's plan was to perform steep climbs and try to figure out why the engine was sputtering. The witness did not know if the accident flight was the first troubleshooting flight.   WRECKAGE AND IMPACT INFORMATIONThe airplane departed on runway 16 and impacted the ground near the south end of the runway, as seen in figure 1.

Figure 1 – Aerial image of the accident site

The accident site consisted of a small initial impact point in the ground about 20 ft south of the main wreckage. The impact point was defined by a divot in the ground which contained a broken red lens, the pitot tube, and a piece of left wing tip. Another impact area was about 6 ft south of the main wreckage, which was about 3 ft in diameter and about 4 inches deep. The small crater contained white paint chips, plexiglass, a propeller blade, and the engine oil filter. Another small divot was observed under the outboard leading edge of the right wing. The three impact areas were in a relatively straight line in a north-south orientation. The airplane came to rest upright facing southwest and was mostly consumed by postcrash fire. An examination of the airframe did not reveal any anomalies that would have precluded normal operation.

The engine remained attached to the engine mounts, which were broken from the airframe. The engine was mostly intact and severely damaged by fire. The propeller hub remained attached to the crankshaft and one blade remained attached to the hub. The second blade was broken from the hub at the blade root and was found next to the initial engine impact crater – it exhibited chordwise scratches on the face. The third blade was also broken from the hub at the blade root and was found about 20 ft west of the main wreckage – it exhibited chordwise scratches and the blade tip was separated. The engine was examined at a secure facility and exhibited significant thermal damage from the postimpact fire. The fuel pump was partially consumed by the fire and a full examination was not possible. According to the engine manufacturers guidance and the fuel pump serial number, the fuel pump had a five-year time limit and should have been replaced in 2010.

The engine did not reveal any anomalies that would have preclude normal operation; however, the examination was limited due to the thermal damage. MEDICAL AND PATHOLOGICAL INFORMATIONAn autopsy of the pilot was performed by Travis County Medical Examiner, Austin, Texas. The cause of death was blunt force injuries.

Toxicology testing of specimens from the pilot, performed by the FAA Forensic Sciences Laboratory, identified three previously reported medications: amlodipine, hydrochlorothiazide, and rosuvastatin. Also present were two other medications: naproxen and salicylate. These medications would not have posed a hazard to the safety of flight.

An autopsy of the pilot-rated passenger was performed by Travis County Medical Examiner, Austin, Texas. The cause of death was blunt force injuries.

Toxicology testing of specimens from the pilot-rated-passenger did not identify any drugs or tested-for substances.

Contributing factors

  • Pilot
  • Airspeed — Not attained/maintained
  • Angle of attack — Not attained/maintained
  • Gusts

Conditions

Weather
VMC, wind 180/15kt, 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.