FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA087 · Stinson 108-3

11 Jan 2026 · Gypsum, CO, United States

Stinson 108-3 · Accident: loss of engine power (partial) during landing

From McElroy Airfield (20V) to McElroy Airfield (20V)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN26LA087
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
Ongoing
Event fatalities
Unknown
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

Stinson 108-3

Aircraft type
Stinson 108
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
N6725M
Operator
Unknown
Onboard fatalities
Unknown
Route Narrative disagrees
From McElroy Airfield (20V), Gypsum, COTo McElroy Airfield (20V), Kremmling, CO
Aircraft age
About 78 years (built 1948)
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
Landing
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
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On January 11, 2026, at 1408 mountain standard time, a Stinson 108-3 airplane, N6725M, sustained substantial damage when it was involved in an accident near Gypsum, Colorado. The pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to the pilot, before the flight the airplane’s fuel system contained about 17 gallons that was evenly distributed between the left and right fuel tanks. He intended to takeoff and conduct a full stop landing at the unnamed private airstrip before continuing to Mc Elroy Airfield (20V), Kremling, Colorado.

The pilot reported that the takeoff was to the southeast and he flew a teardrop pattern to return to land toward the northwest. As he maneuvered the airplane back toward the airstrip, he selected carburetor heat on, propeller control full forward, and kept the mixture setting leaned for the high-altitude engine operation. He subsequently turned off the carburetor heat when the airplane was on final approach and the landing was assured.

The pilot increased the throttle a couple times after the airplane entered an area of sinking air associated with the canyons beneath the airplane’s flight path. He noted that these throttle responses were normal. However, during short final approach, about 25 ft above the ground, the airplane encountered additional sinking air and he “sharply” increased the throttle from near idle to an intermediate position. According to the pilot, the engine “coughed/sputtered” after he rapidly increased the throttle.

The pilot reported that due to the low altitude of the airplane and its proximity to the runway, he continued at a higher-than-normal rate of descent toward the runway. The pilot attempted to flare the airplane as it approached the runway threshold, but it “pancaked” onto the runway and slid to a stop in a nose down pitch attitude.

Based on law enforcement photos, the airplane contacted tree tops and then dispersed broken tree branches beneath the airplane’s flight path about 30 yards from where the airplane came to rest on the runway.

The airplane’s welded steel-tube fuselage and engine mount sustained substantial damage during the hard landing. Both propeller blades exhibited impact-related damage consistent with propeller rotation at impact.

A review of the airplane’s digital engine monitor data did not reveal any evidence of an engine malfunction during the 2 minute 36 second flight. However, due to the device’s 6-second recording interval there was insufficient data to confirm a loss of engine power before the hard landing and interruption of electrical power.

The airplane wreckage was recovered to a secure storage facility for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN26LA087
Event ID
20260112202283
Case number
CEN26LA087
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. 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: eff6d0cf3ea9510bf3b5983e3d460838d975ddb44390fcace14f6a865bc8b636; retrieved 2026-09-16T20:39:59.037Z.