Guidebook for Airport Irregular Operations (IROPS) Contingency Planning (2012)

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.

Part 1 – Fundamentals of IROPS Planning 1 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy INTRODUCTION Why do we need a guidebook? Since aircraft began to fly and carry passengers for hire, there has always been the potential for delays; however, today with the vast number of passengers, airlines and economic and physical constraints placed on the aviation system, the potential for significant delays has never been greater. Over the past ten years, the issue of tarmac delays and related Irregular Operations (IROPS) events has really pushed concern to the forefront of our industry. Passengers and politicians alike are demanding that these issues be addressed. This has prompted ideas like a passenger bill of rights to emerge as well as several U.S. DOT rules in order to protect passenger needs during these delays. The United States Department of Transportation (DOT) recently made changes to its rules concerning the requirement for air carriers to coordinate their Tarmac Delay Contingency Plans directly with airports. While these changes apply only to airlines, your airport’s participation in the response efforts of airlines is crucial to helping prevent the types of Irregular Operations (IROPS) incidents that have happened in the past and that have resulted in significant passenger harm and public relations nightmares for airports. Negative impacts to passengers have been considerably reduced at airports that have developed and implemented their own comprehensive, coordinated plan for dealing with IROPS situations. Participation by airport operators involves a variety of areas, including facilitating communication and providing facilities as well as services to support airline response efforts. Your airport’s IROPS contingency plan will ensure that your support efforts are properly aligned with response efforts of the Federal Aviation Administration (FAA), Transportation Security Administration (TSA), Customs and Border Protection (CBP), and airlines, and that the airport community’s goal of mitigating the hardships on passengers during IROPS situations is realized. Please note that for the purposes of this guidebook, references to the FAA include all forms of air traffic control (ATC) services. For the purposes of this document, the term “IROPS” is intended to describe those exceptional events that require actions and/or capabilities beyond those considered usual by aviation service providers. An example of these events is the occurrence of too many unexpected aircraft at an airport causing unique staffing and resource needs by both the airport and passengers. Additionally, any references to an IROPS contingency plan will be referred to as an “IROPS contingency plan,” an “IROPS response plan,” or an “IROPS plan.” How does this guidebook meet the need? The objective of ACRP Project 10-10, “Guidebook for Airport Irregular Operations (IROPS) Contingency Planning” was to prepare a practical airport IROPS response planning document for commercial passenger service airports of all sizes to improve customer service during times of adverse weather and unplanned conditions. The findings have been published as this report, ACRP Report 65: Guidebook for Airport Irregular Operations (IROPS) Contingency Planning. ACRP Report 65 provides focus on responses to situations that involve: Tarmac delays Passenger surges in terminals and security areas Term • • • inal passenger capacity

2 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning Off-hour conditions related to staffing for key areas such as access through security and staffing for TSA and CBP functions, as well as for concessions Passenger conditions during extended stays both in terminals and off-site Pl • • • anning for special needs passengers Users of this guidebook are given step-by-step instructions on how to prepare and/or refine their IROPS plans. The flexibility of the guidebook material enables airports to either make improvements to existing IROPS plans or create a completely new plan, and it is scalable to relate to large, medium, and small airports. ACRP Report 65 focuses on collaboration and coordination to ensure that customer needs are met. ACRP Report 65 draws from the United States DOT Model Plan for Lengthy Airline Onboard Ground Delays, created by its national task force. However, additional research was performed by the ACRP Project 10-10 team to round out this guidebook, including: Administering a survey that addresses IROPS planning, events, and concerns at 400+ airports Assessing summary material from airport IROPS response workshops held across the nation, independent of this research project Hosting focus groups and site visits Assessing IROPS response planning requirements Id • • • • • entifying examples of IROPS response planning best practices from airports around the country Figure 1 illustrates the sequence of events related to IROPS contingency planning five years prior to the publication of ACRP Report 65. Figure 1. Timeline of IROPS Planning Initiatives. Who can use the guidebook? This guidebook can be used by commercial passenger service airports of all sizes to develop, continually evaluate, and/or update their IROPS plans for procedures pertaining to IROPS. PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

3You will encounter icons throughout this guidebook that will direct you to additional resources available: Topics = This icon highlights topics that can be found in Resource A – Topics for IROPS Plan Development of this guidebook. Tools = This icon highlights tools that can be found in Resource C – Tools of this guidebook. Airports that do not have an existing IROPS plan should consider using Resource A – Topics for IROPS Plan Development to assist in the development of an initial draft IROPS plan for their airport. Airports that do have an existing IROPS plan should use the topics in Resource A to guide an evaluation review and/or update of their plan as needed. Resource C contains tools that can be used by airports in either case to strengthen their IROPS planning efforts. In either instance, the use of a local IROPS Champion (described below) is recommended in implementation of the review and development process. Role of the IROPS Champion and partnering for success During the development of this guidebook, one message emerged as being common to all successful IROPS contingency response efforts. That message is simple, but critically important: communicate - communicate - communicate. In applying this guidebook, this means bringing aviation service provider organizations (listed in Figure 2) together so they can explore ways to support one another to address current and evolving aviation challenges that disrupt the normal flow of passengers through the air transportation system. To best use this guidebook, it is recommended that airport management identify a point person, known as the IROPS Champion, who will be responsible for carrying out all of the necessary tasks, coordinating efforts between all service providers involved in IROPS events, and developing a partnering environment. (Figure 3 outlines the responsibilities of the IROPS Champion.) This person may be the airport manager, or in some instances it may be another management or operations staff member. If an IROPS Champion is utilized, it is imperative that the airport manager exhibit support to the IROPS Champion so the aviation service providers involved in the development and implementation of the IROPS plan know the IROPS Champion is empowered to develop the plan. (Figure 4 illustrates the relationship between airport management, the IROPS Champion, and aviation service providers.) Aviation Service Providers Airport Operations Airlines Government Agencies (FAA, CBP, TSA) Concessionaires Ground Transportation Agencies Fixed Base Operators (FBOs) Overnight Accommodations Emergency Response Providers Military (if joint-use facility) Di • • • • • • • • • • version Airports Figure 2. Aviation Service Providers. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

4Figure 3. IROPS Champion Responsibilities. Figure 4. Relationship between Airport Management, the IROPS Champion, and Aviation Service Providers. One of the most important responsibilities of the IROPS Champion is to encourage communication, coordination, and collaboration between service providers at an airport. In order to provide mutual support and focus on cooperation, service providers must first find a way to bridge the gap between feeling that they need to go it alone with individual plans and reach an environment of partnering for success to develop a collaborative regional contingency plan to provide a coordinated response to IROPS events. This can be accomplished by taking attitudes such as those listed in Figure 5 on the left and converting them to those on the right. Read Part 1 - Fundamentals of IROPS Planning and Part 2 – Resources of ACRP Report 65 Distribute Topic Worksheets to appropriate service providers (Resource A) Collect worksheets Input worksheet data into Model IROPS Plan (Resource B) Distribute completed coordinated IROPS plan to appropriate service providers Update IROPS plan as needed • • • • • • Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

5Figure 5. Partnering for Success. Process for developing an IROPS Response Plan The guidebook recommends starting your airport’s IROPS response planning immediately. Advanced planning is necessary to establish local agreements for cooperation and collaboration between various aviation service providers before potential IROPS events occur. Suggested IROPS planning steps to achieve cooperation and collaboration are provided in Figure 6. Figure 6. IROPS Planning Steps. See Tool 1 – IROPS Planning Process and Tool 2 – DFW’s Sample for Partnering for Success in Resource C for additional support. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

6How does an airport IROPS contingency plan relate to an Airport Emergency Plan (AEP) or National Incident Management System (NIMS)? An AEP contains information describing how an airport plans for response to a variety of emergency situations. A significant portion of the AEP planning information and response procedures will be similar to airport IROPS procedures. Many of the same organizations will be involved in an airport’s coordinated IROPS response strategy, and many of its communication procedures will be similar. Although the two plans are alike, it is important to consider the requirements of each plan separately during the planning process. The NIMS is used across the United States and most emergency management personnel have been trained on the use and usefulness of this system when needed. Setting up the airport’s Emergency Operations Center (EOC) with its inherent NIMS procedures to deal with IROPS is a decision that will need to be made on a case-by-case basis by airport personnel in charge during an IROPS event. For minor or short duration IROPS events it is not likely that an EOC would need to be set up; however, as the magnitude or the duration of the event is extended, establishing the EOC may be necessary to coordinate the activities of all of the service providers. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

7 CHAPTER 1 – EXECUTIVE BUY-IN/GET ORGANIZED 1.1 Description The first step, whether your airport is developing a new plan or reviewing an existing one, is to establish executive buy-in from your airport and each of your local aviation service provider organizations. These should include airport operations, airlines, concessions, ground transportation, local accommodations, government agencies (FAA, CBP, and TSA), fixed base operators (FBOs), refuelers, military (if a joint-use facility), executive management liaison, and emergency response. Next, your airport should create an IROPS Contingency Response Committee that includes representatives from each of your local service providers. The Committee should be led by an IROPS Chairperson, who typically is a representative of your airport. The goal of your airport’s Committee will be to establish and enhance contingency plans for local service providers through their collective, cooperative, and collaborative decision making. 1.2 Creating Executive Buy-In Two elements to executive buy-in must be in place for a successful IROPS plan. The first element is the airport itself. Executive management of the airport must have a firm commitment to develop, implement, and continually improve an IROPS plan that illustrates a full buy-in from the top down within the airport staff. The second element is equivalent buy-in from the executive management of the various aviation service providers. Executive buy-in is fully accomplished when each of the airport aviation service provider organizations has committed their support of a documented, coordinated IROPS plan. 1.3 Identifying the IROPS Champion Before organizational activities can take place, an IROPS Champion must be selected and empowered by airport management. The IROPS Champion is the point person for all activities related to developing an IROPS plan. An airport management employee is often well suited/positioned to be the IROPS Champion; he/she has holistic responsibilities for airport operations, and many times sits in a role that can effectively facilitate bringing aviation service providers together. The activities discussed throughout this guidebook will be led by the IROPS Champion and supported by the airport IROPS Contingency Response Committee. 1.4 Establishing an IROPS Contingency Response Committee The goal of the airport IROPS Contingency Response Committee is to establish and enhance contingency plans through their collective, cooperative, and collaborative decision making. This will ensure that actions result in a coordinated and unified level of customer care across all of the airport’s aviation service providers during IROPS events. It is essential that all local service providers not only develop their own individual IROPS plans, but also participate in the airport’s IROPS Contingency Response Committee activities. Members of an airport IROPS Contingency Response Committee should include representatives of all local aviation service provider organizations. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

8See Tool 3 – Responsibilities of the Airport’s IROPS Contingency Response Committee and Tool 4 – Questions for Initial IROPS Committee Meeting in Resource C for additional support. 1.5 Notification and Contact Lists An important recommendation for IROPS Contingency Response Committee action includes determination and documentation of local methods for 24/7 communications. The contact list should be valid for both normal and off-hour operations. Key point-of-contact information for the airport should be shared with all local air carriers and government agencies. As with other similar information, procedures must be established to keep the information accurate and up to date. These contact lists and notification procedures should be developed and communicated with all service providers. For instance, an airport should create a 24/7 email contact list of major airport stakeholders, including diversion airports, in a region. This list should be used to communicate status and track diverted flights in the region during IROPS events to ensure shared situational awareness. Notification methods should be discussed by the IROPS Contingency Response Committee and chosen based on the most reliable methods for reaching all service providers on an airport’s IROPS contact list. Various methods can include: Email distribution Text messaging Phone tree Conference calls No • • • • • tification/decision tree Based on research completed for this guidebook, it is recommended that hub airports host a conference call with predetermined key service providers at least 24 to 48 hours prior to a severe weather event that has been forecasted to facilitate communications and coordination. Representatives from the following service providers should be included on this call: National Oceanic and Atmospheric Administration’s (NOAA) National Weather Service (NWS), FAA, airlines, CBP, TSA, and airport departments. Recommended guidance is provided in Topic 1: IROPS Contingency Response Committee. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

9 CHAPTER 2 – DOCUMENT CURRENT SITUATION 2.1 Description In this step, your airport’s IROPS Contingency Response Committee should identify, gather, and compare important response plan information from service providers to ensure collaboration and cooperation. The collective comparison of current IROPS plans between service providers should include a review of local IROPS events history, identification of customer needs, evaluation of how to track delayed aircraft, the tracking of equipment inventory, and the determination of skills availability. Key airport implementation should include maintaining and sharing local contact and email distribution lists. 2.2 Reviewing Existing IROPS Response Plans It is recognized that each service provider should have its own plans for response to IROPS events. It is also recognized that the United States DOT’s rules on enhancing airline passenger protections (14 CFR Part 259 Enhanced Protections for Airline Passengers) require air carriers to adopt tarmac delay contingency plans and coordinate those plans with airports at which they operate. Therefore, the purpose of this activity by the IROPS Contingency Response Committee is to identify and gather important response plan information from service providers to ensure that proper communication, cooperation, and coordination occurs between them. Results of this review should include both formal and informal understandings of coordination between these organizations. These response plans from individual organizations should be evaluated for adequacy during the four categories of IROPS impact situations: surge, capacity, after-hours, and extended stay (see Section 2.3 for more information on these scenarios). Each of these situations should be considered for impacts involving unplanned aircraft and unplanned passengers. For example, planning for off-hours situations involving both aircraft and passengers should consider the following: Unplanned aircraft arrivals The ability to meet passenger needs such as concessions Staff access to secure side The av • • • • ailability of CBP and TSA staffing Recommended guidance is provided in Topic 2a: Reviewing Existing IROPS Response Plans. See Tool 5 – Implementation Checklist for Evaluating IROPS Plans and Tool 6 – Self- Assessment Questionnaire in Resource C for additional support. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

10 2.3 Reviewing Local IROPS Events and Assessing Local Situation What causes an IROPS event? Causes of IROPS events can include extreme weather, natural disasters, reduction of airport facility capacity, aircraft mechanical problems, labor issues, and others. What are the potential impacts of an IROPS event? In addition to impacts on passengers, IROPS events can also have an impact on airlines and airports, as shown in Figure 7. The impacts of IROPS events on airlines include flight delays, cancellations, diversions (including non-scheduled airline flights), and crew time expiration, resulting in potentially adverse impacts on passengers and other airport customers. Figure 7. Impacts of IROPS Events. Airport impacts from unscheduled passengers and aircraft can be categorized into four scenarios that must be planned for: Surge: Aircraft and passengers flowing into an airport Capacity: Airport terminal becomes filled with passengers and ramp space/gates become full with aircraft After-Hours: Aircraft land and passengers need to deplane at irregular hours Extende • • • • d Stay: Passengers and aircraft may be stuck at airport for an extended period of time Recommended guidance is provided in Topic 2b: IROPS Event History. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

11 2.4 Passenger Needs Needs of passengers (including animals) on board aircraft on the ground and in airport terminals during lengthy delays vary, and normally require the attention of more than one party. There are five areas of need for passengers including up-to-date information, food and water, safe and secure facilities (including clean restrooms on board an aircraft and in an airport terminal), special services (including services for special needs passengers and ground transportation), and lodging for extended stays. Significant disruptions to airline schedules or operations can adversely impact the passenger experience and their overall satisfaction with the air transportation system. Figure 8 illustrates the needs of passengers (including live cargo) during IROPS events. Figure 8. Passenger Needs. Recommended guidance is provided in Topic 2c: Passenger Needs. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

12 2.5 Current Response Capabilities A number of questions related to several key concepts should be considered when beginning the planning process. Please note the following questions are generic and additional guidance can be found in Resource A – Topics for IROPS Plan Development and Resource C - Tools: Availability of services during an IROPS event – What does an airport have in place to know when an aircraft is experiencing an IROPS event at its location? – What are an airport’s goals for providing service to passengers and other customers during an event? – What contingency response procedures does an airport have in place to achieve these goals? – How is an airport’s IROPS response service coordinated with other local service providers? Coordination of services during an IROPS event – What challenges exist at an airport when an IROPS contingency response requires coordination between two or more service providers? – Are there different types of challenges at an airport during an IROPS event depending on whether it is a departure or arrival? – What steps could be taken to improve the availability of service provided by an airport? Pre-position of resources required during an IROPS event – What resources are required? – What are the arrangements/procedures for shared resources when needed? – What steps have been taken to ensure passenger’s needs are met during extended stays in the terminal? Sharing situational inform • • • • ation during an IROPS event – What type of information is being shared at an airport during an IROPS event? – What is the mechanism by which information is shared? – How is the shared information used by each of the receiving service providers? – What additional shared information would be useful? – What coordination procedures exist for service providers to back up each other during an extended delay, diversion, or special mobility event? – What is the procedure to report the effectiveness of the response to meeting passenger needs during an event by each service provider, individually and collectively, to establish lessons learned and improve response? Recommended guidance is provided in: Topic 2d: Tracking Delayed Aircraft Topic 2e: Trigger Events and Communications Plans Topic 2f: Support for Passengers Topic 2g: Tracking Resource Inventory Topic 2h: Skills Availability See Tool 7 – Example Resource Inventory Checklist in Resource C for additional support. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

13 CHAPTER 3 – ESTABLISH PROCEDURES TO COOPERATE 3.1 Description In this step, your airport will need to determine how to establish cooperation with local service providers in order to meet passenger needs. These include airlines, concessions, ground transportation, and government agencies (FAA, TSA, and CBP) as related to their staffing and resource capabilities. Cooperation is needed for responding to after-hours operation, surge in the number of passengers in the terminal and/or needing transportation to local accommodations, and consideration for diverted flights, including international flights into airports without a CBP presence. Every airport should establish a local process to monitor and maintain its overall airport capacity status during an evolving IROPS event. 3.2 Cooperation Procedures Cooperation procedures are needed for coordinated response to: After-hours operation Surge in number of passengers in terminal and/or needing transportation to local accommodations Other impacts on passenger service caused by lengthy flight delays Consideration • • • • for diverted flights, including international flights to airports without a permanent CBP presence Every airport should establish a local process to monitor and maintain its overall airport capacity status during an evolving IROPS event. This can involve keeping an inventory of data pertaining to IROPS events that will assist and support the acquisition of and/or justification for additional resources and equipment. A group of service providers typically found at airports is vital in local IROPS planning efforts: airlines, concessions, ground transportation, FAA, TSA, and CBP. Coordination with each of these entities is critical in establishing coordinated procedures that will be followed during an IROPS event. Above and beyond these service providers, other service providers should be coordinated with as appropriate to your airport (e.g., overnight accommodations, FBOs, alternate transportation providers). Recommended guidance is provided in: Topic 3a: Establish Procedures with Airlines Topic 3b: Establish Procedures with FAA Topic 3c: Establish Procedures with CBP Topic 3d: Establish Procedures with TSA Topic 3e: Establish Procedures with Concessions Topic 3f: Establish Procedures with Ground Transportation See Tool 8 – Concessions Checklist for Snow and Hurricane Events and Tool 9 – Airport-Airline 24/7 Contact and Capability Summary in Resource C for additional support. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

14 3.3 Technology Considerations A wide variety of technologies can assist in implementing IROPS response plans. It is recommended that an airport try to leverage existing technology before developing new unique systems. Assessments of technology solutions related to effective management of related IROPS contingency response activities are provided in Resource C - Tools of this guidebook. Also provided is a comparison of technology categories by applications and relative cost. See Tool 10 – Technology Solutions in Resource C for additional support. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

15 CHAPTER 4 – REVIEW, UPDATE, AND TRAINING 4.1 Description In this step, your airport should determine what improved procedures are necessary and beneficial to IROPS planning, and then should conduct coordinated training exercises to ensure these plans are understood by all involved service providers. Table-top exercises are recommended to utilize considerations of both local IROPS events and events involving other regional airports. A key element of these exercises should be testing for impacts from each of the four IROPS situation types (surge, capacity, off-hours, and extended stay). 4.2 Periodic Review After reviewing the existing local IROPS plans (as described in Section 2.2) and establishing procedures to cooperate (as described in Chapter 3) it is important to review how well the current plans address potential IROPS impacts. Specific attention should be paid when these response plans from individual organizations are evaluated for adequacy during the four categories of IROPS impact situations (discussed previously). Each of these unplanned situations should be considered for impacts involving both aircraft and passengers. 4.3 Update Individual organization response plans should be updated and/or supplemented based on answers to the questions from the review process. Coordinated plans with local service providers (as described in Section 3.2) should also be reviewed and updated and/or supplemented at this time if needed. 4.4 Training Training exercises should be developed and implemented to emphasize the updated response plans. After determining what improved procedures are necessary and beneficial to IROPS planning, it is important for the airport to support communication, cooperation, and coordination between service providers through workshops and training initiatives. This will ensure that new procedures are understood by all involved service providers. The primary purpose of holding periodic IROPS coordination workshops is to provide a common format and venue for the periodic review and the confirmation and updating of local IROPS plans. It is recommended that these workshops be held biannually, including one during the fall/winter season and one during the spring/summer season. The goals of these local workshops are to: Expedite and facilitate the development of the local IROPS community Establish a communication plan Develop and integrate IROPS plans Encourage agreement to execute the IROPS plan Provide general orientation to explain why planning for mitigating the effects of IROPS events on passengers is critical • • • • • Attendance should include representatives from all organizations with representation on the airport’s IROPS Contingency Response Committee and also representatives of other key airport personnel based on the importance of their understanding of IROPS planning. Additionally, other regional service providers should be invited to participate as appropriate. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

16 Periodic coordinated frontline training for airport contingency response should be conducted to provide an emphasis on actions requiring coordination of two or more organizations and to provide an opportunity to test new policies, practices, and procedures. Contingency training exercises should focus on shared situational awareness in relation to: Mutual support and valuing one another Timing of IROPS responses Effectiveness of responses Shared success Im • • • • • pacts of the United States DOT “3-Hour Rule” and “4-Hour Rule” (see Glossary for definitions of these rules) Table-top exercises are recommended to utilize considerations of both local IROPS events and events involving other regional airports. A key element of these exercises should be testing for impacts from each of the four IROPS situation types (surge, capacity, off-hours, and extended stay). Recommended guidance is provided in: Topic 4a: IROPS Coordination Workshops Topic 4b: IROPS Coordinated Frontline Training See Tool 11 – Sample Workshop Agenda in Resource C for additional support. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

17 CHAPTER 5 – CONSOLIDATED COOPERATION ACTIONS DURING AN EVENT 5.1 Description When your airport is experiencing an IROPS event, three actions are critical: communication, coordination, and collaboration. This requires your local service providers to work together to communicate aircraft status in the air and on the ground, as well as execute IROPS procedures as shown in Figure 9. In this step, your airport IROPS Contingency Response Committee needs to ensure the capability for coordinating shared information for both aircraft status and airport capacity. Relevant aspects of aircraft status should be provided to appropriate aviation service provider organizations during an IROPS event by the airport’s communication center or point of contact. Figure 9. Joint Actions during IROPS Events. 5.2 Monitoring IROPS Event Indicators While some IROPS events are unpredictable, many can be handled successfully if service providers are actively anticipating an event. Certain actions taken by service providers on a constant basis can position them well to handle an IROPS event, should one occur. Some examples of these actions include tracking aircraft status and tracking weather patterns. Aircraft status in the air and on the ground is tracked by airlines and the FAA to provide accurate, complete, and timely information regarding expected flight delays and developing local situations. Recommended guidance is provided in Topic 5a: Aircraft Status. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

18 Weather patterns are tracked by the airport, airlines, and the FAA to predict potential impacts to aircraft operations, as well as to carry out alternate operating procedures, such as diverting flights to alternate airports. This is done to maintain the safety of the crew and passengers, as well as operations staff out on the airfield. Recommended guidance is provided in Topic 5b: Tracking Weather. See Tool 12 –National Oceanic and Atmospheric Administration (NOAA) National Weather Service (NWS) Checklist in Resource C for additional support. A main objective during any type of IROPS event is for all service providers to focus on ensuring an international flight gets to its scheduled arrival airport. If this objective cannot be met, then the focus should be to divert it to a CBP staffed airport with appropriate international aircraft equipment. 5.3 Executing IROPS Response Plans and Procedures Effective response to an evolving IROPS event depends on timely shared situational awareness among all aviation service providers. This awareness includes the early identification of a potential IROPS situation and the evolving IROPS condition as the event advances. Specifically, this involves the sharing of the following: Tracking and sharing aircraft status both in-air and on the ground Passenger needs Capacity constraints Af • • • • ter-hour capabilities, if warranted IROPS communication plans A key benefit of IROPS communication plans include coordinated IROPS response actions by airport operations, the airlines, ATC services, and by affected diversion airports. Based on the situational need, additional communications among other organizations including TSA, CBP, concessions, and ground transportation may also be required. In addition to internal communication, efforts should be made to communicate externally with customers and passengers through airport websites and social media outlets where appropriate. Recommended guidance is provided in Topic 5c: Execute IROPS Communication Plans. See Tool 13 – Sample Communication Plan and Tool 14 – Social Media in Resource C for additional support. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

19 Passenger support plans The key goal of an IROPS plan is to ensure focus on coordinated support of passengers and other customers during an IROPS event. Guidance for planning and developing support capabilities and actions is based on aircraft and passenger location and on duration of passenger stay both on board aircraft and in the terminal. Recommended guidance is provided in Topic 5d: Execute Passenger Support Plans. Airlines Per the United States DOT rules on enhancing airline passenger protections (14 CFR Part 259 Enhanced Protections for Airline Passengers), airlines are required to develop and coordinate their extended delay contingency plans with both the scheduled airports they serve and their diversion airports. It is recommended that the airline contingency plans be fully discussed and understood by your airport so that they can be implemented when needed during IROPS events. Recommended guidance is provided in Topic 5e: Execute IROPS Procedures with Airlines. FAA, TSA, CBP Each of the listed government agencies has established guidelines covering their responsibilities during an IROPS event. These include provisions for coordination with airports during their local IROPS contingency planning efforts. These guidelines include the following: The FAA has agreed to implement aircraft ground control procedures for aircraft making tarmac delay requests per DOT rules on enhancing airline passenger protections. Additionally the FAA currently provides procedures for airport access in regard to expected flight delays and developing local situations. These flight-status-related sources are provided as long as they do not interfere with normal FAA operations. The Department of Homeland Security has issued procedures to TSA Federal Security Directors establishing and utilizing secure areas using procedures in the Airport Security Program or Aircraft Operator Standard Security Program. The TSA organization at local airports should be contacted as needed to implement appropriate security measures for passengers during IROPS events. The • • • Department of Homeland Security through the CBP Office of Field Operation has developed a contingency plan to address unscheduled arrivals, including flight diversions and technical fuel stops. The Director of Field Operations has provided guidance for IROPS events, including recommended response procedures for international flights diverted to airports without a Federal Inspection Station. Additional CBP procedures have been established with consideration of United States DOT regulations covering extended ground delays (3- and 4-hour guidelines for domestic and international flights, respectively). Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

20 Recommended guidance is provided in: Topic 5f: Execute IROPS Procedures with FAA Topic 5g: Execute IROPS Procedures with CBP Topic 5h: Execute IROPS Procedures with TSA Concessions The role of concessions during an IROPS event is to ensure that passenger food and beverage needs (and potentially medicinal and family needs) are met during IROPS events. It is recommended that concessions develop and implement their own IROPS plans for operations to be used during IROPS events. The IROPS operation plans for concessions should be activated as required following situational notification by either an airline or by an airport designated point-of-contact. Recommended guidance is provided in Topic 5i: Execute IROPS Concessions Procedures. Ground Transportation The role of ground transportation during an IROPS event is to ensure that needs (including those resulting in extended passenger and customer stays in the terminal area) can be supported. It is recommended that ground transportation organizations develop and implement their own IROPS plans for use during IROPS events. Ground transportation organizations should activate their IROPS plans when notified of related requirements caused by an IROPS event. Recommended guidance is provided in Topic 5j: Execute IROPS Ground Transportation Procedures. See Tool 15 – During an Event Tools and Tool 16 – Diversion Checklist in Resource C for additional support. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

21 CHAPTER 6 – CAPTURING LESSONS LEARNED AND UPDATING PLANS 6.1 Description In this step, your airport should host an after-action meeting to review performance effectiveness as soon as is practical following return of operations to a normal state after an IROPS event. Part of the recommended debriefing procedures should be the identification of lessons learned. The airport IROPS response planning documentation should be reviewed by the IROPS Contingency Response Committee and updated as appropriate. 6.2 Debrief after an IROPS Event The purpose of the debriefing session is to review each airport organization’s response performance following a major IROPS event. This allows service provider organizations to assess and analyze all aspects of response, to document lessons learned, and to improve performance by sustaining strengths and correcting weaknesses. When necessary, performance improvements should be incorporated into the IROPS plan with staff provided training on any new procedures. Additionally, technology and resources should be evaluated as part of the review to determine if either should be enhanced to assist in improving IROPS event response. Debriefings should cover the following: Communication issues Procedures refinement Service failures and lapses After-hour staffing resources and gaps Operations and maintenance restocking (deicing fluid, concessions, and other) Capability needs Ne • • • • • • • w capital items requisitions Recommended guidance is provided in Topic 6a: Debriefing IROPS Event. See Tool 17 – After an Event Debrief in Resource C for additional support. 6.3 Lessons Learned The primary purpose of gathering lessons learned following an IROPS event is to document what worked and what did not. Lessons learned, both good and bad, should be expected to surface from debriefing meetings held after every major IROPS event. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

22 Following internal management debriefings, each service provider organization should report a summary of its findings (including any lessons learned) and recommendations to the IROPS Champion. The IROPS Contingency Response Committee should consider the several debriefing reports typically expected from each major IROPS event to identify any additional lessons learned that recognize tasks to be performed and the responsible party to perform them. The Committee should track implementation and hold subsequent meetings to confirm completion of the tasks. The IROPS Committee should compile and distribute any resulting new lessons learned to local airport organizations that may be affected. Periodically, a summary of local lessons learned should be shared with other airports in the aviation community. Recommended guidance is provided in Topic 6b: Capturing Lessons Learned. Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

23 SUMMARY Developing and implementing an effective airport IROPS plan requires continuous communication, cooperation, and coordination between the airport and each of the local service providers. Activities associated with the six steps of IROPS plan development process are: know, act, confirm, and improve. Each activity is critical to provide a unified response by all service providers during IROPS events. KNOW: What do we need to accomplish? Step 1 - Executive Buy-In/Get Organized Step 2 - Document Current Situation ACT: How do we partner for success? Step 3 - Establish Procedures to Cooperate Step 4 - Review, Update, and Training for Plan Implementation CONFIRM: Did we do what we said? Step 5 - Consolidated Cooperation During an Event IMPROVE: • • • • Are we communicating our lessons learned to continually advance our response to IROPS events? Step 6 - Capture Lessons Learned and Updating Plans Continually updating and refining an airport’s IROPS plan helps to provide the best customer experience for passengers affected by IROPS events. The most important things to remember for successful IROPS contingency responses are: (1) Success is measured by passenger experience. (2) Success requires top-down commitment of executive management. (3) Success hinges on the ability to communicate-communicate-communicate. Part 1 – Fundamentals of IROPS Planning PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

24 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy PART 2 RESOURCES

PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy Part 2 - Resource A – Topics for IROPS Plan Development 25 RESOURCE A – TOPICS FOR IROPS PLAN DEVELOPMENT INTRODUCTION The topic worksheets presented in the following pages (when completed) combine to create a generic IROPS contingency plan. Once these topic worksheets have been completed, the IROPS Champion will insert them into the appropriate places in Resource B – Model IROPS Contingency Plan. These topics are organized by the chapters in Resource B – Model IROPS Contingency Plan, so they align with each other and the information presented in Part 1 – Fundamentals of IROPS Planning. Please note that the topics presented in this document are only a starting point for the IROPS Champion to begin development of an IROPS plan; each of the topics should be tailored to fit the needs of the airport (in some cases this may require the addition or deletion of tables). For the purposes of this guidebook, references to the FAA include all forms of air traffic control (ATC) services.

26 CONTENTS 29 Topic 1 – IR OPS Contingency Resp on se Co mmitt ee 31 Topic 2 – Docu me nt Cu rr en t Situation 32 Topic 2a – Revi ew ing Existing IR OP S Resp onse Plan s 37 Topic 2b – IR OPS Event Hi story 39 Topic 2c – Passe ng er Needs 41 Topic 2d – Trac ki ng Dela ye d Airc raft 43 Topic 2e – Trigge r Ev ents and Communications Plans 47 Topic 2f – Su ppo rt for Pass engers 49 Topic 2g – Trac ki ng Reso urce Inve ntor y 51 Topic 2h – Sk il ls A vailability 53 Topic 3a – Establish Proce dures wi th Airlines 55 Topic 3b – Establish Proce dures wi th FAA 57 Topic 3c – Establish Procedures wi th CBP 61 Topic 3d – Establish Proce dures wi th TSA 63 Topic 3e – Establish Procedures wi th Concessions 65 Topic 3f – Esta blish Pr oce dures wi th Ground Transportation 67 Topic 4a – IR OPS C oor di na tion Work shop 69 Topic 4b – IR OPS C oor di na ted Frontline Training 71 Topic 5a – Ai rcraft Status 73 Topic 5b – Trac ki ng Weat he r 75 Topic 5c – Exec ute IR OPS Co mm unication Plan s 77 Topic 5d – Exec ute Passe ng er Support Plan s 79 Topic 5e – Exec ute IR OPS Procedures wi th Airlines 81 Topic 5f – Execute IR OP S Proce dures wi th FAA 83 Topic 5g – Exec ute IR OPS Procedures wi th CBP 85 Topic 5h – Exec ute IR OPS Procedures wi th TSA 87 Topic 5i – Ex ecute IR OP S Con cessions Proce dures 89 Topic 5j – Execute IR OP S Ground Transportation Procedures 91 Topic 6a – De brie fi ng IR OP S Even t 93 Topic 6b – Ca pturing Less ons Le arne d Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Part 2 - Resource A – Topics for IROPS Plan Development 27 PA R T 2 PA R T 1 R eso u rce A R eso u rce B R eso u rce C R eso u rce D A p p en d ices B ib lio g rap h y TOPIC MATRIX FOR IROPS PLAN DEVELOPMENT In order to complete these topics, the IROPS Champion will need to coordinate with various agencies, including airlines, concessions, ground transportation, the FAA, CBP, and TSA. The following matrix outlines which topics should be sent to specific agencies in order to complete Resource B – Model IROPS Contingency Plan. Chapter Topic Airport Airlines Concessions Ground Transportation FAA TSA CBP Chapter 1 Executive Buy-In/ Get Organized 1 x x x x x x x Chapter 2 Document Current Situation 2a x x x x x x x 2b x x 2c x x x x x x 2d x x x 2e x x x 2f x x x 2g x x x x x x x 2h x x x x x x x Chapter 3 Establish Procedures to Cooperate 3a x 3b x 3c x 3d x 3e x 3f x Chapter 4 Review, Update, and Training 4a x 4b x Chapter 5 Consolidated Cooperation Actions during an Event 5a x x x 5b x x x 5c x x x x x x x 5d x x x x x x x 5e x x 5f x x 5g x x 5h x x 5i x x 5j x x Chapter 6 Capture Lessons Learned and Updating Plans 6a x x x x x x x 6b x x x x x x x Note: If your airport is joint use, you should add “Military” as an additional column in this table.

