13.07.2014 Views

Integrated Analysis of Airportal Capacity and Environmental ...

Integrated Analysis of Airportal Capacity and Environmental ...

Integrated Analysis of Airportal Capacity and Environmental ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Integrated</strong> <strong>Analysis</strong> <strong>of</strong> <strong>Airportal</strong> <strong>Capacity</strong> <strong>and</strong><br />

<strong>Environmental</strong> Constraints<br />

Shahab Hasan, Principal Investigator<br />

George Hart, Research Fellow<br />

Rosa Oseguera-Lohr,<br />

NASA Technical Monitor<br />

Presented at the JPDO Airports Working Group NextGen Airport <strong>Capacity</strong> Workshop<br />

February 17, 2009


Task Description<br />

• Objective:<br />

– Identify <strong>and</strong> rank the key factors limiting the achievement <strong>of</strong> the<br />

capacity goals <strong>of</strong> NextGen<br />

– Identify gaps in available tools for conducting system-level trade <strong>and</strong><br />

benefit studies<br />

– Results will help prioritize NASA’s research to enable NextGen<br />

• Outcomes:<br />

1. Define a set <strong>of</strong> critical airports <strong>and</strong> the most significant limitations to<br />

airport capacity at those airports<br />

2. Define the relevant environmental constraints that limit <strong>Airportal</strong><br />

capacity growth<br />

3. Catalog the available tool set for analysis <strong>and</strong> modeling, assess gaps<br />

4. Estimate the point <strong>of</strong> diminishing returns for hub capacity increases<br />

vs. shifting to metroplex operations<br />

P A G E 2


Notional Mock-up <strong>of</strong> Key Results<br />

.<br />

.<br />

.<br />

.<br />

.<br />

.<br />

.<br />

.<br />

.<br />

P A G E 3


Overview <strong>of</strong> Subtasks <strong>and</strong> Schedule<br />

1. Develop Set<br />

<strong>of</strong> Scenarios<br />

2. Develop Set <strong>of</strong><br />

Metrics<br />

3. Develop List <strong>of</strong><br />

Critical Airports<br />

4. Analyze <strong>Airportal</strong> <strong>Capacity</strong><br />

Constraints<br />

Runway<br />

Constraints<br />

5. Analyze <strong>Airportal</strong> <strong>Environmental</strong><br />

Constraints<br />

Noise<br />

Constraints<br />

Taxiway<br />

Constraints<br />

Gates<br />

Constraints<br />

Emissions<br />

Constraints<br />

7. Analyze Shift to<br />

Metroplex<br />

Operations<br />

6. Catalog <strong>and</strong> Assess Tool Set<br />

Time<br />

Feb.<br />

2008<br />

Kick<strong>of</strong>f<br />

July<br />

2008<br />

Report, Version 1<br />

Jan.<br />

2009<br />

Report, Version 2<br />

June<br />

2009<br />

Report, Version 3<br />

Dec.<br />

2009<br />

Final Report<br />

P A G E 4


Subtasks Completed<br />

• Subtask 1: Develop Set <strong>of</strong> Scenarios<br />

– 2007, 2015, <strong>and</strong> 2025 dem<strong>and</strong><br />

– <strong>Capacity</strong> per JPDO NextGen deployment schedule<br />

• Subtask 2: Develop Set <strong>of</strong> Metrics<br />

– Primary metric for this study is “projected throughput”<br />

– Recommended rich set <strong>of</strong> metrics for use by NASA <strong>Airportal</strong> project<br />

• Subtask 3: Develop Set <strong>of</strong> Critical Airports<br />

– Set <strong>of</strong> 310 airports which cover 98.6 percent <strong>of</strong> all air carrier<br />

operations <strong>and</strong> 99.8 percent <strong>of</strong> air carrier enplanements<br />

• Subtask 6: Catalog <strong>and</strong> Assess Tool Set<br />

– Final comprehensive report <strong>and</strong> database tool<br />

P A G E 5


Subtasks In Progress<br />

• Subtask 4: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints<br />

– Developed the runway capacities <strong>and</strong> have done initial constraint<br />

analysis<br />

– Completed initial gate constraint modeling <strong>and</strong> analysis<br />

