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

Champion 7GCBC accident near Eatonville, Washington, July 7, 2024

On July 7, 2024 at about 4:22 am local time, a 1969 Champion 7GCBC, registered N3464D, was substantially damaged in an accident during enroute (climb to cruise) near Eatonville, Washington (Swanson Fld airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s exceedance of the airplane’s critical angle of attack while maneuvering to avoid trees, which resulted in an aerodynamic stall.

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

What the record shows

Date
July 7, 2024 · about 4:22 am local time
Place
Eatonville, Washington · Swanson Fld · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Champion 7GCBC, built 1969 · all 7GCBCs on the register
Registration
N3464D · registry record · serial 168
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot planned to depart on his fourth flight of the day. Witnesses reported that the engine run-up, departure, and climbout were normal. When the airplane reached about 500 ft above ground level and was about 0.5 nautical miles (nm) south of the runway, the airplane entered an abrupt left bank, which was immediately followed by a spin before it impacted the ground in a nose-low attitude. Postaccident examination of the engine and flight controls did not reveal any preimpact mechanical anomalies. Witness reports indicated that the engine power was smooth and continuous and then ceased just before the airplane impacted trees. As the propeller damage signatures showed limited to no rotation at the time of impact, the pilot likely reduced the throttle during the descent. In addition, the gascolator sump valve was found in the open position. However, a witness did not observe any fuel leaking from the airplane during taxi or takeoff; thus, the sump valve position was likely a result of the impact. An examination of the engine controls revealed that the mixture control cable had separated at the carburetor. A metallurgical examination did not yield sufficient evidence, on its own, to determine whether the separation occurred prior to the accident. While there was evidence that the mixture cable attachment was worn and may have been slipping before the accident flight, the fracture surfaces showed overstress fracture features that could have occurred during the accident. If the fracture had occurred before the accident, it likely would have required at least one instance of aggressive use of the controls to cause the initial buckling of the control cable. However, evidence showed the pilot was able to adjust engine power during the descent, which suggests the cable failure likely occurred during the impact, and not before. The airplane’s precise fuel quantity at the time of the accident could not be determined, as the pilot also used a personal fuel trailer that did not contain any fuel records. Fuel receipts indicated that the pilot had most recently refueled the airplane at a nearby airport three months prior to the accident. Fuel performance computations showed that he likely filled the tanks to their total capacity during his last refueling, which would have left him with about 18 gallons of fuel on the day of the accident. This was sufficient to complete the estimated 30-minute scenic flight but would have placed the airplane about 40 lbs over its gross weight. The airplane was in a nose-high attitude about 10 ft above trees and approaching rising terrain when it stalled. The airplane impacted the ground after the pilot attempted to avoid the trees by entering a rapid left bank and a pitch attitude that exceeded the airplane’s critical angle of attack, which resulted in an aerodynamic stall and a loss of control.

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 control in flight during enroute (climb to cruise) defining event
  2. Aerodynamic stall/spin during enroute (climb to cruise)
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Capability exceeded
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Aircraft capability › Climb capability › Capability exceeded
  • Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; rotorcraft: unmanned (suas)
  • Flight time: 391 hours in all; 172 in this make and model; 347 as pilot in command
  • Last flight review: March 8, 2024
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: frt
  • Injury: fatal

Passenger

  • Seat: rear

The aircraft

  • Airframe total time: 1,294.4 hours
  • Last inspection: annual inspection, March 18, 2024
  • Maximum gross weight: 1,650 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-320-B2B (piston); 1,294 hours total

The flight

  • Departed from: 2W3 Eatonville WA at 4:21 am
  • Runway 16/3, 2,990 ft by 36 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 73°F (23°C), dew point 52°F (11°C)
  • Altimeter: 29.94 inHg
  • Observation at 9:15 pm from KPLU, 15 miles away

Weather report (METAR): KPLU 070415Z AUTO 00000KT 10SM CLR 23/11 A2994 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

16 documents, released by the NTSB on May 21, 2026. 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.

#DocumentWhat it is
1 Witness Statement PDF, 1 page · our copy View Download
2 Record of Conversation with Passenger's Friend PDF, 1 page · our copy View Download
3 Email Correspondence with Pilot's Wife PDF, 4 pages · our copy View Download
4 Transcribed Witness Interviews PDF, 27 pages · our copy View Download
5 Fuel Receipt PDF, 1 page · our copy View Download
6 Excerpt from Pilot Logbook PDF, 5 pages · our copy View Download
7 Excerpt from Pilot's Operating Handbook PDF, 4 pages · our copy View Download
8 NTSB Onscene and Wreckage Examination Report PDF, 7 pages · our copy View Download
9 Chart Supplement Eatonville PDF, 1 page · our copy View Download
10 Materials Laboratory Factual Report 24-065 PDF, 9 pages · our copy View Download
11 Materials Laboratory Factual Report 25-017 PDF, 6 pages · our copy View Download
12 Email Correspondence with Aca PDF, 4 pages · our copy View Download
13 Pilot FAA Toxicology Report PDF, 1 page · our copy View Download
14 Passenger FAA Toxicology Report PDF, 1 page · our copy View Download
15 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download
16 Statement of Party Representatives to NTSB Investigation PDF, 1 page · our copy View Download

The same docket at the NTSB.

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.