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

Aeronca 7AC accident near East St. Louis, Illinois, June 11, 2016

On June 11, 2016 at about 5:36 pm local time, a 1946 Aeronca 7AC, registered N82694, was substantially damaged in an accident during enroute (cruise) near East St. Louis, Illinois. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power due to fracture of the piston pin, which led to fatigue cracking and eventual fracture of the adjacent connecting rod.

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

What the record shows

Date
June 11, 2016 · about 5:36 pm local time
Place
East St. Louis, Illinois · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Aeronca 7AC NO SERIES, built 1946 · all 7ACs on the register
Registration
N82694 · registry record · serial 7AC-1336
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airline transport pilot and passenger departed on a local flight from an uncontrolled airport. The pilot flew for about 15 minutes when he heard "a loud noise, a rattle," and the engine lost total power. He chose to conduct a forced landing on a section of closed highway; however, the pilot was unable to slow the airplane and impacted barricades at the end of the road closure. Postaccident examination of the engine revealed two holes through the top of the crankcase, and cylinders No. 1 and No. 2 were separated from their mounts on the crankcase. Inside the No. 2 cylinder, the connecting rod was found fractured just below the piston head. Upon further examination of the connecting rod, the piston pin, which was manufactured from resulfurized steel, was also found fractured inside the connecting rod bore. The No. 2 cylinder failed due to a fractured piston pin that retained the connecting rod inside the piston crown underside. The fracture of the piston pin led to misalignment of the connecting rod, which eventually failed from fatigue in reverse bending. The fatigue stresses on the connecting rod were relatively low, consistent with most of the fracture surface exhibiting fatigue propagating from multiple crack initiation sites. The piston pin likely fractured first, in part exacerbated by intergranular cracking in the outer, case-hardened layer. Resulfurized steels, designed for better machinability, exhibit reduced notch toughness and ductility. Carburizing or carbonitriding of these steels is generally not recommended, as the surface treatment can increase susceptibility to intergranular fracture in the hardened condition. In addition, the degree of the surface case hardening was deeper than typical for this alloy. It is likely that a stress high enough to fracture the outer layer would lead to through-fracture of the pin. However, the location of the pin fracture was such that immediate failure of the engine did not occur until the connecting rod subsequently fractured from fatigue. The pin had been partially embrittled by the surface case hardening, which sufficiently lowered the fracture toughness to cause the pin to fracture prematurely.

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. Loss of engine power (total) during enroute (cruise) defining event
  2. Off-field or emergency landing during emergency descent
  3. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Failure
  • Environmental issues › Physical environment › Object/animal/substance › Wall/barricade › Contributed to outcome

Pilot

  • Certificate: airline transport pilot, commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: glider
  • Flight time: 22,077 hours in all; 61 in this make and model; 180 in the last 90 days; 60 in the last 30 days; 7,044 as pilot in command; 800 on instruments
  • Last flight review: August 5, 2015
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: frt
  • Injury: no injuries

Passenger

  • Seat: rear
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,095.9 hours
  • Last inspection: annual inspection, November 2, 2015
  • Maximum gross weight: 1,400 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental A65-8 (piston); 882 hours total

The flight

  • Departed from: H49 Columbia IL at 4:45 pm
  • Destination: H49 Columbia IL
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 250° at 7 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 25,000 ft; scat at 5,500 ft
  • Temperature: 93°F (34°C), dew point 64°F (18°C)
  • Altimeter: 30.05 inHg
  • Observation at 5:51 pm from KSTL, 14 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

4 documents, released by the NTSB on November 3, 2019. 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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.