– Started the detailed taxiway modeling <strong>of</strong> a few airports<br />

• Subtask 5: Analyze <strong>Airportal</strong> <strong>Environmental</strong> Constraints<br />

– 2025 fleet forecast augmented to use FAA’s Continuous Lower<br />

Energy, Emissions <strong>and</strong> Noise (CLEEN) <strong>and</strong> N+1 Subsonic Fixed<br />

Wing projections with a 2016 insertion<br />

• Subtask 7: Analyze Shift to Metroplex Operations<br />

– Started to brainstorm technical approach but have not begun analysis<br />

P A G E 6


Subtask 4.1: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Runways)<br />

Runway <strong>Capacity</strong> <strong>Analysis</strong> at 310 Critical Airports<br />

• We assume no change to the airport capacities at the smaller 200<br />

airports<br />

– Likely cost prohibitive to deploy NextGen technologies so widely<br />

• For the 110 larger airports, their capacities can be increased by<br />

– New runways<br />

– NextGen technologies<br />

• One primary airport runway configuration for each meteorological<br />

operating condition<br />

• Airport runway configurations based on analysis <strong>of</strong> FACT2 <strong>and</strong> FAA<br />

configurations, airport diagrams, capacity data, procedure charts,<br />

<strong>and</strong> knowledge from prior tasks<br />

P A G E 7


Subtask 4.1: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Runways)<br />

Projected Throughput Based on Runway <strong>Capacity</strong><br />

• Only the runway capacities are considered<br />

– There is no other constraint assumed<br />

• Capacities are allocated along the Pareto curve to give the best<br />

balance between the arrival <strong>and</strong> departure capacities<br />

• Extra dem<strong>and</strong> is removed from the schedule (trimmed) according<br />

to rules enforced by our model for dem<strong>and</strong>/capacity (D/C) ratios<br />

– The process is done for every epoch <strong>of</strong> 15 minutes<br />

• The rules for D/C ratios<br />

– Cannot exceed 1.2 for every 15-minute epoch<br />

– Cannot exceed 0.9 for every rolling hour<br />

– Same ratios as used for JPDO studies<br />

– Allows for short-term spikes but also the need for recovery<br />

– Targets a relatively high level <strong>of</strong> service (low delay)<br />

P A G E 8


Subtask 4.1: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Runways)<br />

Projected Throughput Results: Overview<br />

• Significant flight reductions (unsatisfied dem<strong>and</strong>) at the busiest<br />

hub airports<br />

• Flight reductions in later years grow at some major airports, as<br />

dem<strong>and</strong> increases at a rate faster than some <strong>of</strong> the NextGen<br />

improvements<br />

• However, flight reductions at many airports decrease or are<br />

eliminated in future years, as capacity enhancement from new<br />

runways <strong>and</strong> NextGen improvements outpace dem<strong>and</strong> growth<br />

(e.g., ORD in 2025)<br />

P A G E 9


Subtask 4.1: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Runways)<br />

Projected Throughput Results: Top 10 Airports<br />

5000<br />

The percentage = projected throughput / unconstrained throughput<br />

4500<br />

4000<br />

3500<br />

3000<br />

2500<br />

2000<br />

1500<br />

95%<br />

84%<br />

78%<br />

100%<br />

97%<br />

100%<br />

100%<br />

100%<br />

100%<br />

97%<br />

83%<br />

70%<br />

90%<br />

67%<br />

99%<br />

100%<br />

100%<br />

100%<br />

100%<br />

99%<br />

99%<br />

98%<br />

93%<br />

87%<br />

Trimmed Flights<br />

Untrimmed Flights<br />

90%<br />

91%<br />

74%<br />

87%<br />

100%<br />

100%<br />

1000<br />

500<br />

0<br />

ATL - 2007<br />

ATL - 2015<br />

ATL - 2025<br />

ORD - 2007<br />

ORD - 2015<br />

ORD - 2025<br />

DFW - 2007<br />

DFW - 2015<br />

DFW - 2025<br />

LAX - 2007<br />

LAX - 2015<br />

LAX - 2025<br />

LAS - 2007<br />

LAS - 2015<br />

LAS - 2025<br />

DEN - 2007<br />

DEN - 2015<br />

