Airport Terminal Construction: Coordinating the World's Most Complex Buildings

Why Terminal Coordination Is the Coordination Olympics

A typical office building coordinates mechanical, electrical, plumbing, fire protection, and structural systems. An airport terminal coordinates all of that—plus pressurized baggage conveyors, redundant security systems, pneumatic tube mail, aircraft gate power/preconditioned air pedestals, high-security networking infrastructure, emergency generators in parallel with utility feeders, and specialized HVAC zones serving TSA checkpoints that require negative pressure for bio-containment. Everything must work simultaneously. Nothing can fail. And the coordination happens on compressed timelines where the design team has 12 months instead of 18 to deliver construction documents.

The plenum spaces are tighter because the terminal is pushing for height efficiency (every floor must generate revenue). The MEP systems are larger because passenger volumes demand high-capacity trunk lines. The routing is more constrained because terminals have fewer available corridors—TSA processing flows dictate where ductwork can run, and baggage system geometry locks electrical and plumbing into specific paths months before MEP coordination begins. The result: terminal projects face MEP clash rates 2.5× higher than commercial office buildings.

Terminal Systems That Don't Exist in Office Buildings

Before coordinating mechanical, electrical, and plumbing in a terminal, the team must understand the systems that are unique to airport operations. These systems have non-negotiable routing requirements and inflexible timelines.

• Baggage handling systems (BHS): Conveyor belts run on fixed paths—typically in mechanical spaces below passenger levels or in dedicated carrier lines through the terminal. The routing is set in stone before terminal MEP layout begins. All mechanical, electrical, and plumbing must route around the BHS, which often claims the most direct path through the building.
• Pressurized aircraft gate power and preconditioned air (PCA) pedestals: These are located at aircraft parking gates and must connect to centralized utility plants that may be hundreds of feet away. The routing must be coordinated with structural columns, passenger boarding bridges, and ground equipment roadways—all fixed by the gate layout.
• Security checkpoint HVAC: TSA screening areas require negative pressurization and multiple air changes per hour. The ductwork for TSA zones must be separate from public concourse ductwork and cannot share return paths. This doubles the ductwork in the departure level and creates permanent coordination zones that other systems cannot penetrate.
• Aircraft fuel hydrant systems: Underground fuel lines run on fixed routes dictated by airfield operations and ground vehicle movement. Utility tunnels below the terminal must accommodate these lines with minimal clearance to other underground infrastructure.
• Emergency generator plants and fuel storage: Large redundant power systems require dedicated mechanical rooms, fuel oil storage with secondary containment, and exhaust paths that cannot conflict with passenger areas or air intakes.

The Sequence That Works for Terminals

Successful terminal coordination follows a rigid precedence order. Systems that are designed first have priority in routing. Everything else fits around them.

• 1. Baggage system path: The conveyor routing is locked at 30% design. All subsequent MEP coordination assumes this path is untouchable.
• 2. TSA checkpoint zones and HVAC requirements: Once TSA processing layouts are finalized, the ductwork for negative pressurization and air supply/exhaust is routed. This typically happens at 60% design.
• 3. Gate pedestals and their utility connections: PCA, power, and potable water lines to each gate position are routed next. These have geographic constraints that cannot be violated.
• 4. Main utility distribution: Electrical panels, chiller loops, boiler plants, and primary ductwork distribution trunks are coordinated with the fixed systems from steps 1–3.
• 5. Secondary and branch distribution: Smaller ductwork, branch piping, conduit runs, and low-voltage cabling fill remaining space using a zone-based coordination approach.

The problem: most coordination software and processes assume all systems start equal and are layered hierarchically. Terminal projects need a constraint-driven approach where fixed systems are locked in first, and the MEP team works within the boundaries they create. Advanced clash detection tools that understand system precedence can flag violations early—but only if the design team has explicitly marked which systems are immovable.

Common Coordination Failures in Terminal Design

Even with experienced teams, certain patterns emerge repeatedly on terminal projects:

• Incomplete BHS routing during permit phase: Baggage system detailed design lags terminal design by 2–3 months. MEP coordination happens at 80% documents before the final BHS path is confirmed. Changes to BHS routing after permit approval ripple through all other systems.
• TSA requirement changes late in design: TSA checkpoint processing widths or security requirements sometimes change based on operational reviews that occur in the 90% design stage. These changes compress the plenum further and force MEP re-coordination.
• Redundant system routing conflicts: Dual electrical feeds or parallel HVAC circuits may be routed to opposite sides of the terminal for redundancy, but the routing is not coordinated until all systems are drawn. Late discovery of conflicts in the backup systems means duplicating work.
• Utility tunnel depth violations: Fuel lines, chilled water loops, and electrical conduits all run in underground utility tunnels. Elevation coordination in the tunnel is often deferred until equipment selections are finalized, causing changes to already-coordinated MEP zones above floor.
• Commissioning access forgotten: Above-ceiling coordination sometimes eliminates access panels for VAV boxes or fire dampers in TSA areas, forcing field rework during final testing.

Lessons That Transfer to Every Project

Terminal coordination problems are extreme, but the principles apply to any complex project. The core lesson: systems with inflexible routing requirements must be drawn first, locked in place, and protected from later changes. Every other system routes around them.

On a hospital, ICU HVAC has inflexible requirements (code-driven air changes, isolation rooms) and should be routed before general circulation ductwork. On a data center, the cooling systems are the skeleton, and everything else feeds around them. On mid-rise wood-frame projects, fire-rated assemblies dictate where MEP cannot pass, so they must be drawn and understood before coordination begins.

The difference between a terminal and a typical commercial building is only one of scale and complexity. The coordination method is the same: identify immovable systems, lock them in, route everything else around them, and verify coordination early and often.

The Takeaway

Airport terminal projects expose coordination principles that apply everywhere. The terminals that deliver on time and on budget are those where the design team identifies which systems are fixed, locks them in early, and coordinates everything else around them. The terminals that slip are those that try to optimize all systems simultaneously, discovering conflicts too late to resolve them without redesign and delays.