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

Amateur-built GLASTAR GS-1 accident near Columbus, Indiana, July 25, 2013

On July 25, 2013 at about 1:32 pm local time, a 2006 amateur-built GLASTAR GS-1, registered N513GC, was destroyed in an accident during approach (VFR pattern downwind) near Columbus, Indiana (Columbus Municipal Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Slippage in the engine clutch and gear reduction module and a resultant uncommanded movement of the propeller blades into reverse thrust.

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

What the record shows

Date
July 25, 2013 · about 1:32 pm local time · cases in 2013
Place
Columbus, Indiana · Columbus Municipal Airport · cases near this airport · map
Type
Accident
Injuries
1 person was killed and 1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Amateur-built GLASTAR GS-1, built 2006
Registration
N513GC · no longer on the register · serial 5330
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

Family members and friends reported that, 2 years before the accident, the experimental, amateur-built airplane had experienced a serious in-flight engine problem. Since that time, the pilot had been repairing the engine and propeller system, and the accident flight was the airplane's first flight following the reported engine problem. The pilot-rated passenger reported that, just after departing for a short local flight and turning the airplane to enter the downwind leg of the airport traffic pattern, the pilot informed him that there was a problem and that they needed to return to the airport. He added that the pilot began working "frantically on an electric switch for the propeller" while the engine was "screaming" but that the airplane continued descending. The airplane struck a tree and then impacted a house. An explosion and a postimpact fire immediately ensued, which consumed most of the airplane and the house. The pilot and passenger were able to exit the burning wreckage without assistance. An examination of the engine clutch and gear reduction module found some metal contamination and a nonstandard displacement of the sprag clutch elements, and these issues likely resulted in clutch slippage, which can lead to the uncommanded movement of the propeller blades. The propeller blades were observed to be in about 5 degrees of reverse pitch, which would result in a substantial loss of glide capability.

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. Aircraft maintenance event during prior to flight
  2. Aircraft inspection event during prior to flight
  3. Powerplant sys/comp malf/fail during approach (VFR pattern downwind) defining event
  4. Off-field or emergency landing during emergency descent
  5. Collision with terrain or object (not controlled flight into terrain) during emergency descent
  6. Explosion (post-impact) during post (impact)
  7. Fire/smoke (post-impact) during post (impact)
  8. Cabin safety event during post (impact)

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Not specified other cases naming the engine
  • cause Aircraft › Aircraft propeller/rotor › Propeller system › Propeller controlling system › Malfunction
  • Environmental issues › Physical environment › Object/animal/substance › Residence/building › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 286 hours in all; 66 in this make and model; 0 in the last 90 days; 0 in the last 30 days
  • Medical certificate: None
  • Seat: left
  • Injury: fatal

Pilot-Rated Passenger

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 267 hours in all; 0 in this make and model
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: rgt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 66 hours
  • Last inspection: condition inspection
  • Maximum gross weight: 1,960 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Subaru EJ22 (piston); 66 hours total
  • Fire on the ground

The flight

  • Departed from: BAK Columbus IN at 1:29 pm
  • Destination: BAK Columbus IN
  • Flight plan: none
  • Runway 23, 6,401 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 63°F (17°C), dew point 57°F (14°C)
  • Altimeter: 30.09 inHg
  • Observation at 1:38 pm from KBAK, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew11

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

11 documents, released by the NTSB on October 26, 2015. 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/CEN13LA433.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.