Guidebook for Preparing and Using Airport Design Day Flight Schedules (2016)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

29 C H A P T E R 4 This chapter provides guidance on the recommended level of DDFS detail, specifically regard- ing the airline, aircraft, market, gate assignment, and passenger load elements. These elements depend on the type of airport facility being analyzed, the planning tools used, and the likelihood of follow-on DDFS analysis. This chapter is primarily intended to help users appropriately scope a DDFS effort. As noted in Chapter 2, a DDFS consists of many elements, not all of which are required to address a specific problem or issue. Chapter 3 provides guidance on how to determine if a DDFS is required. This chapter provides guidance on which elements are needed to address airfield, terminal, landside, environmental, or operations and management issues once the decision is made to that a DDFS should be prepared. 4.1 Level of Effort Much of the content on the exhibits and tables presented in this chapter is based on indepen- dent research performed as part of the guidebook development regarding the sensitivity of plan- ning results to changes in the individual DDFS elements. Part of the research involved a survey of DDFS preparers to determine approximately how much of the total effort was required for each DDFS element. Exhibit 4.1 provides a summary of the results of that survey. Estimating flight times and then reconciling arrival and departure times when pairing flights are typically expected to account for more than half the effort. Other elements, including pas- senger load factors and O&D percentage, markets (origins for arrivals and destinations for depar- tures), equipment type, and gate assignments account for the remainder of the DDFS effort. Note that the chart represents an estimate that can vary widely depending on the airport and available data, the focus of the analysis, and the approach used. 4.2 DDFS Requirements by Type of Analysis The importance of individual DDFS elements will depend on the type of analysis being conducted. The airside includes runway, taxiway, and apron areas, as well as facilities that directly sup- port the airfield, such as aircraft rescue and firefighting facilities. Elements related to aircraft movements are much more important for airside analysis than elements related to passenger movements. The terminal building area includes the terminal building and all concourses and gates. Most terminal building requirements are determined by passenger flows; therefore, the DDFS Which Elements Need to Be Included in a DDFS

30 Guidebook for Preparing and Using Airport Design Day Flight Schedules passenger elements are critical. However, aircraft movements are also important for determin- ing gate requirements. The landside area is the portion of the airport that provides for ground access to the termi- nal building and airfield, and includes the terminal curbsides, access roads, parking facilities, and the airport portion of all other facilities, such as mass transit, used to access the airport. As noted in Chapter 3, DDFSs are not used for landside analysis as often as for airside and terminal building analysis. When DDFSs are used for landside analysis, passenger elements are the most important. Most quantitative airport activity-related environmental planning involves noise and air qual- ity analyses, although the tools used for these analyses may differ depending on whether the focus is on the airfield or on the landside. Both aircraft and passengers can generate environmental impacts. Therefore, DDFS aircraft and passenger characteristics are both important. The characteristics of DDFSs used for operations and management tend to be real-time or short-term (1 to 2 years out at most) and are sometimes prepared and updated using automated methods and/or third-party vendors. Depending on the type of facility being analyzed, DDFS aircraft and passenger characteristics can be important. It should be noted that, once prepared, DDFSs are often used for more than their original pur- pose. For example, a DDFS could initially be prepared to address an airfield issue, but later could be applied to analyze a terminal building issue. When scoping a DDFS, the user and preparer should consider additional uses beyond the original purpose. From the standpoint of consistency and quality control, it is most effective to prepare all elements of a DDFS concurrently, rather than adding elements incrementally as needed later on. 4.3 Application of Individual DDFS Elements by Type of Analysis Tables 4.1 through 4.6 and the narrative in this section provide guidance on the specific DDFS elements that would be required or useful for the various types of planning and analysis. (Readers using the pdf version of this guidebook may click below to navigate to the appropri- ate table.) • Table 4.1 Required DDFS Elements: Airside Analysis • Table 4.2 Required DDFS Elements: Terminal Building Analysis—Gates and Passenger Departure Facilities Exhibit 4.1. Survey results regarding estimated level of effort required for DDFS elements. 35% 10% 10% Flight Time Arrival/Departure Pairing Markets Equipment Type Gate Assignment Load Factor/O&D Percen 15% 20% 10% t When scoping a DDFS, consider additional uses beyond the original purpose.