28 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

Part 2 - Resource A – Topics for IROPS Plan Development 29 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y TOPIC 1: IROPS CONTINGENCY RESPONSE COMMITTEE This topic describes guidance for establishing an IROPS Contingency Response Committee. The overall goal of the Committee is to establish and enhance contingency plans through collaborative decision making. It is essential that all local service providers not only develop their own individual contingency plans, but also participate in the IROPS Contingency Response Committee activities. The output from this topic is the population of Section 1.1 – Establishing an IROPS Contingency Response Committee of Resource B – Model IROPS Contingency Plan. Purpose: The goal of the Committee is to establish and enhance contingency plans through collaborative decision making. This will ensure that actions result in a unified level of customer care across all aviation service providers during IROPS events. The primary focus of the Committee is the integration of business processes to ensure the consistent delivery of holistic customer service during an IROPS event. The Committee is also responsible for post-event review, as well as the identification and implementation of IROPS process improvements. In addition, the Committee is responsible for identifying the additional training required to ensure the effective delivery of customer service. Process: The process of forming an IROPS Committee is threefold: 1. Chairperson designation: Airport Director/Manager provides the sponsorship and designates the chairperson of the Committee. 2. Local/regional determination: The airport should initiate an initial kick-off meeting, during which it is important that the group takes a step back and establishes realistic parameters for the Committee. The group will need to first delineate a region normally comprised of their airport as well as all reliever airports that could receive diverted aircraft from this airport (or the sending airport if the subject airport is the diversion site) in an IROPS situation. 3. Committee member nomination: Within this region, the group will then need to identify which airport departments, airlines, government agencies, reliever airports, and other aviation service providers are involved in IROPS events and customer-service-related activities. The group will need to engage these organizations so they are willing to appoint a representative to join the Committee. Format: The following suggestions for membership should be considered when establishing the IROPS Committee. It is important to have representatives from all service providers at the airport (e.g., airport operations, airport public safety agency, airlines, FAA, TSA, CBP, concessions, ground transportation, FBO). Appropriate airport representatives who look at the whole picture Appropriate airline representatives: local station managers and corporate management (this is a two- step, ongoing communication process) Appropriate government agency representatives Outsource aviation service providers (where appropriate) A chairperson, ideally a senior-level airport operations manager who can command resources as needed. • • • • •

30 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y Use the table (I ROPS Con tingenc y Response Commit tee) to populate Section 1. 1 of the Model IR OPS Contingenc y Pl an. Cont act information dur in g an IR OP S ev en t: Contact details for the IR OPS Contingenc y Response Co mm ittee and for po ints-o f- contact for agencies du ring an IR OPS event ar e recognized as bein g sensitive informat ion. Since it is desi re d that the IROP S plan be ma de available to the public, it is reco mme nded that the potentiall y sensitive 24- hour contact information be ma in tained separately in an appendix of the IR OPS plan , which will allow the info rm ation to be updated without af fecting the re ma inder of this plan (see Ap pendix D of Resource B – Mo del IR OP S Contingenc y Pl an). IROPS Contingency Response Committee Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Contact Name & Phone Number Alternate Contact Committee Chairperson Airport Operations Airlines Concessions Ground Transportation Hotel Government Agencies Public Safety Operations Diversion Airport(s) Fixed Base Operations Military (if joint-use) Emergency Response Executive Management Liaison Note : Contact details sh ow n ar e for the representative’s orga nizatio n of fice. Contact details fo r the IROPS Cont in genc y Re sponse Co mm ittee and points-of-contact for agenci es during an IROPS ev en t should be listed in Append ix D of Re source B – Model IR OPS Continge nc y Plan .

Part 2 - Resource A – Topics for IROPS Plan Development 31 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y TOPIC 2: DOCUMENT CURRENT SITUATION This topic describes guidance for gathering pertinent IROPS data that, when completed, will provide the base of your IROPS plan. This topic focuses on gathering data for the following: Reviewing existing IROPS Plans Local IROPS events history Local customer needs Local tracking of delayed aircraft Local trigger events and communication plans Local support for passengers on-board, being deplaned, and in-terminal Local tracking of inventory Local skills availability The IROPS Champion is responsible for coordinating with service providers to gather the information needed to complete the tables in this topic. Once the information is collected, it must be inserted into the appropriate tables and inserted into Resource B – Model IROPS Contingency Plan. Coordination with the IROPS Contingency Response Committee will also be necessary throughout this topic. The output from this topic is the population of Chapter 2 (sections 2.1-2.8) of Resource B - Model IROPS Contingency Plan. Each of the data collection activities is addressed separately in the following pages. • • • • • • • •

32 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y TOPIC 2a: REVI EWIN G EXISTING IROPS RESPONSE PLANS This section describes gu idance for reviewing areas of support across all organizatio ns, including cooperative response procedures related to IR OP S events. It is recognized that each of the organizations has its own plan for response to IR OP S events. It is also recognized that the Un ited States DOT’s rule s o n e nh an cing airline passe nger pr otections (14 CF R Pa rt 25 9 Enhanced Protections for Airline Passengers ) r equire air carriers to adopt ta rm ac dela y contingenc y plans and coordinate them with airports. Purp ose: To re view the IR OPS plan s of local airlines, airport operations, and FB O or ganizations as they relate to areas of coordination between organizations. The pur po se of the IR OP S Respons e Manage me nt Pr oc ess (shown in Figure 1 ) is to identi fy a nd docum ent actions requiring coordination between two or mo re aviation service pr ov iders. Jo int actions are identified that reflect both current indivi du al IR OPS plans and areas of recomm ended comm unication, collaboration, and coordination between se rvic e providers. Step 2 in the IR OP S Resp on se Manage me nt Pr ocess requires the IR OP S Contingenc y Response Co mm ittee to prov ide an assessm ent of th e airport’s aviation service prov iders’ existing IR OP S plan s to include important airport factors such as term in al capacity , equipm ent, and governm ent services . Ai rlines – Airport coordinated planning to identi fy av aila ble m eans of deplaning Ai rline – Airport coordination procedures for use of em pt y gates consistent with: Needs of other airline opera ti ons Custom er service needs Technical requirem ents L ease term s Hardst and positions for re mo te parking of aircraft Pr ocess for the airport to coordinate with airline ma nage me nt and operation control, FB Os, F AA, and flight crews to provide access to re mo te ly parked aircraft for serv icing and supply • • • Figure 1. IROPS Response Management Process.

Part 2 - Resource A – Topics for IROPS Plan Development 33 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y Pr ocedures to address pass e nger ne eds after deplanin g following lengthy ground dela y that should invo lv e the airline, the airport, governm ent agencies, and other serv ice providers Pr ocess for the airport to c oordinate with airline ma nage me nt, FB Os, F AA, flight crews, and local area em ergenc y me dical service prov iders to assist in prov iding em ergenc y me dical support and othe r special needs to passengers on re mo te ly parked aircraft Resource B – Model IR OPS Continge nc y Pl an, once co mp leted, se rv es to docum ent the Committee’s assessm ent and its continui ng c oordination and integrati on of related plans held by a ll of the avia tion service prov ider organizations at the airport. Process: As dem onstrated by Figure 2 , it takes a differe nt mi ndset for service prov id er organizations to brid ge the gap between feeling they need to go it alone with individual plans and reach an enviro nm ent of partnering for success to develop a coor dinated regional co ntingenc y plan to miti gate lengt hy ta rm ac dela ys . The first step is to enga ge airlines, airports, gov ernm en t agencies , and other aviation service prov iders to participate in an IROP S Co ntingenc y Response Co mmi ttee for a specific region. These entities should work together to de vel op a coordinated IR OPS plan that is tailored to certain operatio nal parameters , is flexible, and prov ides for optim al custom er service during a length y ta rm ac dela y. It is im perativ e that aviation servic e prov iders include other responsible parties in developing their plans. • • Figure 2. Partnering for Success.

34 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y Format: The IROPS data collection activities should focus on developing plans for things such as deplaning, gate usage, remote aircraft processes, diversion procedures, materials and service availability, and emergency needs. The results of this type of coordination can be procedures, memorandums of understanding, or other documented plans. Some other considerations include planning for: Local tracking of delayed aircraft Local trigger events and communications plans Local support for passengers on-board, being deplaned, and in-terminal Local tracking of inventory Local skills availability Coordination: The overall goal of coordination is for all service provider organizations to work together effectively to provide holistic and seamless customer service during lengthy on-board ground delays. A coordinated IROPS plan helps aviation service providers work together to solve these complex IROPS issues. However, it is important to note that effective planning is required to ensure that executive buy-in occurs in all provider organizations in order to move forward with the overall IROPS plan. Specifically, coordination accomplishes the following: Removes service gaps: When all service providers align their individual plans on behalf of the customers during IROPS events, they move from a position of “going it alone” to “partnering for success.” Improves customer service: Having a proactive and well planned / coordinated process for addressing unique customer needs is the key to effective IROPS plans. Meeting customer needs during difficult and challenging experience builds reputations of aviation providers. Understandings of coordination: The key focus of this topic and the IROPS Contingency Response Committee is recognition of joint actions that reflect both current individual IROPS plans and areas of recommended communication, collaboration, and coordination between service providers. This topic should identify and document all formal and informal understandings of coordination between these organizations, as well as individual organization standard operating procedures (SOP) related to IROPS response. Also included is any documented and agreed mutual support related to response during an IROPS event. This will typically take many forms, such as terms held in lease agreements. These documents may be bilateral between two aviation service providers. The IROPS Contingency Response Committee should provide guidance, as needed, on developing procedures between airlines, government agencies, and other service providers that address: Standard operating procedures Materials and services availability Mutually supportive actions to be taken during any type of lengthy delay event or other IROPS event • • • • • • • • • •

Part 2 - Resource A – Topics for IROPS Plan Development 35 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y Considerations for diversions (for hub airports) In addition to the coordination procedures established between the airlines serving the airport and the diversion airports in the region served by them and their code-sharing partners, coordination procedures should be established with each of the other potential diversion airports in the region. These procedures should provide in-flight notification for the diversion airport authority and local FBO during a diversion event before an aircraft lands to confirm readiness and identification of the local coordination focal point. IROPS trigger event criteria should be communicated to the diversion airports to assist them in preparation for providing support needed by the diverted aircraft and its passengers. Coordination procedures for flights refueling and continuing should be established with local ATC services, airport authorities, vendors, and government agencies as necessary. The following list includes agencies and vendors that should be considered when collecting and reviewing existing plans and procedures (as appropriate to your situation): • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Overnight accommodations: Hotels, churches, Red Cross • Military installations (if a joint-use facility) • Emergency response: Fire, law enforcement officer (LEO), emergency medical technician (EMT) The table (IROPS Response Plan Review) should be inserted in Section 2.1 of Resource B – Model IROPS Contingency Plan and should be used to describe both formal and informal understandings of coordination between organizations, as well as individual organization SOPs related to IROPS response.

36 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y IROPS Response Plan Review Plea se mo di fy this ta ble as appropri at e fo r your needs, and add addi ti on al rows as necessary . Organization Contingency Plan Description of Coordination

Part 2 - Resource A – Topics for IROPS Plan Development 37 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y TOPIC 2b: IROPS EVENT HISTORY This section describes guidance for documenting the history of local IROPS events, including lengthy on- board ground delay events. It also describes the role of various service providers in providing passenger and other customer support during IROPS events. Purpose: To provide a basis for identification and review of IROPS response activities with focus on areas needing process improvement. Process: The IROPS Champion should review local IROPS events, including lengthy on-board ground delay events. Each of these events should be considered as a potential source for information concerning: Type of IROPS event (related to local weather, other emergency, diversions, etc.) Surge: Aircraft and passengers flowing into an airport Capacity: Airport terminal becomes filled with passengers and gates become full with aircraft After-Hours: Aircraft land and passengers need to deplane at irregular hours Extended Stay: Passengers and aircraft may be stuck at airport for extended period of time. Nature of response (related to which organizations were involved or needed support from outside organization(s), unusual response actions, etc.). Response activities considered best practices (generic descriptions documented for consideration for future events, descriptions should be made available for sharing with others in the national aviation service community). Response activities needing process improvement (generic descriptions identifying recommended improvements in the IROPS plan; improvements should address actions by all appropriate organizations with specific identification of all recommended improvements to coordination between organizations and should also address any recommended revision of IROPS coordinated response training). Because IROPS events will continue to occur, this sub-section should be reviewed periodically to keep it updated and relative to the current operational environment at the airport. Format: The table (IROPS Event History) should be filled out with recent IROPS events and event descriptions and be inserted into Section 2.2 of Resource B – Model IROPS Contingency Plan. • • • • •

38 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y IROPS Event History Please modify this table as appropriate for your needs, and add additional rows as necessary. Time/Date Event Description

TOPIC 2c: PASSENGER NEEDS This section describes guidance for documenting needs of passengers and other customers during IROPS events, with special focus provided for special-needs passengers. The needs analysis is provided by consideration of general information of customer needs during IROPS events supplemented by local information derived from the IROPS event and response descriptions described in previous subsections. Purpose: To focus on the needs of passengers and other customers during IROPS events, with special attention provided for special-needs passengers. Process: The IROPS Champion should review the general information related to customer needs during IROPS events described in Part 1 – Fundamentals, with consideration for local applicability. This review should then be supplemented by review of local information derived from previous IROPS events. Following this review and documentation of general customer needs, a subsequent review should be conducted to identify any additional needed support for special-needs passengers, including availability of all elements of 14 CFR Part 382 requirements of the Americans with Disabilities Act: Availability of means for deplaning Requirements for inter-terminal transportation Accessible facilities and services Boarding assistance using mechanical lifts, ramps, or other suitable devices Special-needs passenger considerations (wheelchairs, oxygen, etc.) The categories of support for both general customer needs and special-needs passengers should also be documented for subsequent explicit identification of IROPS response actions to be taken to meet those needs. Obtaining passenger feedback: At the heart of continuous improvement is the effect that the IROPS plan has on passengers. The recommended core mechanism for determining success in meeting IROPS response goals is the implementation of a passenger feedback survey. Evaluation of survey results and trends will enable the IROPS Champion (with help from the IROPS Contingency Response Committee) to evaluate the results of current procedures and efforts and to communicate their recommendations for any identified improvements to the IROPS contingency plan. Format: The table (Passenger Needs) should be filled out with various customer needs as described above, and then inserted into Section 2.3 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 39 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y • • • • •

Passenger Needs Please modify this table as appropriate for your needs, and add additional rows as necessary. Need Descri ptio n 40 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y TOPIC 2d: TRACKING DELAYED AIRCRAFT This section describes guidance for planning and documenting the airport’s processes to describe local situations as they develop, including both flight delays and delayed aircraft on the ground. Purpose: The goal of effective tracking of delayed aircraft in the air and on the ground between airlines, ATC services, and the airport is that it provides accurate, complete, and timely information in regard to expected flight delays and developing local situations. Also, this is beneficial for providers to mitigate potential situations and for passengers to revise travel plans. It is recommended that various service provider organizations work in tandem to accurately track delayed aircraft to advance overall situational awareness, improve communication, and ultimately result in superior response to customers. When aircraft status in the air and on the ground is tracked by both airlines and the FAA and status of significantly delayed and/or diverted flights is shared with the airport, the result is shared situational awareness among the key aviation service providers. The following list includes agencies that should be included and coordinated with when tracking aircraft (as appropriate to your situation): • Government agencies: ATC services • Airport: Operations • Airlines: All airlines operating at an airport Process: It is recommended that preferred communication methods be discussed between airlines, the airport, and the FAA, with the goal of reconciling aircraft status in the air and on the ground. Once this is coordinated, tools, technology, and new procedures can be implemented to ensure effective flight tracking occurs. Some recommendations that can be implemented across regions to enhance overall communication and situational awareness include: Working with the airport, airlines, and the FAA to develop a process for tracking delayed aircraft both in the air and on the ground Developing coordination procedures between the airport and airlines for sharing aircraft status information during IROPS events Developing a plan for diverted flights Using tracking tools as an early notification of potential diversions so user organizations can plan and communicate more effectively Format: The table (Tracking Delayed Aircraft) should be filled out with the processes for tracking aircraft by various service providers as described above. Once complete, it should be inserted into Section 2.4 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 41 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y • • •

TOPIC 2d: TRACKING DELAYED AIRCRAFT This section describes guidance for planning and documenting the airport’s processes to describe local situations as they develop, including both flight delays and delayed aircraft on the ground. Purpose: The goal of effective tracking of delayed aircraft in the air and on the ground between airlines, ATC services, and the airport is that it provides accurate, complete, and timely information in regard to expected flight delays and developing local situations. Also, this is beneficial for providers to mitigate potential situations and for passengers to revise travel plans. It is recommended that various service provider organizations work in tandem to accurately track delayed aircraft to advance overall situational awareness, improve communication, and ultimately result in superior response to customers. When aircraft status in the air and on the ground is tracked by both airlines and the FAA and status of significantly delayed and/or diverted flights is shared with the airport, the result is shared situational awareness among the key aviation service providers. The following list includes agencies that should be included and coordinated with when tracking aircraft (as appropriate to your situation): • Government agencies: ATC services • Airport: Operations • Airlines: All airlines operating at an airport Process: It is recommended that preferred communication methods be discussed between airlines, the airport, and the FAA, with the goal of reconciling aircraft status in the air and on the ground. Once this is coordinated, tools, technology, and new procedures can be implemented to ensure effective flight tracking occurs. Some recommendations that can be implemented across regions to enhance overall communication and situational awareness include: Working with the airport, airlines, and the FAA to develop a process for tracking delayed aircraft both in the air and on the ground Developing coordination procedures between the airport and airlines for sharing aircraft status information during IROPS events Developing a plan for diverted flights Using tracking tools as an early notification of potential diversions so user organizations can plan and communicate more effectively Format: The table (Tracking Delayed Aircraft) should be filled out with the processes for tracking aircraft by various service providers as described above. Once complete, it should be inserted into Section 2.4 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 41 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y • • •

Tracking Delayed Aircraft Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Description 42 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

Tracking Delayed Aircraft Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Description 42 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y TOPIC 2e: TRIGGER EVENTS AND COMMUNICATIONS PLANS This topic describes guidance for establishing and documenting response procedures linked to airline trigger events and resulting communications plans in order to promote effective response to an evolving IROPS event. Recognizing that most IROPS events occur with respect to passengers while they are either on board aircraft or as they are being moved from a parked aircraft to the terminal area, definitions of trigger events are based on related IROPS practices established by local airlines. Effective response to an evolving IROPS event depends on timely shared situational awareness among all aviation service providers. Relevant IROPS information includes the early identification of a potential IROPS situation and the evolving IROPS condition as the event evolves. Key elements of communication during an IROPS event require coordinated IROPS response actions by airport operations, the airlines, ATC services, and by affected diversion airports to track and share aircraft status both in the air and on the ground. Based on the situational need, additional communications among other organizations such as TSA, CBP, concessions, and ground transportation may also be required. Each airline has its own guidelines for establishing triggers. These triggers are usually included as part of the individual airline’s IROPS plans published in compliance with the United States DOT’s “3-Hour Rule” and “4-Hour Rule.” Associated timelines may vary by airport, even within a single airline, and each will generally be tailored to accommodate operational variations. An airline’s internal guidance on trigger timelines should be consistent with its external commitments, both to passengers and to government agencies. Specifically, the airline should coordinate its triggers with the appropriate airport, TSA, and other government agencies, including CBP personnel if international flights arriving in the United States are involved. Information on these guidelines should be provided to the IROPS Champion. At trigger points, airlines generally consider the following factors when making a determination: National weather Crewmember resource planning Airfield situation Gate availability Hardstand availability Passenger disposition Purpose: Triggers are specific events or points in time during an evolving IROPS event including lengthy on- board ground delays when communication with involved stakeholders (including passengers when appropriate) is initiated in order to begin efforts to mitigate the effects of an IROPS event. Such communication is designed to evaluate the situation and reach a decision about the appropriate course of action. Part 2 - Resource A – Topics for IROPS Plan Development 43 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y • • • • • •

Process: When coordinating its IROPS plan with the IROPS Contingency Response Committee, each airline should include its trigger policies, the timelines for each trigger, and what needs to be considered at the trigger time. Format: The table (Trigger Events and Communications Plans) should be filled out with different aviation provider communication plans and trigger events. Once the table has been filled out, it should be inserted into Section 2.5 of Resource B – Model IROPS Contingency Plan. The following steps should be taken by the airport for pre-planning communications once this section has been completed: Consider history of on-board ground delay events at the airport. Determine what they are triggered by (e.g., extreme weather, airport and ATC facility related outages and causes, government system outages or slowdowns, and/or airline unplanned events). Document understanding between airlines and other members of the IROPS Contingency Response Committee for trigger events and communication. Determine how information will be communicated concerning the IROPS event (e.g., conference calls, the airport’s website, individual airlines’ websites, local news media via airport, and airline public relations departments). Develop communication plans. See Tool 13 – Sample Communication Plan in Resource C for additional support. Determine role of the airport’s public relations organization and how it will engage with various media outlets (radio, television, print) before, during, and after an event to provide up-to-date information. The following list includes agencies and vendors that should be considered when documenting and reviewing trigger events and communication plans (as appropriate to your situation): • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Overnight accommodations: Hotels, churches, Red Cross • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Sample process for communicating aircraft status: Establish and use an airport’s communication center to utilize input from local airlines and FAA in regard to expected flight delays and developing local situations to keep stakeholders informed of an IROPS event as it unfolds. The communication center should be responsible for distribution of accurate, complete, and timely information in regard to expected flight delays and developing local situations to other local service providers (beyond the airlines and FAA). 44 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y • • • • •

Trigger Events and Communications Plans Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Trigger Ev en t Resp on sible Part y Target Group(s) Co mm unication Method(s ) Co mme nts Part 2 - Resource A – Topics for IROPS Plan Development 45 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

46 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 2f: SUPPORT FOR PASSENGERS This topic describes guidance for planning and developing support capabilities and actions based on aircraft and passenger location and on duration of passenger stay both on board aircraft and in the terminal. Purpose: To ensure focus on coordinated support of passengers and other customers during an IROPS event. This focus includes, but is not limited to, the three areas of coordination identified as being United States Congressional concerns for the provision of: Support for deplaning of passengers from aircraft Sharing of facilities, including making gates available Having a sterile area available for passengers who have not yet cleared CBP Process: The IROPS Champion (with assistance from the IROPS Contingency Response Committee) reviews and documents each stage of passenger support needs based on aircraft and passenger location. This review should include local consideration of customer needs: Passengers on board aircraft (includes supplemental provision of concessions if required by airline) Passengers deplaning aircraft (includes passenger assistance and transportation to terminal from remotely parked aircraft as needed) Passengers in terminal (includes access to restrooms and concessions as needed) Passengers requiring extended delay accommodations (overnight stay in terminal and/or transportation to local hotel as needed) Additional considerations: Sharing of facilities Making gates available during IROPS event Support to special-needs passengers Having sterile area available for passengers who have not yet cleared CBP Coordination with TSA for accommodating passengers needing to leave screened area Format: The following list includes agencies and vendors that should be considered when documenting and reviewing passenger support efforts (as appropriate to your situation): • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Overnight accommodations: Hotels, churches, Red Cross • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Part 2 - Resource A – Topics for IROPS Plan Development 47 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y • • • • • • • •

The table (Support for Passe ngers) should be co mp leted and inserted into Section 2. 6 of Resource B – Mode l IR OP S Contingenc y Pl an . Support for Passengers Please modify this table as appropriate for your needs, and add additional rows as necessary. Passeng er Location Service Provid er Descri ptio n 48 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 2g: TRACKING RESOURCE INVENTORY This section describes guidance for planning and developing procedures across local organizations identifying resources (equipment and supplies) held by an airport service organization beyond those that have been planned for shared use, but that could be made available for use if requested by another airport organization during an IROPS event. This planning should include identification of the resources (equipment and supplies) that the organization believes are required to meet their response goals. It is further expected that where an organization’s plan identifies resources beyond those held by the organization, they will enter into procedures with other organizations to provide them access to such resources as needed during an IROPS event. Purpose: The purpose of this section is not to document planned inventory resources described above. Rather, its purpose is to describe the identification of inventory flexibility within the airport’s service organizations (including military installations at joint use facilities) that could be made available to another (requesting) organization during an IROPS event when the event requires resources beyond those previously identified. Process: The IROPS Champion is tasked with developing and maintaining an assessment checklist of items (equipment and supplies) held by an airport service organization that could be made available for use by another organization during an IROPS event. A few examples of equipment and supplies to inventory include tugs, towbars, airstairs, buses, food, and water. See Tool 7 – Example Resource Inventory Checklist in Resource C for additional support. Although mutual support is a recommended philosophy of an IROPS plan, it is not intended that this willingness to share unplanned access to resources among airport organizations during an IROPS event should replace comprehensive planning for response by all airport service organizations. Request for unplanned access by a local organization to another organization’s resources during an IROPS event should be evaluated during the debriefing meeting following the event (see Topic 6a: Debriefing IROPS Event) Format: The following list includes agencies and vendors that should be considered for tracking resource inventory (as appropriate to your situation): • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Overnight accommodations: Hotels, churches, Red Cross • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Part 2 - Resource A – Topics for IROPS Plan Development 49 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

The table (T racking Res our ce In ve ntor y) should be co mp leted with airport se rv ic e organizations’ cu rrent inventor y and inserted into Section 2.7 of Reso urce B – Model IR OPS Contingenc y Pl an. Tracking Resource Inventory Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Inventory Item Descri ptio n 50 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 2h: SKILLS AVAILABILITY This topic describes guidance for planning and developing procedures across local organizations identifying categories of skilled personnel employed by an airport service organization beyond those which have been planned for shared use, but that could be made available for use if requested by another airport organization during an IROPS event. This planning should include identification of skilled personnel that the organization believes is sufficient to meet its response goals. It is further expected that where an organization’s plan identifies skilled personnel beyond those employed by the organization, they will develop procedures with other organizations to provide them access to such personnel as needed during an IROPS event. Purpose: The purpose of this topic is not to document the planned skilled personnel described previously. Rather, its purpose is to describe the identification of flexibility of staffing within the airport service organizations that could be made available to another (requesting) organization during an IROPS event when the event requires skilled personnel beyond those previously identified. Examples include staff who may speak more than one language who could provide translation services if needed, or management staff who have the skills needed to operate equipment on the airfield (e.g., tugs), or airline staff who have the training necessary for food preparation if concessions need additional assistance for mass influxes of passengers. Process: The IROPS Champion is tasked with developing and maintaining an assessment checklist of categories of skilled personnel employed by an airport service organization who could be made available for use by another organization during an IROPS event. Although mutual support is a recommended philosophy of an IROPS plan, it is not intended that this willingness to share unplanned access to skilled personnel among airport organizations during an IROPS event as described in this section should replace comprehensive planning for response by all airport service organizations. Request for unplanned access by a local organization to another organization’s skilled personnel during an IROPS event should be evaluated during the debriefing meeting following the event (see Topic 6a: Debriefing IROPS Event). Format: The following list includes agencies and vendors that should be considered when documenting skills availability (as appropriate to your situation): • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Part 2 - Resource A – Topics for IROPS Plan Development 51 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

The table (Skills Av ailability) should be co mp leted wi th airport se rv ice organizatio ns’ skills availability and inserted into Section 2.8 of Resource B – Model IROP S Contingenc y Pl an. Skills Availability Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Sk il l Descri ptio n 52 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 3a: ESTABLISH PROCEDURES WITH AIRLINES This topic describes the collection and development of joint procedures with your local airlines as well as all other airlines which consider your airport for diversions. As noted in Part 1 - Fundamentals, airlines are required to coordinate their extended delay contingency plans with both scheduled airports they serve and their diversion airports. The airline contingency plans should commit sufficient resources for plan implementation, but these resources may include those usually provided by the receiving airport to implement the plan. It is recommended that the airline contingency plans be fully discussed and understood by your airport’s IROPS Contingency Response Committee. Subsequent considerations for potential impact of IROPS events resulting in surge, capacity, off-hours operation, and extended stay of aircraft should be addressed in your airport IROPS plan. The output from this topic is the population of Section 3.1.1 – Airlines of the Resource B – Model IROPS Contingency Plan. Considerations: Safety remains the top priority for your airport. Other considerations may include the following: • Establish a communications procedure with each airline to ensure timely notification of the airline’s decision to divert flights scheduled to arrive at your airport, or for the decision to divert flights to your airport that were scheduled for another airport. • The communication procedure for all diverted flights should include periodic status, continuing until such time the flight either arrives at its scheduled destination or until it has been cancelled. • During extraordinary situations, keeping the runways clear for diversions that may be low on fuel and maintaining the ability to safely park aircraft. • The next priority is to help passengers. • Many airports provide blankets and/or cots, and all ensure the availability of food, water, and toiletries. • Some airports also work with passengers experiencing disruptions to arrange for hotel accommodations and ground transportation. • Under extraordinary circumstances, airports should be able to take control of gates, unload passengers, and direct equipment to serve planes with the greatest need, regardless of company affiliation. Process: Request that each airline that serves your airport be represented on your airport IROPS Contingency Response Committee. Ensure that you have received a contingency plan from each airline that serves your airport (including those that consider your airport for diversions), review these plans, and contact individual airlines to resolve any concerns you may have. Comments are particularly important if the airline has not provided sufficient details regarding how they will deal with extended tarmac delays at your airport (e.g., hasn’t addressed who will provide ground handling services upon arrival, isn’t clear regarding who it would contact at the airport for assistance, doesn’t list who airport staff can contact at the airline to determine flight status). Part 2 - Resource A – Topics for IROPS Plan Development 53 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Note : Ensure y ou ha ve a pl an in place for uns ch eduled international flights. If y ou ha ve local CB P staff, this includes off- hours arrivals and international flights di ve rt ed from other airports. If you do not ha ve local CB P staff at y our airport, ensure an IR OP S pl an is in place with regional CB P a nd local law enforcem ent to handl e and/or offload passe ngers. Form at: Use the table (P rocedures with Ai rlines) to catalog the local airline contingenc y plans and ev aluate an y gaps in equipm ent, gate utilization, ra mp space, and/or co mm unication procedures with passengers . De termine a special pro ce dure for c oordination for nonsched uled airline flights at y our airport and fo r international di versi ons if you do not ha ve local CBP st aff at y our airport. A co py of the vari ous procedures should be included as an ap pe ndix (see Appe ndix B of Re source B – Mo del IR OP S Co ntingenc y Pl an). Procedures with Airlines Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Cont act Name Local Agre em ents 54 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 3b: ESTABLISH PROCEDURES WITH FAA This topic describes the collection and/or development of local procedures with the FAA for aircraft ground control procedures during extended tarmac delays. It also describes guidance for sharing of aircraft status between FAA and airport operations. The output from this topic is the population of Section 3.1.2 – FAA of Resource B – Model IROPS Contingency Plan. Purpose: Establish local procedures and basic guidelines for airport operator coordination with local FAA organization(s) in conjunction with local aircraft operators. Process: The FAA has issued directives to air traffic personnel pertaining to aircraft making tarmac delay requests related to the United States DOT’s rules on enhancing airline passenger protections (14 CFR Part 259 Enhanced Protections for Airline Passengers). These procedures are in addition to providing access to aircraft flight status. These directives provide guidance to aircraft operators for consideration of ground control procedures during situations related to the United States DOT’s “3-Hour Rule” and “4-Hour Rule.” Additionally, the FAA currently provides aviation service providers access to accurate, complete, and timely information in regard to expected flight delays and developing local situations. These information sources are provided on a noninterference to normal FAA operations basis. The IROPS Contingency Response Committee should confirm and document its local ATC service actions specific to IROPS events. Format: Use the table (Procedures with FAA) to catalog the procedures once they are collected/developed to include in the Model IROPS Contingency Plan. Also, the actual procedures should be included as an appendix (see Appendix B of Resource B – Model IROPS Contingency Plan). Note: Consider developing a ramp and tarmac parking plan that illustrates areas on the airfield that may become an issue in the event of an IROPS event, and other movement areas that ATC services may identify as being problematic should you receive multiple diversions. Part 2 - Resource A – Topics for IROPS Plan Development 55 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Procedures with FAA Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Cont act Name Local Agre em ents 56 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 3c: ESTABLISH PROCEDURES WITH CBP This topic describes guidance for planning and developing local procedures with the CBP for unscheduled international flights associated with IROPS events. These should include CBP coordination procedures for international aircraft arriving from abroad that land in the United States for reasons other than as a scheduled arrival and for international aircraft diverted to an airport other than the intended airport of destination. These technical stops or diversions include flights that are technical fuel stops, emergency fuel stops, weather- related stops, mechanical incidents, stops due to illness on board the aircraft, or other emergency stops, including stops for terrorist-related incidents or precautions. These procedures should include provisions for supporting unscheduled and diverted arrivals of international flights into airports not normally staffed by the CBP. Purpose: Establish local procedures and basic guidelines for the airport operator coordination with the CBP in conjunction with the FAA, TSA, and LEO personnel for the appropriate handling and reporting of international aircraft diverted for emergency or exigent circumstances. These procedures are subject to change as events may require. The output from this topic is the population of Section 3.1.3 – CBP of Resource B – Model IROPS Contingency Plan. Process: At the national level, the CBP Headquarters – Office of Field Operations developed a contingency plan to address unscheduled arrivals, including flight diversions and technical fuel stops. The Director, Field Operations has authorized the port director to allow diverted flights in accordance with CBP established procedures. In the event of a diverted international or precleared flight to an airport, the CBP will coordinate with the diverted airline and airport partners to permit deplaning passengers in the event of extended delays in accordance with the procedures below: • The diverted airline will provide initial notification to the CBP duty supervisor or watch commander. • Deplaning of passengers will take place at the Federal Inspection Station (FIS) facility at an airport. • Diverted flights that will not be processed will be secured in the transit lounge. • Airline personnel are permitted in the transit lounge to provide food service to delayed passengers. • The CBP, in coordination with airport partners, will ensure passengers remain secure in the transit lounge in the FIS area, preventing association with other passengers, domestic or foreign. • Crew changes and servicing aboard an aircraft undergoing a technical stop/diversion will be permitted, without full inspection of the passengers and baggage, if the carrier provides 100% advance passenger information (API) prior to the aircraft’s arrival. • All passengers remain on board, except for protracted stays. A “protracted stay” is generally defined as the aircraft remaining on the tarmac in excess of 2 hours where CBP personnel are stationed. • No new passengers or cargo are added at the technical stop. • CBP retains the option to require all passengers, crew, and baggage to disembark and clear through CBP passport and baggage control. Part 2 - Resource A – Topics for IROPS Plan Development 57 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Format: All international diverted aircraft under the jurisdiction of the airport area of responsibility will be closely monitored. All actions related to the aircraft, persons, and cargo on board will be coordinated with the CBP, airport, air carrier, local law enforcement, and other government agency representatives. All actions taken by the CBP, airport, air carrier, local law enforcement, or other government agencies must be immediately reported to the watch commander. Specific procedures and requirements for various situations are detailed below: CBP reporting requirements for all flight diversions: The following notifications must be made to the airport field office, border security staff, field office watch commander, and airport field watch commander: The following information is needed: • Flight number and name of the airport to which the flight has been diverted. • ETA (estimated time of arrival) at original airport, ETA at diverted airport, actual block time. • Types of security at the gate/airport to ensure passengers remain on board, or if deplaned, remain in a secure area while awaiting CBP processing and clearance. • Any types of special requests/needs by the pilot, passengers, or assistance offered by CBP personnel. • Additional updates for the aircraft (e.g., aircraft fueling, departure time). • Closeout information pertaining to flight departure time. CBP procedure for processing diverted flights to the airport: any international airline diverted to the airport due to weather may request permission from the CBP to disembark their passengers and crew into a sterile and secure area. Permission may be granted, and passengers and crew may be held in the transit lounge provided the airline: • Communicates with the watch commander as to the nature of the diversion and the anticipated length of delay. • Updates the status of the diversion upon any changes as they occur. • Controls the movement and secures the passengers from contact with any other domestic or foreign flight. • Requests and receives access to the FIS and the transit lounge in advance in order to care for its passengers. CBP procedures for extended stays/diversions – 3-/4-hour guideline: An extended stay is described as an aircraft remaining on the tarmac in excess of 3 hours, where CBP personnel are stationed. If the air carrier’s representative or aircraft pilot states that the aircraft will depart the airport within 3 hours or within 30 minutes after the third hour on the ground, or determines that deplaning would jeopardize passengers’ safety or security, the passengers can be allowed to remain on board the aircraft. Office of Field Operation personnel have the option to allow passengers to deplane at any time and remain in a secure area until the flight is cleared to depart for the original or alternate final destination to ensure the safety of the passengers. CBP field managers shall use all resources in their power to meet the 3-hour guideline. 58 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