DEN - 2025<br />

IAH - 2007<br />

IAH - 2015<br />

IAH - 2025<br />

PHX - 2007<br />

PHX - 2015<br />

PHX - 2025<br />

PHL - 2007<br />

PHL - 2015<br />

PHL - 2025<br />

CLT - 2007<br />

CLT - 2015<br />

CLT - 2025<br />

P A G E 10


Subtask 4.1: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Runways)<br />

Projected Throughput Results: Comparison<br />

The percentage = projected throughput / unconstrained throughput<br />

180000<br />

160000<br />

Trimmed Flights<br />

Untrimmed Flights<br />

99%<br />

140000<br />

98%<br />

120000<br />

99%<br />

95%<br />

Operations<br />

100000<br />

80000<br />

99%<br />

97%<br />

88%<br />

60000<br />

40000<br />

98%<br />

95%<br />

20000<br />

0<br />

OEP35-2007<br />

LMI110-2007<br />

LMI310-2007<br />

OEP35-2015<br />

LMI110-2015<br />

LMI310-2015<br />

OEP35-2025<br />

LMI110-2025<br />

LMI310-2025<br />

P A G E 11


Subtask 4.2: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Taxiways)<br />

Approach to Developing Taxiway <strong>Capacity</strong> Model<br />

• Divided the airport surface into<br />

two regions: terminal area, <strong>and</strong><br />

outer taxiways<br />

• Focused on the outer taxiways;<br />

for the majority <strong>of</strong> the airports in<br />

this study, congestion in the<br />

terminal area is not a concern<br />

• Flag airports with characteristics<br />

that typically lead to terminal area<br />

congestion (narrow alleyways,<br />

aircraft pushback into taxiways,<br />

etc.) <strong>and</strong> adjust expected taxi<br />

delays appropriately<br />

P A G E 12


Subtask 4.2: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Taxiways)<br />

Approach to Developing Taxiway <strong>Capacity</strong> Model<br />

• Used <strong>of</strong>f the shelf simulation s<strong>of</strong>tware (Rockwell’s Arena)<br />

• Focused only on bottlenecks formed by active runway/taxiway<br />

interaction<br />

• Runways <strong>and</strong> runway crossings modeled as resources<br />

• Taxiing aircraft can be preempted from runway crossings by<br />

l<strong>and</strong>ing or departing (high priority) aircraft<br />

• Delays take place as aircraft wait for runway crossings to<br />

become available<br />

• Delays can be calculated by comparing high dem<strong>and</strong> taxi times<br />

to those <strong>of</strong> very low dem<strong>and</strong><br />

P A G E 13


Subtask 4.2: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Taxiways)<br />

Taxiway <strong>Capacity</strong> Model Example: PHX<br />

P A G E 14


Subtask 4.2: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Taxiways)<br />

Taxiway <strong>Capacity</strong> Model: Progress to date<br />

• Taxiway capacity models have been built for:<br />

– SAN (1 active runway without active runway crossings)<br />

– LGA (2 non-parallel active runways with active runway crossings)<br />

– PHX (2 parallel active runways with active runway crossings)<br />

– SEA (3 parallel active runways with active runway crossings)<br />

• <strong>Analysis</strong> for these models has not yet been conducted<br />

• Next up: ATL, DFW, ORD<br />

P A G E 15


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Determining Airports’ Gate <strong>Capacity</strong><br />

• An airport’s gate capacity is determined by many<br />

complex interrelated factors<br />

• No centralized source for data on gate capacity<br />

– We collected gate count data for the top 310 airports from a<br />

wide variety <strong>of</strong> sources<br />

– No data on which gates can serve which types <strong>of</strong> aircraft<br />

• The data that are available are unreliable <strong>and</strong> follow<br />

many different definitions for a “Gate”<br />

– We focused on gates with passenger bridges<br />

• Adding additional space for ground-loading aircraft is relatively easy<br />

compared with adding additional passenger bridge-equipped gates<br />

• Airlines increasingly prefer to use passenger bridges<br />

P A G E 16


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Gate <strong>Capacity</strong>: Important Assumptions<br />

• All airlines have equal access to all gates, regardless<br />

<strong>of</strong> current gate-access leasing agreements<br />