Which Elements Need to Be Included in a DDFS 31 • Table 4.3 Required DDFS Elements: Terminal Building Analysis—Passenger Arrival Facilities and Other Facilities • Table 4.4 Required DDFS Elements: Landside Analysis • Table 4.5 Required DDFS Elements: Environmental Analysis • Table 4.6 Required DDFS Elements: Operations and Management More detail on the application of individual DDFS elements (first described in Chapter 2) and depicted on Exhibit 2.1: to airside, terminal, landside, and environmental analyses, as well as operations and management, is provided below. Arrival/Departure Designation: The arrival or departure designation is a core element required for any DDFS. Arrival/Departure Pairing or Matching: The pairing or matching of aircraft arrivals with departures is essential for any aircraft parking analysis. Arrival delays can translate to depar- ture delays if the initial delay is long and the turnaround time is short. At congested airports, arrival delays are more likely to translate to departure delays and careful aircraft pairing becomes Table 4.1. Required DDFS elements: airside planning. Type of Planning Analysis Airfield Aircra Parking Safety DDFS Element Capacity/ Delay Operaons and Efficiency Deicing At Gate RON Incursion Analysis Arrival/Departure Designaon Required Required Required Required Required Required Arrival/Departure Pairing Useful Useful Useful Required Required Useful Acvity Category Useful Useful Useful Useful Useful Useful Flight Time Required Required Required Required Required Required Day of Week Useful Useful Useful Useful Useful Useful Airline Designaon Useful Useful Useful Useful Useful Useful Flight Number Useful Useful Useful Useful Useful Useful Domesc/ Internaonal Designaon Not Required Not Required Not Required Useful Useful Not Required Gate Assignment Useful Useful Useful Useful* Useful* Useful RON Status Useful Useful Useful Required Required Useful Origin/Desnaon Useful Useful Useful Useful Useful Useful Equipment Type/Category Required Required Required Required Required Required Aircra Seats Not Required Not Required Not Required Not Required Not Required Not Required Enplaned/Deplaned Passengers Not Required Not Required Not Required Not Required Not Required Not Required O&D/Connecng Passengers Not Required Not Required Not Required Not Required Not Required Not Required Runway Use Designaon Useful Useful Useful Not Required Not Required Useful Arrival/Departure Fixes Useful Useful Useful Not Required Not Required Useful *In some instances, gate assignments are outputs of the DDFS rather than inputs.

32 Guidebook for Preparing and Using Airport Design Day Flight Schedules essential. Some flights will represent the first departure or last arrival of the day and the aircraft will remain overnight at a gate or remote hardstand. These flights do not need to be paired if the DDFS is being prepared for a single day, but should be designated as remaining at gate or towed to a remote hardstand. Aircraft pairing helps ensure that the real world characteristics of passenger flows by gate and concourse are accurately represented when planning other terminal facilities. For landside analyses, aircraft pairing also helps ensure that the real world characteristics of passenger flows by concourse and at curbsides are accurately represented. Pairing of aircraft arrivals with aircraft departures is useful for environmental noise and air quality analysis since arrival delays can translate to departure delays if the initial delay is high Type of Planning Analysis Gates Passenger Departure Facili es DDFS Element Quan ty Sizing Ticket Counter Ticket Queue Passenger Security Screening Baggage Security Screening Baggage Handling Systems Arrival/ Departure Designa on Required Required Required Required Required Required Required Arrival/ Departure Pairing Required Required Useful Useful Useful Useful Useful Acvity Category Useful Useful Useful Useful Useful Useful Useful Flight Time Required Required Required Required Required Required Required Day of Week Useful Useful Useful Useful Useful Useful Useful Airline Designaon Useful Useful Useful Useful Useful Useful Useful Flight Number Useful Useful Useful Useful Useful Useful Useful Domesc/ Internaonal Designaon Required Required Required Required Required Required Required Gate Assignment Useful* Useful* Useful* Useful* Useful* Useful* Useful* RON Status Required Required Useful Useful Useful Useful Useful Origin/ Desnaon Useful Useful Useful Useful Useful Useful Useful Equipment Type/ Category Required Required Useful Useful Useful Useful Useful Aircra Seats Not Required Useful Useful Useful Useful Useful Useful Enplaned/ Deplaned Passengers Not Required Useful Useful Useful Useful Useful Required O&D/Connecng Passengers Not Required Not Required Required Required Required Required Required Runway Use Designaon Not Required Not Required Not Required Not Required Not Required Not Required Not Required Arrival/Departure Fixes Not Required Not Required Not Required Not Required Not Required Not Required Not Required *In some instances, gate assignments are outputs of the DDFS rather than inputs. Table 4.2. Required DDFS elements: terminal building analysis – gates and passenger departure facilities.

