FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Eagle Air Cargo Cessna 208B accident

23 Sept 2004 · Gwinner, ND, United States

Cessna 208B · Accident: in flight collision with terrain/water on approach

From Fergus Falls Municipal Airport - Einar Mickelson Field (FFM) to Gwinner Roger Melroe Field (GWR)

Report a problem

Event

NTSB case
CHI04LA278
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
0 · 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
Charter & commuter
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

Cessna 208B

Aircraft type
Cessna 208
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
N7392B
Onboard fatalities
Unknown
Route
From Fergus Falls Municipal Airport - Einar Mickelson Field (FFM), Fergus Falls, MNTo Gwinner Roger Melroe Field (GWR), Gwinner, ND
Aircraft age
Not recorded
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 135: Air Taxi & Commuter
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 · circling (IFR)
First occurrenceThe 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
In flight collision with terrain/water
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

  • Pilot in command › Altitude, not maintained

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

NTSB narrative

The airplane was substantially damaged when it impacted an open field about 1-1/2 miles south of the destination airport. The pilot had executed an instrument approach and was circling to land when the accident occurred. Night instrument meteorological conditions prevailed at the time. The area south and east of the airport was sparsely populated. The pilot reported that he obtained the Automated Weather Observing System (AWOS) broadcast for the destination via the aircraft radio while en route. He stated the reported visibility was above that required for the Non-Directional Beacon (NDB) approach, however, the ceiling was below the minimum descent altitude (MDA). He reported that he attempted to contact air traffic control (ATC) with the intention of diverting. He was not able to contact ATC and elected to continue to the destination. The pilot reported that he flew the entire NDB approach and stated: "When I arrived at the MDA, I saw the runway, directly below and a little to my left. My plan, at the time, was to circle left and land." He stated after that point he had no further recollection of the events surrounding the accident. The pilot reported that there were no failures or malfunctions associated with the aircraft. Two witnesses reported seeing lights from an airplane near the airport. One recalled that the weather was "foggy and a heavy mist." The other witness stated: "When I saw the plane it was very low but I thought it was going around for the landing because it looked like the plane had its right wing higher, and I could see part of the belly of the plane, which made it look like it was banking around." Flight control continuity was confirmed during a post-accident examination. The airport AWOS recorded an overcast sky at 400 feet above ground level (agl). The MDA for the instrument approach as 694 feet above field elevation.

Probable cause

The pilot's failure to maintain altitude during the circling maneuver. Contributing factors were the pilot's improper decision to execute the approach when weather conditions were below minimums and the low light (dark night) conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA278
Event ID
20040928X01514
Case number
CHI04LA278
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2004-09-24.
  • API snapshot SHA-256: 71639bf32656377218ace7eaf89a3100015ce6bc12ac1934e999bdef3f74f5be; retrieved 2026-09-18T15:16:02.777Z.