CBP procedures for technical stop: Crew changes and servicing aboard an aircraft undergoing a technical stop will be permitted without full inspection of the passengers and baggage, provided the following conditions are met: • The carrier must provide 100% API electronic data in advance of the aircraft’s arrival if the aircraft was scheduled to arrive or stop in the United States • All passengers should remain on board, except in the event of a stay/diversion lasting more than 3 hours or if CBP field personnel determine the passengers should be deplaned for any reason, prior to 3 hours. • No new passengers or cargo are added at the technical stop. • These procedures DO NOT apply to passengers and crew on flights departing the United States for foreign countries that make an unscheduled stop in the United States due to an emergency. Note: There may still be times when these flights require CBP presence (e.g., when deportees are on board). CBP process for diverted flights to airports without a FIS: The following procedures should be developed: • Determine location of the secure area. • Develop plans to maintain security of the area. • Give passengers access to restrooms if the secure area does not have restrooms. • Ensure airport/airlines have responsibility for providing food and water to passengers while maintaining the sterility of the secure area. • Validate passenger information through law enforcement databases as applicable. • Assist with any complex immigration issues that responding officers are not able to address. • Ensure security at the gate/airport to ensure passengers remain on board, or if deplaned, remain in a secure area while awaiting CBP processing and clearance. CPB process for entry without inspection: If a passenger refuses to comply with the instructions to remain in the secured area pending CBP inspection or reboarding in lieu of CBP processing and unlawfully enters the United States without inspection, they may be subject to civil penalty and/or adverse action depending on their citizenship status. CBP procedures for handling garbage and de-catering partially cleared diverted flights: Responding CBP officers shall determine if there is regulated garbage on board the aircraft for a partially cleared diverted aircraft. CBP officers will, in coordination with the destination airport, initiate a CBP Form AI 250 to control the movement of regulated garbage to the destination airport for a partially cleared diverted flight. Use the table (Procedures with CBP) to catalog procedures once they are collected/developed to include in Resource B – Model IROPS Contingency Plan. Also, the actual procedures should be included as an appendix (see Appendix B of Resource B – Model IROPS Contingency Plan). Note: Airport staff should work with CBP to identify secure areas at the airport to be used for holding international passengers should they need to deplane. A graphic of the area(s) should be developed and included in the plan. Part 2 - Resource A – Topics for IROPS Plan Development 59 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Procedures with CBP Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Cont act Name Local Agre em ents 60 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 3d: ESTABLISH PROCEDURES WITH TSA This topic describes the collection and/or development of local procedures with the TSA to develop appropriate security measures for passengers during IROPS events. These involve the ability for passengers to avoid re-screening if they deplane due to an extended tarmac delay and for the TSA to develop contingency plans for after-hour security arrangements. Purpose: To provide a process for the airport to coordinate with the TSA for alternative security measures during IROPS events. The output from this topic is the population of Section 3.1.4 –TSA of Resource B – Model IROPS Contingency Plan. Process: The TSA is responsible for ensuring that plans are in place to have designated checkpoints opened late/early and adequately staffed to support various IROPS events. It is recognized that the Department of Homeland Security has issued procedures to TSA Federal Security Directors concerning establishing and utilizing secure areas using procedures in the Airport Security Program or Aircraft Operator Standard Security Program. It is recommended that the airport and local airlines coordinate with the TSA to establish sterile areas where delayed aircraft may deplane passengers without having to rescreen them. Example procedures – To be coordinated with the TSA for incorporation into the IROPS plan: • If passengers are deplaned into a sterile area and remain in the sterile area, they may be reboarded without additional screening. • The airport or airline may establish a sterile area without TSA presence using procedures in the Airport Security Program or Aircraft Operator Standard Security Program. • Procedures may be established to allow for the escorting of passengers outside of the sterile areas, such as to vending machines, and then returning to the sterile area without TSA screening outside of normal TSA operating hours. Format: The table (Establish Procedures with TSA) should be inserted into Section 3.1.4 of Resource B – Model IROPS Contingency Plan. Note: Airport staff should work with the TSA to identify a method of providing access to secured areas after hours, when needed. For example, if the concessions are post security and concession staff is called back after hours to serve passengers from diversion aircraft, they will need a way to pass through screening. If TSA officers are not on duty at that time, that poses a challenge. Procedures should be established with the TSA for screening after hours. Part 2 - Resource A – Topics for IROPS Plan Development 61 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Establish Procedures with TSA Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Co ntact Na me Local Agre em ents 62 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 3e: ESTABLISH PROCEDURES WITH CONCESSIONS This topic describes the collection and development of local procedures with concessions to provide service during IROPS events, including those resulting in extended passenger (and other customers) stay in the terminal area. Key considerations include agreement to remain open during extended hours and support for special-needs passengers, including infant supplies, as well as maintaining appropriate supply levels of basic needs during periods of passenger surge due to an IROPS event. The output from this topic is the population of Section 3.1.5 – Concessions of the Resource B – Model IROPS Contingency Plan. Purpose: To ensure that passenger needs of food and beverage (and potentially medicinal and family needs) are met during IROPS events. Process: Concessions should develop an IROPS plan for use during IROPS events, including: • Backup to airlines for on-board passenger support by sharing supplies • Support for special-needs passengers • Support for infants • Support for after-hours service • Implement backup staffing to respond to passenger surge Format: The Concessions IROPS Plan should be activated as required following situational notification by either an airline or by an airport-designated point-of-contact. Use the table (Establish Procedures with Concessions) to catalog the procedures with concessionaires (snack stands, restaurants, and other vendors) and then insert into Section 3.1.5 of Resource B – Model IROPS Contingency Plan. A copy of the various procedures should be included as an appendix (see Appendix B of Resource B – Model IROPS Contingency Plan). Note: The airport should consider including language in lease agreements with concessionaires that require them to provide staff to help serve passengers stuck in the terminal in the event of an IROPS occurrence. Part 2 - Resource A – Topics for IROPS Plan Development 63 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Establish Procedures with Concessions Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Cont act Name Local Agre em ents 64 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 3f: ESTABLISH PROCEDURES WITH GROUND TRANSPORTATION This topic describes the collection and/or development of local procedures with ground transportation organizations at an airport to provide service during IROPS events, including those resulting in extended passenger (and other customers) stay in the terminal area. Key considerations include agreement to provide service during extended hours and procedures for obtaining additional resources when required. Purpose: To ensure that ground transportation needs during IROPS events, including those resulting in extended passenger (and other customers) stay in the terminal area, are met during IROPS events. Process: Ground transportation organizations operating at the airport should develop procedures that address: • Support for special-needs passengers • IROPS Ground Transportation Plan for use during IROPS events • These plans should include procedures for obtaining additional resources (staffing/resources) when required • The output from this topic is the population of Section 3.1.6 – Ground Transportation of Resource B – Model IROPS Contingency Plan. Format: The ground transportation organizations should activate their IROPS Ground Transportation Plan when notified of related requirements caused by an IROPS event. Use the table (Establish Procedures with Ground Transportation) to catalog the procedures collected/developed with the local ground transportation providers (including on- and off-site rental car agencies, taxis, local mass transit, bus companies, and military vehicles if the airport is joint-use) in Resource B – Model IROPS Contingency Plan. A copy of the actual procedures should be included as an appendix (see Appendix B of Resource B – Model IROPS Contingency Plan). Note: The airport should consider including language in lease agreements with ground transportation providers that would require them to provide assistance in the event of an IROPS occurrence. Part 2 - Resource A – Topics for IROPS Plan Development 65 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Establish Procedures with Ground Transportation Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Co ntact Na me Local Agre em ents 66 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 4a: IROPS COORDINATION WORKSHOPS This topic describes recommendations for planning and sponsoring an IROPS coordination workshop. The material includes considerations for local organizations that are represented on the IROPS Contingency Response Committee. Holding periodic IROPS coordination workshops provides a common format and venue for periodic review and confirmation/update of the local IROPS plan. It is recommended that these workshops be held at least two times per year. Other regional service providers should be invited to participate as appropriate. Purpose: The goals of the IROPS coordination workshop are threefold: • To explain why planning for mitigating the effects of IROPS events on passengers is critical. • To allow participants to identify areas during lengthy delays that could benefit from increased coordination. This group discussion is helpful for expressing the underlying concepts and objectives in terms familiar to airport departments and key stakeholders. • To allow your airport participants to have an opportunity to buy into the planning process for mitigating effects of IROPS events on passenger service by having their individual concerns made a part of the coordination process. Attendance: This should not be limited to only those representatives from your airport identified earlier as being members of the IROPS Contingency Response Committee but should include other key airport personnel based on the importance of their understanding of IROPS planning. Attendees for this workshop may include individuals from the following agencies and vendors: • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Process: The airport should host workshops periodically throughout the year to coordinate with the various stakeholders outlined in previous topics. The workshop should be tailored to meet the specific needs of the individual airport IROPS activities since the previous workshop was held. See Tool 11 – Sample Workshop Agenda in Resource C for additional support. Format: The table (IROPS Coordination Workshop) should be completed and included in Section 4.1 – IROPS Coordination Workshops of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 67 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

IROPS Coordination Workshop Please modify this table as appropriate for your needs, and add additional rows as necessary. Date Work shop Na me Descri ptio n 68 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 4b: IROPS COORDINATED FRONTLINE TRAINING This topic provides guidance for conducting periodic coordinated frontline training for IROPS response at an airport. In addition to emphasis on actions requiring coordination of two or more organizations, this training provides an opportunity to test new policies, practices, and procedures. Purpose: Proper training for IROPS events ensures that all staff within a region are ready for and prepared to carry out policies, practices, and procedures in alignment with the IROPS plan. The output from this topic is the population of Section 4.2 – IROPS Coordinated Frontline Training of Resource B – Model IROPS Contingency Plan with the table (IROPS Coordinated Frontline Training) and the resulting training exercise(s) that should take place periodically to support the IROPS plan. Attendance: All frontline employees and management from all service provider organizations should be provided training on new procedures. Attendees for the IROPS contingency coordinated training may include individuals from the following agencies and vendors: • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Process: A frontline training program can be accomplished through various methods, including guidebooks, video training, and workshops. One of the most effective training exercises is using table-top scenarios to simulate real-life experiences. Format: Frontline training exercises are normally carried out in a workshop format. A sample agenda is listed below which should be tailored to meet the specific needs of each airport and each training exercise. Sample Agenda Session 1: Questions to discuss: What is the coordination process from early notification through debrief? What are the trigger points? What can be done better for you and your department? How do you and your department stay actively engaged? What can your department do to streamline/help the process? Part 2 - Resource A – Topics for IROPS Plan Development 69 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