Which Elements Need to Be Included in a DDFS 33 and the turnaround time is low. At congested airports, arrivals delays are likely to translate to departure delays and aircraft pairing becomes essential. Any operations or management process involving gates or gate management requires aircraft arrival and departure pairing. Flight pairing can be useful for staffing when multiple concourses or terminals are involved as it ensures consistency between the locations of aircraft arrivals and departures. Activity Category: The activity category (passenger, cargo, etc.) is useful for aircraft parking, gating, and RON analyses to ensure that the demand for and location of aircraft parking positions are accurately represented. If there is no other way to determine the activity category, such as air- line name, the designation becomes essential. The activity category designation is essential for gate management and can be useful for allocating staff. The designation is not essential for other plan- ning analyses not related to aircraft parking, but can be useful for organizing and sorting results. Table 4.3. Required DDFS elements: terminal building analysis – passenger arrival facilities and other facilities. Type of Planning Analysis Passenger Arrival Facilities Other Terminal Facilies DDFS Element CBP Meeter/ Greeter Area Baggage Claim Passenger Conveyance Systems Concessions Arrival/Departure Designaon Required Required Required Required Required Arrival/Departure Pairing Useful Useful Useful Useful Useful Acvity Category Useful Useful Useful Useful Useful Flight Time Required Required Required Required Required Day of Week Useful Useful Useful Useful Useful Airline Designaon Useful Useful Useful Useful Useful Flight Number Useful Useful Useful Useful Useful Domesc/ Internaonal Designaon Required Required Required Useful Useful Gate Assignment Useful Useful Useful Useful Useful RON Status Not Required Not Required Not Required Not Required Useful Origin/ Desnaon Useful Useful Useful Not Required Useful Equipment Type/ Category Useful Useful Useful Useful Useful Aircra Seats Useful Useful Useful Useful Useful Enplaned/ Deplaned Passengers Required Useful Useful Required Required O&D/Connecng Passengers Required Required Required Required Useful Runway Use Designaon Not Required Not Required Not Required Not Required Not Required Arrival/Departure Fixes Not Required Not Required Not Required Not Required Not Required

34 Guidebook for Preparing and Using Airport Design Day Flight Schedules Flight Time: Flight time is a core element of any DDFS and is a required element. Day of Week: Some DDFS applications are run for multiple days and require the day of the week associated with each flight. When a DDFS is prepared for a single design day, the selected day is typically a weekday. It should be noted that load factors can vary by the day of the week. This variation can affect passenger flows in the terminal and vehicular traffic flows even when airline schedules are similar. ACRP Report 82: Preparing Peak Period and Operational Profiles— Guidebook http://onlinepubs.trb.org/onlinepubs/acrp/acrp_rpt_082.pdf provides additional information on these day of the week variations. When used for noise analysis, the design day is intended to represent an average annual day and may be a composite of multiple days. Depending on local needs, air quality analysis may be based on a busy day, which is typically a weekday. Table 4.4. Required DDFS elements: landside analysis. Type of Planning Analysis Roads and Curbsides Parking DDFS Element Access Roads Curb - Private Auto Curb - Com- mercial Vehicles Hourly Entry/ Exit Plaza Taxicab Hold Cell Phone Lot Arrival/Departure Designa­on Required Required Required Required Required Required Required Arrival/ Departure Pairing Useful Useful Useful Useful Useful Useful Useful Acvity Category Useful Useful Useful Useful Useful Useful Useful Flight Time Required Required Required Required Required Required Required Day of Week Useful Useful Useful Useful Useful Useful Useful Airline Designaon Useful Useful Useful Useful Useful Useful Useful Flight Number Not Required Not Required Not Required Not Required Not Required Not Required Not Required Domesc/ Internaonal Designaon Useful Useful Useful Useful Useful Useful Useful Gate Assignment Useful Useful Useful Useful Useful Useful Useful RON Status Not Required Not Required Not Required Not Required Not Required Not Required Not Required Origin/ Desnaon Useful Useful Useful Useful Useful Useful Useful Equipment Type/ Category Useful Useful Useful Useful Useful Useful Useful Aircra Seats Useful Useful Useful Useful Useful Useful Useful Enplaned/ Deplaned Passengers Useful Useful Useful Useful Useful Useful Useful O&D/Connecng Passengers Required Required Required Required Required Required Required Runway Use Designaon Not Required Not Required Not Required Not Required Not Required Not Required Not Required Arrival/Departure Fixes Not Required Not Required Not Required Not Required Not Required Not Required Not Required

