Case Study: Denver International Airport (1990) — When Project Scheduling Failed

Executive Summary

Denver International Airport’s automated baggage handling system became one of the most cited project failure cases in aviation construction and technology integration. The system was intended to move baggage faster than conventional methods and support the airport’s operations, but mechanical, software, testing, phasing, and stakeholder-coordination problems delayed the airport’s opening and forced Denver to build an alternative conventional baggage system. The U.S. GAO reported that the airport was originally scheduled to open in October 1993, but baggage system problems caused repeated postponements

Category	Fact
Original airport opening target	October 1993
Actual opening impact	Multiple postponements; commonly cited as 16 months late
Automated baggage contract	$193 million with BAE
Delay cost estimate by GAO	Up to about $360 million by Feb. 1995
Alternative baggage system	Estimated at about $51 million
Automated system modifications	Estimated at about $35 million
Long-term outcome	System never met original vision; United abandoned it in 2005

Project Scope

DIA planned a highly automated baggage system capable of moving bags from check-in to aircraft within about 20 minutes. GAO reported that the system was considered necessary because the airport was large and conventional tug-and-cart systems were expected to be less efficient.

GAO reported that the system was considered necessary because the airport was large and conventional tug-and-cart systems were expected to be less efficient.

What Went Wrong

Cost and Schedule Impact

GAO estimated that total delay-related costs could reach about $360 million by February 1995, including operating deficits, lost income, alternative baggage system costs, modifications to the automated system, and bond-related fees.

Other project-management summaries commonly cite the baggage system as going 16 months late and about $560 million over budget

Failure Analysis

The Denver case was not simply a technology failure. It was a planning, sequencing, and project-controls failure. The schedule did not adequately reflect the true complexity of the system. Testing was not given enough time. Stakeholder requirements kept evolving. The team eventually had to build a conventional backup system because the automated system could not be reliably commissioned in time. GAO also noted that the airport could not open until an operating baggage system had been successfully tested.

Key Lessons for Aviation Projects

1. Schedule Realism Matters: Aggressive project deadlines must be evaluated against actual design, procurement, system integration, and commissioning requirements to ensure achievable schedules.

2. Phasing Protects Operations: Complex airport systems should be implemented in carefully planned phases to minimize operational disruptions and reduce the risks of a single, airport-wide launch.

3. Testing Is a Critical Path Activity: System testing should begin early, occur repeatedly, and reflect real-world operating conditions to identify and resolve issues before full implementation.

4. Scope Control Prevents Costly Delays: Late design changes and additional requirements must be evaluated through formal schedule and cost impact analyses to prevent delays and budget overruns.

5. Stakeholder Coordination Reduces Schedule Risk: Airlines, airport operations, security teams, tenants, and contractors must be integrated into project planning and scheduling to manage dependencies and avoid conflicts.

6. Early Recovery Planning Minimizes Impacts: Schedule risks and performance issues should be identified early, with proactive mitigation and recovery strategies implemented before delays become critical.