IROPS Coordinated Frontline Training Please modify this table as appropriate for your needs, and add additional rows as necessary. IROPS Training Activity Descri ptio n 70 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5a: AIRCRAFT STATUS Aircraft status in the air and on the ground is tracked by both airlines and ATC services to provide accurate, complete, and timely information in regard to expected flight delays and developing local situations. Purpose: To outline a checklist of activities to determine aircraft status during an IROPS event. Procedures for sharing status information are documented in Section 2.4 – Tracking of Delayed Aircraft, while the output from this topic is the population of Section 5.1.1 – Aircraft Status of Resource B – Model IROPS Contingency Plan. Process: Using the table (Aircraft Status) as a template, the IROPS Champion, in cooperation with the IROPS Response Committee, can develop an aircraft status checklist that can be used to provide information on local situations. Format: The following list contains agencies that should be included and coordinated with when tracking aircraft status (as appropriate to your situation): • Government agencies: ATC services • Airport: Operations • Airlines: All airlines operating at an airport The table (Aircraft Status) can be incorporated into Resource B – Model IROPS Contingency Plan within Section 5.1.1 – Aircraft Status and used by airports, airlines, and ATC services where appropriate. Note: See Tool 10 – Technology Solutions in Resource C for additional support. Part 2 - Resource A – Topics for IROPS Plan Development 71 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Aircraft Status Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Ai rcraft St atus Acti on s 72 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5b: TRACKING WEATHER Weather patterns are tracked by the airport, airlines, and ATC services to predict potential impacts to aircraft operations and to carry out alternate operating procedures (such as diverting flights to alternate airports) to maintain the safety of the crew and passengers as well as operations staff out on the airfield. It is important for the airport to coordinate with NOAA’s National Weather Service to keep up to date on the most current weather affecting air travel or having a potential to affect air travel. Contact information for your local NOAA National Weather Service station and representative can be found in Tool 12 – National Oceanic and Atmospheric Administration (NOAA) National Weather Service (NWS) Checklist in Resource C. Purpose: To outline the roles and responsibilities of airport, airline, and ATC service staff for tracking weather and communicating status prior to and during an IROPS event. The output from this topic is the population of Section 5.1.2 – Tracking Weather of Resource B – Model IROPS Contingency Plan. Process: Using the table (Tracking Weather Patterns) as a template, the IROPS Champion, in cooperation with the IROPS Response Committee, can develop a weather tracking checklist that can be used to provide information on local situations. Format: The following list contains agencies that should be included and coordinated with when tracking weather (as appropriate to your situation): • Government agencies: ATC services, NOAA • Airport: Operations • Airlines: All airlines operating at an airport The table (Tracking Weather Patterns) can be incorporated into Resource B – Model IROPS Contingency Plan within Section 5.1.2 – Tracking Weather and used by airports, airlines, and the FAA where appropriate. Part 2 - Resource A – Topics for IROPS Plan Development 73 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Tracking Weather Patterns Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Cont act Name Weathe r Tr ac ki ng/Comm unicating Resp on sibilities 74 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5c: EXECUTE IROPS COMMUNICATION PLANS This topic helps the airport de vel op an appropriate chec klist for im plem enting an IR OP S co mm unication plan as part of the ov erall IR OP S plan. Sin ce relevant IR OPS information, including status and related situational informat ion, needs to be co mm unicated am ong appropriate airport organizations during an IR OPS event, defining a specific plan is cr it ical to the actual im plem entation. Purp ose: To describe the checklist of comm unications actions during an IR OPS even t. Process: Once completed, the airport should use the table (Execute IROPS Communication Plans) as a guide for the types of communication actions necessary, related to the various service providers at the airport, to identify methods of communication and specific activities to be carried out by each. Key elements of communication plans of airport service organizations are documented in Section 2.5 – Trigger Events and Communication Plans of Resource B – Model IROPS Contingency Plan. The output from this topic is the population of Section 5.2.1 – IROPS Communications Plans of Resource B – Model IROPS Contingency Plan. Form at: The following lis t includes agencies and ve ndors that should be considered when executing comm unication plans (as ap pr opriate to y our situation): • Ai rlines: Al l airlines operating at an airpor t • Govern me nt age ncies: F AA, TS A, CB P • Con cessionaires: Sn ack sta nds, restaurants, stores • Fixed ba sed operator: Lo cal FB O • Ground transportation: Re ntal cars (on- and off- site), taxis, local ma ss transit, bus co mp anie s • Overnight accommodations: Ho tels, churches, Red Cros s • Military installations (if a joint- use facility ) • Em ergency re sponse: Fi re, LE O, EM T Co mp letion of the table (I ROPS Co mm unication Pl ans) prov ides the necessary guidance to populate Section 5.2.1 of Reso urce B – Mo de l IR OP S Continge nc y Pl an . Part 2 - Resource A – Topics for IROPS Plan Development 75 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Execute IROPS Communication Plans Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Co mm unications Action s 76 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5d: EXECUTE PASSENGER SUPPORT PLANS This topic addresses the development of a checklist to support the procedures necessary to accommodate passengers and other customers at the airport during IROPS events, including those times when they are: • On-board aircraft • Deplaning aircraft • In the terminal • In need of ground transportation • In need of hotel accommodations Purpose: To define a checklist of activities to provide support procedures for passengers and other customers at the airport during IROPS events, including the four primary situations where passengers may require support. Process: Once completed, the table (Passenger Support) should highlight tasks and associated responsible parties that should be considered and included in the support of passenger needs. Procedures for passenger support are documented in Section 2.6 – Support for Passengers of Resource B – Model IROPS Contingency Plan. The output from this topic is the population of Section 5.2.2 – Passenger Support Plans in Resource B – Model IROPS Contingency Plan. Format: The following list includes agencies and vendors that should be considered when executing passenger support plans (as appropriate to your situation): • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Overnight accommodations: Hotels, churches, Red Cross • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Completion of the table (Passenger Support) provides the necessary guidance to populate Section 5.2.2 of Resource B – Model IROPS Contingency Plan. This checklist should be evaluated at least annually to address any changes that may be necessary to accommodate changes in IROPS passengers’ support needs. Part 2 - Resource A – Topics for IROPS Plan Development 77 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Passenger Support Please modify this table as appropriate for your needs, and add additional rows as necessary. Passeng er Location Service Provid er Descri ptio n 78 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5e: EXECUTE IROPS PROCEDURES WITH AIRLINES This topic describes the interactive coordination between your airport and your local airlines, as well as all other airlines that consider your airport for diversions as it is carried out during an IROPS event. As noted in Part 1 – Fundamentals of IROPS Planning, airlines are required to plan for allowing passengers on board aircraft experiencing extended delays to deplane no longer than specified by DOT rules. At the time of this writing, this time period is 3 hours for domestic and 4 hours for international flights. You should confirm the latest specifics on this requirement. Considerations: Following the procedures previously documented in Topic 3a – Establish Procedures with Airlines, your airport IROPS plan should address how you will maintain shared situational awareness among all local service providers. Since the response triggering event for most of your providers is the decision of an airline to deplane passengers due to an extended tarmac delay, a key consideration is the timely notice that such an event is likely to occur. Other considerations may have been identified during your coordinated IROPS planning. These should be documented to ensure their consideration during development of specific procedures for each of your airport’s associated airlines. Purpose: To create a checklist of activities to implement airline support during an IROPS event. The output from this topic is the population of Section 5.2.3 – Procedures with Airlines of Resource B – Model IROPS Contingency Plan. Format: Completion of the table (Execute IROPS Procedures with Airlines) provides the necessary guidance to populate Section 5.2.3 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 79 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Execute IROPS Procedures with Airlines Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization (24/7 Contact #) Local ag reem ent(s) 80 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5f: EXECUTE IROPS PROCEDURES WITH FAA This topic addresses the coordination of specific activities with the FAA that are to be carried out during an IROPS event. Purpose: To describe the checklist of activities to implement FAA support during an IROPS event. The output from this topic is the population of Section 5.2.4 – Procedures with FAA. Process: ATC services have agreed to implement aircraft ground control procedures pertaining to aircraft making tarmac delay requests related to the United States DOT’s rules on enhancing airline passenger protections (14 CFR Part 259 Enhanced Protections for Airline Passengers). Additionally, the FAA currently provides aviation service providers access to accurate, complete, and timely information in regard to expected flight delays and developing local situations. This information is provided as long as it does not interfere with normal FAA operations. Procedures for local ATC service to implement specific measures during IROPS events have been previously documented in Topic 3b – Establish Procedures with FAA. Format: Use the table (Execute IROPS Procedures with FAA) to catalog a checklist of support activities that are to be carried out with the FAA; the completed table populates Section 5.2.4 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 81 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Execute IROPS Procedures with FAA Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization (24/7 Contact #) Local ag reem ent(s) 82 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5g: EXECUTE IROPS PROCEDURES WITH CBP This topic addresses the coordination of specific activities with the CBP that are to be carried out during an IROPS event. Purpose: To describe checklists of activities to implement CBP support during an IROPS event. The output from this topic is the population of Section 5.2.5 – Procedures with CBP of Resource B – Model IROPS Contingency Plan. Process: The CBP organization at the airport has agreed to implement appropriate procedures for unscheduled international flights associated with IROPS events. These include CBP coordination procedures for international aircraft arriving from abroad that land in the United States for reasons other than as a scheduled arrival and for international aircraft diverted to an airport other than the intended airport of destination. These technical stops or diversions include flights that are technical fuel stops, emergency fuel stops, weather- related stops, mechanical incidents, stops due to illness on board the aircraft, or other emergency stops, including stops for terrorist-related incidents or precautions. The procedures include provisions for supporting unscheduled and diverted arrivals of international flights into airports not normally staffed by the CBP. Procedures for CBP implementing specific local measures during IROPS events have been previously documented in Topic 3c – Establish Procedures with CBP. Format: Use the table (Execute IROPS Procedures with CBP) to catalog a checklist of support activities that are to be carried out with the CBP; the completed table populates Section 5.2.5 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 83 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Execute IROPS Procedures with CBP Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization (24/7 Contact #) Local ag reem ent(s) 84 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5h: EXECUTE IROPS PROCEDURES WITH TSA This topic addresses the coordination of specific activities/procedures with the TSA that are to be carried out during an IROPS event. Purpose: To describe the checklist of activities to implement TSA support during an IROPS event. The output from this topic is the population of Section 5.2.6 – Procedures with TSA of Resource B – Model IROPS Contingency Plan. Process: The TSA organization at the airport has agreed to implement appropriate security measures for passengers during IROPS events. These involve the ability for passengers to avoid rescreening if they deplane due to an extended tarmac delay and for the TSA to develop contingency plans for after-hour security arrangements. It is recognized that the Department of Homeland Security has issued procedures to TSA Federal Security Directors concerning establishing and utilizing secure areas using procedures in the Airport Security Program or Aircraft Operator Standard Security Program. Procedures for the TSA implementing specific local measures during IROPS events have been previously documented in Topic 3d – Establish Procedures with TSA. Format: Use the table (Execute IROPS Procedures with TSA) to catalog a checklist of support activities/procedures that are to be carried out with TSA; the completed table populates Section 5.2.6 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 85 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Execute IROPS Procedures with TSA Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization (24/7 Contact #) Local ag reem ent(s) 86 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5i: EXECUTE IROPS CONCESSIONS PROCEDURES This topic addresses the coordination of specific activities with concessionaires (including snack stands, restaurants, and other vendors) that are to be carried out during an IROPS event. Purpose: To create a checklist of activities to implement concessions support during an IROPS event. The output from this topic is the population of Section 5.2.7 – Concessions Procedures of Resource B – Model IROPS Contingency Plan. Process: Concessions at the airport have agreed to provide service during IROPS events, including those resulting in extended passenger (and other customers) stay in the terminal area. Key considerations include agreement to remain open during extended hours and support for special-needs passengers, including infant supplies, as well as maintaining appropriate supply levels of basic needs during periods of passenger surge due to an IROPS event. Procedures for concessionaires providing specific support during IROPS events have been previously documented in Topic 3e – Establish Procedures with Concessions. Format: Completion of the table (Execute IROPS Procedures for Concessions) provides the necessary guidance to populate Section 5.2.7 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 87 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Execute IROPS Procedures for Concessions Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization (24/7 Contact #) Local agreement(s) Corporate Agreements 88 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 5j: EXECUTE IROPS GROUND TRANSPORTATION PROCEDURES This topic addresses the coordination of specific activities with ground transportation agencies that are to be carried out during an IROPS event. Purpose: To describe the checklist of activities to implement ground transportation support during an IROPS event. The output from this topic is the population of Section 5.2.8 – Ground Transportation Procedures of Resource B – Model IROPS Contingency Plan. Process: Ground transportation organizations (including on- and off-site rental car agencies, taxis, local mass transit, bus companies, and military vehicles if the airport is joint-use) at the airport have agreed to provide service during IROPS events, including those resulting in extended passenger (and other customers) stay in the terminal area. Key considerations include agreement to provide service during extended hours and procedures for obtaining additional resources when required. Procedures for ground transportation organizations providing specific support during IROPS events have been previously documented in Topic 3f – Establish Procedures with Ground Transportation. Format: Use the table (Execute IROPS Procedures for Ground Transportation) to catalog a checklist of support activities that are to be carried out with ground transportation; the completed table populates Section 5.2.8 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 89 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Execute IROPS Procedures for Ground Transportation Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization (24/7 Contact #) Local ag reem ent(s) Co rp orate Ag reem ents 90 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 6a: DEBRIEFING IROPS EVENT This topic addresses the debriefing activities that should be carried out with all aviation service providers following an IROPS event. Purpose: The purpose of the debriefing session is to review response performance following a major IROPS event. This allows service provider organizations to assess and analyze all aspects of response, to document lessons learned, and to improve performance by sustaining strengths and correcting weaknesses. When necessary, performance improvements should be incorporated into the IROPS plan, and staff training should be provided on any new procedures. Additionally, technology and resources should be evaluated as part of the review to determine if either should be enhanced to assist in improving IROPS event response. It is recommended these sessions be held after every major IROPS event. The emphasis on debrief should be on what airport organizations can do better for the next event. The list below includes agencies and vendors that should be invited to participate, as appropriate, depending on their involvement in the IROPS event: • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP, NOAA • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Process: Each organization should first hold a debriefing meeting with its management to review its response to the IROPS event. (Generally this should occur within 48 hours following the conclusion of the IROPS event.) A sample list of debriefing questions can be found in Tool 17 – After an Event Debrief in Resource C. Following its internal management briefing, each organization should report its findings (including any lessons learned) and recommendations to the IROPS Champion and the IROPS Contingency Response Committee for review. The Committee should consider if further study is required to fully understand the effectiveness of the airport’s response. Results of the review (and study if required) should be considered by the Committee to determine if any revisions are required in the IROPS plan. The Committee should re-distribute the IROPS plan following any required revisions. Format: Debriefings should cover analysis of the effectiveness of staffing, resources, equipment, and technology used during response to the IROPS event. Use the table (Debriefing IROPS Event) to document debriefing actions with airport service providers; the completed table populates Section 6.1 of Resource B – Model IROPS Contingency Plan. Part 2 - Resource A – Topics for IROPS Plan Development 91 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Debriefing IROPS Event Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Deta il 92 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

TOPIC 6b: CAPTURING LESSONS LEARNED This topic describes considerations recommended for discovering lessons learned after an IROPS event. The material includes considerations for airport service organizations that are represented on the IROPS Contingency Response Committee. Purpose: The primary purpose of gathering lessons learned during an IROPS event is to document what worked and what did not. Lessons learned (both good and bad) should be expected to surface from debriefing meetings held after every major IROPS event. Process: Each service provider organization should review all aspects of their organization’s response to an IROPS event. Generally, this review precedes a debriefing to the organization’s management shortly after the conclusion of the event. During this process, each organization should document lessons learned, including what worked and what did not. Following their internal management debriefing, each airport organization should report a summary of their findings and recommendations to the IROPS Champion and the IROPS Contingency Response Committee. The Committee should consider the debriefing reports from each major IROPS event to identify any additional lessons learned from examples of coordinated response by airport organizations. The IROPS Champion should compile and distribute any resulting new lessons learned following an IROPS event. Periodically, a summary of lessons learned should be shared with other airports in the general aviation community. Format: Use the table (Capturing Lessons Learned) to catalog lessons learned and actions that need to be taken by agencies and vendors following an IROPS event; the completed table populates Section 6.2 of Resource B – Model IROPS Contingency Plan. Agencies and vendors that should be considered (as appropriate to your situation) when documenting lessons learned are listed below: • Airlines: All airlines operating at an airport • Government agencies: FAA, TSA, CBP, NOAA • Concessionaires: Snack stands, restaurants, stores • Fixed based operator: Local FBO • Ground transportation: Rental cars (on- and off-site), taxis, local mass transit, bus companies • Military installations (if a joint-use facility) • Emergency response: Fire, LEO, EMT Part 2 - Resource A – Topics for IROPS Plan Development 93 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Capturing Lessons Learned Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Deta il 94 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

Part 2 – Resource B – Model IROPS Contingency Plan 95 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y RESOURCE B – MODEL IROPS CONTINGENCY PLAN (AIRPORT NAME) IROPS Contingency Plan Date adopted Date of final revision

96 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y Document Revision Revision Date Content Revision Date Content

CONTENTS 99 INTRODUCTION 101 C HAPTER 1 – EXECUTIVE BUY-IN/G ET ORGAN IZED 101 1.1 Establis hi ng an IROPS Co nti nge nc y Response Co mm itte e 103 C HAPTER 2 – DOCUMENT CURRENT SITUATIO N 103 2.1 Re vi ew ing Existi ng IROPS Response Plans 103 2.2 Re vi ew ing Lo cal IROPS Events and As se ss in g Lo cal Situation 104 2.3 Pa ssenger Needs during an IROPS Ev en t 104 2.4 Tr acking of Dela ye d Ai rcra ft 104 2.5 Tr igger Even ts and Co mm unica tions Pl ans 105 2.6 Su pport fo r Pa ssenge rs 105 2.7 Tr acking Inventor y 105 2.8 Sk ills Availability 107 C HAPTER 3 – ESTABLISH PROCEDURES TO COOPER AT E 107 3.1 Coope ration Proc ed ures 107 3.1.1 Airlines 107 3.1.2 FAA 107 3.1. 3 C BP 108 3.1.4 TS A 108 3.1.5 Co ncessions 108 3.1.6 Gro und Transportati on 109 3.2 Ot her Pr ov iders to Consid er 111 C HAPTER 4 – REVIEW , UP DATE, AND TR AI NING 111 4.1 IROPS Coor di natio n Work sh op 111 4.2 IROPS Coor di nate d Fron tl ine Tr aining 113 C HAPTER 5 – CONSOLIDA TED COOPER AT ION AC TI ONS DURING AN EVENT 113 5.1 Mon itoring IROP S Ev en t Indicators 114 5.1.1 Aircraft Status 114 5.1.2 Tracki ng We ather 114 5.2 Ex ecuting IROPS Plans a nd Pr ocedures 115 5.2.1 IROPS Communications Plans 115 5.2.2 Passenger Support Plans 115 5.2.3 Procedures with Airlines 115 5.2.4 Procedures with FAA 116 5.2.5 Procedures with CBP 116 5.2.6 Procedures with TSA 116 5.2.7 Co ncessions Procedures 116 5.2.8 Gro und Transportatio n Procedures 116 5.2.9 Procedures with Other Providers 117 C HAPTER 6 – CAPTURE LESSONS LEAR NE D AN D UPDATING PLANS 117 6.1 Afte r an IR OPS Event 117 6.2 Less ons L ear ne d Part 2 – Resource B – Model IROPS Contingency Plan 97 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

119 APPENDICES 121 Appendix A – Compliance Matrix of (AIRPORT NAME) IROPS Contingency Plan with DOT Model Contingency Plan 123 Appendix B – Reference Documents 125 Appendix C – Status of Plan Details 127 Appendix D – Contact Details for (AIRPORT NAME) IROPS Contingency Response Committee and Points of Contact for Agencies during an IROPS Event 98 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

INTRODUCTION Purpose This document provides the coordinated IROPS Contingency Plan for (AIRPORT NAME). It was developed by the airport’s IROPS Contingency Response Committee under the sponsorship of Airport Operations. Membership in (AIRPORT NAME)’s IROPS Contingency Response Committee comprises representatives from each of (AIRPORT NAME)’s aviation service providers. The committee recognizes that individual plans and a coordinated effort by the airlines, airports, government agencies, and other aviation service providers is essential to successfully minimizing the impact of IROPS events on passengers. This coordinated contingency management plan provides a common point of focus for (AIRPORT NAME)’s coordinated response to IROPS events. The emphasis for this plan is the identification and documentation of areas of contingency activities of (AIRPORT NAME)’s aviation service providers that require support from one or more service provider organizations. The plan format follows the recommendations provided in ACRP Report 65: Guidebook for Airport Irregular Operations (IROPS) Contingency Planning. (AIRPORT NAME) has recognized the importance of the guidance provided by the U.S. Department of Transportation (DOT) and its Model Contingency Plans to Deal with Lengthy Onboard Ground Delays. To this end, a compliance matrix is provided in Appendix A to relate specific sections of the Model Contingency Plan to those of this document. Use of Terms The following is a list of terms and definitions used throughout this Model Plan and associated topic worksheets. See the glossary contained in ACRP Report 65: Guidebook for Airport Irregular Operations (IROPS) Contingency Planning for additional terms and definitions. Irregular Operations (IROPS) – Exceptional events that require actions and/or capabilities beyond those considered usual by aviation service providers. Generally speaking, an impact of these events is the occurrence of passengers experiencing delays, often in unexpected locations for an undetermined amount of time. Examples include extreme weather events (such as snowstorms, hurricanes, tornados), geological events (such as earthquakes, volcanoes), and other events (such as power outages or security breaches). Passengers – Includes people traveling, service animals in the cabin, and live cargo onboard aircraft and in the terminal area. Customers – Includes both passengers and other non-aviation service personnel such as meeters and greeters who are in the terminal area. FAA – Federal Aviation Administration - Please note that for the purposes of this guidebook, references to the FAA include all forms of air traffic control (ATC) services. CBP – Customs and Border Protection TSA – Transportation Security Administration Part 2 – Resource B – Model IROPS Contingency Plan 99 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

Service Providers – All entities at an airport that provide services for customers and passengers including but not limited to: airports, airlines, concessionaires, ground transportation agencies, government agencies, fixed base operators (FBO), overnight accommodations, emergency response, military (if joint-use facility), and diversion airports. Passenger Needs Needs of passengers, both on board aircraft on the ground or in the airport terminal during lengthy delay or other IROPS events, vary and normally require the attention of more than one party to be met. By understanding the needs of passengers during such delays, (AIRPORT NAME), diversion airports, airlines, government agencies, and other aviation service providers can take appropriate steps to anticipate and address such needs Causes of IROPS Events Causes of IROPS events can include a number of conditions such as extreme weather, geological events, reduction of airport facility capacity, aircraft mechanical problems, and labor issues. The impacts of IROPS events include flight delays, cancellations, and diversions resulting in potentially adverse impacts on passengers and other airport customers. In addition to impacts on passengers, IROPS events also have an impact on airport operations. As noted in the guidebook, there are four phases of impact during an IROPS event that must be planned for: Surge • • • • Capacity Off-hours Extended stay Each IROPS event is unique, and airlines, diversion airports, government agencies, and other aviation service providers will benefit from the (AIRPORT NAME) IROPS Contingency Plan accounting for diverse IROPS characteristics by adapting to changing conditions. Planning for Contingency Response The purpose of the (AIRPORT NAME) IROPS response management process is to identify and document actions requiring coordination between two or more aviation service providers. Joint actions are identified that reflect both current individual contingency plans and areas of recommended communication, collaboration, and coordination between service providers. 100 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

CHAPTER 1 – EXECUTIVE BUY-IN/GET ORGANIZED Activities described in this chapter provide for: The establishment of • • • • the (AIRPORT NAME) IROPS Contingency Response Committee Establishment of 24/7 contact/notification list Documentation of procedures with airlines, government agencies, and support organizations Conducting workshops and training (including table-top exercises) 1.1 Establishing an IROPS Contingency Response Committee The (AIRPORT NAME) IROPS Contingency Response Committee has been established following the guidelines of the DOT’s Model Contingency Plan. (AIRPORT NAME)’s (ORGANIZATION and TITLE) provides the sponsorship and designates the chairperson of the Committee. The goal of the committee is to establish and enhance contingency plans through collaborative decision making. This will ensure that actions result in a unified level of customer care across all (AIRPORT NAME) aviation service providers during IROPS events. Members of the (AIRPORT NAME) IROPS Contingency Response Committee include representatives of all local aviation and customer service provider organizations. Organizations and representatives are shown in the IROPS Contingency Response Committee table along with their 24/7 contact and notification information. Insert completed table from Topic 1: IROPS Contingency Response Committee Note to User: Tables needed to complete each of the sections in this Model Plan are provided in Resource A – Topics for IROPS Plan Development, and they are identified in this Model Plan with the following icon: Part 2 – Resource B – Model IROPS Contingency Plan 101 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

102 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

CHAPTER 2 – DOCUMENT CURRENT SITUATION The IROPS data collection activities focus on: Re• • • • • • • viewing existing IROPS response plans from service providers, including airlines, government agencies, and support organizations Local IROPS event history Local customer needs Local tracking of delayed aircraft Local trigger events and communications plans Local support for passengers on board, being deplaned, and in-terminal Lo • cal tracking of inventory Local skills availability 2.1 Reviewing Existing IROPS Response Plans It is recognized that (AIRPORT NAME)’s organizations may have their own plans for response to IROPS events. It is also recognized that United States DOT’s rules on enhancing airline passenger protections (14 CFR Part 259 – Enhanced Protection for Airline Passengers) require air carriers to adopt tarmac delay contingency plans and coordinate those plans with airports. The purpose of this section is to identify the several IROPS plans of local airlines, airport operations, and FBO organizations as they relate to areas of coordination between organizations. The Review Existing IROPS Response Plans table describes both formal and informal understandings of coordination between these organizations, as well as individual organization Standard Operations Procedures (SOPs) related to IROPS response. Descriptions of procedures with concessions, ground transportation, and government agencies (FAA, TSA, and CBP) are found in Sections 3.1.1 through 3.1.5 of this plan. Insert completed table from Topic 2a: Reviewing Existing IROPS Response Plans 2.2 Reviewing Local IROPS Events and Assessing Local Situation The IROPS Event History table describes the history of local IROPS events, including lengthy onboard ground delay events. It also describes the role of various service providers in providing passenger and other customer support during IROPS events. The purpose of this history is to provide a basis for identification and review of IROPS response activities with focus on areas needing process improvement. Insert completed table from Topic 2b: IROPS Event History Part 2 – Resource B – Model IROPS Contingency Plan 103 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

2.3 Passenger Needs during an IROPS Event The Passenger Needs table focuses on needs of passengers and other customers during IROPS events, with special focus provided for special needs passengers. The needs analysis is provided by consideration of general information of customer needs during IROPS events. Insert completed table from Topic 2c: Passenger Needs 2.4 Tracking of Delayed Aircraft The Tracking Delayed Aircraft table describes (AIRPORT NAME) processes providing accurate, complete, and timely information in regard to expected flight delays including diversions. These processes describe local situations as they develop, including both flight delays and delayed aircraft on the ground. Insert completed table from Topic 2d: Tracking Delayed Aircraft 2.5 Trigger Events and Communications Plans Effective response to an evolving IROPS event depends on timely shared situational awareness among all aviation service providers. Relevant IROPS information includes the early identification of a potential IROPS situation and the evolving IROPS condition as the event evolves. Key elements of communication during an IROPS event require coordinated IROPS response actions by airport operations, the airlines, ATC services, and by affected diversion airports to track and share aircraft status both in-air and on-ground. Based on the situational need, additional communications among other organizations such as the TSA, CBP, concessions, and ground transportation may also be required. The Trigger Events and Communication Plans table describes shared information, including aircraft delay tracking performed by airlines, the FAA, (AIRPORT NAME) airport operations, and diversion airports. Insert completed table from Topic 2e: Trigger Events and Communications Plans 104 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

2.6 Support for Passengers The key goal of the (AIRPORT NAME) IROPS plan is to ensure focus on coordinated support of passengers and other customers during an IROPS event. Three areas of coordination recognize U.S. Congressional concerns for the provision of: Support for deplaning of pass• • • engers from aircraft Sharing of facilities, including making gates available Having a sterile area available for passengers who have not yet cleared CBP The Support for Passengers table describes passenger coordinated support for passengers at airports while they are on board aircraft, during their deplaning (especially from remote parking areas), in the terminal, and when they need ground transportation. Insert completed table from Topic 2f: Support for Passengers 2.7 Tracking Inventory This section describes guidance for planning and developing procedures across local organizations identifying resources (equipment and supplies) held by an airport service organization beyond those which have been planned for shared use, but that could be made available for use if requested by another (AIRPORT NAME) organization during an IROPS event. Descriptions of understandings of planned coordination related to sharing of resources are listed in Section 2.1 – Reviewing Existing IROPS Response Plans. The Tracking Resource Inventory table describes specific categories of resources that have been identified as being available for shared use. Insert completed table from Topic 2g: Tracking Resource Inventory 2.8 Skills Availability This section describes guidance for planning and developing procedures across local organizations identifying categories of skilled personnel employed by an airport service organization beyond those which have been planned for shared use, but that could be made available for use if requested by another (AIRPORT NAME) organization during an IROPS event. Descriptions of understandings of planned coordination related to sharing of skilled staff are listed in Section 2.1 – Reviewing Existing IROPS Response Plans. The Skills Availability table describes specific categories of skilled personnel which have been identified as being available for shared use. Insert completed table from Topic 2h: Skills Availability Part 2 – Resource B – Model IROPS Contingency Plan 105 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

106 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

CHAPTER 3 – ESTABLISH PROCEDURES TO COOPERATE The following sections document the establishment of operating procedures with service providers (e.g., airlines, FAA, CBP, TSA, concessions, ground transportation) for use during IROPS events. 3.1 Cooperation Procedures There are a group of service providers that are considered to be typically found at airports that are vital in local IROPS planning efforts. Coordination with these entities (identified in the following sections) is critical in order to establish procedures that will be followed during an IROPS event. 3.1.1 Airlines It is recognized that the DOT has issued a rulemaking that requires airlines to adopt tarmac delay contingency plans and coordinate them with both scheduled airports they serve and their diversion airports. The Establish Procedures with Airlines table describes airline procedures specific to IROPS events for each airline operating out of the airport. Appendix B contains copies of specific airline procedures and tarmac delay contingency plans on file. Insert completed table from Topic 3a: Establish Procedures with Airlines 3.1.2 FAA It is recognized that FAA has issued directives to air traffic personnel pertaining to aircraft making tarmac delay requests related to United States DOT’s 14 CFR Part 359 Enhanced Protection for Airline Passengers. The FAA has also established procedures allowing airports access to aircraft flight status. The Establish Procedures with FAA table describes (AIRPORT NAME) FAA actions specific to IROPS events. Appendix B contains copies of specific procedures with the FAA. Insert completed table from Topic 3b: Establish Procedures with FAA 3.1.3 CBP It is recognized that CBP has issued guidance to directors of field operations concerning passengers on diversion flights, including those into airports not normally staffed by CBP. The Establish Procedures with CBP table describes (AIRPORT NAME) CBP procedures specific to IROPS events. Appendix B contains copies of specific procedures with the CBP. Insert completed table from Topic 3c: Establish Procedures with CBP Part 2 – Resource B – Model IROPS Contingency Plan 107 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

3.1.4 TSA It is recognized that the Department of Homeland Security has issued procedures to TSA Federal Security Directors concerning establishing and utilizing secure areas using procedures in the Airport Security Program or Aircraft Operator Standard Security Program. The Establish Procedures with TSA table describes (AIRPORT NAME) TSA procedures specific to IROPS events. Appendix B contains copies of specific procedures with the FAA. Insert completed table from Topic 3d: Establish Procedures with TSA 3.1.5 Concessions Concessions at (AIRPORT NAME) have been requested to agree to provide service during IROPS events, including those resulting in extended passenger (and other customers) stay in the terminal area. Key considerations include agreement to remain open during extended hours and support for special-needs passengers, including new infant supplies. The Establish Procedures with Concessions table describes specific concessions support procedures identified as being available during IROPS events. Appendix B contains copies of specific concession procedures. Insert completed table from Topic 3e: Establish Procedures with Concessions 3.1.6 Ground Transportation Ground transportation organizations at (AIRPORT NAME) have been requested to agree to provide service during IROPS events, including those resulting in extended passenger (and other customers) stay in the terminal area. Key considerations include agreement to provide service during extended hours and procedures for obtaining additional resources when required. The Establish Procedures with Ground Transportation table describes specific ground transportation support procedures identified as being available during IROPS events. Appendix B contains copies of specific ground transportation procedures. Insert completed table from Topic 3f: Establish Procedures with Ground Transportation 108 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

3.2 Other Prov ider s to Consid er Above and bey ond the service prov iders identified in the prev ious section, several other entities should be coordinated with, as appropriate to (A IR PORT NA ME ). The list below highlig ht s so me of these service prov iders that should be considered when establishing procedures to follow during IROP S events. Al ternate transportation providers (mass transi t, bussing companies, off-s ite rental car agencies) Ov ernight acco mm odations (nearby hotels* ) Military installations (if joint- use) FB Os Refueler s Off- site restaurants Em ergenc y response (L EO, fire, EMT) Red Cros s FE MA Special needs se rvice provid ers (wheelchairs, oxy gen, etc.) • • • • • • • • • • * * Nearly every ma jor city and hub airport has a ho tel service which m onitors the av ailability of hotel ro om s in the local area. Ob tain a local and/or national co ntact to pr ov ide hotel availabi li ty when required. Note to User: Alth ou gh no sp ecif ic topics are ava ila ble in Re so ur ce A – To pi cs for IROP S Pl an De ve lo pment for these addi ti onal pr ov id er s, you ca n copy and mo dify an y of th e tables in Ch ap ter 3 to ad dr es s any ad dit io nal serv ic e pr oviders, as ap pr op riat e to yo ur ai rpor t. Part 2 – Resource B – Model IROPS Contingency Plan 109 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

110 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

CHAPTER 4 – REVIEW, UPDATE, AND TRAINING The (AIRPORT NAME) IROPS Plan should be updated periodically throughout the year with improved practices, procedures, and coordinated response. In order for this to happen, the IROPS Contingency Response Committee should host coordination workshops and training at least a couple times annually. 4.1 IROPS Coordination Workshops Periodic IROPS coordination workshops are held at (AIRPORT NAME) providing a common format and venue for periodic review and confirmation/update of local IROPS plans. The (AIRPORT NAME) will determine the frequency and specific agenda for these meetings, as appropriate. The IROPS Coordination Workshop table describes (AIRPORT NAME) plans for holding these workshops. Appendix B contains copies of previous workshop summaries that can be referenced. Insert completed table from Topic 4a: IROPS Coordination Workshops 4.2 IROPS Coordinated Frontline Training Periodic coordinated frontline training for IROPS response is held at (AIRPORT NAME). In addition to emphasis on actions requiring coordination of two or more organizations, this training provides an opportunity to test new policies, practices, and procedures. During the annual or biannual security badging process at (AIRPORT NAME), IROPS training and/or procedure updates have been reviewed with appropriate airport departments. The IROPS Coordinated Frontline Training table describes (AIRPORT NAME) plans for holding this training. Appendix B contains copies of previous training exercises that can be referenced. Insert completed table from Topic 4b: IROPS Coordinated Frontline Training Part 2 – Resource B – Model IROPS Contingency Plan 111 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

112 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

CHAPTER 5 – CONSOLIDATED COOPERATION ACTIONS DURING AN EVENT The joint actions occurring during an IROPS event are described in the following diagram. The (AIRPORT NAME) IROPS Contingency Response Committee ensures the capability for coordinating shared aircraft status information. Notification of relevant aspects of aircraft status are provided to appropriate aviation service provider organizations during an IROPS event by the (AIRPORT NAME) communication center or point of contact, as appropriate. 5.1 Monitoring IROPS Event Indicators While some IROPS events are unpredictable (such as power outages, security breaches), many can be handled successfully if service providers are actively anticipating an event. Certain actions taken by service providers on a constant basis can position them well to handle an IROPS event should one occur. Some examples of these actions include tracking aircraft status and tracking weather patterns. Each of these is discussed in more detail in the following sections. Note to User: Depending upon the specific airport structure and staffing, an airport communication center may not be in place at your airport; therefore, a single point of contact may be sufficient to reference in the plan. Part 2 – Resource B – Model IROPS Contingency Plan 113 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y Figure1. Joint actions during an IROPS Event.

5.1.1 Aircraft Status Ai rcraft status in the air and on the gro und is tracked by both airlines and the FA A to prov ide accurate , co mp lete, and tim ely info rm ation in regard to e xpected flight dela ys and de vel oping local situations. The Ai rcraft Status table describes (A IR PORT NA ME) pr oce dure checklists for tracking aircraft during IR OP S events. Insert co mp leted table fr om Topic 5a: Aircraft St atus 5.1.2 Tracking W eat he r Weather patterns are tracked by th e airport, airlines, a nd the FA A to predict potential im pacts to aircraft operations and to carry out alternate operating procedur es (such as di verti ng flights to alternate airports) to ma intain the safety of the crew and passe ng ers as well as operations staff out on the airfield. The Tr ac ki ng Weather table outlines the roles and responsibilities of airport, airline, and F AA st aff in tracking weather. Insert co mp leted table fr om Topic 5b: Trac ki ng Weathe r 5.2 Executing IR OPS Pl ans and Pr ocedur es In S ection 3.1 of this plan, pr ocedures were established with se rv ice prov iders, including concessions, gr ou nd transportation, the F AA, CB P, a nd TS A. This section pr ov ides specific procedures that are to be exec uted at the time of an IR OPS event. The following para graphs outli ne procedures for eac h of th e service providers. Note to User: It is re cogn iz ed that IR OPS response pr ocedures for se rv ic e prov id er s have be en previo us ly do cu me nt ed in Chap te r 3. The following sections outline the execution of these plans and procedures. 114 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

5.2.1 IROPS Communications Plans Relevant IROPS information, including status and related situational information, is communicated among appropriate (AIRPORT NAME) organizations during an IROPS event. The Execute IROPS Communication Plans table describes key elements of (AIRPORT NAME) IROPS communications plans. Insert completed table from Topic 5c: Execute IROPS Communication Plans 5.2.2 Passenger Support Plans Support procedures for passengers and other customers at (AIRPORT NAME) during IROPS events include focus while they are on board aircraft, during their deplaning, in the terminal, and when they need ground transportation. The Execute Passenger Support Plans table describes procedures at (AIRPORT NAME) for support during an IROPS event. Insert completed table from Topic 5d: Execute Passenger Support Plans 5.2.3 Procedures with Airlines Airlines operating out of (AIRPORT NAME) have implemented procedures pertaining to the DOT “3-Hour Rule” and “4-Hour Rule” relating to IROPS event response. The Execute IROPS Procedures with Airlines table describes the actions to be taken during IROPS events. Insert completed table from Topic 5e: Execute IROPS Procedures with Airlines 5.2.4 Procedures with FAA The FAA organization at (AIRPORT NAME) has implemented procedures pertaining to tarmac delay requests related to United States DOT’s 14 CFR Part 359 Enhanced Protection for Airline Passengers. The Execute IROPS Procedures with FAA table describes (AIRPORT NAME) FAA actions specific to IROPS events. Insert completed table from Topic 5f: Execute IROPS Procedures with FAA Part 2 – Resource B – Model IROPS Contingency Plan 115 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

5.2.5 Procedures with CBP (AIRPORT NAME) has implemented procedures with CBP relating to response to IROPS events. The Execute IROPS Procedures with CBP table describes (AIRPORT NAME) CBP actions specific to IROPS events. Insert completed table from Topic 5g: Execute IROPS Procedures with CBP 5.2.6 Procedures with TSA The TSA organization at (AIRPORT NAME) has implemented procedures concerning establishing and utilizing secure areas using procedures in the Airport Security Program or Aircraft Operator Standard Security Program. The Execute IROPS Procedures with TSA table describes (AIRPORT NAME) TSA actions specific to IROPS events. Insert completed table from Topic 5h: Execute IROPS Procedures with TSA 5.2.7 Concessions Procedures Concessions at (AIRPORT NAME) have agreed to provide specific support during IROPS events. The Execute IROPS Concessions Procedures table describes these procedures. Insert completed table from Topic 5i: Execute IROPS Concessions Procedures 5.2.8 Ground Transportation Procedures Ground transportation organizations at (AIRPORT NAME) have agreed to provide specific support during IROPS events. The Execute IROPS Ground Transportation Procedures table describes these procedures. Insert completed table from Topic 5j: Execute IROPS Ground Transportation Procedures 5.2.9 Procedures with Other Providers The (AIRPORT NAME) has coordinated with additional service providers to provide specific support during IROPS events. Specific procedures for each of these service providers are listed here. 116 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

CHAPTER 6 – CAPTURE LESSONS LEARNED AND UPDATING PLANS Since recovery from an IROPS event is critical to the continual improvement of the (AIRPORT NAME) IROPS plan, this chapter is divided into two sections: debrief after an IROPS event and lessons learned. The following tables describe (AIRPORT NAMES) procedures for these actions, including incorporation of lessons learned into the update of (AIRPORT NAME) IROPS Contingency Plan, as appropriate. 6.1 After an IROPS Event After an IROPS event, it is important to have a timely and comprehensive assessment of the event. The (AIRPORT NAME) will coordinate this debriefing meeting and include all aviation service providers as well as the IROPS Contingency Response Committee. The Debriefing IROPS Event table describes (AIRPORT NAME) plans for holding this training. Appendix B contains copies of previous debriefing activities that can be referenced. Insert completed table from Topic 6a: Debriefing IROPS Event 6.2 Lessons Learned As part of the debriefing, it is important to catalog the lessons learned from the individual IROPS events. The (AIRPORT NAME) will coordinate these lessons learned and provide them to the aviation service providers as well as the IROPS Contingency Response Committee members. The Capturing Lessons Learned table describes (AIRPORT NAME) plans for collecting lessons learned. Appendix B contains copies of previous lessons learned that can be referenced. Insert completed table from Topic 6b: Capturing Lessons Learned Part 2 – Resource B – Model IROPS Contingency Plan 117 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

118 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

APPENDICES Appendix A – Compliance Matrix of (AIRPORT NAME) IROPS Contingency Plan with DOT Model Contingency Plan Appendix B – Reference Documents Appendix C – Status of Plan Details Appendix D – Contact Details for (AIRPORT NAME) IROPS Contingency Response Committee and Points of Contact for Agencies during an IROPS Event Part 2 – Resource B – Model IROPS Contingency Plan 119 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

120 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

Appendix A – Compliance Matrix of (AIRPORT NAME) IROPS Contingency Plan with DOT Model Contingency Plan Note: The (AIRPORT NAME) IROPS Contingency Plan (this document) describes the overall coordination process used by the (AIRPORT NAME) IROPS Contingency Response Committee. It also serves to identify and document contingency-related actions requiring coordination between two or more aviation service providers. This section provides a compliance summary of the (AIRPORT NAME) IROPS Contingency Plan with [to be named requirement document]. [Note: This matrix will be populated following establishment of a required guideline by DOT, if and when such guideline is published.] Individual service provider contingency plans for airlines, airports, and federal government agencies and indications of their compliance with the DOT Model Contingency Plan are not included. Questions concerning content and compliance of these individual plans should be directed to the individual service provider organizations. The following compliance matrix addresses the overall coordination process used by the (AIRPORT NAME) IROPS Contingency Response Committee and those elements of individual compliance plans identified as requiring action by two or more service providers. DOT Reference Guideline (TBD) (AIRPORT NAME) IROPS Response Plan Section Title Section Title 1.0 Introduction 1.0 Introduction 1.1 (etc.) 1.1 (etc.) Part 2 – Resource B – Model IROPS Contingency Plan 121 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

122 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

Appendix B – Reference Documents Reference documents that should be included in this appendix include: Copies of procedures put in • • • • • • • place with aviation service providers, such as: – Airlines – FAA – CBP – TSA – Concessions – Ground transportation Copies of previous workshop summaries Copies of previous training exercises Copies of previous debriefing activities Copies of previous lessons learned Other reference documents an airport may want to place in this appendix include guidance from the United States DOT, such as: “Development of Contingency Plans for Lengthy Airline On-Board Ground Delays,” Developed by the United States DOT National Task Force to Develop Model Contingency Plans to Deal with Lengthy Airline On-Board Ground Delays, November 12, 2008. United States DOT final rulemaking 14 CFR Part 259 Enhanced Protection for Airline Passengers 2010 and 2011. Part 2 – Resource B – Model IROPS Contingency Plan 123 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

124 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

Appendix C – Status of Plan Details The following table serves as a working summary of the actions within the current version of the (AIRPORT NAME) IROPS Contingency Plan. It is intended that each item in the table be reviewed periodically for status and outlook by the IROPS Contingency Response Committee. Topic Last Update Expected Update IROPS Contingency Response Committee IROPS Response Plan Review IROPS Event History Customer Needs Tracking Delayed Aircraft Trigger Events And Communication Plans Support For Passengers Tracking Resource Inventory Skills Availability Procedures With Airlines Procedures With FAA Procedures With CBP Procedures With TSA Procedures With Concessions Procedures With Ground Transportation IROPS Coordination Workshops IROPS Coordinated Frontline Training Aircraft Status Tracking Weather Execute IROPS Communication Plan Execute Passenger Support Plans Executing IROPS Procedures With Airlines Executing IROPS Procedures With FAA Executing IROPS Procedures With CBP Executing IROPS Procedures With TSA Executing IROPS Procedures For Concessions Executing IROPS Procedures For Ground Transportation Debriefing IROPS Event Capturing Lessons Learned Part 2 – Resource B – Model IROPS Contingency Plan 125 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

126 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

Appendix D – Contact Details for (AIRPORT NAME) IROPS Contingency Response Committee and Points of Contact for Agencies during an IROPS Event IROPS Contingency Response Committee Please modify this table as appropriate for your needs, and add additional rows as necessary. Organization Contact Name & Phone Number Alternate Contact Committee Chairperson Airport Operations Airlines Concessions Ground Transportation Hotel Government Agencies Public Safety Operations Diversion Airport Fixed Base Operations Military (if joint-use) Emergency Response Executive Management Liaison Part 2 – Resource B – Model IROPS Contingency Plan 127 PA R T 2 PA R T 1 Reso u rce A Reso u rce B Reso u rce C Reso u rce D A p p en d ices B ib lio g rap h y

128 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 Re so u rc e A Re so u rc e B Re so u rc e C Re so u rc e D A p p en d ic es B ib li o g ra p h y

RESOURCE C – TOOLS INTRODUCTION This resource of the guidebook is intended to provide valuable tools that can be used in the implementation of an IROPS plan. These tools are meant to be used in conjunction with the information contained in Part 1 – Fundamentals of IROPS Planning, as well as with the implementation of Resource B – Model IROPS Contingency Plan. These tools range from planning tools that can be used to educate interested parties in the IROPS process to checklists that can be used by frontline staff during an IROPS event. Each tool has been developed to contain general elements that should be considered regarding the individual subject matter. Each airport that uses these tools should edit the tools as necessary to meet its specific needs. For example, larger airports many need to add more details to the various checklists, while smaller airports may find that deleting some of the elements may be appropriate. The items listed were collected to reflect best practices and are based on lessons learned from the development of the guidebook. They are not meant to be an exhaustive list of options, but rather a general guide that can be modified to fit the needs of each airport that may use the guidebook. For the purposes of this guidebook, references to the FAA include all forms of air traffic control (ATC) services. Part 2 – Resource C – Tools 129 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

130 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TABLE OF CONTENTS 133 Tool 1 – IROPS Planning Process 135 Tool 2 – DFW’s Sample for Partnering for Success 139 Tool 3 – Responsibilities of the Airport IROPS Contingency Response Committee 141 Tool 4 – Questions for Initial IROPS Committee Meeting 143 Tool 5 – Implementation Checklist for Evaluating IROPS Plans 145 Tool 6 – Self-Assessment Questionnaire 151 Tool 7 – Example Resource Inventory Checklist 153 Tool 8 – Concessions Checklist for Snow and Hurricane Events 157 Tool 9 – Airport-Airline 24/7 Contact and Capability Summary 159 Tool 10 – Technology Solutions 167 Tool 11 – Sample Workshop Agenda 169 Tool 12 – National Oceanic and Atmospheric Administration (NOAA) National Weather Service (NWS) Checklist 177 Tool 13 – Sample Communication Plan 179 Tool 14 – Social Media 181 Tool 15 – During an Event Tools 187 Tool 16 – Diversion Checklist 193 Tool 17 – After an Event Debrief Part 2 – Resource C – Tools 131 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

132 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 1 – IROPS PLANNING PROCESS Purpose: This tool illustrates the process for IROPS planning, which has been outlined in greater detail in Part 1 – Fundamentals of IROPS Planning of ACRP Report 65. This tool is intended for use by the IROPS Champion and IROPS Contingency Response Committee to demonstrate the sequence of steps necessary to carry out successful IROPS planning to all affected entities. Figure 1. IROPS Response Management Process. 1. Executive buy-in/get organized: The first step is to establish executive buy-in from your airport and each of your local aviation service provider organizations. These should include airport operations, airlines, concessions, ground transportation, local accommodations, government agencies (Transportation SecurityAgency–TSA, Federal Aviation Administration–FAA, Customs and Border Protection–CBP), Fixed-Base Operators (FBOs), refuelers, military (if a joint-use facility), executive management liaison, and emergency response. Next, your airport should create an IROPS Contingency Response Committee that includes representatives from your local providers. The committee should be led by an IROPS chairperson, who typically is a representative of your airport. The goal of your airport’s committee will be to establish and enhance contingency plans for local service providers through their collective, cooperative, and collaborative decision making. 2. Document current situation: Your airport’s IROPS committee should identify and gather important response plan information from service providers to ensure collaboration and cooperation. These response plans from individual organizations should be evaluated for adequacy during four categories of IROPS impact situations, which are surge, capacity, off-hours, and extended stay. Each of these unplanned situations should be considered for impacts involving aircraft and passengers. For example, planning for an off-hours situation involving both aircraft and passengers should take into consideration unplanned aircraft arrivals, the ability to meet passenger needs such as concessions, staff access to secure side, and the availability of CBP and TSA staffing. The collective comparison of current IROPS plans between service providers should include a review of local IROPS event history, identification of customer needs, evaluation of how to track delayed aircraft, the tracking of equipment inventory, and the determination of skills availability. Key airport implementation should include maintaining and sharing local contact and email distribution lists. Part 2 – Resource C – Tools 133 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

3. Establishing Procedures to Cooperate: Your airport will need to determine how to establish cooperation with local service providers in order to meet passenger needs. These include concessions, ground transportation, and government agencies (FAA, TSA, and CBP) as related to their staffing and resource capabilities. Cooperation is needed for responding to after-hours operation; surge in the number of passengers in the terminal and/or needing transportation to local accommodations; and consideration for diverted flights, including international flights in to airports without a CBP presence. Every airport should establish a local process to monitor and maintain its overall airport capacity status during an evolving IROPS event. 4. Review, Update, and Training for Plan Implementation: After determining what improved procedures are necessary and beneficial to IROPS planning, your airport should conduct coordinated training exercises to ensure these plans are understood by all involved service providers. Tabletop exercises are recommended to utilize considerations of both local IROPS events and events involving other regional airports. A key element of these exercises should be testing for impacts from each of the four IROPS situation types. 5. Summary of Consolidated Cooperation Actions to be Taken During IROPS Events: When your airport is experiencing an IROPS event, three actions are critical: communication, coordination, and collaboration. This requires your local service providers to work together to communicate aircraft status in the air and on the ground, as well as execute IROPS procedures. Your airport IROPS Committee needs to ensure the capability for coordinating shared information for both aircraft status and airport capacity. 6. Capturing Lessons Learned and Plan Updates as Required: Your airport should host an after-action meeting to review performance effectiveness as soon as is practical following return of operations to a normal state following an IROPS event. Part of the recommended debriefing procedures should be the identification of lessons learned. The airport IROPS response planning documentation should be reviewed by the IROPS Contingency Response Committee and updated as appropriate. 134 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 2 – DFW’S SA MP LE FO R PARTNERING FO R SUCCE SS Purp os e : In order to successfully appl y this guidebook, it is essential that all aviation se rv ice pr ov ider organizations in a region work together so th ey can explore wa ys to mu tual ly s upport one another to addres s current and evolving aviation challenges that disrupt the nor ma l flow of passengers through the air transportation sy st em . This tool, courtesy of Da ll as/F ort Worth In ternationa l Ai rport (D FW ), describes the role their IR OPS Contingenc y Response Co mm it tee has in bringing al l of their service prov iders together to co mm unicate, cooperate, a nd c oordinate so their plans are aligned. This involves changing the mi ndset for these organizations fro m feeling th ey n eed to go it alone with indi vi dual plans to reac hing an environm ent of partnering for success to de vel op a coordinated regional contingenc y plan to mi tigat e lengthy ta rm ac dela ys at DF W. This tool can be used by an airport’s IR OP S Continge nc y Response Committee to help create a partnering environm ent for all service prov iders to bridge the gap at their airport, no ma tter what size it ma y be (s ma ll hub, me dium hub, or large h ub) . Figure 2. Part neri ng for Success: Eight Step s for Mitigating Effects of IROPS Events on Passenger Service. Part 2 – Resource C – Tools 135 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

“Airline Industry Delivers Record On-time Performance Despite Season of Bad Weather.” That is a headline any airport operations director or airline president would love to read. However, the reality remains that passengers continue to wait for hours on tarmacs during extreme weather or other irregular operations events. This happens primarily because there is limited communication, collaboration, and coordination across service providers in the aviation industry. To remedy this situation, DFW established an IROPS Contingency Plan based on guidelines developed last year by the 2008 U.S. DOT Tarmac Delay Task Force. A major component of the DOT plan is that it calls for partnering between the airlines and airports for the ground handling and deplaning of passengers to avoid the types of unacceptable situations that have been experienced by passengers stranded on aircraft. DFW discovered that its own individual contingency plan would only work if it partnered with key organizations and agencies that the airport depends on during IROPS events. They found that in addition to each of the airlines serving DFW, they needed cooperation from groups like diversion airports, the TSA, FAA, and CBP in order to compare and align plans to meet all passenger needs during atypical situations and to ensure there were no gaps or overlap in service. In creating a partnering environment, DFW found it helpful to take a regional approach and bring together a diverse group of people from its own airport staff, diversion airports, and government agencies. However, it became immediately apparent that not everyone in DFW’s region felt that formal plan alignment was necessary. Therefore, the airport took some time to examine how to get the entire group on board. They found that an eight-step process helped describe the gap between providers feeling they should go it alone with their own individual plans to partnering for success where providers all share in the overall planning and response to IROPS situations to mitigate passenger inconvenience. First, providers have to get past the mindset of “it’s not my job” or “what does that have to do with me?” This initial step is critical in setting the stage for developing a regional approach to meet IROPS challenges. It can be achieved by bringing groups together in a nonthreatening format, like a workshop, to begin a dialogue. In this setting, the group discusses how each organization plays an integral role in meeting passengers’ needs during these times. This dialogue exposes where efforts are duplicated by organizations or where organizations are missing critical actions for addressing passenger service. In DFW’s case, it created a group consisting of all of its diversion airports, major airlines, and key TSA, FAA, and CPB personnel. The airport brought individuals from its region together in a workshop format to begin reviewing past handling of IROPS situations and discuss suggestions for future improvement. During early meetings, it is important that a regional group confront the attitude of “it’s their fault” or “if they only did their job.” By introducing a region of aviation service providers to one another, this puts a face with a job and makes it harder for people to shift blame to them. DFW found that when individuals in its region were held accountable to one another, they were less likely to point fingers. Once providers have met with and become comfortable with one another, they begin seeing the value in being a part of a bigger group where shared ideas and resources can be beneficial to the region as a whole. They are then ready for the next step, which is discovering they actually have a need to forge formal partnerships with others in their region to achieve success during irregular operations events. During this step, they also start feeling invested in the group and want to do their part to make their entire region excel at meeting passenger needs during these challenging operational times. They then begin recognizing areas where they can use help from others, as well as where they can provide assistance. 136 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Next, providers can begin more serious dialogue with one another and start sharing resources and identifying mutual support areas where they can fill gaps and prevent overlaps in customer care. Individuals find they possess ideas, processes, or even equipment that can be shared to help one another during these delay events. However, organizations reach a point where they discover this is all we can do without requiring formal written agreements or management authorization. This is the precipice where many actions seem to fall into the abyss of red tape. It is the point where groups fail unless the organizations pull together to mutually support one another. Jumping over the gap requires each provider to eliminate individual silos by reaching out to gain management support from their respective organizations in order to share and integrate business practices between providers in a region. Getting management agreement to implement mutually beneficial business practices is a critical step in moving toward full communication, collaboration, and coordination between providers. Some integrated business practices include not only developing a system for all providers to share data with one another to ensure situational awareness during delay events, but also a means for identifying and leveraging joint resources with other providers to ensure gaps in customer service are filled. In practice, this can be accomplished by formulating procedures between airlines and airports to share ground equipment in times of bad weather or formalizing written agreements to staff beyond normal working hours to make sure passengers receive the food or hygiene products they need to get them through an unexpected event. Once procedures are in place, organizations in a region need to practice working together. This requires taking the next step of aligning communications, processes, and training so individuals understand how to effectively and efficiently share information in order to deliver passenger needs during delay events. It means early notification, testing how effective these methods are at communicating and meeting passenger needs during events, and analyzing the results. Beyond this, the final step requires the region to learn and grow as a team through continuous improvement. This can be done through follow-up meetings, quarterly teleconferences, or annual workshops. No matter what the format, the important thing for a region to remember is to remain dedicated to communication, collaboration, and coordination. This focus will keep the dialog open within a region to continually find ways to improve performance during IROPS events and keep passengers satisfied during these challenging periods. Part 2 – Resource C – Tools 137 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

138 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 3 – RESPONSIBILITIES OF THE AIRPORT IROPS CONTINGENCY RESPONSE COMMITTEE Purpose: This tool is intended for use by the IROPS Champion and the IROPS Response Committee to identify the responsibilities of the committee for IROPS planning. The committee has four main responsibilities: know, act, confirm, and improve their airport’s IROPS plan. The following list and graphic provide additional detail on these four responsibilities: 1. KNOW: What do we need to accomplish? This phase is demonstrated in Chapters 1 and 2 of the IROPS planning process (described in Part 1 – Fundamentals of IROPS Planning). It includes determining processes for improved shared situational awareness for all aviation service providers. This also includes processes for the rapid flow of information between airfield status, airline flight schedules, and airport information systems. 2. ACT: How do we partner for success? This phase is demonstrated in Chapters 3 and 4 of the IROPS planning process. It involves communicating and leveraging resources, combining capabilities to meet passenger needs, and becoming a team. It means considering that an airport has a joint reputation with all aviation service providers in a region. 3. CONFIRM: Did we do what we said? This phase is demonstrated in Chapter 5 of the IROPS planning process. It involves confirming everyone’s response and recovery to the event, and holding debriefing sessions to review performance. 4. IMPROVE: Are we communicating our lessons learned to continually advance our response to IROPS events? This phase is demonstrated in Chapter 6 of the IROPS planning process. It involves sharing best practices with peers in the industry so mistakes are not repeated and best practices are implemented. Part 2 – Resource C – Tools 139 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

140 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 4 – QUESTIONS FOR INITIAL IROPS COMMITTEE MEETING (Edit as necessary to meet your airport’s needs) Purpose: This tool is intended to facilitate initial discussions at the first meeting of the IROPS Response Committee. This tool provides some kick-off questions to begin the meeting and then strategic questions that can be asked of each service provider regarding performance and quality of customer service provided. Kick-Off Questions 1. What causes an IROPS event (e.g., thunderstorm, fog, snow, blizzard, power outage), or parts of it, to become challenging, inconvenient or frustrating? 2. What infrastructure innovations/social media tools have you leveraged during an event? 3. What causes an IROPS event to go off track? 4. What causes the IROPS event to waste resources (e.g., time, resources, equipment)? Performance and Quality of Customer Service 1. Availability of service provided by various service operators. The passenger experience is significantly influenced by the interface between service providers all with their own business drivers, business models, customer approaches, incentives and operational constraints. Strategic questions: • What are your goals for the quality of service you provide passengers? • What are the procedures you have in place to achieve these goals? • How do you coordinate your service-related activities with other service providers? 2. Coordination between various service providers. The quality of passenger experience can suffer where there is a lack of understanding between the service providers. Often, airport and airline service providers can more successfully meet their quality goals when they coordinate their response plans and procedures. Strategic questions: • What challenges exist where the response requires the involvement of two or more different service providers? • Are there different types of challenges depending on whether the passenger is on the outbound or the returning leg of a flight? • Are there different types of challenges depending on whether the passenger is domestic or international? • What are examples of ways these challenges could be addressed to improve overall service quality? Part 2 – Resource C – Tools 141 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

3. Sharing of information on real-time situational awareness/performance A key element of success during an IROPS event, whether due to a ground delay, diverted flight, or special mobility event, is maintaining real-time shared situational awareness among all service providers. This shared awareness is best achieved through continuous communication and coordination of response efforts. In addition to supporting timely response to events, this sharing of situational information can help detect service quality areas needing additional attention. Strategic questions: • What type of information is shared at your airport between service providers? • What is the forum and format of the shared information? • How is the shared information used by each of the receiving organizations? • What additional shared information would be useful? • What coordination procedures exist for organizations to back up each other during an extended delay, diversion, or special mobility event? 4. Planning for when difficulties occur to the passenger experience Extended ground delays are a general theme throughout the aviation passenger industry. The challenge is identifying methods and procedures that can improve the passenger experience. Strategic questions: • How do early warning signals work between the different service providers at the airport on the potential difficulties to the passenger experience? • What planning currently occurs at the airport for key scenarios when major delays or critical system failures occur? • How do different organizations plan for unexpected increases in passenger capacity levels? • How do aviation service providers inform each other when difficulties occur that affect passenger service? • How is notification made when aircraft flights are delayed or diverted? • How do individual service provider organizations respond when concerns are identified relating to their service? • What additional actions are taken by individual service provider organizations to mitigate the impact of irregular operations on passengers? • What are the special needs concerns for passengers (availability of wheelchairs, oxygen, etc.)? 142 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 5 – IMPLEMENTATION CHECKLIST FOR EVALUATING IROPS PLANS (Edit as necessary to meet your airport’s needs) Purpose: This checklist should be used by the IROPS Response Committee to identify and gather important response plan information from service providers to ensure collaboration and cooperation. These response plans from individual organizations should be evaluated for adequacy during the four categories of IROPS impact situations, which are surge, capacity, off-hours, and extended stay. Each of these unplanned situations should be considered for impacts involving aircraft and passengers. For example, planning for an off-hours situation involving both aircraft and passengers should take into consideration unplanned aircraft arrivals, the ability to meet passenger needs such as concessions, staff access to secure side, and the availability of CBP and TSA staffing. It is recommended that a key element of your airport’s training exercises should be testing for impacts from each of the four IROPS situation types. Surge: Potential impact caused by the rate of arrival of aircraft, timing of deplaning passengers, and subsequent movement of passengers through airport • Aircraft Frequency of unplanned flights Gate availability Local airline station management availability • Passengers (including animals) Rate at which movement can be made through terminal Rate of handling re-entry for screening access Accommodations for special-needs passengers Local airline station management availability Capacity: Potential impact caused by the total number of aircraft that have arrived at the airport and of the number of passengers located in any particular areas of the airport • Aircraft Gate availability Refueling availability Deicing availability Off-gate parking availability Local airline station management availability • Passengers (including animals) Number of passengers that can be accommodated at gate area Number of passengers that can be accommodated in terminal area Capacity of concessions Part 2 – Resource C – Tools 143 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Accommodations for special-needs passengers Local airline station management availability Off-Hours: Potential impact caused by the time of day at which aircraft arrive at airport and the subsequent need to process passengers • Aircraft Ground crew availability Aircraft servicing availability Local airline station management availability • Passengers (including animals) Availability of concessions Accommodations for special-needs passengers Local airline station management availability Extended Stay: Potential impact caused by duration of stay (often measured in days) that aircraft remain at airport and passengers are delayed before resuming their travel • Aircraft Extended parking availability Ground crew availability Aircraft servicing availability Local airline station management availability • Passengers (including animals) Availability of concessions Availability of overnight accommodations at airport Availability of off-airport accommodations Availability of local transportation Accommodations for special-needs passengers Local airline station management availability 144 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy TOOL 6 – SELF-ASSESSMENT QUESTIONNAIRE (Edit as necessary to meet your airport’s needs) Purpose: This tool is intended for use by the IROPS Champion and IROPS Response Committee, and includes a series of questions related to each of the six steps of IROPS planning. These questions serve as a self-assessment to identify where the airport and its service providers are in the IROPS planning process and to align any existing processes and/or procedures. 1. Executive Buy-in/Get Organized First, your airport should establish executive buy-in from your airport and each of your local aviation service provider organizations. These should include airport operations, airlines, concessions, ground transportation, local accommodations, government agencies (TSA, FAA, and CBP), fixed-base operators (FBO), refuelers, military (if a joint-use facility), executive management liaison, and emergency response. Next, your airport should create an IROPS Contingency Response Committee that includes representatives from your local providers. The committee should be led by an IROPS Chairperson, who typically is a representative of your airport. The goal of your airport’s Committee will be to establish and enhance contingency plans for local service providers through their collective, cooperative, and collaborative decision making. Some questions to ask include: • Have you hosted and/or participated in regional IROPS response workshops? • Have you established a local IROPS response coordination planning committee that meets periodically and includes representatives from all key aviation service providers in your region? • Have they coordinated/aligned the IROPS plans of all local aviation service providers? 2. Document Current Situation Your airport’s IROPS Committee should identify and gather important IROPS response plan information from service providers to ensure collaboration and cooperation. These IROPS response plans from individual organizations should be evaluated for adequacy in the four categories of IROPS impact situations: surge, capacity, off-hours, and extended stay. Each of these situations should be considered for impacts involving unplanned aircraft and unplanned passengers. For example, planning for an off-hours situation involving both aircraft and passengers should take into consideration unplanned aircraft arrivals, the ability to meet passenger needs such as concessions, staff access to secure side, and the availability of CBP and TSA staffing. The collective comparison of current IROPS plans between service providers should include reviewing local IROPS event history, identifying customer needs, evaluating how to track delayed aircraft, tracking equipment inventory, and determining skills availability. Key airport implementation should include maintaining and sharing local contact and email distribution lists. Some questions to ask include: Reviewing past history • Do you have a record of past IROPS events and a description of responses provided? • What have been your top five IROPS events over the last 2 - 3 years? • Do you have a documented IROPS response procedure? An SOP? A memorandum of understanding? Part 2 – Resource C – Tools 145 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

TOOL 6 – SELF-ASSESSMENT QUESTIONNAIRE (Edit as necessary to meet your airport’s needs) Purpose: This tool is intended for use by the IROPS Champion and IROPS Response Committee, and includes a series of questions related to each of the six steps of IROPS planning. These questions serve as a self-assessment to identify where the airport and its service providers are in the IROPS planning process and to align any existing processes and/or procedures. 1. Executive Buy-in/Get Organized First, your airport should establish executive buy-in from your airport and each of your local aviation service provider organizations. These should include airport operations, airlines, concessions, ground transportation, local accommodations, government agencies (TSA, FAA, and CBP), fixed-base operators (FBO), refuelers, military (if a joint-use facility), executive management liaison, and emergency response. Next, your airport should create an IROPS Contingency Response Committee that includes representatives from your local providers. The committee should be led by an IROPS Chairperson, who typically is a representative of your airport. The goal of your airport’s Committee will be to establish and enhance contingency plans for local service providers through their collective, cooperative, and collaborative decision making. Some questions to ask include: • Have you hosted and/or participated in regional IROPS response workshops? • Have you established a local IROPS response coordination planning committee that meets periodically and includes representatives from all key aviation service providers in your region? • Have they coordinated/aligned the IROPS plans of all local aviation service providers? 2. Document Current Situation Your airport’s IROPS Committee should identify and gather important IROPS response plan information from service providers to ensure collaboration and cooperation. These IROPS response plans from individual organizations should be evaluated for adequacy in the four categories of IROPS impact situations: surge, capacity, off-hours, and extended stay. Each of these situations should be considered for impacts involving unplanned aircraft and unplanned passengers. For example, planning for an off-hours situation involving both aircraft and passengers should take into consideration unplanned aircraft arrivals, the ability to meet passenger needs such as concessions, staff access to secure side, and the availability of CBP and TSA staffing. The collective comparison of current IROPS plans between service providers should include reviewing local IROPS event history, identifying customer needs, evaluating how to track delayed aircraft, tracking equipment inventory, and determining skills availability. Key airport implementation should include maintaining and sharing local contact and email distribution lists. Some questions to ask include: Reviewing past history • Do you have a record of past IROPS events and a description of responses provided? • What have been your top five IROPS events over the last 2 - 3 years? • Do you have a documented IROPS response procedure? An SOP? A memorandum of understanding? Part 2 – Resource C – Tools 145 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

• Do your plans include FBOs? • Do you have a deicing plan and does each airline know what it is? • Have you conducted risk assessments to identify the nature, scope, and scale of airport response efforts in support of IROPS events? • Do you know your overall capacity constraints (which aircraft types, what limiting factors, which extenuating circumstances)? Identifying customer needs • Do you have procedures to provide customer service needs (food, medical, supplies) beyond normal service hours when needed? • Have you developed a process for allowing passengers who deplane and remain in a secure area to reboard aircraft without additional TSA screening? • Do you have provisions in your plan for the care and feeding of service animals and animals in transit? • Do you have a process to relate current resources to passenger needs and to identify additional resources as needed? • Do you coordinate with airlines to support passengers being deplaned during IROPS events? • Do you have a plan or procedure for providing special-needs passengers support as required by 14 CFR Part 382? • Do you have procedures for responding to passenger medical needs? • Do you have a communications plan to keep passengers informed during IROPS events and to help them communicate their status with others outside the terminal? • Do you have procedures in place to allow both passengers and those meeting them access to food, hydration, and lavatory facilities during an IROPS event? • Do you have procedures to provide information on lodging and rest accommodations in the airport during an IROPS event? • Do you have a coordination plan with local ground transportation for continued availability during extended IROPS events? • Have you identified methods to address IROPS events and large numbers of passengers and personnel in terminals? • Do you offer accommodations (discounted hotels)? • What IROPS plans do you have with local medical support? • Do you have a plan for making announcements to customers detailing which concessions will be open? Evaluating how to track delayed aircraft • Have you coordinated procedures for addressing the needs of diverted aircraft with various diversion airports? • Do you have a process to provide for unscheduled and diverted arrivals of international flights into airports not normally staffed by CBP? • Have you coordinated with CBP to develop security plans for diversions at your airport? • Have you explored, with the FAA, procedures enabling aircraft in departure queue to return to a gate without losing their position in the queue? 146 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

• Do your plans include FBOs? • Do you have a deicing plan and does each airline know what it is? • Have you conducted risk assessments to identify the nature, scope, and scale of airport response efforts in support of IROPS events? • Do you know your overall capacity constraints (which aircraft types, what limiting factors, which extenuating circumstances)? Identifying customer needs • Do you have procedures to provide customer service needs (food, medical, supplies) beyond normal service hours when needed? • Have you developed a process for allowing passengers who deplane and remain in a secure area to reboard aircraft without additional TSA screening? • Do you have provisions in your plan for the care and feeding of service animals and animals in transit? • Do you have a process to relate current resources to passenger needs and to identify additional resources as needed? • Do you coordinate with airlines to support passengers being deplaned during IROPS events? • Do you have a plan or procedure for providing special-needs passengers support as required by 14 CFR Part 382? • Do you have procedures for responding to passenger medical needs? • Do you have a communications plan to keep passengers informed during IROPS events and to help them communicate their status with others outside the terminal? • Do you have procedures in place to allow both passengers and those meeting them access to food, hydration, and lavatory facilities during an IROPS event? • Do you have procedures to provide information on lodging and rest accommodations in the airport during an IROPS event? • Do you have a coordination plan with local ground transportation for continued availability during extended IROPS events? • Have you identified methods to address IROPS events and large numbers of passengers and personnel in terminals? • Do you offer accommodations (discounted hotels)? • What IROPS plans do you have with local medical support? • Do you have a plan for making announcements to customers detailing which concessions will be open? Evaluating how to track delayed aircraft • Have you coordinated procedures for addressing the needs of diverted aircraft with various diversion airports? • Do you have a process to provide for unscheduled and diverted arrivals of international flights into airports not normally staffed by CBP? • Have you coordinated with CBP to develop security plans for diversions at your airport? • Have you explored, with the FAA, procedures enabling aircraft in departure queue to return to a gate without losing their position in the queue? 146 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy • Do you have a process for coordinated capability planning for gates and equipment during an IROPS event? • Do you have a tool to allow ATC services to know who is occupying gates? • Have you explored processes for providing accurate, complete, and timely information in regard to expected flight delays and developing local situations between the FAA and airport? • Have you worked with the airport, airlines, and FAA to develop a process for tracking delayed aircraft both in the air and on the ground? Tracking equipment inventory • Have you identified resource requirements to meet needs of all entities dependent on airport services (passengers, personnel meeting delayed passengers, airlines, CBP, FAA, TSA, airport operator employees, contractors, and tenants)? • Do you take inventory and resupply resources on a regular basis? • What aircraft ground support equipment do you have available for the types of aircraft that can land at your airport (e.g., tow bars, tugs, pushback units, baggage carts, ground power units)? • What capability do you have to service aircraft beyond those that can be accommodated at a gate? Air stairs? • What is your aircraft parking capability? • What is your gate availability? Determining skills inventory • What airport staff is available to handle extra flights (e.g., duty manager, supervisor, service specialists, and crew members for above and below the wing)? 3. Establishing Procedures to Cooperate Your airport will need to determine how to establish cooperation with local service providers in order to meet passenger needs. These include concessions, ground transportation, and government agencies (FAA, TSA, and CBP) as they relate to their staffing and resource capabilities. Cooperation is needed for responding to after-hours operation, surge in the number of passengers in the terminal and/or needing transportation to local accommodations, and consideration for diverted flights, including international flights into airports without a CBP presence. Every airport should establish a local process to monitor and maintain their overall airport capacity status during an evolving IROPS event. Some questions to ask include: • Do you have documented support procedures (e.g., gate sharing)? • Do you have resource and equipment procedures? • Do you have documented response plans with the TSA, CBP, and FAA? • What IROPS coordination plans do you have with local government organizations? • Do you provide outreach to government organizations (FAA, TSA, and CBP) and regional diversion airports? • Have you identified collaboration procedures to determine and document the scope and scale of aviation service providers’ roles and responsibilities for specific IROPS situations? Part 2 – Resource C – Tools 147 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

• What IROPS plans do you have with the airlines serving your airport? • What IROPS plans do you have with nongovernmental support agencies such as the Red Cross and social services? • Do you have a plan for your airport to send community events calendars (e.g., conventions) to all stakeholders? • Have you coordinated procedures that provide continuous and consistent relevant communications among all aviation stakeholders, including diversion airports? 4. Review, Update, and Training for Plan Implementation After determining what improved procedures are necessary and beneficial to IROPS planning, your airport should conduct coordinated training exercises to ensure these plans are understood by all involved service providers. Table-top exercises are recommended to utilize considerations of both local IROPS events and events involving other regional airports. A key element of these exercises should be testing for impacts from each of the four IROPS situation types: surge, capacity, off-hours, and extended stay. Some questions to ask include: • Do you have a process for airport-wide coordinated IROPS response contingency training? • Do you have a mechanism for individual service providers to identify key areas requiring coordination training with other service provider organizations? • Do you have a process to update and provide revised training? 5. Summary of Consolidated Cooperation Actions to be Taken during IROPS Events When your airport is experiencing an IROPS event, three actions are critical: communication, coordination and collaboration. This requires that your local service providers work together to communicate aircraft status in the air and on the ground, as well as execute IROPS procedures. Your airport IROPS committee needs to ensure the capability for coordinating shared information for both aircraft status and airport capacity. Some questions to ask include: Contacts • Do you have a plan for each organization to provide a point of contact (POC) for keeping its organization’s information up to date? • Have you established a notification/decision tree (helps airlines know who to call for a gate, how to get an available hardstand, etc.)? Notification procedures • How are you notified of a pending IROPS event? • Do you have a plan for the airport to provide a daily briefing (similar to a broadcast announcement) or at least make information available on your website (feature all events such as which gates are inoperative, parking full, as well as combine all vendors’/partners’ operating conditions)? • What process is used to plan, notify, and use local government organizations? • Do you have a coordinated communications procedure for providing information to both aviation service organizations and passengers? • Do you have procedures for working with local media? 148 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Processes • Do you have a process to identify and define a communications office to receive and distribute all relevant information to keep all aviation service providers and customers informed of the IROPS event as it unfolds? • Do you have procedures to share empty gates as needed during IROPS events (considering needs of other airline operations, customer service needs, technical requirements, lease terms, and hardstand positions for remote aircraft parking)? • Do you have a process for airport (with airline management and operation control, FBOs, FAA, and flight crews) to provide access to remotely parked aircraft for servicing, emergency medical support, and supply? • Do you have procedures to provide support as needed for aircraft delayed on the ground with passengers on board? • Do you have procedures to provide support as needed for deplaning of passengers from remote locations and/or during extended hours of operation? • Do you have procedures in place for service providers to share status for coordinating mutual support? • Do you have trigger criteria and process aligned between airlines and appropriate airport, TSA, and CBP personnel? • Have you established and clearly communicated trigger criteria to all aviation service providers and developed a communication plan to inform customers about what to expect during extended delays, cancellations, and/or diversions? • Do you have coordination procedures in place between the airport and airlines for sharing aircraft status information during IROPS events? • Do you have a process for a deplaning trigger event (i.e., action alert for coordination with airport operations and others as needed)? • Do you have a procedure in place for airlines to provide early notification of pending IROPS events? • Have you developed a process for the airport or airline to establish a secure area using procedures in its Airport Security Program or Aircraft Operator Security Program without TSA presence? • When extra staff is required, what process is used to plan, notify, and utilize the affected staff? 6. Capturing Lessons Learned and Plan Updates as Required Your airport should host an after action meeting to review performance effectiveness as soon as practical following return of operations to a normal state after an IROPS event. Part of the recommended debriefing procedures should be the identification of lessons learned. The airport IROPS response planning documentation should be reviewed by the IROPS Contingency Response Committee and updated as appropriate. Part 2 – Resource C – Tools 149 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Some questions to ask include: • Do you have a coordination procedure (debriefing process) for your committee to review response effectiveness following an IROPS event? • Do you have a procedure for incorporating lessons learned into the airport’s IROPS Contingency Plan? • Do you have a process for each aviation service provider to identify necessary improvements to individual IROPS plans? • Do you have a process to update and provide revised training? • Do you have a process to identify maintenance actions or resupply efforts necessary to be prepared for the next IROPS event? • Do you have a process for coordinating information and recommended actions among the aviation service providers before being coordinated with the airport-wide community? 150 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 7 – EX AM PLE RESOURCE INVENTORY CHECKLIST (E dit as necessary to meet your airport’s needs) Purp ose: This exam ple inventor y checklist is intended to prov ide a co mp rehensiv e lis t of the resources that are available at an airport between all service prov ider s, as well as the skills of staff available to use these resources. (Having the equipm ent av ailable for use is im portant, but ha vi ng so me one to operate the equi pm ent is also necessary .) Once co mp leted, this li st s hould be distributed to se rv ice providers so that th ey can consult the list during IROP S ev ents if th ey need certain equipm ent or resources they mi ght not ha ve . Of ten the status of certain resources at an airport can influence di versi on decisions. A checklist outlining so me of these factors is prov ided below. Resource Inventory Checklist Inventory Item Ow ne r Staff Sk il ls • Hard stands • Ai rcra ft park ing locations • Ai rcra ft flee t mi x • Shuttle buses • Ai r stairs • Medical transport/f acility • Conces sion facilit y - food and beverage servic e • La vato ry equi pm ent/facility • Po table wa ter car t • Cabin se rv ice li ft truc k • Fuel tr uc ks an d/or serv ice/ faci lit y • To w tugs and baggage carts • Pu shback tug /tractor • To wb ars • Co mmu nica tion equi pm en t/ fa cilit y acce ss • Recove ry equi pm en t/ servic e • Cust om er se rv ice care facil ity /e nterta in me nt • Ai rcra ft ha ng ers • Refr ig erated/deliver y truc ks or m obile carts • Port able pow er supply • Port able A/C sy st em s • Cust om er assistance personnel Part 2 – Resource C – Tools 151 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Factors That Influence Diversion Decisions Factor at Receiving Airpor t Organization Mo nitoring an d Reporting • Navigation equi pm en t st at us • Ai rcra ft park ing status • Gate availability st at us • Cust om s capaci ty status • Refuel in g stat us • Deicing assets status • Jetw ay an d air stair access stat us • General ra mp operations status • Securi ty status 152 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 8 – CONCESSIONS CHECKLIST FOR SNOW AND HURRICANE EVENTS (Edit as necessary to meet your airport’s needs) Purpose: This checklist is intended for use between airport staff and concessions staff to handle IROPS events resulting from snow and hurricane weather. A separate checklist is provided for use during each event. Each checklist provides a set of actions to be taken before, during, and after the event. Snow Events Pre-Planning • Establish manager’s responsibilities during snow events. • Establish “Snow Team” associates who will “ride out the storm” at the airport • Establish lodging for associates • Establish transportation for associates • Establish which key units to keep open to meet the needs of the public and airport personnel • Establish catering needs for the airport ops center • Establish levels for products and merchandise to meet the needs of stranded passengers • Go over and above normal day-to-day business practices During the Snow Event • Attend all snow event meetings to stay up to date on the progress of the storm • Be aware of the approximate time the storm will hit • Be aware of inclement weather in other cities (It will affect your airport/inventory as well.) • Place additional orders for food and merchandise • Reserve rooms at local hotels for staff if needed • Prepare the schedule for the snow event • Call management and Snow Team associates into the airport before the inclement weather strikes • Set up catering in “Snow Event” Emergency Room • Begin stocking the units • Be prepared to help passengers with special needs (e.g., warming up baby formula, having diapers on hand, toiletries, personal care needs) • Stock personal care needs available in every store • Keep the units well-stocked • Keep units well-staffed • Keep in touch with airport authority and airlines – Keep airport and airlines informed if anything changes with which locations you have open – Keep the airport and airlines informed as to which locations will be open for the duration of the storm – Keep the airport and airlines informed as to what you can do to help their stranded passengers • Keep passengers’ and associates’ spirits up during the difficult travel time Part 2 – Resource C – Tools 153 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Debrief after the Storm • Attend the airport meetings • Determine if all needs were met or if there are other needs that could be met moving forward • Hold management meeting with Snow Team • Get feedback from staff to see if the needs of the traveling public as well as the airport personnel were met • Get feedback on what ran smoothly and what areas have room for improvement • Get feedback on food and merchandise needs Hurricane Events Pre-Planning – Hurricane Watch • Update employee phone list: current for all employees, including managers’ cell phones • Update vendor phone list: current and correct • Ensure equipment is in good working order • Purchase enough battery-operated radios and batteries • Purchase enough working two-way radios, batteries, and chargers • Create manager rotation list • Assign area where associates can relax to keep them occupied and break up monotony • Have HR associate update weather hotline extension • Attend airport authority meetings and determine expectations • Determine what stores will be open • Determine how many managers and associates will be needed • Book hotel rooms if needed • Determine vendors’ ordering and delivery schedule, as well as trash pickup • Determine/order food and beverage, including bottled water, ice, etc. • Order refrigerated trucks, if necessary • Fill CO2 • Order extra coin and currency for cash room • Update weather bulletin board Pre-Planning Hurricane Warning • Continued daily meetings by GM with direct reports • Have HR associate update weather hotline extension • Have HR check bus schedule • Attend airport authority meetings and respond to needs • Check flight schedules, airport closing times, etc. • Determine managers’ and associates’ schedules • Have managers make up shift set-up sheets • Determine when airsides will be closed • Evacuate associates • Turn off breakers, gas, equipment 154 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

• Cover microwaves in plastic • Remove banks • Empty coolers and bring perishable food to landside • Bring in blankets, pillows, mattresses, battery-operated radios, DVDs, etc. • Monitor TV weather broadcasts During the Hurricane Event • Continued daily meetings by GM with direct reports • Keep communication lines open with airport authority • Monitor store openings, managers’/associates’ schedules • Take pictures • Encourage associates • Check in hotel rooms • Monitor TV/radio broadcasts • Monitor opening/closing times • Have HR associate update weather hotline extension Debrief after the Hurricane • Meet with airport authority and airlines – Assess damages – Come up with re-opening game plan – Meet the needs of airport personnel, returning traveling public ¬ Communicate opening schedule ¬ Communicate any variations in services ¬ Debrief with airport/airlines on best practices moving forward • Plan staffing and opening hours – Have HR associate update weather hotline extension – Get airsides ready before associates arrive Part 2 – Resource C – Tools 155 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

156 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 9 – AIRPORT-AIRLINE 24/7 CONTACT AND CAPABILITY SUMMARY (Edit as necessary to meet your airport’s needs) Airport Operations Name: Phone: Email: Aircraft Capabilities/Special Use Equipment • Aircraft tow bars - A320/319/321 family based on airline ownership - Interchangeable tow bars • Aircraft stairs - Passenger stairs: determine what stairs are needed for aircraft type - Stair-truck: narrow and/or wide body Ground Handlers Name: Phone: Email: Fuelers Name: Bowsers Phone: Hydrant Email: Deicers Name: Phone: Email: Part 2 – Resource C – Tools 157 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Sample Equipment Checklist (Edit as necessary to meet your airport’s needs) Sample Equipment List Airline Airline Airline Airline Airline Airport Other 737 To w Bar (T B) 757 TB 767 TB A319/320 TB AI RB US TB A320 TB MD80/90 TB CRJ 200 TB CRJ 700/900 TB E190 TB Q-400 TB Universal TB 737 Pu shup stairs 737 Ai r stairs 757 Cabi n access stairs 757 Pa ssenger stairs no n- mo torized 767 Stairs 767 Pu shup stairs 747/77 7 Stairs A320 Diesel po we red air stai rs A320 Pu shup stairs MD80 Galle y access stairs Ai r start Ai r Start Wide body Capable Ground Po we r Unit (GPU) Bottle air start La vato ry service truc k La vato ry service truc k, wi de body capable Po table wa ter cart Cabin se rv ice li ft truc k wi de body Pu shback tractor, wi de body capable Pu shback tu g 158 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 10 – TECHNOLOGY SOLUTIONS Purp ose: Vari ous technol ogy solutions exist to enable more effectiv e pl anning and manage me nt of the IR OP S contingenc y response activities. While mo st of these so lutions deal with comm unication and information sharing, so me are specific solutions that address uni qu e pro cesses. This ov erview section prov ides information in two separate form ats. Th e first is a breakdown of ke y functional require me nts and the ty pe of technology solution that is av ailable at va ry ing cost le vels . The second is a breakdown of the vari ous solution ty pes with summ ary le vel info rm ation on the function, phase of use, operational impl em entation location, and ke y operational stakeholders. Technology Suppo rt fo r Func tiona l Requ ir em en ts The following table identi fi es a set of generalized functi on al requirem ents of the IR OPS contingenc y planning and ma nage me nt process. Fo r each require me nt noted, technology solutions at a progressi ve leve l of ma gnitude in both cost and co mp lexi ty are identified. The intent of this table is to pr ov ide guidance as to th e vari ous options available to m eet the functional needs. While it can be seen that standard com puter and comm unication de vices can prov ide the required functionalit y, specialized solutions can greatly im pr ov e the m onitoring, comm unication, a nd response ca pabilities. It should be noted that a single solution ma y be configured to m eet mu lt iple functional requirements. Functional Requirement $ 5K $$ 50K $$$ 500K Co mmu nica tion – st an dard Em ail, teleph on e, intern et , m onitors Web da shboard – si mp le Web da shboard – co mp le x Co mmu nica tion – ma ss Em ail, in ternet, te xt Auto ma ted calling sy st em , cu st om ized m obile de vice application, prog rammable video displa y – si mp le Radio broadcasting sy st em , progra mma ble vi deo displa y – co mp lex Collaboration / te am building Pr od uctivit y so ft wa re, Em ail, in ternet, we b portal, we b conf erence, decision tree Web da shboard – si mp le Web da shboard – co mp le x Contact ma nage me nt Pr od uctivit y so ft wa re, Em ail, in ternet Cust om ized database Operational database In fo rm a tion gatheri ng Pr od uctivit y so ft wa re, Em ail, teleph on e, inte rn et Cons ulta nt – assess me nt Cons ulta nt – plan de velo pm ent Docu me ntatio n Pr od uctivit y so ft wa re Cust om ized database Operational database Data tracking Pr od uctivit y so ft wa re Cust om ized database Operational database Report generation Pr od uctivit y so ft wa re Cust om ized database Operational database Ai rs pace mo nitori ng Radio GPS-based flight trackin g Ai rs pace mo nitori ng sy st em Flight trac ki ng Internet Flight status data feeds Flight trac ki ng mana ge me nt sy st em Ai r tra ffic fl ow mana ge me nt Internet Flight status data feeds Ai r tra ffic fl ow mana ge me nt sy st em Su rf ace detection Ca me ra surveillance Ca me ra surveillance Su rf ace detection sy st em Part 2 – Resource C – Tools 159 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Functional Requirement $ 5K $$ 50K $$$ 500K Su rf ace ma nage me nt Radio Su rf ace ma nage me nt system Su rf ace ma nage me nt sy st em Weather detection Internet (w eather displa y system, lightning detection), lightning detectio n sy st em , ca me ra su rv eilla nc e Weather detection syst em – short range, lightning detectio n sy st em Weather detection sy st em – long rang e Flight status info rm a tion shar in g Internet Cust om ized m obile de vice a pplication Flight in fo rm ation displa y sy st em Pa ssenger handli ng Port able ai rcra ft stairs Ai rcra ft stair truc k, bus – standard capaci ty Auto dock syst em , bus – large capaci ty Resource mana ge me nt Pr od uctivit y so ft wa re Cust om ized database Gate ma nage me nt sy st em , reso urce mana ge me nt sy st em Ba gga ge ma na ge me nt Pr od uctivit y so ft wa re Cust om ized database Ba gga ge so rtation sy st em , ba gga ge tracking syst em , ba gga ge reco ve ry sy st em , ba gga ge reconciliation syst em Pa ssenger processing Pr od uctivit y so ft wa re Lo cal departure control sy st em Co mmo n use passen ger processi ng sy st em Solution Su mm aries Specific technology solutions ha ve been define d in the fo llowing table in general terms. Ma ny products exist that prov ide the capabilities listed. These solutions ha ve been grou ped into categories of comm on solution ty pes and identified by the phases of IR OP S response being before, during, and after the IR OP S event, the operational impl em entation being airside or landside, a nd the ke y operational stakeholders. The technology solutions identified are In te gration/Strate gy Services, IT Supp ort, Da ta Manage me nt, Shared Ai rcraft Status , Co mm unication of Status, Resource Manage me nt, Pa ss enger Ha nd ling, Bagg age Manage me nt, Pa ssenge r Pr ocessing, and Weather Detection. The intent of this table is to prov ide an ov er view of the specialized solutions available to m eet specific functional requirements and define when, where, and by w hom th ey are used. Many of these soluti on s serve a single purpose during a single phase, while others can support a broa d range of tasks that span the entire IR OPS spectru m. 160 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Category Solution Type Function Phase Ops Stakeholder B ef o re D u ri n g A ft er A ir si d e La n d si d e A ir p o rt A ir C ar ri er / G ro u n d H an d le r FA A In te gr at io n / St ra te gy Cons ulti ng services Prov ides professional consul ti ng support for defini ng technology inte gratio n strate gy be fo re an event, and revise s strate gy based on lessons learned after an ev ent. X X X X X Data inte gratio n services Prov ides professional data in te gratio n services be fo re an event to enable the shari ng of in fo rm ation am on g vari ou s technolo gy solutio ns, an d mo di fies data inte gratio n strate gy based on lessons learned after an ev ent. X X X X X Sy stem inte gratio n services Prov ides professional syst em s inte gratio n se rv ices be fo re an event to enable the sharing of in fo rm ation am ong vari ou s tec hno logy so lu tions, and m odi fi es syst em inte grat io n strategy based on lesso ns lear ne d af ter an ev en t. X X X X X IT Su pp or t IT sy st em mana ge me nt Prov ides for the ongoi ng an d em erge nc y response mana ge me nt an d ma in tena nce of te ch no logy as sets an d sy st em s. X X X X X X X D at a M an ag em en t Air port operatio nal database Serves as a ce ntral data repository fo r airport operational sy st em s to enable the sharing of in fo rm atio n am ong vari ou s te ch no logy solu ti on s be fo re, du ring, and af ter an ev en t. X X X X X X Part 2 – Resource C – Tools 161 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Category Solution Type Function Phase Ops Stakeholder Sh ar ed A ir cr af t S ta tu s Ai rs pace mo nitori ng sy st em Prov ides overvi ew of airspace enviro nm en t around the airport us in g real-t im e data fr om the airport' s radar sy st em , fo r the purpose of sc hedu ling airport resources . X X X Flight trac ki ng / mana ge me nt tool Prov ides aircraft planni ng an d mana ge me nt cap abilities by mo nitori ng real -t im e aircraft positio ns, air port stat us, an d weat her conditions . X X X Ai r tra ffic fl ow mana ge me nt Prov ides capability to ma na ge the co mp lete ra nge of aircra ft operatio ns fr om gate to gate, as we ll as provides operatio nal an d post operatio ns metrics an d perf or ma nce an alysis . X X X X X X Flight status data f eeds Prov ides data stream to support f light info rm ation di spla ys an d custom fl ig ht track i ng solu ti on s. X X X Su rf ace detectio n sy st em (A SDE- X) Prov ides a traffic mana ge me nt sy st em fo r the airport su rf ace that ma in ta in s se am le ss covera ge an d aircraft identificatio n to air traf fic controllers. X X X Su rf ace mana ge me nt sy st em Prov ides a br ow se r- based su rf ace mana ge me nt sy st em fo r ef ficient and cost-e ffec tive ma nage me nt a nd measur em en t of airside operations . X X X X X X In fo rm a tion we b dash board Prov ides info rm ation dashboard over the Inte rn et to facilitate collaborative decision ma ki ng fo r airside and landside operations . X X X X X Navigation sy st em Prov ides the operational info rm ation, altitude, and position necessary for aircraft guidance in all fli ght ph as es (in fl ig ht an d on gr oun d ta xi in g). X X X Cons ulti ng services Prov ides professional consul ti ng support for strategic im plem en tation, im plem enta tion oversight, an d im prov em ent of shared aircra ft status solutio ns . X X X X X X X X 162 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy B ef o re D u ri n g A ft er A ir si d e La n d si d e A ir p o rt A ir C ar ri er / G ro u n d H an d le r FA A

Category SolutionType Function Phase Ops Stakeholder C om m un ic at io n of S ta tu s Real-t im e aircraft data feed Prov ides data stream to support fl ig ht in fo rm ation displa ys a nd cust om fl ight trac ki ng solutio ns . X X X X Flight info rm ation displa y sy st em - airpor t Prov ides flight in fo rm ation on a mo nitor mo un ted in th e airport us in g a real-t im e aircraft data feed or ma nu al in pu t. X X X X Flight info rm ation displa y - intern et Prov ides flight in fo rm ation vi a the Inte rn et using a real-time aircraft data feed or ma nu al input. X X X X Flight info rm ation displa y - m obile Prov ides flight in fo rm ation to a m obile de vice usi ng a real-t ime aircraft data feed or ma nu al input. X X X X Ai r tra ffic displa y - airpor t Prov ides real-t im e air tra ffic info rm ation, in cluding dela ys and cancellatio ns, in graphica l fo rm at us in g a m onitor mo un ted in th e airport. X X X X Ai r tra ffic displa y - intern et Prov ides real-t im e air tra ffic info rm ation, in cluding dela ys and cancellatio ns, in graphica l fo rm at via the In ternet . X X X X Messa ge broadcasti ng sy st em Prov ides auto ma ted text -b ased me ss age broadcasting to a predef ined distribution li st according to a predefined communication ch a nnel. X X X X X Em erge nc y no tification call sy stem Prov ides auto ma ted audio me ss age broadcasting to a predef ined distribution li st . X X X X X Social me dia (Facebook, Tw it ter, blog s, podcasts, etc.) Prov ides the abilit y to se nd ongoi ng co mm unicatio n to a ma ss num ber of subscribers vi a the Inte rn et or m obile de vice applications and receive feedback . X X X X X X Flight status alert - em ail, text Prov ides auto ma ted text -b ased me ss age broadcasting to a distribu tion li st of subscribers via em a il or text me ssa ge regarding a speci fic fl ig ht status . X X X X X Part 2 – Resource C – Tools 163 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy B ef o re D u ri n g A ft er A ir si d e La n d si d e A ir p o rt A ir C ar ri er / G ro u n d H an d le r FA A

Category Solution Type Function Phase Ops Stakeholder R es ou rc e M an ag em en t Ai rcra ft , gate, an d concourse availability Prov ides the abilit y to anal yz e the cause of dela ys in order to determ ine th e mo st ti me - efficient usage of aircra ft , gates, an d stan ds. X X X X X X X Gate mana ge me nt sy st em Prov ides the abilit y to plan a nd ma in ta in the sche du ling, allocation, and real-t im e status of gates. X X X X X X Ground hand li ng staff mana ge me nt sy st em Prov ides the abilit y fo r scheduling an d deploy me nt of ra mp personnel to optim ize gro und hand li ng operations. X X X X X Ground hand li ng resource mana ge me nt Prov ides the abilit y fo r scheduling an d ma nage me nt of ra mp personnel an d gr oun d hand li ng equi pm en t to opt im i ze gro und hand li ng operations. X X X X X Resource mana ge me nt sy st em Prov ides the abilit y to plan a nd ma in ta in the sche du ling, allocation, and real-t im e status of resources including gate s, aircraft parking st an ds, ch ec k- in counters, airl in e back office s, ki os ks, an d bagg ag e carousels. X X X X X X Pa ss en ge r H an dl in g Cons ulti ng services Prov ides professional consulting support for defini ng passeng er ha nd ling strategy be fo re an event, and revising strategy based on lesso ns learned after an ev ent. X X X X Pa ssenger transport fr om aircra ft Prov ides phy sical me ch anis m fo r transporting passenge rs fr om an aircra ft th at is no t doc ke d at a gate to the te rm in al bu ilding. X X X X Visu al doc king gui dan ce sy st em Prov ides auto ma ted vi su al doc king gu idance fo r aircra ft based on the active ra mp enviro nm en t to maxi mize safe ty and ef ficiency . X X X X 164 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy B ef o re D u ri n g A ft er A ir si d e La n d si d e A ir p o rt A ir C ar ri er / G ro u n d H an d le r FA A

Category Solution Type Function Phase Ops Stakeholder A ir C ar ri er / Ba gg ag e M an ag em en t Baggage sortation Provides for the automatic verification of baggage and its destination for accurate and efficient routing. X X X X Baggage tracking Provides for the automated tracking of baggage from check-in to final destination. X X X X X Baggage recovery Facilitates the efficient recovery of bags due to mishandling or disrupted aircraft operations. X X X X Baggage reconciliation Provides for the identification of passengers that have not yet boarded and prevents their baggage from being loaded. X X X X Pa ss en ge r Pr oc es sin g Common use passenger processing Provides the ability to share check-in and gate resources among airlines for flexibility and efficiency in passenger processing. X X X X X Local departure control system Provides the ability for airline operations without a locally accessible proprietary departure control systems to process passenger and baggage. X X X X X W ea th er D et ec tio n Weather display Provides visual information regarding current weather conditions. X X X X X X Weather forecasting and reporting system Provides the ability to analyze probable weather conditions to enable decisions to be made prior to and during an event. X X X X X X X Instant alert weather system Provides the ability to receive instant alerts at the desktop workstation for relevant weather events. X X X X X X X Lightning detection system Provides the ability to detect lightning in local and/or long range conditions. X X X X X X X Part 2 – Resource C – Tools 165 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy B ef o re D u ri n g A ft er A ir si d e La n d si d e A ir p o rt G ro u n d H an d le r FA A

166 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 11 – SAMPLE WORKSHOP AGENDA (Edit as necessary to meet your airport’s needs) Purpose: Workshops are an effective way to bring together service provider organizations to compare plans, review past performance, and get organizations thinking about the benefits of a consolidated IROPS plan. This tool provides a sample workshop agenda so that an airport can see what topics should be discussed in initial workshops in order to facilitate communication, cooperation, and coordination between all service providers. Sample Workshop Agenda Workshop Goals and Objectives 1. Identify hot button issues and insights from previous IROPS events 2. Review status and examples of airline and airport response to the United States DOT’s rules on enhancing airline passenger protections (14 CFR Part 259 Enhanced Protections for Airline Passengers) 3. Discuss operational challenges associated with IROPS/extended delays: i. Communication and early notification ii. Shared situational awareness iii. Tracking diverted aircraft (flow of information) 4. Update airline station managers on the airport’s IROPS plans 5. Share relevant regional experiences and IROPS planning activities 6. Review IROPS best practices 7. Strategize for mutual assistance and coordination during the forthcoming fall/winter and/or spring/summer season Part One 1. Update airport staff on local and national IROPS response information Review recent IROPS events at the airport, including lengthy tarmac delays. This information will summarize the current state of readiness to successfully minimize the effects of lengthy tarmac delays within a more global summary of related passenger service activities based on experiences in the United States. Current pending passengers’ rights legislation and DOT requirements pertaining to IROPS events, including extended tarmac delays, should also be reviewed. This review serves to provide a better understanding of the purpose of the airport’s overall IROPS planning process and related activities to date. Part 2 – Resource C – Tools 167 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

2. Describe approach during an IROPS event/lengthy tarmac delay Review key steps necessary for dealing with an irregular operations event, as well as best practice joint actions that have been developed by airports in the United States that have been successfully implemented to mitigate the effects of IROPS events/lengthy tarmac delays on passengers. Part Two 1. Identify hot buttons and insights from a recent IROPS event/lengthy tarmac delay In breakout sessions, first focus the group on recent local IROPS events/lengthy delays where individuals will have the opportunity to describe what happened from their own perspectives and begin to identify “where your IROPS plan affects my plan.” The discussion opens the dialogue for improved coordination, collaboration, and communication between all aviation service organizations. Part Three 1. Strategize mutual assistance and coordination during the forthcoming season In a group discussion, request that all aviation service organizations discuss/vocalize what mutual assistance looks like from their perspective. The group should be challenged to use tools from ACRP Report 65 to describe how to improve local response to IROPS events. 2. Discuss specific operational challenges associated with customer service during IROPS events, including extended delays: • Communication and mutual assistance • Ground handling equipment • Gate and hard stand availability • Tracking diversion aircraft (flow of information) • Unforeseen operational activities – system implications • Technology enablers 3. Describe how recommendations from the workshop will be incorporated into the IROPS plan. 168 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 12 – NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION (NOAA) NATIONAL WEATHER SERVICE (NWS) CHECKLIST Purpose: The NWS provides climate, water, and weather forecasts and warnings to protect life and property and enhance the economy. Support to aviation is a part of this mission. The NWS supports aviation through all phases of flight, from the local weather conditions and forecasts at the airport to forecasts for en-route and international weather. This support is provided by professional meteorologists at 122 Weather Forecast Offices (WFOs), 9 National Centers, and 21 Center Weather Services Units. This tool includes a sample weather checklist for use before, during, and after an event, as well as contact information for NWS offices across the United States. Aviation support is through all phases of flight. International flight forecasts and advisories are provided by three Meteorological Watch Offices: the Aviation Weather Center (World Area Forecast Center) in Kansas City, the Alaska Aviation Weather Unit in Anchorage, and the WFO in Honolulu. En-route forecasts and advisories for the National Air Space are provided by 21 Center Weather Services Units (CWSUs) and Meteorological Watch Offices, and take-off and landing forecasts are provided by WFOs for over 620 U.S. airports. The NWS vision is for a weather-ready nation, which is a society prepared for and responding to weather- dependent events. With improved collaboration with airport managers and understanding of weather impacts to airport operations, the NWS can provide decision-support services to reduce the impact of weather. Each airport is affected differently by weather conditions, and the NWS provides a wide variety of weather information to assist in planning and tactical decisions. For example, National Centers for Environmental Prediction (NCEP) produce long-range forecasts for significant events. These are available at www.hpc.ncep.noaa.gov or www.spc.noaa.gov for thunderstorm outlooks. For weather events affecting a region’s airport, that local NWS Office will have the best information. A quick glance at weather hazards is available at http://www.nws.noaa.gov/largemap.php. Each NWS office provides localized warnings of hazardous weather for their area of responsibility, including severe thunderstorms, high winds, icing, and snowfall. NWS offices can also provide Airport Weather Warnings (AWW). These airport-specific warnings address weather phenomena that can adversely affect airport ground operations. Information contained in the AWW is useful to airport managers, fixed-base operators, airline ground personnel, and others responsible for the safety of ground operations. The criteria used to issue these warnings are coordinated between the local airport management and the NWS office so that they focus on those weather conditions that affect the operations of the airport. Improved weather information through NWS decision-support services before, during, and after weather events will assist airport managers in mitigating the impact of weather on operations. The contact information contained in this tool is provided by NOAA for internal governmental use including airport managers, the IROPS Champions, and aviation service providers. Part 2 – Resource C – Tools 169 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Sample Weather Checklist Before: • Contact your local NWS office Meteorologist-in-Charge or Warning Coordination Meteorologist (public telephone number lists follow) • Discuss best method/number for contacting the office • Discuss critical thresholds for your operations o Threshold for planning 2 - 5 days ahead of time, for example Significant snow/ice Significant winds Significant thunderstorm outbreak o Thresholds for real-time decisions, for example Onset of snow/icing Amount of snow/ice/rain Onset of significant winds Onset of thunderstorms • Determine best method of communicating weather information for strategic planning • Routinely exercise this process to ensure smooth operations during an event During: • Contact local NWS office for updated information on weather events and impact • Receive information from NWS office from predetermined sources After: • Provide feedback to NWS office on content and flow of weather information • Review event for improvements in the process 170 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Permission to print this content has been issued by NOAA on 12/20/11 Part 2 – Resource C – Tools 171 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Permission to print this content has been issued by NOAA on 12/20/11 172 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Permission to print this content has been issued by NOAA on 12/20/11 Part 2 – Resource C – Tools 173 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Permission to print this content has been issued by NOAA on 12/20/11 174 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Permission to print this content has been issued by NOAA on 12/20/11 Part 2 – Resource C – Tools 175 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

176 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 13 – SAMPLE COMMUNICATION PLAN (E dit as necessary to meet your airport’s needs) Purp ose: In order for se rvice prov iders to achieve effe ctive situational awareness between all organi za tions during an IR OPS event, it is essential that an agreed- upo n co mm unication plan be de vel oped, understood, and comm unicated to all parties. This tool prov ides the structure for service prov iders to use during an IROP S event to ensure the right inform ation is discussed in clear language, both oral and written. Sample Communication Plan Establish talk ing points : Pr epare for the following questions/data requests that ar e co mm onl y asked, such as : • What is the im pact to the airpor t? • What are the im pacts to our custom ers? • What is the estim ated length of ti me before operations return to nor ma l? • What actions are we taki ng no w? • Is there an y sy st em or technolog y issue arising? • Is the airport closed ? YE S or NO • Is the airfield closed ? Websites : Pr epare to use we bsites during IR OP S events to comm unicate both internally and externally . • In ternal website : – Establish what needs to ha pp en and who will do it – Status board: Di spla y ongoing upd ates fro m airport operations cente r • External website: – Meet with the airport’s IT organization to keep flight inform ation displa y sy st em (F ID S) and pa ging sy st em s u pdated durin g IR OP S ev ents – Establish co mm unication links and interfaces Part 2 – Resource C – Tools 177 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

178 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 14 – SOCIAL MEDIA (Edit as necessary to meet your airport’s needs) Purpose: This tool is intended for use by airport staff to help get started using social media forums to promote their airport and benefit from the leverage these social media sites provide. In a time of emerging social media forums (e.g., Twitter, Facebook, blogging) it is becoming increasingly important for airports to embrace the leverage these social media forums can provide. It only takes one second for a negative post to reach thousands of people who will now see your airport in a negative light (e.g., “I will never fly out of this Airport again. TSA lines were out the door and I had to wait over an HOUR to get through security!”). Often when passengers are upset, it is directed at an airline, long security lines, concessionaires, etc.; however, because it happened at your airport, you can end up taking the brunt of the comments. Fortunately, it takes just as long for a message to be sent out via social media that sheds a positive light on your airport and airport operations, especially during IROPS events. However, benefits from social media will not be experienced if nobody at an airport is taking the initiative to utilize social media tools. Available airport staff should work with TSA, CBP, and the airlines during IROPS events to get the message out. Some ideas for social media posts include: 1) Post information related to widespread delays as soon as you are made aware to notify passengers before they arrive at the airport (e.g., delays as a result of weather, power outages). Direct them to their airline provider for specific information. 2) Post information related to extra security measures that are in effect so passengers can arrive at the airport with plenty of time to get through the TSA security lines. No need to divulge why; just post a friendly reminder to arrive at the airport with plenty of time prior to departure. 3) Post other information you believe would help enhance the passenger experience, especially during IROPS events. Setting up an account with a social media outlet is simple. Log on to your preferred social media forum (or multiple forums) via the internet and follow the instructions on how to set up a new account. Most social media sites have tips to help new users take full advantage of the options available to them, including how to make posts to their account (such as those suggested in the list above). It is important for airport staff to keep posts relevant to their audience and not to oversaturate the lines of communication with messages unrelated to the passenger experience. In order for an airport’s intended audience to receive posted messages, they need to know that their local airport participates in social media forums. There are several ways an airport can attract their audience, or “followers,” and let them know they partake in social media outreach. A couple ideas include a signage campaign at an airport, or a news story on local television about “friending” or “following” their airport on the appropriate social media site. Consider reaching out to other airports who engage in social media for tips and tricks on how to most effectively use these tools. Staying in contact with people who are affected by the airport reassures individuals that airport staff does care and are trying to make the passenger experience more enjoyable. IROPS events are inevitable, but the way you approach it can make all the difference. Part 2 – Resource C – Tools 179 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Use the table below to orga nize y our social me dia outreach by identi fy ing the staff responsible for prov iding updates on each social me dia foru m (if y ou use mu lt iple foru ms ) and to docum ent the trigger events and the frequenc y of updates need ed during an IROP S event. Pl ea se m odify the table as appropriate to y our situation. Organization Media Platform Staff Responsible Trigger Events Frequency of Updates Air port na me Facebook Contact na me (Diversions, long TS A li nes, po we r outages, wi despread weat her dela ys an d cancellatio ns, etc.) (Per trigger event or per ti me allo tm en t [e.g., 15, 30, 60+ mi n]) Tw it ter Contact na me (Diversions, long TS A li nes, po we r outages, wi despread weat her dela ys an d cancellatio ns, etc.) (Per trigger event or per ti me allo tm en t [e.g., 15, 30, 60+ mi n]) Blo ggi ng Contact na me (Diversions, long TS A li nes, po we r outages, wi despread weat her dela ys an d cancellatio ns, etc.) (Per trigger event or per ti me allo tm en t [e.g., 15, 30, 60+ mi n]) Te xt me ss aging Contact na me (Diversions, long TS A li nes, po we r outages, wi despread weat her dela ys an d cancellatio ns, etc.) (Per trigger event or per ti me allo tm en t [e.g., 15, 30, 60+ mi n]) 180 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 15 – DURING AN EVENT TOOLS (E dit as necessary to meet your airport’s needs) Purp ose: It is important to gather data on all aspects of IR OP S response to ma ke sure no gaps in passe ng er service exist. This docum ent provides two tools that can be used during all ty pes of IR OP S events: 1. A table for service provider management to document ac tions made 2. A ch ec klist outlining item s that should be addressed dur in g an IR OPS event for front li ne staff Tool #15a – Du ri ng an E vent Action Tab le fo r Se rvic e Prov ider Manage ment Airport Operations Department Offer and render assistance as available to air carriers and tenants. Assi st in selecti ng a park in g loca tion for the aircraft. Ground handlers are responsible for park ing aircraft because airport operations personnel will not perfor m th is func ti on . Ensure diverted aircra ft do no t obstruct loading gates fo r scheduled inco mi ng flights or trap parked aircra ft alread y at a gate or hardstand. It is preferable that all carriers coordinate parking early to ensure orderl y fl ow . Ad vise res ponsible gr oun d ha nd lers if parked aircraft mu st be mo ve d. Assi st wi th ve hicle in spectio ns an d mo ve me nt of perso nnel, vehi cl es, and equi pm en t in a nd ou t of the airport operatio ns area or th e security identification displa y area (SIDA) to unload, load, and service diverted co mp an y equi pm en t parked in th e SI DA , or on cargo aprons, tenant ra mp s, or closed taxi wa ys. Evaluate all actions fr om a cu st om er se rv ice st an dpoi nt. If passe ngers mu st be deplan ed to m eet DOT requir em en ts, coordinate response and necessa ry holding areas wi th airline, airport police, TS A, and CBP pe rsonnel. Coordinate wi th airport police, CB P, TS A, and airline supervisors all pla nne d ho ldi ng area s to segreg at e passeng ers (P AX ) if th ey are deplan ed. Ensure that ho lding area(s) ha ve operable la vato ries and othe rw is e m eet DO T requirem en ts . Ensure that the stor m is mo ni tored real -t im e and co mmu nica te updates to all ag en cies at le ast ever y 30 mi nu tes. Other. Airport Police Department Prov ide securi ty fo r containment of international passe ng ers in the sterile area as neces sa ry . If any no n-sterile area is used fo r holding inte rn atio nal PA X, assist in providing se cu rity fo r PA X. If necessa ry , request mu tu al aid support. As nece ssar y, co nt ac t other airport depart me nts or airport te nant bu si nesse s direct ly fo r assistance. Other. Airport Fire-Rescue Department Prov ide space as needed to segregate passengers. Augm en t se cu rity ef fo rts as ne eded. In addition to no rm al fi re responsibilities, provide em erge nc y fi rs t aid to passengers as ne ce ssa ry . If necessa ry , request mu tu al aid. Other. Part 2 – Resource C – Tools 181 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Airport Marketing and Community Relations Department Coordinate wi th natio na l/i nternatio nal ne ws me dia an d all in vo lved parties to ensure proper release of public info rm ation as nece ssa ry . Other. Airlines Notif y the CB P of an y di vert ed internatio nal fl ight s that are landing at th e airport, regardle ss of th e reason. Internatio nal passe nge rs w ill not be de plan ed until adequate holding facilities ha ve b een coordinated wi th airport perso nnel. Ensure all decisions regarding deplaning and segregatio n of interna tional passengers are ma de in concert with CB P perso nnel. Notif y the TS A Coordination Center at le as t tw o ho ur s prior to reboarding wh en passe ng ers ha ve deplan ed at the airport. Manual screening requires additional time needed for screening/reboarding. Maintain an acc urate passe nge r ma ni fe st at all ti mes an d presen t it to CB P pers onnel for im mi gratio n or accountability purposes. Coordinate an y passen ger ne ed s (e.g., food, wa ter, me dici ne , child care, health an d h ygi en e) wi th CBP and all appropriate organizations as soon as possible. Co mf ort, h ealth, and cust om er se rv ice need s mu st be proactivel y met. For situatio nal aw arene ss an d ra mp fl ow , advise airport ope ratio ns wh en ex pecti ng th e arrival of an y di verted aircraft. Coordinate wi th AT C se rv ices, by wa y of fli ght cr ew co mm unica tions, on wh ere to direct diverted aircraft for ground hand li ng purposes so as to av oi d havi ng a nega tive im pact on the mo ve me nt of other aircra ft . Coordinate an y passen ger ne ed s (e.g., food, wa ter, me dici ne ) wi th the appropriate organization or airport tenant as soon as possible. If support ma y be n eeded fr om other airport tenants (e.g., TS A, CBP, concessions, car rental agenci es ), ma ke the cal l as ear ly as possible, pref erably be fo re they close. Wh erever possible, assist wi th gro und ha nd li ng support equi pm en t to acco mm odate ot her di verted aircra ft . Ensure that passengers and crew re main wi th qu ick- tu rn or gas and go aircra ft . Ensure that fl ig ht crew co mm unica tion to airport personnel (e.g., operations, police) pass through local airl in e superv is or y st af f. Th is is a MU ST . Be fo re deplaning, advise passenge rs of th ei r circumstances and plan for their care and acc ommodations. Th is adviso ry should co me fr om the cr ew in coordination wi th st ation ma na ge me nt. Air port perso nnel sh ou ld also be info rm ed. Ensure that deplaning passengers understand that they ma y re mo ve th eir car ry -o n l ugg age, blankets, and pillo ws if th ey w ill later retu rn and subsequently depart on the sa me ai rcra ft . Co mmu nica te that passengers ma y be deplan ed into the conc ou rse in accordance wi th airline policies. It is critical that th e airline advise passe ngers th at if th ey le av e the sterile area th ey w ill no t be allo we d to re -enter . Passenger and ba gga ge screen in g serv ices ar e una vaila ble wh en the TS A ch eckpoint is closed . Ensure that fl ig ht crew s re ma in wi th passe nge rs until alte rn at e provisions are ma de. Th ey wi ll serve as the cu st om er service representa ti ve to and ad vo cate for their cust om ers. Ensure ground handling and pa rking of aircraft and of those of airlin es wi th whic h airl in es have gr oun d hand li ng agre em en ts . Make nece ssa ry arrang em en t if passe nger tr an sportation is needed from a re mo te park in g loca tion to the concourse or term in al. Vehicles mu st be operated by properl y qu a lified driver/escorts wh en accessing an y mo ve me nt area, n on- mo ve me nt area, or th e SIDA . Im plem en t corporate aircraft diversion pl an . Other. 182 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