• Due to the shortage <strong>of</strong> airport-specific information, we<br />

have also assumed that all gates can service all<br />

aircraft types<br />

– This ignores aircraft spacing requirements<br />

– Unfortunately there is no information available on what types<br />

<strong>of</strong> aircraft a given gate at a given airport can accommodate<br />

– We developed a supplementary tool to track growth in the<br />

maximum required terminal frontage for each airport (more<br />

on this later)<br />

P A G E 17


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Developing the Gate <strong>Capacity</strong> Model<br />

• Basic steps <strong>of</strong> the model<br />

1. Use FAA-provided schedules to estimate the number <strong>of</strong> aircraft on<br />

the ground at the beginning <strong>of</strong> the day for each airport<br />

2. Use this reference point <strong>and</strong> the same schedules to track the<br />

number <strong>of</strong> aircraft at the gates throughout a 24 hour period<br />

3. When gate capacity is exceeded, trim arrivals (<strong>and</strong> departures)<br />

from the schedule<br />

4. Adjust the estimate for the number <strong>of</strong> aircraft on the ground at the<br />

beginning <strong>of</strong> the day to reflect schedule trimming<br />

5. Repeat steps 3 <strong>and</strong> 4 until the reduction in operations is<br />

proportional to the reduction in the number <strong>of</strong> aircraft on the ground<br />

at the beginning <strong>of</strong> the day<br />

P A G E 18


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Model Execution: Terminal Frontage Requirements<br />

• The model also calculates <strong>and</strong> compares current <strong>and</strong> future<br />

terminal frontage requirements to help identify aircraft spacing<br />

problems<br />

– We categorized aircraft according to the FAA's gate-group<br />

categorization system<br />

– Space requirements were defined as each category's maximum<br />

wingspan plus the FAA's suggested wingtip-to-wingtip gate spacing<br />

– We cycle through the arrival <strong>and</strong> departure schedules to calculate<br />

the change in the terminal frontage requirement throughout the day<br />

– We can get an estimate <strong>of</strong> each airport’s growth in this requirement<br />

by comparing the 2007, 2015, <strong>and</strong> 2025 maxima<br />

P A G E 19


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Model Execution Example: JFK Int’l Airport (JFK)<br />

Reference Point<br />

200<br />

180<br />

Aircraft at the gates throughout a 24 hour period (JFK - 2015)<br />

160<br />

Adjusted<br />

Reference Point<br />

Aircraft at Gates<br />

140<br />

120<br />

100<br />

80<br />

Gate <strong>Capacity</strong><br />

Trimmed<br />

Untrimmed<br />

Gate Limit<br />

60<br />

40<br />

Net Departures<br />

Net Arrivals<br />

20<br />

0<br />

0 3 6 9 12 15 18 21 24 27 30 33 36 39 42 45 48 51 54 57 60 63 66 69 72 75 78 81 84 87 90 93<br />

Epoch<br />

Note: Epoch 0 corresponds to 9:00 AM GMT<br />

P A G E 20


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Preliminary Results for a Sample <strong>of</strong> Large Airports<br />

1800<br />

1600<br />

92%<br />

80%<br />

Arrivals Trimmed<br />

Arrivals Accepted<br />

1400<br />

100%<br />

1200<br />

100%<br />

95%<br />

69%<br />

100%<br />

1000<br />

90%<br />

78%<br />

77%<br />

800<br />

600<br />

400<br />

200<br />

89%<br />

96%<br />

95% 100%<br />

100%<br />

99%<br />

100%<br />

100%<br />

92% 85%<br />

91%<br />

100%<br />

100%<br />

100%<br />

100%<br />

100%<br />

100%<br />

82%<br />

86%<br />

98%<br />

0<br />

ATL-2007<br />

ATL-2015<br />

ATL-2025<br />

BOS-2007<br />

BOS-2015<br />

BOS-2025<br />

EWR-2007<br />

EWR-2015<br />

EWR-2025<br />

IAD-2007<br />

IAD-2015<br />

IAD-2025<br />

JFK-2007<br />

JFK-2015<br />

JFK-2025<br />

LAX-2007<br />

LAX-2015<br />

LAX-2025<br />

