FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA291 · American Champion Aircraft 8GCBC

1 Sept 2024 · Meeteetse, WY, United States

American Champion Aircraft 8GCBC · Accident: loss of engine power (partial) en route

From Yellowstone Regional Airport (COD) to an unrecorded destination

Report a problem

Event

NTSB case
WPR24FA291
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
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

American Champion Aircraft 8GCBC

Aircraft type
American Champion 8
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
N23BD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Yellowstone Regional Airport (COD), Cody, WYTo not recorded
Aircraft age
About 15 years (built 2009)
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
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 engine power (partial)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft power plant

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 reported that the purpose of the flight was to fly to a predetermined location in a nearby national forest, locate the passenger’s relatives on the ground, and spread the ashes of the passenger’s recently deceased family member. After arriving at the location, they observed the family members on the ground, circled, and spread the ashes. After releasing the ashes, the pilot leveled the airplane and applied engine power. He stated that the airplane “reached an altitude where it could not climb” and that the airspeed was near stall speed. He did not recall the airplane’s altitude at the time it stopped climbing, and reported that due to his injuries, he did not recall any of the subsequent events of the flight.

ADS-B flight track data showed that the airplane departed the airport and flew in a southerly direction toward the national forest. The data depicted a series of heading and altitude changes that were consistent with the family member’s statement. The airplane then departed to the southwest along a valley toward an area of rising terrain. The airplane began to climb from about 8,550 ft mean sea level (msl) with a corresponding decrease in groundspeed until flight track data ended in the vicinity of the accident site. The airplane’s last recorded altitude and groundspeed was 9,625 ft msl and 63 knots, respectively.

A pilot-rated witness did not observe the accident sequence, but did hear a sputtering engine followed by the sound of the accident airplane impacting terrain with a “loud bang.” He then observed black smoke emanating from a group of trees about 3/4 mile from his location. The airplane impacted mountainous terrain along the southern edge of a valley at an elevation of 9,850 ft mean sea level. All major structural components of the airplane were located near the main wreckage. The airplane was mostly consumed by post impact fire. The engine remained attached to the engine mount and fuselage. Thermal damage was observed throughout the engine from post impact fire. Disassembly of the engine revealed a slight bend on the crank shaft about mid span, consistent with impact damage.

Even though the witness report of a sputtering engine could not be corroborated due to the extensive thermal damage from the post-crash fire, ADS-B data indicated that the airplane continued to climb until the collision with rising terrain. Although the airplane’s climb performance could not be assessed, the airplane’s controlled flight into terrain was consistent with the pilot’s decision to continue the flight with the airplane approaching its maximum gross weight at a low altitude in a high-elevation, high-density-altitude environment.

Probable cause

The pilot’s decision to continue the flight over rising terrain at a low altitude in a high-elevation, high-density-altitude environment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA291
Event ID
20240901195035
Case number
WPR24FA291
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, coordinates, cause areas. 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: 248ca306feaa1f1d3c2fcb19a3fb7bcd820fe36ea0b9fac44ef28e8fee9df0e3; retrieved 2026-09-15T08:57:20.936Z.