WPR25FA268

NTSB accident investigation · Cessna 172M · Fort Morgan, CO · August 31, 2025

Accident · FatalClass 3 · FieldPreliminary report
Date
August 31, 2025, 10:40 local (16:40 UTC)
Place
Fort Morgan, CO · Runway 14 at FMM
Injuries
1 fatal, 1 serious, 2 minor
Phase of flight
Approach
Aircraft
N61657Cessna 172MN330ANExtra Flugzeugproduktions-Und EA 300/LC
Defining events
Approach-VFR pattern final: Midair collisionApproach-VFR pattern final: Midair collision
Weather
Visual (VMC) · Day
Status
Investigation ongoing
Investigation class
Class 3
NTSB office
Western Pacific Region
Parties
FAA Denver FSDO
Case key
200906

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Preliminary report

What NTSB knew early in the investigation. It may change in the final report.

On August 31, 2025, about 1040 mountain daylight time, a Cessna 172M, N61657, and an Extra Flugzeugproduktions-UND EA 300/LC, N330AN, were both destroyed when they collided midair near Fort Morgan, Colorado. The pilot and safety pilot of the Cessna received minor injuries. The pilot of the Extra 300 was seriously injured, and the safety pilot of the Extra 300 was fatally injured. Both airplanes were operated as Title 14 Code of Federal Regulations Part 91 personal flights. According to the pilot of the Cessna, he was conducting instrument flight training with the assistance of a safety pilot. They were performing the RNAV GPS approach to runway 14 at Fort Morgan Municipal Airport (FMM) Fort Morgan, Colorado, while in visual flight rules (VFR) conditions. The pilot had made multiple radio calls on the common traffic advisory frequency (CTAF) to notify the FMM traffic of his arrival and was aware of aerobatic flights occurring at the airport. He recalled hearing two airplanes in the traffic pattern and understood that one may have landed. The pilot then continued the instrument approach to the decision altitude of 4,845 ft mean sea level, or about 250 ft above ground level (agl), then removed his view limiting device. He identified the runway and continued the approach visually. The pilot estimated that they were over the threshold when he heard a bang and felt a forward and downward acceleration. After the impact the two pilots immediately exited the airplane. According to the pilot of the Extra 300, he was competing in an aerobatic competition over the airport and completed his sequence. He exited the box and maneuvered to enter the traffic pattern at the traffic pattern altitude. He made multiple radio calls stating his intention to land on runway 14. He heard a previous competitor on the CTAF who would be landing before him, but no one else. While on the downwind leg, he entered a continuous left descending turn to the runway. He was on final approach and about ready to begin the flare when the Cessna appeared underneath the nose of the Extra 300. The impact happened quickly afterwards and there was no time for maneuvering or go around. According to a competition judge, located about 1 mile south of the approach end of runway 14, he was observing the Extra 300 and saw both airplanes nearing the runway. He noticed that the Cessna was in front and below the Extra 300 and estimated that the Cessna was at a low altitude of about 10-15 ft agl, while the Extra 300 was about 15-20 ft agl. He saw the two airplanes collide and fall onto the runway. He immediately notified the chief judge who then called 911. Both airplanes came to rest inverted, alongside each other, and off the right side of runway 14. A line of debris, from both airplanes, extended from the wreckage about 500 ft northwest. The left wing of the Cessna separated from the airplane at the root and was located about 100 ft north of the main wreckage. Both the left horizontal stabilizerand left elevator separated from the empennage. The left elevator exhibited multiple spanwise cuts, consistent with impacts from a sharp object. The wood and composite material propeller of the Extra 300 fractured into multiple pieces and was scattered throughout the debris field. The pilots of the Cessna exited their airplane and saw the pilot of the Extra 300 was out of his airplane and calling for assistance. According to the pilot of the Extra 300, he attempted to extricate the safety pilot until help arrived. Heat from a postaccident fire precluded rescue the effort. The airplanes were recovered to a secure facility for further examinations.

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

N61657 · Cessna 172M

Midair collisionApproach-VFR pattern finalCessna 172M: 5 casesAll aircraft: 196 casesDefining event

N330AN · Extra Flugzeugproduktions-Und EA 300/LC

Aircraft · 2

Registration
N61657
Reported as
Cessna 172M
Category
Airplane
Serial number
17264706
Built
1975
Damage
Destroyed
Fire
On-Ground
Flight
Personal · Part 91
Operator
Bell Ornithopters Flying Club Inc
Registered owner
Bell Ornithopters Flying Club Inc
Airworthiness certificate
Standard, Normal
Departed
BJC · Denver, CO
Destination
Same as departure
Flight plan
IFR
Airport
FMM · Fort Morgan Muni, runway 14, 5,731 × 74 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Registration
N330AN
Reported as
Extra Flugzeugproduktions-Und EA 300/LC
Category
Airplane
Serial number
LC051
Built
2015
Damage
Destroyed
Fire
On-Ground
Flight
Personal · Part 91
Registered owner
333an LLC
Airworthiness certificate
Standard, Aerobatic
Destination
Same as departure

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Weather

Conditions
Visual (VMC) · Day
Visibility
10 statute miles
Lowest ceiling
None
Temperature
70 °F, dew point 54 °F
Altimeter
30.31 inHg
Observed at
KFMM, 1 nm away
METAR
KFMM 311635Z AUTO VRB05KT 10SM CLR 21/12 A3031 RMK AO2

FAA reports on this event · 2

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.