ERA25FA239 · Piper J3C-65
Piper J3C-65 · Accident: collision with terrain/object (non-CFIT) during landing
Event
- NTSB case
- ERA25FA239
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper J3C-65
- Aircraft type
- Piper J3
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N28DR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 80 years (built 1945)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On June 24, 2025, about 18:23 central daylight time, a Piper J3C-65, N28DR, was substantially damaged when it was involved in an accident near Dunlap, Tennessee. The commercial pilot was fatally injured and the passenger was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the passenger, the purpose of the flight was to continue instructional training that he had started a couple of days prior to the accident. Regarding the accident flight, he recalled that they were at a nearby airstrip about 7 miles north of the accident location. He does not recall departing that airfield, the accident flight, or the accident events. The accident site was located at the airplane owner’s private airstrip, about 40 feet to the left side of the runway. The runway heading was 240° and the airplane came to rest on a 335° heading. The airplane came to rest mostly upright in a hay field. A ground scar was observed directly in front of the airplane’s engine and was 8 inches deep. The scar was centered with the airplane and protruded to the airplane’s right by 2 feet. The right main landing gear collapsed, and the airplane was partially resting on the right wing. The cockpit instrumentation, firewall, and engine were displaced upwards from the fuselage. Witnesses that responded to the accident site confirmed that the fuel selector was in the “both” position. One witness reported that the forward occupant was wearing the installed four-point harness, and the aft seat occupant was not wearing a harness or lap belt, but that the lap belt was in close proximity to the occupant. A second witness recalled that the aft seat occupant had the lap belt secured, but the shoulder harnesses were not utilized. First responders that documented the scene noted several broken tree limbs with yellow paint transfer about 113ft from the main wreckage. A postaccident examination of the airframe and engine was conducted. There were no preaccident mechanical malfunctions or failures found with the engine that would have precluded normal operation. An examination of the airframe revealed damage to the left-wing leading edge with tree foliage found underneath the damaged skin, consistent with the tree foliage at the location of the broken tree limbs exhibiting yellow paint transfer. A puncture hole through the top and bottom of the left wing forward and at the outboard side of the left aileron was observed. A Garmin GPSmap396 was recovered and retained. The grass runway measured 40ft in width. A clearing at the beginning of the runway measured about 100ft wide and was about 50ft from the cut grass on the runway. According to the Federal Aviation Administration, the airstrip was about 2,100ft in length.
Figure 1: Main Wreckage Location in Proximity to the Private Airstrip and Broken Tree Limbs
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA25FA239
- Event ID
- 20250625200387
- Case number
- ERA25FA239
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b59ee70a9391ba38094a58aec2e81e9a696d9c17ce5c8db78545f921ae568771; retrieved 2026-09-15T09:06:00.562Z.