MSP-2007<br />

MSP-2015<br />

MSP-2025<br />

ORD-2007<br />

ORD-2015<br />

ORD-2025<br />

PHX-2007<br />

PHX-2015<br />

PHX-2025<br />

SAN-2007<br />

SAN-2015<br />

SAN-2025<br />

Airport-Year<br />

P A G E 21<br />

Arrivals


Remaining Work<br />

• We are on schedule<br />

• Subtask 4: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints<br />

– Complete the constraint analysis under the hypothetical scenarios<br />

when the ROT or MIT are not binding, respectively<br />

– Update gate constraint analyses<br />

– Continue the detailed taxiway modeling <strong>of</strong> airports<br />

• Subtask 5: Analyze <strong>Airportal</strong> <strong>Environmental</strong> Constraints<br />

– Airport modeling <strong>and</strong> environmental constraint modeling<br />

• Subtask 7: Analyze Shift to Metroplex Operations<br />

– Outline the approach <strong>and</strong> start the modeling<br />

• Results synthesis<br />

– Compile <strong>and</strong> identify the primary <strong>and</strong> secondary airportal constraints<br />

P A G E 22


Backup Material<br />

P A G E 23


Subtask 4:<br />

Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints<br />

• Along with the analysis <strong>of</strong> environmental constraints, this is<br />

(half <strong>of</strong>) the heart <strong>of</strong> the work<br />

• We will rely on the approach we have developed <strong>and</strong> refined over<br />

several years <strong>of</strong> NASA <strong>and</strong> JPDO work which estimates a metric<br />

called “projected throughput”<br />

• Use <strong>of</strong> this metric allows for an analytical “common currency” to<br />

evaluate the <strong>Airportal</strong> constraints<br />

– Runways<br />

– Taxiways<br />

– Gates<br />

– (as well as the environmental constraints)<br />

P A G E 24


Motivation for Using Projected Throughput as<br />

a Metric (“schedule trimming”)<br />

• “Unconstrained dem<strong>and</strong>” (e.g., the FAA’s Terminal Area Forecast)<br />

represents the public’s desire for air transportation regardless <strong>of</strong><br />

whether sufficient future NAS capacity will exist<br />

• Without sufficient capacity, future flight schedules would incur<br />

unrealistically large delays if all the flights in the unconstrained<br />

schedule were actually flown<br />

– Traditional valuation methods based on delay reduction may not be<br />

appropriate for far-term states <strong>of</strong> the system<br />

– While it’s easy to mathematically compute the DOC <strong>and</strong> passenger value<br />

<strong>of</strong> time benefits for a hypothetical case <strong>of</strong> reducing delay from 500<br />

minutes to 300 minutes, what is the interpretation?<br />

P A G E 25


Motivation for Using Projected Throughput as<br />

a Metric (“schedule trimming”)<br />

• At some point, capacity constraints would lead schedule-conscious<br />

airlines to cease adding additional flights to the schedule, even though<br />

the dem<strong>and</strong> would exist; to represent this, we analytically remove<br />

flights from future flight schedules according to specified airport delay<br />

tolerances or dem<strong>and</strong>/capacity ratios <strong>and</strong> sector capacities<br />

– This can also reflect service provider policies such as slot controls<br />

• We call this consolidated capacity metric “projected throughput”<br />

which estimates the number <strong>of</strong> flights that could be scheduled <strong>and</strong><br />

flown for a given level <strong>of</strong> system capacity<br />

• Airline coping strategies such as using larger aircraft, shifting flights to<br />

other times <strong>of</strong> the day or other airports, etc., are all possible but all<br />

have their own ramifications <strong>and</strong> costs<br />

• Projected throughput thus measures the effect <strong>of</strong> insufficient capacity<br />

<strong>and</strong> estimates the benefit <strong>of</strong> additional system capacity<br />

P A G E 26


Process for Going from Unconstrained Dem<strong>and</strong> to<br />

Projected Throughput<br />

• To represent this behavior, we analytically remove flights from the<br />

future flight schedule according to specified airport dem<strong>and</strong>/capcity<br />

ratios <strong>and</strong> sector capacities<br />

Trim the flight with<br />

the worst score;<br />

Update score for the<br />

