Piper J3C-65 accident near Gosport, Indiana, August 6, 2021
On August 6, 2021, a 1946 Piper J3C-65, registered N6269H, was substantially damaged in an accident during enroute near Gosport, Indiana. It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was 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 during cruise flight due to the failure of a cylinder exhaust valve stem, which led to a forced landing during which the airplane impacted terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 6, 2021
- Place
- Gosport, Indiana · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper J3C-65, built 1946 · all J3C-65s on the register
- Registration
- N6269H · registry record · serial 19449
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that, during cruise flight, the airplane experienced “significant” vibration, which was followed by a total loss of engine power. The pilot performed a forced landing to a field, during which the airplane nosed over and impacted terrain. Postaccident examination of the airplane engine revealed that the No. 4 cylinder exhaust valve stem was broken at its base and the seat was turned sideways. Pieces of the stem were found in the cylinder. The failure of the exhaust valve resulted in reduced engine compression leading to the total loss of engine power.
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
- Loss of engine power (total) during enroute
- Off-field or emergency landing during landing
- Collision during takeoff/land during landing
- Powerplant sys/comp malf/fail during enroute defining event
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Failure
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,425 hours in all
- Medical certificate: Class 3
- Seat: unk
- Injury: no injuries
The aircraft
- Airframe total time: 3,677 hours
- Last inspection: annual inspection, September 3, 2020
- Maximum gross weight: 1,220 lb
- Seats: 2
- Landing gear: fixed
- Engine: Continental A-65-8 (piston); 0 hours total
The flight
- Departed from: 0I2 Brazil IN
- Destination: IG03 Paragon IN
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 77°F (25°C), dew point 64°F (18°C)
- Altimeter: 30.08 inHg
- Observation at 7:53 pm from BMG, 15 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on November 16, 2022. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 6 pages | View Download |
| 2 | Record of Correspondence - FAA | PDF, 1 page | View Download |
| 3 | Photo Log | PDF, 1 page | View Download |
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.