Which Elements Need to Be Included in a DDFS 35 Gate requirements and staffing requirements vary by day of the week and therefore the day of the week associated with each flight is required. Airline Designation: An airline designation is not essential, but can be useful for organizing and sorting results and for determining gate or parking assignments. In addition, the informa- tion can be used to help refine load factors and O&D percentages for each flight, which, in turn, makes estimating passenger and vehicular flows more accurate for terminal, landside, and envi- ronmental analyses, as well as staffing. For noise analysis, airline designation can also be useful in identifying aircraft engine types with multi-engine configurations. Flight Number: Flight numbers are not essential, but are useful for organizing and pairing flights to existing schedules and across multiple DDFSs. Domestic/International Designation: Identifying a flight as domestic or international is useful for analyzing aircraft parking because the CBP facilities required for nonprecleared international arrivals are often restricted to certain areas or gates. Some terminal facilities, such as international re-check and CBP are only used by international passengers. In addition, international passen- gers have longer lead and lag times than domestic passengers and therefore show different arrival Table 4.5. Required DDFS elements: environmental analysis. Type of Planning Analysis Noise Air Quality DDFS Element Airfield Landside Airspace Dispersion - Airside Dispersion - Landside Arrival/Departure Designaon Required Required Required Required Required Arrival/Departure Pairing Useful Useful Useful Useful Useful Acvity Category Useful Useful Useful Useful Useful Flight Time Required Required Required Required Required Day of Week Useful Useful Useful Useful Useful Airline Designaon Useful Useful Useful Useful Useful Flight Number Useful Useful Useful Useful Useful Domesc/Interna- onal Designaon Not Required Not Required Not Required Not Required Not Required Gate Assignment Not Required Not Required Not Required Required Not Required RON Status Not Required Not Required Not Required Required Not Required Origin/ Desnaon Useful Useful Useful Useful Useful Equipment Type/Category Required Not Required Required Required Not Required Aircra Seats Not Required Useful Not Required Not Required Useful Enplaned/ Deplaned Passengers Not Required Useful Not Required Not Required Useful O&D/Connecng Passengers Not Required Required Not Required Not Required Required Runway Use Designaon Required Not Required Required Required Not Required Arrival/Departure Fixes Required Not Required Required Required Not Required

36 Guidebook for Preparing and Using Airport Design Day Flight Schedules profiles. These differing profiles can also affect the sizing of terminal and landside facilities used by both domestic and international passengers. Identifying a flight as domestic or international is essential in gate management and staffing because nonprecleared international flights require special gate facilities and staffing. Gate Assignment: Gate assignments are useful for detailed airside and terminal building analy- ses as they allow aircraft paths to be more precisely defined in simulation modeling among other activities. At larger airports with multiple terminals or concourses, international gates, or multiple points of ingress and egress, some kind of locational identification (e.g., concourse) is necessary to ensure that passenger flows are modeled with reasonable accuracy. Gate assignments are also useful for detailed air quality dispersion analyses as they enable the identification of source point locations for aircraft and GSE emissions, but they are not necessary for noise analysis. Gate assignments are also essential for short-term gate management and some staff planning, such as for the TSA. DDFSs are sometimes used in conjunction with gate allocation models to determine gate assign- ments. In those instances, gate assignments are an output of the DDFS rather than an input. Type of Operations and Management DDFS Element Gate Management - Short-Term Gate Management - Medium Term Staffing Irregular Operaons Arrival/Departure Designaon Required Required Required Required Arrival/Departure Pairing Required Required Useful Required Acvity Category Useful Useful Useful Useful Flight Time Required Required Required Required Day of Week Required Useful Required Useful Airline Designaon Required Required Useful Required Flight Number Required Useful Useful Required Domesc/ Internaonal Designaon Required Required Required Required Gate Assignment* Required Useful Required Required RON Status Required Required Useful Required Origin/ Desnaon Useful Useful Useful Useful Equipment Type/Category Required Required Useful Required Aircra Seats Not Required Not Required Useful Not Required Enplaned/De- planed Passengers Not Required Not Required Required Not Required O&D/Connecng Passengers Not Required Not Required Required Not Required Runway Use Designaon Useful Not Required Not Required Useful Arrival/Departure Fixes Not Required Not Required Not Required Not Required *In some instances, gate assignments are outputs of the DDFS rather than inputs. Table 4.6. Required DDFS elements: operations and management.