rest<br />

Airport Capacities;<br />

Sector Capacities<br />

No<br />

Unconstrained<br />

Dem<strong>and</strong> Schedule<br />

Dem<strong>and</strong> <strong>and</strong> <strong>Capacity</strong><br />

Compared;<br />

Delays Calculated<br />

D/C Ratio Okay?<br />

Sectors Below MAP?<br />

Yes<br />

Objective:<br />

Trim the flights to<br />

satisfy the D/C rules<br />

<strong>and</strong> ATC sector<br />

capacities while<br />

maintaining maximum<br />

system throughput<br />

Projected Throughput<br />

Schedule<br />

P A G E 27


Subtask 4.2: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Taxiways)<br />

Airport Taxiway Constraints <strong>Analysis</strong><br />

• Approach 1: Use queuing theory to construct a taxi model:<br />

– Most previous studies have focused on runways-not applicable here<br />

– We analyzed average taxi-in time as a function <strong>of</strong> dem<strong>and</strong> for 70<br />

airports:<br />

• Generally linear functions, <strong>and</strong> <strong>of</strong>ten with near-zero slope<br />

• Taxi time is a flat function <strong>of</strong> dem<strong>and</strong> if the arrivals do not cross an active<br />

runway active runway/taxiway interaction is the main driver <strong>of</strong> extra taxi<br />

time<br />

– The linear relationship <strong>of</strong> the empirical functions cannot be explained<br />

by the st<strong>and</strong>ard queuing models:<br />

• Model suggests exponential growth while observed behavior is linear<br />

• Taxi time cannot be successfully modeled with queuing theory<br />

P A G E 28


Subtask 4.2: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Taxiways)<br />

Approach 2: Develop a physics-based model<br />

• Approach 2: Build physics-based model <strong>of</strong> taxiway operations<br />

at airports:<br />

– Use simulation to determine taxi-time as a function <strong>of</strong> dem<strong>and</strong><br />

– Model a small subset <strong>of</strong> airports from the OEP35 that together<br />

represent the majority <strong>of</strong> common airport layouts<br />

– Identify problematic airport layout/dem<strong>and</strong> level combinations<br />

– Extend findings to similar airports<br />

• Challenges:<br />

– Limited data available, especially pathway data<br />

– Taxiway interaction with other airport elements (gates, apron areas,<br />

service equipment) complicates analysis<br />

– Building accurate physics-based simulations <strong>of</strong> taxiway<br />

operations is highly labor intensive <strong>and</strong> time consuming<br />

P A G E 29


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Preliminary Results: Overview<br />

Percentage <strong>of</strong> Airports that are Gate Constrained<br />

60%<br />

50%<br />

2007<br />

2015<br />

2025<br />

Percentage<br />

40%<br />

30%<br />

20%<br />

10%<br />

0%<br />

1 2 3 4 All<br />

Priority Group<br />

• More priority 1 airports are gate-constrained than any other priority group<br />

• The percentage <strong>of</strong> airports that are gate-constrained stays relatively stable from<br />

2007 to 2025 in low priority airports<br />

• There is a dramatic increase in the percentage <strong>of</strong> gate-constrained airports in<br />

priority 1, from 21% in 2007 to 25% in 2015, to 53% in 2025<br />

P A G E 30


Subtask 4.3: Analyze <strong>Airportal</strong> <strong>Capacity</strong> Constraints (Gates)<br />

Preliminary Results: Overview<br />

100%<br />

90%<br />

80%<br />

70%<br />

Acceptance Rate for Gate Constrained Airports<br />

2007<br />

2015<br />

2025<br />

Percentage<br />

60%<br />

50%<br />

40%<br />

30%<br />

20%<br />

10%<br />

0%<br />

1 2 3 4 All<br />

Priority Group<br />

• Most priority 1 airports have acceptance rates in the 90-100% range<br />

– This corresponds to some small amount <strong>of</strong> gate-related delays at peak operating periods<br />

• The average acceptance rate for gate-constrained priority 1 airports steadily<br />

declines over time<br />

• Dem<strong>and</strong> will surpass capacity at a greater number <strong>of</strong> priority 1 airports by a greater<br />

amount in the future<br />

P A G E 31

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!