GOVERNMENT AGENCIES TSA Establish procedures to screen international passengers that have b een ou t of a sterile area prior to reboa rding an aircraft wh ose destin ation is into a controlled sterile area. Cons ider mu tu al aid requests. Passenger screening an d augmen tation to mo nitor se cu re/n on secure areas ma y be needed in extr em e situatio ns. Other. ATC Services Establish aircra ft gro und cont ro l procedures to quickl y, an d sa fe ly park aircra ft fo r unloading. Maintain open lines of co mmu nicatio n wi th airl in es and ground ha nd lers operating at th e airport. Other. CBP Authorize an y aircra ft servicing or cr ew mo ve me nt on inte rna tional flight s. Th is au th orizatio n can be gi ven in advance by CB P pers onnel vi a telephone if servic ing/cr ew pref li gh t inspection is critic al and a CBP officer ha s not yet arrive d at th e diverted aircraft. Coordinate inte rn ational di versio n deplan i ng wi th airport personnel. Pa sse ng ers will be deplaned and mo ve d directly to the designated area. Th at location will be dete rm in ed by the num ber of passengers on the diverted aircra ft and available fa cu ltie s. Ever y ef fo rt w ill be ma de to k eep passengers se gregated in the conc ou rs e for security, co mf ort, and rapid reboarding. Ensure that security fo r the segregatio n of passe ng ers and cr ew wi ll be a coordinated effort by the CBP, TS A, and airport pe rsonnel. Ensure that due to personnel, equi pm en t, and regulatio n is sues , clearing passengers fo r entr y in to th e United States wi ll only be done as a last resort. Ever y ef fo rt wi ll be ma de to mo ve in ternatio nal passengers to th eir original destin atio n fo r clearance purp oses. Ensure that the processing of pa ssengers fo r entr y at the airport port of entr y is coordinate d wi th the port of original destin atio n. If au thorit y to clear passenge rs is grante d, th ey mu st be processed for entr y with all car ry -o n an d ch ec ke d ba gga ge. A separate clearance area w ill be set up wh ere both electronic processing and luggage search can be acco mp li sh ed wi th th e appropriate level of privac y. To do so, TS A requires a mini mu m of tw o ho urs ad va nce notice. Other. OTHER TENANTS Concessions See To ol 8 – Co ncessi on s Ch ec klist for Sn ow an d Hu rricane Events fo r a sa mp le co ncessi on s chec kl is t. Ground Transportation Cargo, Etc. Part 2 – Resource C – Tools 183 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

