Stack (Holding Pattern at Multiple Altitudes) – Aviation Operations

1. Introduction to the Aviation Stack

A stack in aviation is a vertically organized sequence of aircraft, each flying the same holding pattern but at a distinct, ATC-assigned altitude above a navigational fix. This configuration is essential for managing large volumes of inbound traffic, weather-related delays, or operational constraints at busy airports. By keeping aircraft in a precise vertical and lateral structure, controllers maintain safe separation, orderly sequencing, and efficient absorption of arrival delays.

Stacks are most commonly centered on a VOR, NDB, or RNAV waypoint, called the holding fix, and leverage both vertical and lateral airspace. Unlike extended vectoring, stacks confine holding to a small area, minimize fuel burn, and simplify sequencing, especially during peak periods or when approaches are unavailable. They are a key element of modern terminal airspace management.

2. The Holding Pattern: Building Block of the Stack

A holding pattern is a racetrack-shaped flight path anchored at a specific fix. Each aircraft in the stack flies this pattern at its assigned altitude. The standard pattern consists of:

• Two straight legs (inbound and outbound)
• 180-degree standard-rate turns connecting the legs
• Timed or distance-based inbound legs (typically 1 minute at or below 14,000 ft, 1.5 minutes above)

Holding patterns absorb delays, sequence arrivals, and provide a safe buffer during weather or congestion. They are depicted on approach charts and governed by strict speed limits, which vary with altitude, as defined by ICAO and the FAA.

3. The Holding Fix: Anchor of the Stack

The holding fix is the precise point around which the stack is organized. It is usually defined by:

• A VOR, NDB, or DME station
• An intersection of radials or bearings
• A GPS/RNAV waypoint

This fix must be easily identifiable and well-placed within protected airspace, free of conflicting routes or obstacles. The fix orientation, leg length, and turn direction are communicated in the holding clearance and are crucial for maintaining stack integrity and safety.

4. Vertical Separation: The Foundation of Stack Safety

Vertical separation between aircraft is mandatory within a stack. Standard minimums are:

• 1,000 feet below FL290 (Flight Level 290)
• 2,000 feet at or above FL290 (unless in RVSM airspace, then 1,000 feet up to FL410)

Controllers strictly enforce these separations, only clearing an aircraft to a lower altitude when it is vacated. Altitude compliance is monitored with radar and transponder data, ensuring that the entire stack remains safely separated at all times.

5. EFC Time: Predictability and Lost Communications

EFC (Expect Further Clearance) time is a key component of the holding clearance. It tells pilots when they can expect further instructions to leave the hold. If a communication failure occurs, the EFC time becomes the authorized time to depart the hold and proceed as cleared. This provides predictability and ensures compliance with international lost-communications procedures.

6. Protected Airspace: Safety Buffer for the Stack

The protected airspace around a stack encompasses all levels of the holding pattern, vertically and laterally. Its dimensions are defined by ICAO Doc 8168 and national rules, accounting for:

• Aircraft speed and performance
• Navigation accuracy and system tolerances
• Wind drift and turn radius
• Obstacle clearance

Controllers ensure that all aircraft remain within the protected airspace of their assigned stack, and the design of the area prevents conflicts with adjacent traffic or airspace users.

7. FIFO System: Fair and Orderly Sequencing

Stacks operate on a FIFO (First-In, First-Out) basis. Aircraft are sequenced in the order they arrive at the holding fix. The first aircraft gets the lowest altitude and is cleared first for approach or further routing. As each aircraft leaves, those above descend to the next available level, maintaining sequence and fairness. Exceptions are made only for emergencies or ATC priorities.

8. Multi-Stack and Linked Stack Management

In complex airspace or at major hubs, controllers may operate multiple stacks at different fixes or use linked stacks to coordinate en-route and terminal delays. This spreads holding demand, segregates traffic by runway or arrival stream, and allows for more strategic flow management. Upstream stacks hold aircraft farther from the airport, releasing them as space becomes available in the terminal stack.

9. ATC Procedures: Issuing and Managing Stack Clearances

A standard stack holding clearance includes:

1. Direction from the fix (e.g., “Hold north of the ABC VOR”)
2. Name of the holding fix
3. Radial/course/bearing/route
4. Leg length or time
5. Turn direction (standard right, left if specified)
6. Assigned altitude
7. EFC time

Controllers continuously monitor aircraft in the stack, verify compliance, and only clear descents when lower levels are vacated. Modern radar and automation systems support stack visualization, helping controllers efficiently sequence multiple aircraft and maintain safety.

10. Pilot Responsibilities in the Stack

Pilots assigned a stack level must:

• Read back and confirm the holding clearance
• Tune and identify the holding fix
• Determine and execute the correct entry procedure (direct, parallel, teardrop)
• Precisely fly the pattern and maintain assigned altitude and speed
• Report entering and leaving the hold as required
• Remain alert for further ATC instructions
• Follow lost-communications procedures using the EFC time if necessary

Modern avionics and RNAV/FMS systems assist with pattern accuracy, but manual vigilance and communication remain essential.

11. Radar Identification and Visualization

Controllers use radar and surveillance systems to track aircraft within a stack, displaying unique transponder codes, altitude, and position. Multiple aircraft may appear over the same fix but are distinguished by altitude. Automation tools offset data blocks and highlight stack occupancy, reducing clutter and aiding rapid decision-making.

12. Common Operational Use Cases

Arrival Sequencing at Major Hubs

At airports like Heathrow, Frankfurt, and JFK, stacks absorb excess arrivals during peak periods. Aircraft are sequenced in the stack and released for approach as runway capacity allows.

Weather Delays and Runway Closures

During adverse weather or closures, inbound aircraft are held in stacks until conditions permit safe approach and landing.

Upstream Delay Management

Controllers may establish stacks far from the airport to hold traffic before terminal airspace saturates, smoothing arrival peaks.

Emergency and Non-Routine Scenarios

Stacks provide flexibility for integrating missed approaches, handling emergencies, or accommodating special needs—ATC can adjust levels, separation, or sequencing as required.

13. Regulatory Framework

Stack and holding pattern procedures are standardized by:

• ICAO Doc 4444 (PANS-ATM): Defines stack management, separation, and controller procedures
• ICAO Doc 8168 (PANS-OPS): Specifies protected airspace and obstacle clearance
• FAA AIM Section 5-3-7: US-specific holding procedures and speed limits
• National AIPs: Local variations and published stack locations

Adherence ensures international consistency, safety, and interoperability.

14. Benefits and Limitations

Benefits

Limitations

15. Conclusion: Why Stacks Matter

The stack is a vital air traffic management tool, enabling ATC to maintain safe, orderly, and efficient sequencing of inbound aircraft during periods of congestion, weather disruption, or operational constraint. By leveraging vertical airspace, stacks keep arrivals flowing, minimize risk, and support the complex demands of modern terminal environments. Advanced procedures, automation, and international regulation ensure stacks remain a cornerstone of aviation safety and efficiency.