The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA26LA328 · Preliminary: the investigation is not finished

Piper PA-28-180 accident near Dallas, Georgia, September 4, 2026

On September 4, 2026, a 1964 Piper PA-28-180, registered N7635W, was substantially damaged in an accident during initial climb near Dallas, Georgia (Paulding Northwest Atlanta airport). It was an instructional flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
September 4, 2026
Place
Dallas, Georgia · Paulding Northwest Atlanta · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-180, built 1964 · all PA-28-180s on the register
Registration
N7635W · registry record · serial 28-1604
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

On September 3, 2026, at 2004 eastern daylight time, a Piper PA-28-180, N7635W, was substantially damaged when it was involved in an accident near Dallas, Georgia. The flight instructor and student pilot were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The student pilot and flight instructor reported that the purpose of the flight was to perform practice takeoffs and landings at Paulding Northwest Atlanta Airport (PUJ), Dallas, Georgia. The student pilot arrived at the airport and performed a preflight inspection of the airplane. He sampled the fuel and found no contaminants, then checked its quantity with a fuel stick. He also checked the engine oil quantity and reported there were 6 quarts indicated on the oil dipstick. The flight instructor stated that he also checked the fuel and oil on the airplane and noted that there was nothing abnormal with the airplane. They then started the airplane and taxied to runway 13 for departure from PUJ. The student and flight instructor both stated that before departure, they performed an engine runup and did not notice anything abnormal. After departure they performed a series of uneventful touch-and-go landings at PUJ. During the accident touch-and-go, on initial climb the engine “cut out.” The flight instructor reported the airplane’s nose pitched down and the engine rpm abruptly dropped, but the propeller continued rotating. The student pilot reported that the flight instructor took control of the airplane and intended to land on a nearby road. Unable to reach that road, the flight instructor performed a forced landing in a densely wooded area. Preliminary review of ADS-B data showed that shortly after crossing the departure end of runway 13, and about 175 ft above ground level, the airplane turned left to the northeast. The airplane stopped climbing, continued to the northeast toward a road, and began descending. Just south of the road, the airplane turned east. Shortly thereafter ADS-B data showed no additional movement of the airplane. An on-scene examination by an FAA inspector found the airplane fuselage laying on its right side, with substantial damage, and both wings separated and suspended in trees. The airplane was equipped with avionics that were capable of recording flight data. They were recovered and sent to the NTSB Vehicle Recorders Laboratory for data download. The airplane’s most recent 100-hour inspection occurred on September 1, 2026. The accident flight was the fifth flight after that inspection. The wreckage was recovered and retained for further examination.

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 initial climb defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing
  3. Off-field or emergency landing during landing

The aircraft

  • Last inspection: 100-hour inspection, September 1, 2026
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Operator: Dependable Aviation

The flight

  • Departed from: PUJ Dallas GA

Weather at the time

  • Light: dusk
  • Wind: from 060° at 2 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 7,000 ft
  • Temperature: 88°F (31°C), dew point 73°F (23°C)
  • Altimeter: 30.02 inHg
  • Observation at 8:00 pm from PUJ, 1 miles away

Weather report (METAR): METAR KPUJ 032355Z AUTO 06002KT 10SM FEW070 31/23 A3002 RMK AO2 10355 20307

Injuries

FatalSeriousMinorNone
Flig2

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA26LA328.