184 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Tool #15b – Du ri ng an Event Fron tline Che cklis t AIRPORT Co mm unication Media and co mm unication pl an activated Term inal Capacity provided for large num ber of passengers Rest areas prov ided/blankets La vato ry serv ic e Park ing/Ground Transportation Groun d transportation plan ac tivated Passeng er Essential Provisions F ood / hy dration (concession s plan activated) Retail (concessions plan activ ated) L odging (hotels notified) Additional Staffing Em pl oy ee transportation Supplem ent staffing Assistance desk Special serv ices Medical response Tracking aircraft Coordination with relief orga nizations Equipm en t Ga te sharing Hard st ands Part 2 – Resource C – Tools 185 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

AIRLINES Depl an ing On ward transportation Coordination with airport operations Groun d supp ort equipm ent (e.g., gates, hardstands, tugs, towb ars, AC) requested Passeng er Care L odging Bagga ge Co mp ensation In fo rm ation/co mm unicatio n F ood/ hy dr atio n Cleanliness Special serv ices GOVERNMENT AGENCIES AT C Services Pr iority treat me nt for dela ye d flights if requested by the aircraft operator or a designe e (pilots, dispatchers, etc. ) CB P Ac tivate plan for after-hour capabilities Creation of ad hoc sterile ar ea s via me mo randum of unde rstanding (MOU) activation TS A Creating of ad- hoc sterile ar ea s via MOU activatio n Escort plans activ ated Re -tic keting plan activ ated CD C Pl an activation for internatio nal flights subject to quarantine Pl an activation for diversion airports in the sy st em FB O FB O suppor t equipment provided 186 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 16 – DIVERSION CHECKLIST (Edit as necessary to meet your airport’s needs) Purpose: When aircraft are diverted, passengers end up in unexpected places at unexpected times, and service providers need to coordinate efforts to accommodate their needs. In the event an aircraft is diverted to a diversion airport, this tool provides the steps that should be taken by airlines and the diversion airport (including their public safety department [airport police]) before, during, and after a diversion event. Roles of airlines, airport operation (specifically the operations manager and duty manager), and the public safety department are outlined in this tool. AIRLINE Before: • Notify airport operations. Include: – Airline – Approximate arrival time – Approximate departure time – if available – Reason for potential diversion – Intentions (examples: gas and go, extended delay, or unknown) – Potential services needed – Number of passengers on board During: • Communicate plane’s intentions to airport operations. • Confirm airport operations and ensure that the duty manager will assist with communication. • If necessary, ask for assistance. Determine who will coordinate passenger accommodations, including: – Food – Transportation – Lodging – Security – Special Needs • Communicate status to necessary service providers at least every 30 minutes. After: • Supervisor – obtain feedback from employees about what went well, what did not, and what changes could be made. • Manager and supervisor join post-diversion conference call with airport. Part 2 – Resource C – Tools 187 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

