NTSB CAROL · Event
Event CHI04LA278
Aircraft involved
Probable cause & findings
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.
Factual narrative
On September 23, 2004, at 2345 central daylight time, a Cessna 208B (Caravan), N7392B, operated by Eagle Air Cargo, Inc. and piloted by an airline transport pilot, was substantially damaged during an in-flight collision with terrain near Gwinner-Roger Melroe Field Airport (GWR), Gwinner, North Dakota. The flight was operating under 14 CFR Part 135 on an instrument flight rules (IFR) flight plan. Night instrument meteorological conditions prevailed at GWR at the time of the accident. The pilot sustained serious injuries. The flight departed Fergus Falls Municipal Airport (FFM), Fergus Falls, Minnesota, at 2307. The intended destination was GWR. The pilot reported that the flight originated in Escanaba, Michigan. He noted that due to excessive headwinds en route and a lack of Jet-A fuel at GWR, he elected to land at FFM. After re-fueling and filing an IFR flight plan, he departed for GWR. The pilot noted that he obtained the GWR Automated Weather Observing System (AWOS) broadcast via the aircraft radio while en route. He stated the GWR AWOS 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 to Fargo. However, he was not able to contact ATC and elected to continue to GWR. The pilot reported that he flew the entire NDB approach to GWR. He 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 about 2 miles south of the city of Gwinner reported seeing lights from an airplane near the Gwinner airport. They stated that it was about 2345. 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." The aircraft impacted an open field about 1-1/2 miles south of GWR. The distance from the point of initial impact to the aircraft was approximately 450 feet. The cargo pod was separated and located in the debris path. The aircraft was upright, resting on the bottom, right side of the fuselage and the right wing tip. The right main landing gear strut was bent aft approximately 60 degrees. The outboard section of the right wing was bent upward about 20 degrees. Each wing appeared to be rotated forward approximately 10 degrees over the entire span about each wing root. The right aileron was damaged. The left horizontal stabilizer exhibited leading edge crushing. The engine remained attached to the firewall, however, the engine mount was damaged and the engine was dislocated to the right. The propeller blades were twisted. The outboard portion of one blade separated about mid-span. The separated blade was in the debris path. The cargo consisted of 64 loose castings. Each casting weighed approximately 46.75 lbs. Partition nets were installed between cargo zones 1 and 2 and between cargo zones 3 and 4. The forward net was torn from the lower anchor points and the castings were piled against the aft side of the cockpit cargo barrier. A Federal Aviation Administration inspector confirmed flight control continuity during a post-accident examination. The altimeter was set to 29.70 when observed after the accident. Weather recorded by the GWR AWOS at 0445 was: Wind from 250 degrees at 8 knots; overcast sky at 400 feet above ground level (agl); temperature and dew point were 10 degrees Celsius; and the altimeter setting was 29.70 inches of Mercury. Instrument approaches available at GWR were an NDB or global positioning system (GPS) approach to runway 34. The MDA was 1,960 feet mean sea level (MSL), which was 694 feet above field elevation. The required visibility was 1 statute mile. The airport is located about 1 mile southeast of the city of Gwinner. With the exception of the city, the area surrounding the airport is sparsely populated with several small lakes. The National Transportation Safety Board (NTSB) investigator-in-charge reviewed a tape of the communications between the accident aircraft and Minneapolis Air Route Traffic Control Center. During the aircraft's descent into GWR, the controller was unable to maintain voice contact with N7392B. The ATC approach clearance was relayed through another aircraft operating in the vicinity of GWR. The pilot who relayed the clearance reported that it was received and read back correctly. 14 CFR Part 135.225, IFR: Takeoff, approach and landing minimums, stated: "No pilot may begin an instrument approach procedure to an airport unless . . . the latest weather report issued by that weather reporting facility indicates that weather conditions are at or above the authorized landing minimums for that airport." 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_CHI04LA278.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
- arXiv 2022 · arXiv preprint
Enhanced Prediction of Three-dimensional Finite Iced Wing Separated Flow Near Stall
Icing on three-dimensional wings causes severe flow separation near stall. Standard improved delayed detached eddy simulation (IDDES) is unable to correctly predict the separating reattaching flow due…
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Analysis on the Negative Emotional, Physiological, and Cognitive Responses Elicited from of the Activation of a Stall Alarm
Failing to identify an aerodynamic stall can lead to the inability of an aircraft to sustain flight. To warn pilots of an impending or fully-developed stall, many aircraft have safety devices installe…
Browse the full corpus — academia portal ↗