Cessna 172F accident near Battle Ground, Washington, September 26, 2025
On September 26, 2025 at about 8:06 pm local time, a 1964 Cessna 172F, registered N8219U, was destroyed in an accident during maneuvering (low-alt flying) near Battle Ground, Washington (Goheen airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
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 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 26, 2025 · about 8:06 pm local time
- Place
- Battle Ground, Washington · Goheen · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172F, built 1964 · all 172Fs on the register
- Registration
- N8219U · registry record · serial 17252119
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On September 26, 2025, about 1306, Pacific daylight time a Cessna 172F, N8219U, was destroyed when it was involved in an accident near Battle Ground, Washington. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Preliminary ADS-B data (see figure 1) indicated that after departure from Southwest Regional Airport, Kelso, Washington (KLS), the airplane flew southeast along the Columbia River to Goheen Airport, Battle Ground, Washington (W52) which is at a field elevation of 292 ft mean sea level (msl). ADS-B data showed that the airplane approached W52 from the northeast at an altitude of 1,800 ft msl on an approximate 45° angle to the runway. At 1300:30, as the airplane was about 700 ft east of the approach end of runway 15, a left turn was initiated to a southerly heading, parallel to the runway, at an altitude of about 800 ft msl. The airplane’s flight track remained parallel to the runway until a left turn was initiated to the crosswind leg of the airport traffic pattern at 1300:55. The airplane continued a left turn to the downwind leg of the airport traffic pattern and climbed to 1,400 ft msl, before it began a descending left turn to the base leg of the traffic pattern at about 1302:05. The airplane continued the descending left turn, onto final for runway 15. ADS-B contact was lost at 1303:27, as the airplane was about 300 ft msl, and 642 north of the approach end of runway 15. Video surveillance footage showed the airplane cross the runway threshold about 10 ft above ground level, perform a touch and go on the last 1/3rd of the runway at 1303:43. The video showed that after touchdown, the airplane began a shallow climb. ADS-B contact was reestablished at 1304:09, when the airplane was about 2,000 ft southeast of the departure end of runway 15, at an altitude of about 200 ft msl. The airplane remained at 200 ft throughout the turn from crosswind to the downwind leg of the airport traffic pattern. ADS-B data showed that at 1304:44, the airplane’s altitude was 600 ft msl, abeam the approach end of runway 15, on the downwind leg. The airplane continued to climb to 900 ft msl, and initiated a left turn, onto the base leg, and continued to the west, past the extended runway centerline at 1305:36, while maintaining an altitude of 900 ft msl. At 1304:42, the airplane began a descending left turn, to a heading about 15° left of runway heading. The last recorded ADS-B data point was at 1306:12, at an altitude of about 300 ft msl, and about 122 ft northwest of the approach end of runway 15. Figure 1: ADS-B flight path. A witness that was situated midfield on the east side of the runway reported that the airplane sounded normal, like it was making full power. She saw the airplane conduct a touch and go landing, then depart while it remained within the traffic pattern. She could hear the airplane on the downwind leg of the traffic pattern and noted that while it was on final, it was coming in fast. Instead of landing, the airplane banked right and impacted trees. Examination of the accident site revealed that the initial point of impact (IPOI) was identified by witness marks on a large tree about 75 ft above the base (see figure 2). Below the IPOI, was a 4 ft section of the outboard right wing, aileron, and wing tip that came to rest on the ground near the base of the tree. The outboard section of the right wing showed a concave depression consistent with the shape and diameter of the IPOI. Aileron control cables were entangled with the tree branches. The propeller was separated from the crankshaft and came to rest about 22 ft southwest of the IOPC. The propeller blades exhibited S-bending, leading edge polishing, and embedded wood fibers. The main wreckage came to rest inverted, about 138 ft south of the IPOI and consisted of the inboard right wing and flap, the entire left wing, empennage, cabin, and engine (see figure 2). The cabin and cockpit section sustained thermal damage, that consumed both inboard wings and extended from the engine compartment to the baggage compartment where the auxiliary fuel cell was located. Flight control continuity was established from the cockpit controls to all primary flight control surfaces. The wreckage was recovered to a secure location for further examination. Figure 2: Aerial view of initial point of impact and main wreckage (Courtesy of airport manager)
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
- Collision with terrain or object (not controlled flight into terrain) during maneuvering (low-alt flying) defining event
- Landing area overshoot during landing
- Collision with terrain or object (not controlled flight into terrain) during landing
The aircraft
- Airframe total time: 3,903.8 hours
- Last inspection: annual inspection, August 6, 2025; 0.7 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Fire on the ground
The flight
- Departed from: KLS Kelso WA at 7:18 pm
- Flight plan: none
- Runway 15/3, 2,565 ft by 50 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 64°F (18°C), dew point 48°F (9°C)
- Altimeter: 30.19 inHg
- Observation at 12:53 pm from KSPB, 12 miles away
Weather report (METAR): METAR KSPB 261953Z AUTO VRB03KT 10SM CLR 18/09 A3019 RMK AO2 SLP223 T01830094=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
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 documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text 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 WPR25FA294.