AIRPORT OPERATIONS Before: • Create a 24/7 email contact/distribution list of major airport stakeholders in your region, including diversion airports, to communicate status and track diverted flights. For hubs and large airports, establish a conference call with key stakeholders 24 to 48 hours prior to severe weather forecasts to facilitate communications and coordination (i.e., National Weather Service, FAA, airlines, CBP, TSA, and airport departments). • When notified by airline of a diversion, communicate to airlines that airport operations will be the point of contact during the event. • Determine whether this is a regular diversion (airline and aircraft that are regularly serviced at airport). – If regular aircraft/airlines, determine and communicate equipment available to help service (see attached sample equipment list) – If airline has no representation at airport, determine potential services needed and communicate what equipment/options are available to service particular aircraft (see included sample equipment list) • International diversions: Have a plan in place ahead of time with CBP to handle and/or offload passengers from international diversions, especially if there are no CBP officers or facilities present at an airport. At a minimum, coordinate with the regional CBP official and local law enforcement to share important CBP contact information, such as 24/7 phone numbers. During: Operations Center Notify: • Airport duty manager in charge • Law enforcement officer (LEO) in charge • Federal security director (FSD) • Senior duty manager (or deputy aviation director – airside operations) • Concessions, if services are needed • CBP (if international flight, need 24/7 contact information) • Communicate with airlines frequently during event (at least every half hour). • Remind airlines of available assistance, including: – Additional resources (If aircraft cannot taxi from its location, coordinate to use local FBOs and/or aircraft recovery service to have aircraft removed.) – Ability to contact resources for airlines if requested – Use of social media to inform passengers – Providing of flight information display systems (FIDS) updates Communicate status to necessary service providers at least every 30 minutes. Ascertain who is making the decisions about the status of an aircraft regarding loading and unloading of passengers, bags, and cargo. This is especially important if an airline is not represented at an airport; airport staff should find out from the flight crew some of the system operations centers (SOCs) or headquarters phone numbers so that they can contact someone in a position to make a decision at critical times (such as when the 3- and 4-hour rule is reached). This should be done as soon as the aircraft is grounded and parked. 188 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Airport Operations Manager • When notified of a possible diversion, contact the applicable airline to determine the potential length of the delay. • Record in diversion contact log: – Date/time – Air carrier name and contact information – Flight number – Aircraft type and tail number – Passenger count – Arriving from/original route – Parking location – Reason for diversion – ETA/ETD – Jet bridge use and departing flight number – Crew time left (international flights only) – Services needed • Determine gate needs (coordinate a gate from which to deplane if delay exceeds 3 hours for domestic flights and 4 hours for international flights), whether airline will accommodate aircraft at their regularly assigned gate(s), and can or will they accommodate other airlines. Gate options must take into consideration: – Aircraft type/size – Access to restroom facilities and restroom service needs – Access to vending machines – Access to drinking fountains – Food and beverage services through tenant restaurant vendor – Ability to restrict international passengers from mixing with domestic passengers* – Airline support to contain passengers isolated from domestic passengers* – No CBP processing available for international flights* *international flights only • If no gates are available: – Coordinate with airlines and ATC services to direct aircraft to park at alternate parking location, escort marshaling/ground handling crew as necessary – Coordinate with airline or ground handlers to provide access to aircraft for air stairs, refueling, lavatory services, ground power units (GPUs), and other ground service equipment (GSE) – Coordinate deplaning of passengers via air stairs and buses or via loading bridge at terminal when delay exceeds 3 hours (4 hours for international flights) and/or when airline requests access to terminal • If the aircraft delay is a departure and the passengers are deplaned at the terminal: – Screening for passengers who leave the concourses must be provided or passengers must remain in the sterile area and food, beverage, and restroom facilities must be provided until the passengers are reboarded for departure Part 2 – Resource C – Tools 189 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

• If the projected time at the gate is after the time that screening is closed: – Coordinate passenger screening operations to remain open or coordinate with the LEO to provide staffing of the checkpoint to prevent re-entry of unscreened passengers • Coordinate provisions with the airport’s concessions. • Ensure that LEO is available to assist with disruptive passenger(s). • Maintain contact with the airline representative to determine if the flight may be cancelled and, if so, the airline’s intentions concerning its passengers. • For international flights: – Coordinate with CBP port director for any concerns for passenger boarding/containment – Arrange for LEO to monitor passengers to prevent mixing with domestic passengers (must be local airline employee or air crew members when no local representative is available) – Establish visual or physical perimeter stanchions, seating, and so forth to contain passengers (perimeter should allow restroom access without escort) • Communicate status to necessary service providers at least every 30 minutes. After: • Initiate conference call: – Obtain feedback on what went well, what didn’t go well, and any changes that need to be made • Type up notes from conference call – disseminate to all entities as lessons learned/action items. • Check that the following entities attended conference call: – Airport operations – Airlines – FAA – TSA – CBP – LEO – Public safety – Concessions – Car rental – Parking – Military (if on-site) – FBO 190 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

PUBLIC SAFETY DEPARTMENT Before (if notified prior to aircraft landing): • Notify airport operations specialist on duty. • Fill out diversion contact log. • If warranted, notify additional personnel or entities such as concessions, FBO, and the like. • For extended delays at the airport, determine the resources to accommodate the situation and call up resources as appropriate. During: • Obtain additional information about aircraft: – Tail number – Time landed – Any other pertinent information – Fill out diversion contact log • Inform airlines of public safety assistance available. • Communicate status to necessary service providers at least every 30 minutes. After: • Obtain feedback from officers regarding what went well, what didn’t, and any changes that need to be made (similar to post-incident discussion). • Join the post diversion conference call and provide input. Part 2 – Resource C – Tools 191 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Sampl e Equi pm ent Ch ec klist (E dit as necessary to meet your airport’s needs) Sample Equipment List Airline Airline Airline Airline Airline Airport Other 737 To w Bar (T B) 757 TB 767 TB A319/320 TB AI RB US TB A320 TB MD80/90 TB CRJ 200 TB CRJ 700/900 TB E190 TB Q-400 TB Universal TB 737 Pu shup stairs 737 Ai r stairs 757 Cabi n access stairs 757 Pa ssenger stairs no n- mo torized 767 Stairs 767 Pu shup stairs 747/77 7 Stairs A320 Diesel po we red air stai rs A320 Pu shup stairs MD80 Galle y access stairs Ai r start Ai r Start Wide body Capable Ground Po we r Unit (GPU) Bottle air start La vato ry service truc k La vato ry service truc k, wi de body capable Po table wa ter cart Cabin se rv ice li ft truc k wi de body Pu shback tractor, wi de body capable Pu shback tu g 192 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

TOOL 17 – AFTER AN EVENT DEBRIEF (Edit as necessary to meet your airport’s needs) Purpose: It is important to debrief the response to an IROPS event in order to discover lessons learned and improve passenger service during an event. This tool describes how to discuss and document lessons learned, as well as response actions needed by each service provider related to surge, capacity, off-hour, and extended delay situations. Brief description of event Date_____________________ Insert a brief description of event Causes: • Local weather • Diversion(s) • Aircraft mechanical • Aircraft crew • ATC service system • Other Impacts Surge: Potential impact caused by the rate of arrival of aircraft, timing of deplaning passengers, and subsequent movement of passengers through airport. • Aircraft • Passengers* Capacity: Potential impact caused by the total number of aircraft that have arrived at the airport and of the number of passengers located in any particular areas of the airport • Aircraft • Passengers* Off-hours: Potential impact caused by the time of day at which aircraft arrive at airport and the subsequent need to process passengers • Aircraft • Passengers* Extended Stay: Potential impact caused by the duration of stay (often measured in days) that aircraft remain at the airport and that passengers are delayed before resuming their travel • Aircraft • Passengers* *Including animals Part 2 – Resource C – Tools 193 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Lessons Learned Response Action Response Party Term inal • Co mm unication center • Ra mp • Ga tes • Concessions • Groun d transportation Ai rcraft • Tarm ac • Cock pit comm unication • Pa ss enger deplanes • Additional service IROPS Action s • Co mm unication issues • Pr ocedure m odifications • Equipm ent and resour ce s • Serv ice lapse • Operat ions a nd ma intenance restock • Ne w capabilit y • Ot he r 194 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

RESOURCE D – SAMPLE IROPS PLAN Grand Bay International Airport Irregular Operations Contingency Plan Adopted 12/12/11 All persons, places and scenarios listed in this sample plan are only examples and are not intended to represent any actual persons, places or situations. Part 2 – Resource D – Sample IROPS Plan 195 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Document Revision Revi sion Date Cont en t Revi sion Date Cont en t 196 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

CONTENTS 199 INTRODUCTION 201 C HAPTER 1 – EXECUTIVE BUY-IN/G ET ORGAN IZED 201 1.1 Establis hi ng an IROPS Co nti nge nc y Response Co mm itte e 203 C HAPTER 2 – DOCUMENT CURRENT SITUATIO N 203 2.1 Re vi ew ing Existi ng IROPS Response Plans 204 2.2 Re vi ew ing Lo cal IROPS Events and As se ss in g Lo cal Situation 205 2.3 Pa ssenger Needs during an IROPS Ev en t 206 2.4 Tr acking of Dela ye d Ai rcra ft 206 2.5 Tr igger Even ts and Co mm unica tions Pl ans 207 2.6 Su pport fo r Pa ssenge rs 209 2.7 Tr acking Inventor y 209 2.8 Sk ills Availability 211 C HAPTER 3 – ESTABLISH PROCEDURES TO COOPER AT E 211 3.1 Coope ration Proc ed ures 211 3.1.1 Airlines 211 3.1.2 FAA 212 3.1. 3 C BP 213 3.1.4 TS A 214 3.1.5 Co ncessions 214 3.1.6 Gro und Transportati on 215 3.2 Ot her Pr ov iders to Consid er 217 C HAPTER 4 – REVIEW , UP DATE, AND TR AI NING 217 4.1 IROPS Coor di natio n Work sh op 218 4.2 IROPS Coor di nate d Fron tl ine Tr aining 219 C HAPTER 5 – CONSOLIDA TED COOPER AT ION AC TI ONS DURING AN EVENT 219 5.1 Mon itoring IROP S Ev en t Indicators 219 5.1.1 Aircraft Status 221 5.1.2 Tracki ng We ather 221 5.2 Ex ecuting IROPS Plans a nd Pr ocedures 222 5.2.1 IROPS Communications Plans 222 5.2.2 Passenger Support Plans 224 5.2.3 Procedures with Airlines 224 5.2.4 Procedures with FAA 224 5.2.5 Procedures with CBP 225 5.2.6 Procedures with TSA 225 5.2.7 Co ncessions Procedures 226 5.2.8 Gro und Transportatio n Procedures 226 5.2.9 Procedures with Other Providers 227 CHAPTER 6 – CAPTURING LESSONS LEARNED AND UPDATING PLANS 227 6.1 Afte r an IR OPS Event 227 6.2 Less ons L ear ne d Part 2 – Resource D – Sample IROPS Plan 197 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

198 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

INTRODUCTION Purpose This document provides the coordinated IROPS Contingency Plan for Grand Bay International Airport. It was developed by the airport’s IROPS Contingency Response Committee under the sponsorship of the airport operations department. Membership in Grand Bay International Airport’s IROPS Contingency Response Committee comprises representatives from each of Grand Bay International Airport’s aviation service providers. The committee recognizes the importance of individual plans and that a coordinated effort by the airlines, airports, government agencies, and other aviation service providers is essential to successfully minimizing the impact of IROPS events on passengers. This coordinated contingency management plan provides a common point of focus for Grand Bay International Airport’s coordinated response to IROPS events. The emphasis for this plan is the identification and documentation of areas of contingency activities of Grand Bay International Airport’s aviation service providers that require support from one or more service provider organizations. The plan format follows the recommendations provided in ACRP Report 65: Guidebook for Airport Irregular Operations (IROPS) Contingency Planning. Grand Bay International Airport has recognized the importance of the guidance provided by the U.S. Department of Transportation (DOT) and its Model Contingency Plans to Deal with Lengthy On-Board Ground Delays. Use of Terms The following is a list of terms and definitions used throughout this Model Plan and associated topic worksheets. See the glossary contained in ACRP Report 65: Guidebook for Airport Irregular Operations (IROPS) Contingency Planning for additional terms and definitions. Irregular Operations (IROPS) – Exceptional events that require actions and/or capabilities beyond those considered usual by aviation service providers. Generally speaking, an impact of these events is the occurrence of passenger experiencing delays, often in unexpected locations for an undetermined amount of time. Examples include extreme weather events (such as snowstorms, hurricanes, tornados), geological events (such as earthquakes, volcanoes), and other events (such as power outages or security breaches). Passengers – Includes people traveling, service animals in the cabin, and live cargo onboard aircraft and in the terminal area. Customers – Includes both passengers and other non-aviation service personnel such as meeters and greeters who are in the terminal area. FAA – Federal Aviation Administration - Please note that for the purposes of this guidebook, references to the FAA include all forms of air traffic control (ATC) services. CBP – Customs and Border Protection TSA – Transportation Security Administration Service Providers – All entities at an airport that provide services for customers and passengers including but not limited to airports, airlines, concessionaires, ground transportation agencies, government agencies, Part 2 – Resource D – Sample IROPS Plan 199 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

fixed base operators (FBO), overnight accommodations, emergency response, military (if joint-use facility), and diversion airports. Passenger Needs Needs of passengers, both on-board aircraft on the ground or in the airport terminal during lengthy delay or other IROPS events, vary and normally require the attention of more than one party to meet their needs. By understanding the needs of passengers during such delays, Grand Bay International Airport, diversion airports, airlines, government agencies, and other aviation service providers can take appropriate steps to anticipate and address such needs. Causes of IROPS Events Causes of IROPS events can include extreme weather, geological events, reduction of airport facility capacity, aircraft mechanical problems, labor issues and others. The impacts of IROPS events include flight delays, cancellations and diversions resulting in potentially adverse impacts on passengers and other airport customers. In addition to impacts on passengers, IROPS events also have an impact on airport operations. As noted in ACRP Report 65, there are four types of impact during an IROPS event that must be planned for: • Surge • Capacity • Off-hours • Extended Stay Each IROPS event is unique, and airlines, diversion airports, government agencies, and other aviation service providers will benefit from the Grand Bay International Airport IROPS Contingency Plan accounting for diverse IROPS characteristics by adapting to changing conditions. Planning for Contingency Response The purpose of the Grand Bay International Airport IROPS response management process is to identify and document actions requiring coordination between two or more aviation service providers. Joint actions are identified that reflect both current individual contingency plans and areas of recommended communication, collaboration, and coordination between service providers. 200 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

CHAPTER 1 – EXECUTIVE BUY-IN/GET ORGANIZED Activities described in this chapter provide for: • The establishment of the Grand Bay International Airport IROPS Contingency Response Committee • Establishment of 24/7 contact/notification list • Documentation of procedures with airlines, government agencies, and support organizations • Conducting workshops and training (including table-top exercises) 1.1 Establishing an IROPS Contingency Response Committee The Grand Bay International Airport IROPS Contingency Response Committee has been established following the guidelines of the DOT’s Model Contingency Plan. Grand Bay International Airport’s manager Rodney Leavitt provides the sponsorship and designates the chairperson of the committee. The goal of the committee is to establish and enhance contingency plans through collaborative decision making. This will ensure that actions result in a unified level of customer care across all Grand Bay International Airport aviation service providers during IROPS events. Members of the Grand Bay International Airport IROPS Contingency Response Committee include representatives of all local aviation and customer service provider organizations. Organizations and representatives are shown in the following table (IROPS Contingency Response Committee). Part 2 – Resource D – Sample IROPS Plan 201 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

IROPS Contingency Response Committee As of 12 /15/11 Organization Cont act Name & Phone Nu mb er Al ternate Co ntac t Co mm ittee Chairperson Grand Ba y In ternatio nal Ai rp ort Ja me s Ro w Ad am Si eg fr ie d Airport Operation s La nd side Rand y Holbrook To m Mulc as ter Ai rs ide Rachel Clark Sean Ha ye s Airlines Fl ye r Ai rlines Za ch Th om ps on Dan Walter Om eg a Ai r Ga ry Nettleto n Jo hn Davi s Conces sions GBI Concessi on s Je nnell Black Ja mi e Willia ms Gr ound Transportation Zo om Re ntal s Al Ke ho e Nath an Johns on Hote l Shoreline Hote l Nolan Jackson Katie Carter Govern me nt Agenci es F AA Je ff Ballard Brett Ad am s TS A Jared E ngel La nce Foster CB P Ron Hoover Br ya n Dean Public Safety Operations Po lice Be n W ilson Ry an Banks Diversion Airpor t Long Isle Air port Matt Young Je ssica Ri ch ardson Fixed Base Operations Cent en nial FB O Lynn Schell Ashl ey Sc hille r Exec utive Man age me nt Liai so n Grand Ba y In ternatio nal Ai rp ort Rodn ey Le av itt Al li son Robins on 202 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

CHAPTER 2 – DOCUMENT CURRENT SITUATION The IROPS data collection activities focus on: • Reviewing existing IROPS contingency plans • Local IROPS events history • Local customer needs • Local tracking of delayed aircraft • Local trigger events and communications plans • Local support for passengers on-board, being deplaned, and in-terminal • Local tracking of inventory • Local skills availability 2.1 Reviewing Existing IROPS Response Plans It is recognized that each of Grand Bay International Airport’s organizations may have their own plans for response to IROPS events. It is also recognized that United States DOT’s rules on enhancing airline passenger protections (14 CFR Part 259 Enhanced Protections for Airline Passengers) require air carriers to adopt tarmac delay contingency plans and the coordination of those plans with airports. The purpose of this section is to identify the several IROPS plans of local airlines, airport operations, and FBO organizations as they relate to areas of coordination between organizations. The following table (IROPS Response Plan Review) describes both formal and informal understandings of coordination between these organizations, as well as individual organization standard operations procedures (SOPs) related to IROPS response. Descriptions of procedures with concessions, ground transportation, and government agencies (FAA, TSA, and CBP) are found in Sections 3.1.1 through 3.1.5 of this plan. Part 2 – Resource D – Sample IROPS Plan 203 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

IROPS Response Plan Review Organization Cont ingency Plan Descri ptio n of C oor dinati on Fl yer Ai rlines • Depl an in g – If deplanin g, c ontact police and the TS A, determ ine if passengers will st ay in st erile area, and coordinate with TSA for bo arding passes that will be issued for reentr y into the sterile area. • Not deplanin g – Fl yer airlines will coordinate with police and airpor t operations regarding their needs (and concessions if th ey n eed food and/or water). • Fuelin g – Fl ye r air lines wi ll c oordinate with Cente nnial FB O. Om ega Ai r • Depl an ing – If deplanin g, c ontact police and the TS A, determ ine if passengers will st ay in st erile area, and coordinate with TSA for bo arding passes that will be issued for reentr y into the sterile area. • Not de planing – Om eg a Ai r will coordinate with police and airpor t operations regarding their needs (and concessions if th ey n eed food and/or water). • Fueling – Om ega Ai r will coordinate with Centennial FB O. Ai rport Operations If Grand Ba y receives a di versi on, airport operations will be av ailable during nor ma l hours and after hour s if necessary . Ad mi nistration will be notified in the event of a di versi on in order to stre am line co mm unication between affected parties and the local co mmu nity . Centennial Centennial will prov ide fueling and other services to di versio n aircraft when notified by the airline and/or chief pilot. Ce ntennial wi ll handle scheduled flights first and diversion flights sec ond. GB I Co ncessions Concessions will st ay after hours when ne ed ed to handl e aircraft di versi ons and an influx in passengers. Zoom Rentals Zoom Re ntals will k eep nor ma l offi ce hours; howev er, in the event of a di versi on event, ke y staff wil l return to the airport to handle passengers who need gro und transportation. Shoreline Ho tel Shoreline Ho tel staff is av a ilable 24 hours a da y/ 7 da ys a week to book hotel reservations if needed. 2.2 Re vi ewing Lo cal IR OPS Even ts and Asse ss ing Local Si tuat io n Th e fo llo wi ng table (IROPS Event Histor y) describes th e histor y of local IR OPS ev ents, incl ud ing le ng th y on board gro und dela y ev ents. It also describes the role of vari ou s service prov iders in prov idi ng passe nger an d ot her cust om er su pport du ring IR OP S events. Th e pu rpose of th is histor y is to prov ide a basis fo r id en ti ficati on an d review of IROPS response activitie s wi th fo cu s on areas ne edi ng process im pr ov em en t. 204 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

IROPS Event History Date Event Desc ription 1/15/2009 GB I received 20 diversion flights during a snowstor m. 3/2/2009 GB I had to shut down temporaril y after the ma in power feed was da ma ged during a tornado. Opera tions resumed to full capaci ty after 2 da ys . 5/17/2009 A thunderstorm near GBI grounde d all flights for 12 ho urs; te rm inal reached cap ac it y since no passengers were ab le to fl y out. 2/23/2010 Fl yer Ai rlines staff went on strike and all scheduled flight s were cancelled. 6/10/2010 A fire in the tower at Boston required evacuation of F AA personnel, and all flights in the area were grounded until the tower was up and running from the backup site. 7/12/2010 The Pr esident of the Un ited States was flying into a nearby airport, and the F AA shut down the nearby airspace for a period of 8 h ours. Al l flights were grounded during this time. 12/23/2010 A snowstor m in the Midwest resulted in num erous wide bod y aircraft di versi ons of flights originally h eaded for Chicag o, which were di verted to GB I. CB P had to be ca lled in off- si te to handle the international passengers. 2.3 Passenger Needs du ring an IR OP S Event The following table (P asse ng er Ne eds) focuses on ne eds of passengers a nd other cu stom ers during IR OPS events, wi th special focu s prov ided for special -n eed s passengers. The ne ed s analysis is provided by consideration of ge neral info rm ation of custom er needs during IR OP S events. Passenger Needs Need Descri ptio n Custom er needs during an IR OPS event • Lavatory services – Restroom s are available while on the aircraft and in the terminal within the ster il e area for deplaning passengers. • Food an d bev erage – Ai rlines prov ide water and snacks on board the aircraft when possible; once passe ng ers are deplaned GBI Conc essions will provide food and water as ne cessary . Duri ng times of mu ltip le di versi ons or cancellations, bul k food orders fro m nearby restaurants will be placed by airlines . Support for special -n eeds passengers • Tran sp ortation – Wh eelch air services and mo to ri zed ve hicle serv ices available. • Lavatory services – Handicap accessible restroom s ar e locat ed in the steril e area for passengers. • Medical ne ed s – Lo cal hospital and ph ar ma cy to prov ide deliv ery of vi ta l me dications for special -n ee ds passeng ers if they do not ha ve the me dications needed with them . • Depl an ing/boarding – Ha nd icap accessible jet bridges, air stairs, and lif t de vices are available if needed. Ob taining passenger feedback Pa ss engers ar e able to prov ide feedba ck through vari ous me thods including em ail, airport website, ma il, in -p erson comm ents with airport staff and service prov ider staff, and social network sites. Part 2 – Resource D – Sample IROPS Plan 205 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

2.4 Tracking of Delaye d Aircraft The following table (Tracking De la ye d Ai rcraft) describes Grand Ba y In ternational Ai rport processe s prov iding accurate, co mp le te, and time ly inform at ion in regard to expected flight dela ys including di versi ons. These processe s describe local situations as they de velo p, including both flight dela ys a nd dela ye d aircraft on the ground. Tracking Delayed Aircraft Organization Descri ptio n Fl yer Ai rlines Ai rline staff tracks flights via www.fl ightaware.co m to see where potential di ve rs ion flights are relative to GB I Ai rport. Ai rline- specific tools are also utilized to track flights identified as potential diversi ons. Om ega Airlines Al l aircraft are tracked by Om ega Ai rlines Di spatch at airline headquarters. Staff at the GB I are notified by dispatch when a flight has been identified as a di vers ion and is gi ve n the flight number so staff can track the flight via www.f light aware.co m. F AA Up on request by GB I staff, the AT C ma y advise on general arrival and departure dela y situations and potential diversions to GB I. Ai rport Opera tions Ai rport operations staff (including police) will record time aircraft landed and will m onitor to ensure aircraft are being prov ided necessary se rvice. If a potential problem is noted, ope ra tions will contact the proper airline authorities for correction. L ong Is le Ai rport (pri ma ry di vers ion airport) Coordinate e xpected duratio n of the ev ent to help the num ber of di vers ions. 2.5 Trigger Events an d Communications Pl ans Effective response to an evolving IR OP S event depend s on timel y shared situatio na l awareness am ong al l aviation se rv ice pr ov iders. Rele va nt IR OPS informatio n includes the early identifica tion of a potential IR OP S situation and the evolving IR OP S condition as th e event evolves. Ke y el em ents of comm unication during an IROP S event require coordinated IRO PS response actions by airport operations, the airlines, the FA A ATC, a nd by a ffected di versi on airports to track and share aircraft status both in -a ir and on -g round. Base d on the situational need, additional co mm unications am ong other organizations such as the TSA, CB P, co ncessions, a nd gr ound transp ortation ma y also be required. The following table (Trigger Ev ents and Co mm unication Pl an s) describes shared informat ion, including aircraft dela y tracki ng perform ed by airlines, the F AA, Grand Ba y In ternationa l Ai rport operations, and di versi on airports . 206 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Trigger Events and Communication Plans Organization Trigger Even t Resp on sible Part y Target Group(s) Co mm unication Method(s ) Co mme nts Fl yer Ai rlines IR OP S situation alert Ai rcraft pilot in charge Ai rline operations In ternal “Your station has be en selected as an alternate for flight XXX. ” Fl yer Ai rlines Pr ep aration for deplaning PAX Ai rcraft pilot in charge Ai rport operations In ternal Pi lot will generall y advise of an appr oxi ma te ti me of when they want to deplane passengers . Om ega Ai r IR OP S situation alert Ai rcraft pilot in charge Ai rline operations In ternal “Your station has be en selected as an alternate for flight XXX. ” Om ega Ai r Pr ep aration for deplaning PAX Ai rcraft pilot in charge Ai rport operations In ternal Pi lot will generall y advise of an appr oxi ma te ti me of when they want to deplane passengers . Ai rport Di verted flight Ai rport operations Serv ice prov ider s In ternal “P re pare to ha ndle. ” Ai rport Co mp lex di versi on situations Ai rport Pa ss engers Social me dia, in person, F light In fo rm ation Di spla y Sy st em (F ID S) Ai rport staff will use social me dia outlets and be available in person to record passenger comm ents and handle passenger c oncerns . 2.6 Support for Passe ng ers The ke y goal of the Gran d Ba y In ternational Ai rport IR OP S plan is to en sure focus on coordinated support of passengers a nd other custom ers during an IR OPS ev ent. Three ar ea s of c oor dination recognize U.S. Congressional concer ns for the prov ision of: • Support for de planing of pa ss engers fro m aircraft • Sharing of facilities, including ma king gates av ailable • Ha vi ng a sterile area av ailable for passengers who have not ye t cleared CBP The following table (S up port for Passengers) descri be s coordinated support fo r pa ssengers at airports while th ey are on- board aircraft, du ring their depl an ing (especiall y fro m re mo te parking ar eas), in the terminal, and when they need ground trans portation. Part 2 – Resource D – Sample IROPS Plan 207 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Support for Passengers Passeng er Location Service Provid er Descri ptio n On bo ard aircraft Fl yer Ai rlines The crew will pr ov ide support for passengers. Fl ye r Ai rlines will deplane passengers after 90 mi nutes. If n eeded, Fl ye r Ai rlines will service th e lavato ry on- board and prov ide air conditioning/heat cart. Om ega Ai r Ensure flight attendant(s) ha s enough drin ks and ice onb oard. If n eeded , GB I concessions will be contacted for additional supplies. La vato ry wi ll be serv iced when aircraft arrives. Ai rport Ai rport police will be info rm ed of a di versi on. Ai rport staff wi ll note th e flight num ber and time that plane arrived to track time spent on board the aircraft. If airline requests assistance, airport will provide bottled water. GB I Concessions If n ecessary , GB I Concessions will prov ide ai rlines with additional supplies for passengers aboa rd aircraft. Depl aning aircraft Fl yer Ai rlines Fl yer Ai rlines wi ll coordinate with the crew of the aircra ft about possible deplanem ent. Wh en deplan ing passe ng ers, airline will inform the TS A, CB P, an d airport police of its intentions. Om ega Ai r If aircraft is off the je t brid ge, Om ega Ai r will ensure there are enough em pl oy ees to escort the custom ers to the term inal . Ai rport GB I will ma ke resources available and coordinate resource use (jet bridges, parking areas, sp ec ial needs assistance, and more) In term inal Fl yer Ai rlines Ai rline will coordinate with TS A about po tentiall y allowing passe ng ers to leave the sterile area depending on the length of the dela y. Special -n eeds passengers will be acco mmo dated as ne ed ed . Om ega Ai r If the dela y is short, Om ega Air will try to keep custom ers in the gate area. If the dela y is longer, th ey will advise passengers to retain boardin g passes so they can enter el se where through security . If dela ys are mo re than 4 hours long, Om ega Air will call the local pizza restaurant to orde r pizza and drinks for the pass engers . Ai rport Ai rport police and the TS A will be on site to ensure passe ngers are ke pt in the sterile area, unless passe ngers are allowed to leave in the event of an extended dela y. They wi ll a ssist airlines/passengers by whatever m eans necessary . GB I Concessions GB I Co ncessions will accomm odate passenger ne ed s as n eeded, including callback after hours. Spec ial dietar y needs and infant needs will be acco mm odated as needed . TS A The TS A and airport polic e will determ ine need for pa ssengers to leav e the sterile area. They will help ke ep passe ng ers in th e sterile area if needed . CB P In the event of an internatio nal di versi on, agreem ents wi th the CB P will be in effect. An area for deplaning international passengers has been ma de, and this area will be m onitored by the CB P, TS A, and airport police. Extende d dela y acco mm odations Zoom Rental s Ai rlines will contact Zoom Re ntals for extend ed dela y situations. Shoreline Ho te l Ai rlines will contact Shoreline Ho tel for extended dela y or extended stay situations. GB I Concessions GB I Concessions will ma ke staff available after hours to serve passengers during extend ed dela ys . 208 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Support for Passengers Passeng er Location Service Provid er Descri ptio n Ai rport The airport ha s cots available for pass engers w ho will be sp ending the night in the terminal. This is a last resort and is no t offered as an alternative to st ay ing at the Shoreline Hotel. 2.7 Trac ki ng Invento ry This section describes guida nce for planning and de vel oping procedures across local organizations identi fy ing resources (equipm ent and s upplies) held by an airport service organization bey ond t hose which ha ve be en planned for sh ared use, bu t that could be ma de available for use if requested by a nother Gran d Ba y In ternational Ai rport organization during an IROP S event. Descri ptions of un derstandi ng s of planned coordination re lated to sharing of resources are listed in Section 2. 1 – R eviewing Existing IR OPS Resp on se Pl ans. The following table (Tracking Resource In ve ntor y) describes specific categories of resources that have been identified as being available for shared use. Tracking Resource Inventory Organization Inventory Item Descri ptio n Fl yer Ai rlines Tugs Fl yer Ai rlines has 10 tugs to service their standard aircraft. Om ega Ai r Ai r stairs Om ega Ai r has two sets of air stairs that are stored in the equipm ent building on airpor t propert y. Ai rport Cots The airport has a total of 50 0 cots available for use if needed. They are stored in the fi rst floor storage closet ne ar the escalators. GB I Co ncessions Bottled water GB I Co ncessions has 200 bo ttles of water on hand at all times . Centennial FB O Fu el Centennial FB O ke ep s fuel tanks at levels that wi ll last 2 da ys under nor ma l operating levels. Zoom Rentals One- wa y rental car s Zoom Rentals keeps 10 ca rs designated for one- wa y rent al s. 2.8 Skills Availability This section describes guida nce for planning and de vel oping procedures across local organizations identi fy ing categories of skilled personnel em pl oy ed by an airport service organization be yo nd t hose which ha ve been planned for sh ared use, bu t that could be ma de available for use if requested by a nother Gran d Ba y In ternational Ai rport organization during an IROP S event. Part 2 – Resource D – Sample IROPS Plan 209 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Descri ptions of understandi ng s of planned coordination related to sharing of skilled st aff are li sted in Section 2.1 – R eviewing Existing IR OP S Res ponse Pl ans. The fo llowing table (Skills Av ailability) describes specific categories of skilled personnel that have been identified as being av ailable for shared use. Skills Availability Organizatio n Sk ill Description Fl yer Ai rlines Vari ous Each em pl oy ee is trained on every piece of equipm ent that is owned by the airline. If agents are un co mf ortable ope ra ting a piece of equipm ent, th ey are encourag ed to ask for assistance until they are co mf ortable them selves to perform the task. Om ega Ai r Vari ous Al l em pl oy ees are trained on loading/unloading airc raft , parking aircraft, servicin g lavatories, and so forth. Al l em pl oy ees can be ma de available for assistance in an y area needed . Ai rport Je t bridge operation Ai rport holds annual training on the use of jet bridges. Airlines are responsible for training new hires to en sure that all em pl oy ees are trained properl y on the use of jet bridges. GB I Co ncessions Multilingual GB I Co ncessions staff is multilingual and can speak English, Spanish, and Fr ench. If translation services are needed, c ontact GB I Co ncessions. Centennial FB O Ai r carrier fueling Al l Ce ntennial FB O staff are NAT A trained and cer tified. They are trained and ce rtified to fuel bo th Fl yer Ai rlin es and Om ega Ai r aircraft. Gro und ha ndling is lim it ed to the availability of equipm ent on hand. Zoom Rentals Pa ging Zoom Rentals staff are trai ne d on the use of the airport public address (PA) sy st em a nd can assist with a nnouncem ents during ti me s of extended dela ys . 210 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

