Case Study: Delay Caused by Weather on Minneapolis Light Rail Extension (Minnesota, 2014)

Project Overview
• Name: Minneapolis Light Rail Transit Extension
• Location: Minneapolis, Minnesota
• Year: 2014
• Project Size: $450 million
• Scope: Construction of new light rail tracks and stations
• Lead Agencies/Contractors: Metropolitan Council /

Category of the Issue, Problem, or Challenge
• Weather Impacts
• Project Delay

Summary of the Issue, Problem, or Challenge
Extended periods of severe winter weather and early spring flooding delayed earthworks and track laying activities.

Root Cause Analysis

• Unseasonably Harsh Winter: Snow and freezing conditions persisted longer than historical averages.
• Flooding in Construction Zones: Spring meltwater caused waterlogging and erosion.
• Limited Weather Contingency Planning: Project schedule did not fully incorporate weather risks.
• Equipment Limitations: Some construction equipment was not suitable for wet/frozen conditions.

Impacts Due to the Issue, Problem, or Challenge

• Delay of 6 months in earthworks and track installation.
• Increased costs for weather mitigation and equipment rentals.
• Rescheduling impacts on subsequent project phases.

Corrective Actions Taken

1. Integrated advanced weather forecasting into schedule risk management.
2. Procured all-weather construction equipment and materials.
3. Developed contingency plans for weather-related disruptions.
4. Adjusted project timelines to better reflect regional climate risks.

Lessons Learned

• Weather risk must be a core element of project planning.
• Equipment must match environmental conditions.
• Proactive contingency and mitigation plans reduce delays and costs.

Audit & Prevention: Project Control Questions to Ask on Future Projects to Help Control the Situation

• Is weather risk quantified and planned for?
• Are appropriate equipment and materials used for expected conditions?
• Are contingency plans for weather events integrated into schedules?