Which Elements Need to Be Included in a DDFS 37 RON Designation: A RON designation indicates whether a gated aircraft departs to or arrives from a remote hardstand. This information is essential for gate or RON analysis as it determines which of the two aircraft parking alternatives will be required for the aircraft. For airside analysis, this information is also essential to distinguish between aircraft that leave a gate for a RON posi- tion versus an aircraft that leaves a gate to take-off. Except for gates, most terminal and landside facilities are affected by passenger flows; therefore, as long as enplaned or deplaned passengers are modeled correctly, RON status is not needed. RON assignments are useful for detailed air quality dispersion analyses because they enable the identification of point source locations for GSE emissions. RON status is not necessary for noise analysis. A RON designation is essential for gate management as it determines whether a gate can be made available for another arriving or departing flight. Some airline staffing (tow crews, etc.) will also be affected by RON needs. As with gate assignments, RON assignments may sometimes be an output of a DDFS rather than an input. Origin/Destination: For airside and environmental analyses, identifying the origin of an arriv- ing flight and the destination of a departing flight can help determine runway use and arrival/ departure fixes. It adds accuracy and precision to the DDFS planning results, but has less effect on ultimate delay or capacity results than the number or timing of flights. For terminal and landside analyses, flight origins and destinations may have a significant effect on load factors, O&D/connecting passenger ratios, and gate assignments for efficient access to preferred runways and flight paths. Providing that load factors and O&D/connecting passenger ratios are differentiated by market, O&D information can be very useful in planning most ter- minal building and landside facilities. Flight origins and destinations may affect optimal gating for efficient access to preferred run- ways and flight paths and are essential inputs for gate management. O&D information can also have a significant effect on load factors and O&D/connecting passenger ratios, which can affect staffing requirements at some terminal building facilities. Equipment Type/Category: Identification of aircraft equipment type or, at a minimum, size and performance category, is essential for airside analysis because it determines separation dis- tances and the types of runway an aircraft can use, thereby significantly affecting capacity and delay analyses. It also determines which gates or RON parking positions an aircraft can use. It is indirectly useful for categories of terminal facility and landside planning and staffing that are dependent on passenger flows because the information is used to estimate numbers of aircraft seats, which helps determine the number of enplaned and deplaned passengers. Identification of aircraft equipment type is also essential for airside noise and air quality analyses, but is not required to estimate landside environmental impacts. Aircraft Seats: The number of seats on an aircraft, along with the aircraft equipment type, is often used to determine holdroom size. Seat information also can be used to help determine the numbers of enplaned and deplaned passengers to assist in planning other terminal building and landside facilities. Aircraft seat information can also be indirectly useful to estimate O&D passenger flows and resultant ground vehicle flows for environmental analysis. Enplaned/Deplaned Passengers: It is not necessary to identify the numbers of enplaned or deplaned passengers on each flight for airside analysis unless the delay costs to passengers are being calculated. Post-security concession requirements are generally dependent on passengers enplaning and deplaning, while U.S. CBP facilities are dependent on deplaned international passengers. Landside facilities are affected by originating and terminating passengers instead of enplaned and deplaned passengers. However, numbers of enplaned and deplaned passengers

38 Guidebook for Preparing and Using Airport Design Day Flight Schedules are still useful as an intermediate step in calculating O&D traffic. Numbers of enplaning or deplaning passengers on each flight do not need to be identified for environmental analysis, but the information can be indirectly useful to estimate O&D passenger flows and resultant ground vehicle flows. Enplaned/deplaned passenger information is necessary for some terminal staffing facilities, such as restrooms and post-security retail concessions, and can be indirectly useful in estimating other terminal staffing requirements because the information can be used to help determine O&D passenger flows. O&D/Connecting Passengers: The numbers of O&D or connecting passengers by flight is essential for planning ticket counter, ticket queuing, passenger and baggage security screening, U.S. CBP, meeter/greeter, and baggage claim facilities. Similarly, O&D passenger estimates are required for just about all landside facilities as these facilities are dependent on O&D passenger flows. Numbers of O&D or connecting passengers by flight are not needed for airside environ- mental analysis, but the information is required to estimate resultant ground vehicle flows for landside environmental analysis. O&D passenger estimates are not needed for gate management. However, the information is essential for staffing ticket counter, passenger and baggage security screening, U.S. CBP, and baggage handling facilities. Runway Use Designation: Most DDFSs do not include runway use designations. The informa- tion is often determined within an airfield simulation model based on rules defined by the airside planner. Runway use designations are also essential for airside noise and air quality analyses, but this information is often added subsequent to the DDFS preparation process. These designations can be useful for optimizing short-term gate assignments, but are not needed for staffing. Arrival/Departure Fixes: Most DDFSs do not include arrival or departure fixes. However, the information can be helpful in developing the internal rules to identify runway use priorities within airfield simulation models. Arrival and departure fix information is not needed for termi- nal building or landside planning. This information is essential for airside noise and air quality analyses, but is often added subsequent to the DDFS preparation process. Arrival and departure fix information is not needed for gate management or staffing.