CHAPTER 3 – ESTABLISH PROCEDURES TO COOPERATE The fo llowing sections do cu me nt the establishm ent of operating proced ures with service prov iders (e.g., concessions, gr ound trans por tation, F AA, TS A) for use du ring IR OP S events. 3.1 Coopera tion Proced ures Th ere are a gr ou p of service prov iders that are considered to be ty pically f oun d at airports that are vi tal in local IROPS plan ning e ffo rts. C oordi natio n wi th th ese en tit ies (identified in th e fo llo wi ng s ections) is critic al in order to establish procedures that will be fo llo we d du ring an IROPS event. 3.1.1 Airlines It is recognized that the DOT has issued a rule ma king that requires airlines to adopt tarm ac dela y contingenc y plans and coordinate them with both scheduled airports they serve and thei r di vers ion airports. The followin g table (P rocedures with Ai rlines) describes airline procedures specific to IR OP S events fo r each airlin e operating out of the airport. A ppendix B contains copies of specific airline procedures and tarmac dela y contingenc y plans on file. Procedures with Airlines Organization Cont act Name Local Agre em ents Fl yer Ai rlines Zach Thom pson Fl yer Ai rlines wi ll c oordinate existing ta rm ac dela y contingenc y plans with the Gra nd Ba y In ternat ional Ai rport IR OPS Contingency Resp on se Co mm ittee and will notif y the appropriate entities of an y changes or m odifications to the plan as th ey ma y occur. See Appe ndix B for specific proc edures . Om ega Ai r Gary Nettleton Om ega Ai r will coordinate existing ta rm ac dela y contingenc y plans wi th th e Grand Ba y In ternational Ai rport IR OP S Contingency Response Co mm ittee and will notif y the appropriate entities of an y changes or m odifications to the plan as they ma y occur. Se e Appe ndix B for specific proc edures . 3.1.2 FAA It is recognized that F AA has issued directiv es to air tr affic personnel pertaining to aircraft ma king ta rm ac dela y requests related to Un it ed States DO T’s 14 CF R Part 259 Enh anced Pr otections for Airline Passeng er s . The F AA has al so establishe d procedures allowing Airp orts access to ai rcraft flight status. The following tabl e (P rocedures with F AA) desc ribes Grand Ba y In ternationa l FA A/ATC facility actions specific to IR OPS events . Appe ndix B contains c opies of specific procedures with the FA A. Part 2 – Resource D – Sample IROPS Plan 211 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Procedures with FAA Organizatio n Cont act Name Local Agre em ents F AA Je ff Ballard & Brett Adam s AT C will taxi all aircraft to the terminal ra mp . When a request is ma de by the pilot- in -c om ma nd of an aircraft to return to th e ra mp , gate, or alternate deplanin g area du e to the 3- hour rule, ATC will coordinate necessary parties to quickly re locate the aircraft for deplaning. AT C will provide support and advisory info rm ation to the Grand Ba y In ternational Ai rport when workload allows (consider ing traffic load, co mp lexi ty a nd other available resources). In fo rm atio n prov ided ma y include: ¬ No tifying airport when dive rs ion flights are inbound. ¬ Es ta blis hi ng irregular parki ng ar ea s fo r IROP S ev en ts with the ai rp ort. ¬ Ad visi ng the airport on known ground dela y program s that could affect developing or active IROPS events. 3.1.3 CBP It is recognized that CBP has issued guidan ce to dire ctors of field operations concerning passe ngers on di versi on flights, including those into airports not norm ally staffed by CBP . The fo llowing table (P rocedures with CBP ) describes the Gr an d Ba y In ternational CB P proced ures specific to IR OP S ev ents. Appe ndix B contains copies of specific procedures with the CB P. Procedures with CBP Organizatio n Cont act Name Local Agre em ents CB P Ron Ho ov er & Br ya n Dean The airline or pilot in command will notif y the CB P officer on duty or th e CB P port director of an in tended or actual arrival, whether ma king em ergenc y or technical fuel stops, a weather related st op, stops du e to illness on board the aircraft, or other em ergenc y stop s. No tifications ma de to CB P will include the following: • Na me and co ntact num ber of airline representativ e • Fli ght nu mb er • Or iginal routing • Pa ss enger c ount • ET A an d actual lock ti me • Reason for diversion, intention of airline, special request s/n eeds • Crew status • Additional updates and flight departure ti me Duri ng an ex tended stay in excess of 2 hours, an airline ma y request 212 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Procedures with CBP Organizatio n Cont act Name Local Agre em ents perm is si on fro m CB P to de plane passe ngers of a di vert ed aircraft into a sterile and secure holding area. Pe rm ission ma y be granted if the airline comm unicates with CB P the nature of the di versi on and the an ticipated length of dela y and secures passengers fro m contact wi th other do me stic or foreign flights. If a di versi on occurs outsi de nor ma l business hours, Ai rport Operat ions are to call the CBP. If ther e is no answer, th ey are to call the regional CB P office and speak to the Du ty Officer. If n ecessary , the duty officer will issue a permit to proceed and other necessary perm is si ons ov er th e phone. 3.1.4 TSA It is recognized that the Department of Ho me land Security has issued proced ures to TSA Fe deral Security Di rectors conc erning establ is hing and utilizing secure ar eas using pr ocedures in the Ai rport Se cu rity Pr ogram or Aircraft Op erator Standa rd Security Pr ogram . The following table (P ro ce dures with TS A) descri be s Gran d Ba y In ternational Ai rports TS A proced ures specific to IR OP S ev ents. Appendix B co ntains copies of specific procedures with th e F AA. Procedures with TSA Organization Cont act Na me Local Agre em ents Grand Ba y In ternational Ai rport TSA Ja red Engel & La nce Fo ster • Duri ng reg ular op erating ho ur s Pa ss engers fro m di verted flights will ha ve discretion wh ether to leave the sterile area. If that occurs, TS A st aff will ensure that appropriate screening staff are ma intained at the airport in order to process the increased influx of passengers back into the sterile area. • Duri ng mi ni ma l operating hours TSA officers will be briefed by airline and/or ai r port operators to determ ine the mo st appropria te course of ac tion under the im pending circ um st ances. In these in st an ces, the TSA encourages the airline operato r to info rm passengers that th ey should re ma in in the ai r port sterile area and that should th ey exit the sterile area, th ey ma y be dela ye d in rega ining access to the sterile ar ea, wh ich ma y affect thei r tr av el th at da y. Regional TS A Center • Duri ng of f ho ur s If IR OPS oc cu r at the airpor t during a ti me when the secu rity screening checkpoint is closed and no TS A offi cers are pres en t at the airport, the airline and/or airport operators will call the 24-hour TS A Regional Part 2 – Resource D – Sample IROPS Plan 213 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Procedures with TSA Organization Cont act Na me Local Agre em ents Center with details of the IR OP S flight and wait for further instructions. 3.1.5 Conc ession s Concessions at Gran d Ba y International Ai rport ha ve be en requested to agre e to prov ide service during IROP S events, including those resulting in extended passe nger (a nd other custom ers) st ay in the terminal area. Ke y considerations include agre em ent to re ma in open dur ing extended ho urs and support for special -n eeds passengers, includi ng new in fant supplies. The following table (P rocedures with Concessions) describes specific concessi ons support proce dures identified as being available during IROPS events. Procedures with Concessions Organization Cont act Name Local Agre em ents GB I Co ncessions Je nn ell Black & Ja mi e Willia ms • GB I Co ncessions will acco mm odate the sharing of supplies. • Additional staffing will be called back if needed to provide services during IR OP S ev en ts . • If assistance is needed after hours, Jenn ell Black ne eds to be contacted and efforts will be ma de to acco mm odate passenger n eeds. • If special needs are identified (e.g., dietar y needs, infant needs), GB I Con cessions will ma ke arrange me nts to m eet the needs of passengers. • Menu availability at the rest au rant ma y be limited during IR OP S ev ents, but pass enge rs will be cared for. • Ai rport police and TSA staf f will assi st GB I Concessions staff through security when called back after hours. 3.1.6 Ground Tr ans por ta tion Groun d transportation orga nizations at Gran d Ba y In ternat ional Ai rport ha ve be en requested to agree to prov ide service during IR OPS events, including those resulting in extended passe ng er (and other custom ers) st ay in the te rm inal area. Ke y considerations include agreem ent to pr ov ide se rv ice du ring extended ho urs and procedures for obtaining a dditi onal resources when requi re d. The following table (P rocedures with Ground Transp ortation) describes specific grou nd transportation suppor t procedures id en tified as being available during IROP S events. 214 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Procedures with Ground Transportation Organization Cont act Name Local Agre em ents Zoom Rentals Al Ke hoe & Na than Johnson • In the ev ent of an IR OPS event, Fl ye r Airlines and Om ega Air ha ve agreem ents with Zo om Re ntals to prov ide a limi ted number of one -w ay rentals. • Should a ma jor IROP S event occur, Zoom Rentals will assist the Shoreline Ho tel in shuttling passengers back and forth to the hotel. Ai rport Randy Holbrook & To m Mulcaster • Should passengers need bussing to a nearby airport, GB I- owned busses will be used . • If additional ground transportation is needed, the airport will help Fl yer Ai rlines and Om ega Ai r in securing additional transportation by the local bussing co mp any and/or taxi co mp anies. 3.2 Other Prov ider s to Consid er Above and bey ond the service prov iders identified in the prev ious section, several other entities should be coordinated with, as appropriate to Grand Ba y In ternatio nal Ai rport. The list below highlights so me of thes e service providers that shoul d be consider ed when esta blishing proced ures to follow du ring IR OP S ev ents. • Al ternate transportation providers (mass transi t, bussing companies, off- si te rental car agencies) • Extende d stay acco mm odations (nearby hotels) • Military installations (if joint- use) • Fi xed base operators (F BO) • Refueler s • Off- site restaurants • Em ergenc y response (local police, fire, EMT) • Red Cros s • FE MA • Special needs se rvice provid ers (wheelchairs, oxy gen, etc.) The Gran d Ba y In ternationa l Ai rport has re quested s uppo rt service for special -n eeds passe ngers durin g IR OPS events, including those resulting in extended passe nger (a nd other custom ers) st ay in the terminal area. Ke y considerations include an agr eem ent to prov ide service during extended hours, off- hours, and proce dures fo r obtaining additional resource s when required. The following table (P rocedures with Ot her Pr ov iders) describes specific special-needs passe ng er suppor t procedures id en tified as being available during IROP S events. Part 2 – Resource D – Sample IROPS Plan 215 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Procedures with Other Providers Organization Cont act Name Local Agre em ents A- 1 Medical Samm i Fo lick • In the ev ent of an IR OPS event, Grand Ba y In ternational Ai rport has an agre em ent with A- 1 Medical to provide a lim it ed num ber of wheelchairs and ox yg en tanks. 216 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

CHAPTER 4 – Review, Update, and Training The Grand Ba y In ternational Ai rport IR OPS plan should be updated periodically throughout the y ear with impr ov ed practices, procedur es, and c oordinated resp ons e. In order for this to happen, the IR OP S Co ntingenc y Respons e Comm ittee should host coordination workshops and training at least a couple of times annuall y. 4.1 IROP S Coor di nation Workshop s Pe riodic IR OP S c oordinati on workshops are held at Gr and Ba y In ternational Ai rport prov iding a comm on form at and ve nue for periodic review and confir ma tion/ update of local IR OPS plans. The Gran d Ba y In ternational Ai rport will determ ine the frequenc y and specific agenda for thes e m eetings, as appropriate. The following table (I ROPS Coor dination Worksh op) describes Gran d Ba y In ternational Ai rport plans for holding these worksh ops. IROPS Coordination Workshops Date Work shop Na me Descri ptio n 10/10/2010 Grand Ba y In ternational Ai rport IR OP S Works hop #1 In Oct ober 2010, the first IROPS m eeting was held at the airport. The outco me of this workshop is su mma ri ze d below: • DO T update s on protectin g passe ng er rights were presented to ensure co mp liance with the mo st recent regulations • IR OP S op erational chal lenges were identified including: o Im portance of effectiv e and early comm unication o Situational awareness by ensuring tim ely sharing of inform ation between service prov ider s o Reporting a nd tracking di verted aircraft Serv ice prov iders were urge d to share an y prov ider -s pecific changes (e.g., pers onnel changes, proc edural changes, inventor y changes) to the wo rkshop attendees who ma y be affected. Service prov iders were also ur ge d to sh are an y experiences or lessons lear ned with the group to suppor t continued improv em ent an d coordination during IROP S events. A table-top exercise was co mp leted at the end of th e workshop that required all se rv ice providers to work through an IROP S scenario t ogether. Part 2 – Resource D – Sample IROPS Plan 217 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

4.2 IR OPS Coo rdin at ed Frontline Tr ai ni ng Pe riodic coordinated frontline training for IROP S response is held at Gran d Ba y In ternational Ai rport. In addition to em phasis on actions requiring coordination of two or mo re organizations, this training prov ides an opportunity to test new policies, practices, and procedures. The fo llowing table (I ROPS Co ordinated Fr ontline Trai ni ng) describes Gran d Ba y In ternational Ai rport pl an s for holding this training. IROPS Coordinated Frontline Training IROPS Training Activity Descri ptio n In it ial IR OP S training Training include d discussion and instruction on th e following topics: • IR OP S plan fa mili arizatio n • Trigger points for serv ice providers • Contact inform ation • Skills tracking • Effective comm unication strategies Fo llo w- up IR OP S training Training include d discussion of the following: • Updates to DOT regulations affecting service provider s • IR OP S lessons lear ned fro m the airport and other airports • Feedback and ideas for im prov em ent fro m experiences No te: In itia l IR OP S training was coordinated during the annual and/or bian nu al security badging process at Grand Ba y In ternational Ai rport. 218 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

CHAPTER 5 – Consolidated Cooperation Actions during an Even t The joint actions occurring during an IR OPS event are described in the following diag ra m. The Grand Ba y In ternational Ai rport IR OPS Contingenc y Respons e Co mmi ttee ensures that there is capabilit y for coordinating shared aircraft status info rm ation. No tification of rele va nt aspects of ai rcraft status are provided to appropriate aviation service prov ider organizations du ring an IROP S event by the Gran d Ba y In ternationa l Ai rport co mm unication center or point of cont ac t, as appropriate. 5.1 Mo ni to ri ng IROP S Event In di ca tors While so me IR OP S events are unpr ed ictable (such as power outag es, and security breaches), ma ny can be handled su ccessfully if se rv ice prov iders are activel y anticipating an event. Certain actions taken by service prov iders on a constant ba si s can position them well to handle an IR OPS event, should one occur. So me exam ples of these actions are tracking aircraft st at us and tracking weather patterns. E ach of these is discussed in more detail below. 5.1.1 Aircraft Status Ai rcraft status in the air and on the gro und is tracked by both airlines and the FA A to prov ide accurate , co mp lete, and ti me ly informat ion in regard to expected flight dela ys a nd de vel oping local situations. The following table (Aircraft St at us) describes Gran d Ba y In ternational Ai rport pro cedur e chec klists for tracking aircraft during IR OP S ev ents . Part 2 – Resource D – Sample IROPS Plan 219 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy Figure 1. Joint Actions during an IROPS Event.

Aircraft Status Organization Ai rcraft St atus Acti on s Fl yer Ai rlines Om ega Ai r Di verted Flight s • Maintains status of aircraft in flight with respect to schedule • De termines aircraft requires flight divers ion • Ensures aircraft di versi on no tice is communicated to Ai rport Operat ions at L ong Is le Ai rport • Ensures aircraft di versi on status is ma in tained (ongoing) with updated status comm unicated to Airport Operations at airport wh er e flight was initial ly planned to arri ve • Continues tracking and co mm unicating status until flight ulti ma te ly arrives at original destination Fl yer Ai rlines Om ega Ai r Ai rcraft on Ground • Maintains status of arriving and departing aircraft to determine co mp liance with "3 -H our Ru le" • De termines aircraft situat ion ma y result in lengt hy ground dela y • Ensures other rele va nt serv ice providers are notified of possible IR OP S related im pact and to confir m an y related support including gate av ailability that is potentiall y needed is available if required • De termines aircraft wil l deplane passengers after lengthy ground dela y • Ensures other rele va nt serv ice providers are notified of unplanned passengers arri vi ng in term in al L ong Is le Ai rport Operations Di verted Flight s • In it iates m onitoring of flight when notified of flight dive rs ion • Confir ms rele va nt serv ice providers have been notified of unplanne d passengers arri vi ng in term in al o Concessions o TS A o CB P o Groun d Tr an sportation Grand Ba y In ternational Ai rport Operat ions Ai rcraft on Ground • Tracks status of arri vi ng and departing aircraft to determ ine co mp liance with "3 -H our Ru le" • When no tified aircraft will de plane passe ng ers after lengt hy ground dela y, confir ms rele va nt service prov iders have been notified of unplanne d passe ng ers arrivi ng in term inal o Concessions o TS A o CB P o Groun d Tr an sportation 220 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

5.1.2 Tracking Weat he r Weather patterns are tracked by th e airport, airlines, a nd the FA A to predict potential im pacts to aircraft operations and to carry out alternate operating procedur es (such as di verti ng fl ights to alternate airports) to ma intain the safety of the crew and pass engers, as well as operations staff out on the airfield. Th e following table (Tracking Weather Pa tt erns) outlines the roles an d responsibilities of airport, ai rline, and F AA staff in tracking weather. Tracking Weather Patterns Organization Cont act Name Weathe r Tr ac ki ng/Comm unicating Resp on sibilities Fl yer Ai rlines Zach Thom pson & Dan Walter Fl yer Ai rlines staff will check weather reports ever y mo rning. If w eather reports indicate severe weather that ma y im pact operations at the airport, the weather reports will be checked mo re frequently until the weather has passed. Fl yer Ai rlines will comm unicate an y se vere weather to Om ega Air and vice versa. Om ega Ai r Gary Nettleton & Jo hn Da vis Om ega Air staff will check weather reports ever y mo rning. If w eather reports indicate severe weather that ma y im pact operations at the airport, the weather reports will be checked mo re frequently until the weather has passed. Om ega Air will comm unicate an y se vere weather to Fl yer Ai rlines and vice versa. Grand Ba y In ternational Ai rport Rachel Clark & Sean Ha ye s Ai rside operations staff will m onitor weather patterns throughout the da y and comm unicate to all serv ice prov iders who ma y be affected, especially in the event of diversions or cancellations. F AA Je ff Ballard & Brett Adam s F AA AT C staff at the airpor t constantly m onitor weather patterns in the surrounding areas . Sh ould an y se vere weather have the potential to im pact operations at the airport, AT C staff will notif y airside operations im me diatel y to pr epare. 5.2 Executing IR OPS Pl ans and Pr ocedur es In S ection 3.1 of this plan, pr ocedures were established with se rv ice prov iders, including concessions, gr ou nd transportation, the F AA, CBP , a nd TS A. This section pr ov ides specific procedures that are to be executed at the time of an IR OPS event. The following para graphs ou tline procedures for each of the service providers. Part 2 – Resource D – Sample IROPS Plan 221 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

5.2.1 IROPS Communica tions Plans Rele va nt IR OPS informat ion including status and related situational info rm ation is comm unicated am ong appropriate Gran d Ba y In te rnational Ai rport organizations during an IR OPS event. The following table (I ROPS Co mm unication Pl ans) describes ke y el em en ts of Grand Ba y In ternational Ai rport IR OPS comm unications plans. IROPS Communication Plans Organization Co mm unication Action s Fl yer Ai rlines Om ega Ai r Di verted flight s • Ensures aircraft di versi on no tice is communicated to Ai rport Operat ions at L ong Is le Ai rport • Co mm unicates di versi on status to onbo ard passenger s • Co mm unicates di versi on status to passengers awaiting ne xt segm ent of flight and to pe op le meeti ng arri vi ng passengers (in term inal where initiall y planned to land and externally via electronic notification) • Update d status co mm unicated to Airport Operat ions at air port where flight was initi al ly planned to arri ve • Continues tracking and co mm unicating status until flight ulti ma te ly arrives at original destination Fl yer Ai rlines Om ega Ai r Ai rcraft on ground • Co mm unicates dela y st atus to onboard passenger s • Ensures other rele va nt serv ice providers are notified of possible IR OP S related im pact and to confir m an y related support including gate av ailability that is potentiall y needed is available if required • Co mm unicates dela y st atus to passengers awaiting next se gm ent of flight and to people m eeting arriving passengers (in terminal where initial ly planned to land and externally via electronic notification) • Ensures other rele va nt serv ice providers are notified of unplanned passengers arri vi ng in term in al after lengt hy ground dela y L ong Is le Ai rport Operations Di verted flight s • Confir ms rele va nt serv ice providers have been notified of unplanne d passengers arri vi ng in term in al Grand Ba y In ternational Ai rport Operat ions Ai rcraft on ground • When no tified aircraft will de plane passe ng ers after lengt hy ground dela y, confir ms rele va nt service prov iders have been notified of unplanne d passe ng ers arrivi ng in term inal 5.2.2 Passenger Su ppor t Plans Support proc edures for passe ngers and other custom ers at Grand Ba y In ternatio na l Ai rport during IROP S events include focus while they are on- board aircraft, during their deplaning, in the terminal, and when they need gr ound transportation. The following table (P as senger Support) de sc ribes pro cedures at Gra nd Ba y In ternational Ai rport for support during an IROP S event. 222 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Passenger Support Passeng er Location Service Provid er Descri ptio n On- board aircraft Fl yer Ai rlines Om ega Ai r • Support for sp ec ial needs passengers • Pa ss enger support (status not ification, water/food, restrooms, etc.) per DOT “Three- hour rule” On- board aircraft Grand Ba y In ternational Ai rport • Backup (to airlines) passenger support by sharing supplies On- board aircraft GB I Co ncessions • Backup (to airlines) passenger support by sharing supplies Depl aning aircraft Fl yer Ai rlines Om ega Ai r • Shared gate (as required) • Pa ss enger support for de plan ing aircraft at re mo te parkin g area (provision of m obile stairs, bus transport to term inal , special needs lift, etc.) Depl aning aircraft Grand Ba y In ternational Ai rport • Status for shared gate availa bility • Shared e quipm ent support for re mo te ly parked aircraft (m obile stairs, bus transport to term inal, special needs lift, etc.) In term inal Fl yer Ai rlines Om ega Ai r • Pe riodic status update • Re- booking as re qu ired • Support for providing acc o mm odations for lengt hy dela ys (including food / lodging as re quired) In term inal Grand Ba y In ternational Ai rport • Support for sp ec ial needs passengers • Support for after- hours acco mm odations • Agreem ent with TSA for af te r- hours secure area • Agreem ent with CBP for after- hours dela ye d flights In term inal GB I Co ncessions • Support for after- hours opera tion • In ve ntor y support for infants and special ne eds passe nge rs In term inal TS A • Ut ilization strate gy for after-hours secure ar eas In term inal CB P • Af ter hours support for delayed flights • Support to diversion airports not having CBP pres en ce Extende d dela y acco mm odations Zoom Rentals • Support for sp ec ial needs passengers • Af ter hours transportation to/from of f- si te accommodati on s Extende d dela y acco mm odations Shoreline Ho tel • Ov ernight acco mm odations for stranded passe ngers incl ud ing shuttle to and fro m Grand Ba y In ternational Ai rport Part 2 – Resource D – Sample IROPS Plan 223 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

5.2.3 Proce dur es with Ai rlines Ai rlines operating out of Gra nd Ba y In ternational Ai rport ha ve im plem ented procedur es pertaining to the DO T 3- Hour Rule and 4- Hour Rule relating to IR OP S event response. Th e following table (Execute IROP S Pr ocedures with Ai rlines) describes the actions to be taken during IR OPS events. Execute IROPS Procedures with Airlines Organization (24/7 Contact #) Local ag reem ent(s) Fl yer Ai rlines Zach Thom pson (777) 777- 7777 Execution of proce dures doc um ented in Fl yer Ai rlines Tarm ac Dela y Contingenc y Pl an upon request by airline Om ega Ai r Gary Nettleton (555) 555-5555 Execution of proce dures doc um ented in Om ega Air Tarm ac Dela y Contingenc y Pl an upon request by airline 5.2.4 Proce dur es with FA A The F AA/ ATC organizatio n at Grand Ba y In ternationa l Ai rport has impl em ented procedures pertaining to tarmac dela y requests re late d to the Un ited States DO T’ s 14 CF R Pa rt 259 Enha nc ed Pr otections for Ai rline Pa ss engers. The following table (Execute IR OP S Pr o ce dures with F AA) describes Grand Ba y In ternational Ai rport F AA/ ATC facilit y actions specific to IR OP S ev ents. Execute IROPS Procedures with FAA Organization (24/7 Contact #) Local ag reem ent(s) F AA Ai r Traffic Co ntrol Towe r Grand Ba y In ternational Ai rport Je ff Ballard & Brett Adam s (999) 999- 9999 F AA TR ACON (888) 888- 8888 • Lo cal execution of aircraft ground control procedures pe r the DOT 3- hour rule • Execution of IROP S proc ed ures including prov iding information to the airport on: o Ai rcraft status related to flight diversions o Ai rcraft status related to ground dela ys during taxi-in o Ai rcraft status related to ground dela ys during taxi- out 5.2.5 Proce dur es with CBP Grand Ba y In ternational Ai rport has im plem ented procedures with CB P relating to res ponse to IR OP S events . The following table (E xecu te IR OP S Proced ures with CBP ) de sc ribes Gra nd Ba y In ternational Ai rport CBP actions specific to IR OP S events. 224 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

Execute IROPS Procedures with CBP Organization (24/7 Contact #) Local ag reem ent(s) Grand Ba y In ternational Ai rport CBP Ron Ho ov er & Br ya n Dean (333) 333- 3333 • Execute IROP S proced ures fo r CBP in situations including: o Scheduled international flight arri va ls o Unsc he duled international flight arri vals o Scheduled international flight arri va ls after hours o Unsc he duled international flight arri vals after hours 5.2.6 Proce dur es with TS A Th e TS A or ga nizatio n at Gr an d Ba y In ternatio nal Air port has im plem ented proced ures concerning establishing an d utiliz in g secure areas usin g proced ures in the Air port Securi ty Prog ra m or Ai rcra ft Op erator Standard Securi ty Prog ra m. Th e fo llo wi ng tabl e (Execute IROPS Proced ures with TS A) describes Grand Ba y Inte rn ationa l Air por t TS A actions specific to IROP S ev en ts. Execute IROPS Procedures with TSA Organization (24/7 Contact #) Local ag reem ent(s) Grand Ba y In ternat ional Ai rport TS A Ja red Engel & La nce Fo ster (111) 111- 1111 Regional TS A Center (222) 222- 2222 • Execute IROP S proced ures fo r TSA, including: o Rescreenin g proc edures fo r passengers deplan ed du ring regular, mi ni ma l, and off-ho urs operations at the airport. 5.2.7 Concessi ons Pr oc ed ures Concessions at Gran d Ba y International Ai rport have agreed to prov ide specific support during IR OPS events. The following table (E xecute IR OP S Pr ocedures for Conc essions) describes these proc edures. Execute IROPS Procedures for Concessions Organization (24/7 Contact #) Local ag reem ent(s) GB I Co ncessions Je nn ell Black & Ja mi e Willia ms (123) 456- 7891 • Pr ov ide ba ckup (to Fl yer Ai rlines and Om ega Ai r) fo r on bo ard passenger support by sharing supplies such as bo ttled water and granola bars • Execute IROP S proced ures fo r concessions • Pr ov ide support for special-needs passengers • Pr ov ide support for infants (diapers, formula, etc.) Part 2 – Resource D – Sample IROPS Plan 225 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

Execute IROPS Procedures for Concessions Organization (24/7 Contact #) Local ag reem ent(s) • Pr ov ide support during after-hours service • Im plem ent backup staffing to respond to passenger surg e if needed 5.2.8 Ground Tr an s porta tion Procedures Groun d transportation orga nizations at Grand Ba y In terna tional Ai rport ha ve agreed to prov ide specific support during IR OP S events. The following table (Ex ecute IR OP S Pr oce dures for Ground Tr an sportation) describes these proc edures . Execute IROPS Procedures for Ground Transportation Organization (24/7 Contact #) Local ag reem ent(s) Zoom Rentals Al Ke hoe & Nath an Jo hn son (987) 654- 3210 • Execute IR OPS proc edures, prov iding one -w ay rentals fo r passengers and assisting Shor eline Hotel in shuttling passengers to and fro m the hotel • Support for sp ec ial-needs passengers • Im plem ent backup staffing/resources to respond to passe nger surg e Grand Ba y In ternational Ai rport Randy Ho lbrook & To m Mulcaster (012) 345- 6789 • The airport will execute IRO PS proc edures fo r groun d transportation, prov iding airport busses if needed for shuttling passe ng ers to and fro m the airport and off-site locations and assisting airlines in securing additional support fro m local bussing companies if needed. 5.2.9 Procedures with Other Providers The Gran d Ba y In ternat ional Ai rport has coordinated with additional service prov iders to prov ide specifi c support during IROP S events. Specific proce dures for ea ch of these service providers are listed here. Execute IROPS Procedures with Other Providers Organization (24/7 Contact #) Local ag reem ent(s) A- 1 Medical Samm i Fo lick (444) 444- 4444 • Execute IR OPS proc edur es, prov iding a limite d num ber of wheelchairs and tanks of oxy gen for special -n eeds passengers when needed, including during ex te nded h ours an d off- hours. 226 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy

CHAPTER 6 – CAPTURING LESSONS LEARNED AND UPDATING PLANS Since recovery fr om an IR OPS event is critical to the continual im prov em ent of the Grand Ba y In ternational Ai rport IR OP S Pl an, this chapter is di vi ded into two sections: debrief after an IROPS event and lessons learned. The following tables describe Gran d Ba y International Ai rport’s proce dures for these actions , including incorporation of lessons learned into the up date of Grand Ba y In tern at ional Ai rport’s IR OPS Contingenc y Pl an, as appr op riate. 6.1 After an IROP S Eve nt Af ter an IR OP S ev ent, it is im portant to ha ve a ti me ly an d co mp rehensive assess me nt of the event. Th e Gra nd Ba y In ternational Ai rport wi ll coordinate this debriefing m eeting and include all aviation service prov iders, as well as the IROP S Continge nc y Response Co mmi tt ee. The following table (Debriefing IR OPS Ev ent) describes Grand Ba y In ternat ional Ai rport’s plans fo r holding this training. Debriefing IROPS Event Organization Deta il Fl yer Ai rlines Om ega Ai r GB I Co ncessions Zoom Rentals F AA TS A CB P Ai rport Po lice L ong Is le Ai rport (pri ma ry di versi on airport) Centennial FB O • Re view and debriefing with Grand Ba y In ternational Ai rport IR OP S Cham pion and Co ntingenc y Response Co mmi tte e • Summ arize findings (including an y lessons learned) and recomm endations • Send to Chairperso n of Gran d Ba y In ternational Ai rport Contingenc y Response Comm it te e Grand Ba y In ternational Ai rport IR OP S Contingenc y Response Co mm itte e • Consideration if further study is required to full y understand the effectiveness of Grand Ba y In ternational Ai rport’s respons e • Results of the re view (and study if required) considered to determ ine if re visi ons are required in Gra nd Ba y In ternat ional Ai rport’s IR OP S Resp onse Plan • Redistribution of Gra nd Ba y In ternational Ai rport’s IR OPS Respons e Pl an (if revised) 6.2 Lesso ns Le ar ne d As part of the debriefing, it is im portant to catalog the le ss ons learned fro m the individual IR OP S events. Th e Grand Bay In ternational Ai rport wil l coordinate these le ss ons learned and prov ide th em to the av ia tion se rv ice prov iders, as well as the IRO PS Contingenc y Response Comm it tee me mb ers. Part 2 – Resource D – Sample IROPS Plan 227 PA R T 2 PA R T 1 R eso urce A R eso urce B R eso urce C R eso urce D A p p end ices B ib lio g rap hy

The following table (C apturing Le ssons L earned) describes Gran d Ba y In ternati onal Ai rport’s plan s fo r collecting lessons learned. Capturing Lessons Learned Organization Deta il Fl yer Ai rlines Om ega Ai r GB I Co ncessions Zoom Rentals F AA TS A CB P Ai rport Po lice L ong Is le Ai rport (pri ma ry di versi on airport) Centennial FB O • Re view and debriefing with Grand Ba y In ternationa l Ai rport IR OP S Cham pion and Co ntingenc y Respons e Co mm itte e • Summ arize findings (including an y lessons learned) and recomm endations • Send to Chairperso n of Gra nd Ba y In ternat ional Ai rport Contingenc y Response Commi tte e Grand Ba y In ternational Ai rport IR OP S Contingenc y Response Co mm itte e • Consideration of an y additional lessons learned from exam ples of coordinated response by Grand Ba y In ternational Ai rport service providers • Co mp ile and distribute an y ne w lessons learned • Pe riodic sharing of lessons learned with other airports in the aviation communi ty 228 Guidebook for Airport Irregular Operations (IROPS) Contingency Planning PA R T 2 PA R T 1 R es o ur ce A R es o ur ce B R es o ur ce C R es o ur ce D A p p en d ic es B ib li o g ra p hy