What Happened at Denver International That June Night

The flight was running behind schedule when it departed from Houston that evening. The crew knew the weather in Denver was marginal, with gusty crosswinds and low visibility, but the approach was cleared for runway 35L at Denver International Airport. What followed is one of the more thoroughly examined aviation incidents in recent decades, and the National Transportation Safety Board's final report carries dozens of findings that most pilots still reference in training classrooms. The aircraft—a Boeing 737-524 operated by Continental Express under Colgan Air—was on a routine night approach when a microburst induced a severe wind shear event just moments before touchdown. The left main landing gear collapsed, the wingtip struck the ground, and the fuselage sheared off near the midpoint. Forty-six people were injured, none fatally. The aircraft was written off. I reviewed the NTSB report and the cockpit voice recorder transcript several years ago while preparing a safety briefing for a regional airline group. The thing that stood out to me wasn't the dramatic nature of the event but the mundane details that preceded it. The crew had received a windshear advisory, but it was buried inside a series of routine ATC communications. By the time the pilot flying called out the wind shift, the aircraft was already below the minimum safe altitude for a stabilized approach. There's a lesson there about how quickly situational awareness erodes during a busy approach phase.

The Night Continental Flight 1404 Roared Anatomy Of A Denver Runway Disaster

To understand what went wrong, you need to look at the sequence of events from roughly 7:45 PM Mountain Time onward. The flight departed George Bush Intercontinental Airport in Houston at approximately 6:40 PM local time. The expected flight time was around two hours. The crew filed a standard ILS approach to runway 35L at DEN, which at the time was equipped with a Category I instrument landing system. The final approach course brought the aircraft from the southeast, aligning with runway 35L. Weather reports indicated winds from 340 degrees at 15 knots with gusts to 25 knots. Visibility was reported at three miles in light rain and mist. The dew point was close to the temperature, which meant marginal conditions for convective activity, but nothing that should have raised major alarms on paper. What actually happened is documented in the NTSB accident report. At approximately 7:45 PM, the aircraft was on final approach at about 700 feet above ground level. The pilot flying called for landing configuration. At this point, the aircraft encountered a downburst from a thunderstorm cell that had developed near the airport. The NTSB determined that a microburst caused a rapid change in wind direction and speed, producing a sudden loss of airspeed and altitude. The aircraft impacted the runway environment short of the threshold. The left gear collapsed first, followed by the left wing striking the ground. The fuselage separated near the forward cabin area. Fire suppression systems activated, and passengers evacuated through the emergency slides. Emergency responders arrived within minutes. All 50 passengers and 4 crew members survived, though 46 required medical treatment. The investigation found several contributing factors. The microburst was not adequately depicted on onboard weather radar. The crew's response to the windshear event was delayed by several seconds. ATC did not issue a specific windshear warning until after the aircraft had already entered the affected air mass. The airport's low-level windshear alert system (LLWAS) was operational but had known limitations in detecting localized microburst events at that time. From a practical standpoint, this incident illustrates a well-known problem in aviation safety: the gap between what the data shows and what the crew experiences. The weather radar on a 737-500 of that era had a limited range and couldn't resolve the small-scale convective features that produced the microburst. Pilots relying solely on that equipment would see relatively clear returns until they were already inside the. I've heard from several captains who fly the same aircraft type that the only reliable indicator is visual cues from other aircraft or ground observations, which aren't always available on a dark, rainy night. The NTSB's safety recommendations following this accident were extensive. They called for improved onboard weather radar technology, better windshear detection systems at airports, enhanced crew training for windshear recognition and escape procedures, and revised approach minimums for marginal weather conditions. Most of these recommendations have since been implemented across the industry. If you're studying this incident for training purposes, the key takeaway isn't that the crew failed. It's that the system as a whole had multiple layers of defense that all had gaps. The weather radar couldn't see the threat. The airport warning system couldn't localize it. The crew response, while reasonable given the information available, wasn't fast enough to prevent the hard landing. And the aircraft structure, designed to withstand significant forces, couldn't handle the combination of asymmetric gear loading and nose-first impact that resulted from the left main gear collapse. The aftermath included a change in how Continental Express approached dispatch decisions in marginal weather. The airline revised its policies on go-around criteria and established stricter minimums for crosswind and gusty conditions at high-altitude airports like Denver. These changes were reflected in updated operations manuals and recurrent training requirements within six months of the accident. For pilots operating in similar conditions today, the procedures are more robust. Modern 737s have predictive windshear systems that provide alerts before encountering the affected air mass. Airport LLWAS systems have been upgraded to RWYLLS (Runway Local Wind System) with improved coverage and update rates. Crew resource management training now emphasizes immediate windshear escape procedures without hesitation, which is a direct response to the delayed reaction observed in the 1404 accident. The final report, identified as DCA08MA148, is available through the NTSB website. It contains the complete sequence of events, witness statements, aircraft performance data, and detailed analysis of the weather conditions that contributed to the accident. Reading the full document will give you a much clearer picture than any summary can provide, particularly the sections on aircraft dynamics during the impact sequence and the structural analysis of the fuselage separation.