WPR24FA226 · Champion 7GCBC
Champion 7GCBC · Accident: loss of control in flight en route
From Swanson Airport (2W3) to an unrecorded destination
Event
- NTSB case
- WPR24FA226
- 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
- Completed
- API-reported fatalities
- 2 · 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
Champion 7GCBC
- Aircraft type
- Champion 7
- 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
- N3464D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Swanson Airport (2W3), Eatonville, WATo not recorded
- Aircraft age
- About 55 years (built 1969)
- 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
- En route · climb to cruise
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The pilot’s exceedance of the airplane’s critical angle of attack while maneuvering to avoid trees, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA226
- Event ID
- 20240707194619
- Case number
- WPR24FA226
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2024-07-07.
- API snapshot SHA-256: 5d4c7b302951e67c1e748a60be4a34d006f004a64fab1979b44930205b7f784c; retrieved 2026-09-15T08:24:09.180Z.