The U.S. aircraft register, updated daily
Accidents · NTSB CEN11FA324 · Final report

Amateur-built RAVIN 500 accident near Conroe, Texas, May 7, 2011

On May 7, 2011 at about 1:55 pm local time, a amateur-built RAVIN 500, registered N913RA, was destroyed in an accident during initial climb near Conroe, Texas (Lone Star Executive 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

An in-flight smoke event on takeoff and the pilot’s failure to maintain control of the airplane, which resulted in an aerodynamic stall.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 7, 2011 · about 1:55 pm local time · cases in 2011
Place
Conroe, Texas · Lone Star Executive Airport · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Amateur-built RAVIN 500
Registration
N913RA · no longer on the register · serial 07050013
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

Airport tower personnel gave the pilot clearance to depart with a right turn on course. The airplane departed, and as the pilot began the initial right turn, he reported to the tower that he had smoke in the cockpit. The airplane was cleared to land on any runway and was told the wind was from 160 degrees at 8 knots. A witness observed the airplane perform a 240-degree right turn and crossed back over the departure runway before the airplane entered a left downwind leg for runway 14. While on the downwind leg of the traffic pattern, the witness stated that the airplane was flying “slow” with its wings level at an estimated altitude of 700 to 800 feet above the ground. While about 4,500 feet on the downwind leg, the landing gear was extended. Shortly thereafter, the airplane started a descending left turn toward the closer runway 19. The airplane overshot the extended centerline to runway 19 and the airplane’s bank angle increased. The airplane continued in the descending left turn toward the runway until about 300 feet above the ground, at which point the airplane appeared to “stall” and disappear in the trees. Tower personnel reported that during the event, they did not observe any smoke or flames coming from the airplane until impact. A pilot-rated eyewitness located near the crash site reported hearing what he described as an engine that was “screaming” and varying in rpm. When he saw the airplane, it was flying “very slow” at an estimated altitude of 300 to 500 feet above the ground. As the airplane made a high bank angle turn back toward the airport, the witness observed the nose and left wing drop before the airplane went out of sight. Seconds later, he heard it impact trees followed by an explosion. A postimpact fire ensued, which consumed the airplane’s structure. An examination of the remainder of the airplane confirmed control continuity and no apparent anomalies to the airplane’s engine or systems. The examination failed to reveal the origin of the reported in-flight smoke.

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

  1. Fire/smoke (non-impact) during initial climb defining event
  2. Collision with terrain or object (not controlled flight into terrain) during emergency descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • cause Environmental issues › Task environment › Physical workspace › Air quality/dust/smoke › Effect on personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 3,400 hours in all; 150 in this make and model
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

Dual student

  • Certificate: student
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Last inspection: condition inspection, July 14, 2010
  • Seats: 4
  • Landing gear: retractable
  • Engine: Chevrolet LS1 (piston); 0 hours total
  • Not recorded

The flight

  • Departed from: KCXO Conroe TX
  • Destination: Temple TX
  • Flight plan: not recorded
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 180° at 6 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 23,000 ft
  • Temperature: 68°F (20°C), dew point 63°F (17°C)
  • Altimeter: 29.95 inHg
  • Observation at 1:53 pm from KCXO

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

12 documents, released by the NTSB on February 4, 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.

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

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN11FA324.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.