WPR25FA268 · Cessna 172M
Bell Ornithopters Flying Club Cessna 172M and Extra Flugzeugproduktions-UND EA 300/LC · Accident: midair collision on approach
Event
- NTSB case
- WPR25FA268
- 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
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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
Aircraft 1 · Cessna 172M
- Aircraft type
- Cessna 172
- 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
- N61657
- Operator
- Bell Ornithopters Flying Club
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), Denver, COTo not recorded
- Aircraft age
- About 50 years (built 1975)
- 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
- Approach · VFR pattern final
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Extra Flugzeugproduktions-UND EA 300/LC
- Aircraft type
- Extra Flugzeugproduktions Und EA-300
- 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
- N330AN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 10 years (built 2015)
- 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
- Approach · VFR pattern final
- 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
- Midair collision
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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 stabilizer and 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.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR25FA268
- Event ID
- 20250831200906
- Case number
- WPR25FA268
- 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. 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: 866af24ff30cd756049454258d6bb539572bc38ea4ab75087d4da65220b8e819; retrieved 2026-09-13T18:12:30.763Z.