Irregular Operations (IROPS) Contingency Plan (SSI Removed Version)

Transcription

1 Irregular Operations (IROPS) Contingency Plan (SSI Removed Version)

2 2 Document Revision Revision Date Content Revision Date Content

3 3 TABLE OF CONTENTS Chapter 1 - Introduction 1.1 Purpose 1.2 Use of Terms 1.3 Passenger Needs 1.4 Causes of IROPS Events 1.5 Planning for Coordinated Response to IROPS Events Chapter 2 - Before an IROPS Event 2.1 Establishing an IROPS Contingency Response Committee 2.2 IROPS Contingency Response Committee Pre-Planning Coordinating Existing IROPS Response Plans IROPS Events History Customer Needs Tracking of Delayed Aircraft Trigger Events and Communication Plans Support for Passengers Tracking Inventory Skills Inventory 2.3 Established Agreements with Concessions 2.4 Established Agreements with Ground Transportation 2.5 Established Agreements with FAA 2.6 Established Agreements with TSA 2.7 Established Agreements with CBP 2.8 IROPS Coordination Workshop 2.9 IROPS Contingency Coordinated Training Chapter 3 - During an IROPS Event 3.1 Aircraft Status 3.2 Implementing IROPS Communications Plans 3.3 Implementing IROPS Passenger Support Plans 3.4 Implementing IROPS Concessions Agreements 3.5 Implementing IROPS Ground Transportation Agreements 3.6 Implementing IROPS Agreements with FAA 3.7 Implementing IROPS Agreements with TSA 3.8 Implementing IROPS Agreements with CBP Chapter 4 - After an IROPS Event 4.1 Debriefing 4.2 Lessons Learned

4 4 APPENDICES Appendix A Tasks and Tables to support development of the Model Airport IROPS Response Plan Before an IROPS Event Task 1 - IROPS Contingency Response Committee Task 2A - IROPS Response Plan Coordination Task 2B - IROPS Events History Task 2C - Customer Needs Task 2D - Tracking Delayed Aircraft Task 2E - Trigger Events and Communications Plans Task 2F - Support for Passengers Task 2G - Tracking of Inventory Task 2H - Skills Availability Task 3 - Establishing Agreements with Concessions Task 4 - Establishing Agreements with Ground Transportation Task 5 - Establishing Agreements with FAA Task 6 - Establishing Agreements with TSA Task 7 - Establishing Agreements with CBP Task 8 - IROPS Contingency Workshop Task 9 - IROPS Contingency Coordinated Training During an IROPS Event Task 10 - Aircraft Status Task 11 - Implementing IROPS Communications Plan Task 12 - Passenger Support Task 13 - Implementing IROPS Concessions Agreements Task 14 - Implementing IROPS Ground Transportation Agreements Task 15 - Implementing IROPS Agreements with FAA Task 16 - Implementing IROPS Agreements with TSA Task 17 - Implementing IROPS Agreements with CBP After an IROPS Event Task 18 - Debriefing and Capturing Lessons Learned Appendix B Status of Plan Details Appendix C - Reference Documents (copies of various agreements put in place to support the IROPS Plan) Appendix D - Compliance Matrix of IROPS Contingency Plan to US-DOT Model Contingency Plan Appendix E - Contact details for (AIRPORT NAME) IROPS Contingency Response Committee and for Points-of-Contact for Agencies during an IROPS Event

5 5 Chapter 1 Introduction 1.1 Purpose This document provides the coordinated IROPS Contingency Response Plan for Fort Wayne International Airport. It was developed by the Airport s IROPS Contingency Response Committee under the sponsorship of Airport Operations. Membership in Fort Wayne International Airport s IROPS Contingency Response Committee comprises representatives from each of Fort Wayne International Airport s aviation service providers. The Committee recognizes the importance of individual plans and a coordinated effort by the airlines, airports, government agencies, and other aviation service providers are essential to successfully minimizing the impact of IROPS events on passengers. This coordinated contingency management plan provides a common point-of-focus for Fort Wayne International Airport s coordinated response to IROPS events. The emphasis for this plan is the identification and documentation of areas of contingency activities of Fort Wayne International Airport s aviation service providers which require support from one or more service provider organizations. The plan format follows the recommendations provided in the Airport Cooperative Research Program s "Guidebook for Airport Irregular Operations (IROPS) Contingency Planning. Fort Wayne International Airport has recognized the importance of the guidance provided by the U.S. Department of Transportation and its Model Contingency Plans to Deal with Lengthy On-Board Ground Delays. To this end, a compliance matrix is provided in Appendix B to relate specific sections of the Model Contingency Plan to those of this document. 1.2 Use of Terms The following is a list of terms and definitions that are used throughout this Model Contingency Plan and associated task worksheets. Irregular Operations (IROPS) - For the purposes of this document, the term IROPS event is intended to describe those exceptional events that require actions and/or capabilities beyond those considered usual by Fort Wayne International Airports aviation service providers. Generally speaking, an impact of these events is the occurrence of: Unexpected people In unexpected places At unexpected times 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 CBP Customs and Border Protection TSA Transportation Security Administration Aviation Service Providers May include FAA, CBP, TSA, along with concessionaires and ground transportation agencies.

6 6 1.3 Passenger Needs Needs of passengers, both onboard 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, Fort Wayne International Airport, diversion airports, airlines, government agencies, and other aviation service providers can take appropriate steps to anticipate and address such needs 1.4 Causes of IROPS Events Causes of IROPS Events can include a number of conditions such as extreme weather, natural disasters, 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. Each IROPS event is unique, and airlines, diversion airports, government agencies, and other aviation service providers will benefit from the Fort Wayne International Airport IROPS Contingency Response Plan accounting for diverse IROPS characteristics by adapting to changing conditions. 1.5 Planning for Coordinated Response to IROPS Events The purpose of the Fort Wayne 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 response plans and areas of recommended communication, collaboration, and coordination between service providers.

7 7 Chapter 2 Before an IROPS Event Activities described in this Chapter provide for: The establishment of the Fort Wayne International Airport IROPS Contingency Response Committee The Committee's pre-planning actions Documentation of agreements with support organizations and government agencies Conducting workshops and training Note to User: Guidance for planning each of the following sections are described as Tasks 1 through 9 in Appendix A of this IROPS Response Plan and supported with various Tools listed in Part 5 of the Guidebook.. At the discretion of the airport, Appendix A may be deleted after the IROPS Response Plan has been developed or it may be kept as a reference. 2.1 Establishing an IROPS Contingence Response Committee The Fort Wayne International IROPS Contingency Response Committee has been established following the guidelines of the Department of Transportation s Model Contingency Plan. Fort Wayne International Airport s Operations Department 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 Fort Wayne International Airport aviation service providers during IROPS events. Member Organization and Representatives Members of the Fort Wayne 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. TASK 1 TABLE 1 - IROPS Contingency Response Committee Organization Name (Contact) Alternate (Contact) Airport Operations Airlines Concessions Government Agencies Fixed Base Operations Miscellaneous Organizations Executive Management Liaison

8 8 TASK 1 TABLE 1 - IROPS Contingency Response Committee Organization Name (Contact) Alternate (Contact) NOTE: Contact details shown in the table are for the Representative s Organization Office. Contact details for the IROPS Contingency Response Committee and for points-of-contact for agencies during an IROPS event are found in Appendix E. 2.2 IROPS Contingency Response Committee Pre-Planning The IROPS Contingency Response Committee Pre-Planning activities focus on: Coordinating existing IROPS Contingency Response 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 de-planed, and in-terminal Local tracking of inventory Local skills availability Coordinating Existing IROPS Contingency Response Plans It is recognized that each of Fort Wayne International Airport organizations may have their own plans for response to IROPS Events. It is also recognized that DOT Rules on Enhancing Airline Passenger Protections 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 describes both formal and informal understandings of coordination between these organizations as well as individual organization Standard Operations Procedures (SOP) related to IROPS response. Descriptions of agreements with concessions, ground transportation, and government agencies (FAA, TSA, and CBP) are found in Sections 2.3 through 2.7 of this plan. TASK 2 TABLE 1 - IROPS Response Plan Coordination *Please modify the table below as appropriate for your needs, and add additional rows as necessary

9 IROPS Events History The following 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. TASK 2 TABLE 2 - IROPS Event History *Please modify the table below as appropriate for your needs, and add additional rows as necessary Customer Needs The following 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 described in the Part 5 - Tools of the Guidebook. TASK 2 TABLE 3 - Customer Needs *Please modify the table below as appropriate for your needs, and add additional rows as necessary Meeting Customer needs Maximum time allotted prior to requiring to deplane- 3 hrs. during IROPS Events Restrooms- lavatory services available by the airlines Support for Special Needs Passengers Obtaining Passenger Feedback o Restrooms inside terminal within the sterile area are available for deplaning passengers Food & Beverage- airport provides water, restaurant available as necessary Passengers are often given food vouchers to purchase items from the restaurant. At times we have placed bulk orders from the airport restaurant or other local restaurants, such as Pizza Hut (Regional Elite). American Eagle also has agreements in place that they will purchase pizza and drinks for lengthy delays. Transportation o Wheel chair service available Handicap accessible restrooms Medical needs Handicap accessible deplaning/boarding o Jet bridges, air stairs, and lift devices Passengers are able to provide feedback via various methods including , phone, mail, in person comments, and social networking sites. Airport operations staff is on hand to ensure passenger needs are met as well as correcting unsatisfactory experiences or service.

10 Tracking of Delayed Aircraft The following table describes Fort Wayne International Airport 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. TASK 2 TABLE 4 - Tracking Delayed Aircraft *Please modify the table below as appropriate for your needs, and add additional rows as necessary Delta Global Services (Delta/United American Eagle Allegiant-Trego Dugan We often track aircraft via to see how close potential diversions are to our airport. Using tools provided by DL/UA- we track flights that have been advised might diver to FWA, but generally online flight tracking tools give us a better idea of where the a/c is. All aircraft are tracked by Dispatch in headquarters. In the event we will have a diversion we are notified of the flight number and estimated time of arrival we also use to track when we have a flight number. Additional for American Eagle dispatch will also send a diversion alert message when we have a potential for diversions. In addition to this for American Eagle aircraft after a diverted flight arrives we use a program call diversion tracker to keep all internal departments informed of the status. This allows us to track how long customers have been on the aircraft and if any catering or lavatory service has been provided. This is also used to ensure we do not leave customers on the aircraft longer than the 3 hour limit. The manager of the station also receives text messages when an aircraft has been on the ground longer the 1 hour with updates if they remain on the ground longer. FAA Upon request by FWACAA, ATC may advise on general arrival and departure delay situations and potential diversions to FWA. ATC shall not release information from any National Airspace System (NAS) database regarding the position, altitude, heading, flight plan, origination or destination of a single aircraft ( Flight Track Data ) upon the oral request of an individual outside of the FAA. Diversion Airport(s) Aircraft Parking Configuration Coordinate expected duration of the event, to help for the amount of diversions. This spreadsheet has been developed to aid in the maximum parking potential for the terminal ramp with access to boarding gates/ jet bridges. This document is an attachment to this plan.

11 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, the FAA ATC, and by impacted diversion airports to track and share aircraft status both inair and on-ground. Based on the situational need, additional communications among other organizations such as TSA, CBP, concessions and ground transportation may also be required. The following table describes shared information including aircraft delay tracking performed by airlines, the FAA, For Wayne International airport operations, and diversion airports. TASK 2 TABLE 5 - Trigger Events and Communication Plans *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Trigger Event Sending Group Target Group(s) Delta Global Services (Delta/United) Delta Global Services (Delta/United) United & Delta American Eagle& Allegiant IROPS Situation Alert Preparation for Deplaning Passengers FWA is a level 1 diversion city any weather or flow issues into ORD generally cause diversions to be sent to FWA. IROPS Situation Alert Aircraft Pilot in Charge/ Operations Control Center Aircraft Pilot in Charge UA operations control center Aircraft Pilot in Charge Airline Operations Airline Operations Airline Operations Communicatio n Method(s) We get telex print offs advising us of possible diversions, and or calls to station / station manager Pilot make radio contact with operations, or speaks directly to the ramp or gate crew Radio, headset, in person Comments Your station has been selected as an alternate for flight XXX They generally advise us of an approximate time of when they want to deplane the passengers. This generally depends entirely on how the crew wants to handle the passengers. Some are fine with keeping passengers on board for a while, meanwhile others want them deplaned immediately so that the ground crew deals with the passengers. stand-by

12 12 TASK 2 TABLE 5 - Trigger Events and Communication Plans *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Trigger Event Sending Group Target Communicatio Comments Airport Preparation for deplaning passengers Preparation for deplaning passengers Passengers being deplaned More complex diversions that are greater in length and severity Aircraft Pilot in Charge Airline Operations Group(s) Airline Operations Airport Operations n Method(s) Radio, headset, in person Phone and radio Airport Passengers Social media, website, face to face communication, FIDS displays prepare to receive prepare to receive Receiving Feedback: Airport authority personnel have discussed possibility of collecting comments from passengers. This would be done by either handing out cards with a link to our website or social media page and having a brief survey posted there.

13 Support for Passengers The key goal of the Fort Wayne International Airport IROPS Contingency Response 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 concern for the provision of: Support for deplanement of passengers from aircraft Sharing of facilities including making gates available Having a sterile area available for passengers who have not yet cleared CBP The following 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. TASK 2 TABLE 6 - Support for Passengers *Please modify the table below as appropriate for your needs, and add additional rows as necessary Passenger Location On-Board Aircraft Service Provider Delta/United American Eagle Allegiant Airport Concessions Description The crew will provide support for passengers. Delta/United will deplane at 90 minutes. If needed airline will service lavatory and provide conditioning/heat cart. Ensure flight attendant has enough drinks and ice if needed contact restaurant for additional supplies. Ensure lavatory is serviced when aircraft arrives. PSD will be informed of diversion. They will note the flight number and time plane landed to track time spent on aircraft. If airline requests assistance, airport will provide it. (Bottled water, etc) If necessary, provide airlines with additional supplies for passengers on the aircraft. Delta/United Regional Elite will coordinate with the crew of the aircraft about possible deplanement. When deplaning passengers, airline will inform TSA and PSD of its intentions. Deplaning Aircraft American Eagle Allegiant Airport If aircraft is off the jet bridge, ensure airline has enough employees to escort the customers to the terminal. Airport will make available resources/ help coordinate resource use. These resources include jet bridges, parking areas, special needs assistance, etc.

14 14 TASK 2 TABLE 6 - Support for Passengers *Please modify the table below as appropriate for your needs, and add additional rows as necessary Passenger Location Service Provider Delta/United Description Depending on the length of delay, airline will coordinate with TSA about possibility of allowing passengers to leave sterile area. Airline prefers not to have passengers leave, but depending on length of time, they will coordinate with TSA. Special needs passengers will be accommodated as needed. American Eagle Allegiant If delay will be short, try to keep the customers in the gate area. If the delay will be extensive, advise customers to retain boarding pass to re-enter security. For delays of over 4 hours airline has an agreement set up with a pizza place to provide pizza and drinks for the customers. In Terminal Airport PSD will be on site with TSA to ensure passengers are kept in the sterile area, unless it is determined that due to the length of the delay that they are allowed to leave; they will assist airline/passengers in whatever means necessary. Extended Delay Accommodations Concessions TSA CBP Ground Transportation Airport FCC will accompany passenger s needs as needed, including callback during afterhours. Special dietary needs, infant needs, etc. will be provided to passengers. TSA along with PSD will determine need for passengers to leave sterile area/ plan for re-entry to sterile area. They will help keep passengers in sterile area if needed. In the event of an international diversion, agreement with CBP will be in effect. Area for deplaning international passengers has been made. This area will be monitored by CBP, TSA and PSD. Airline will contact ground transportation/ make hotel accommodations for extended delays. Airport has cots available for passengers if deemed necessary for them to spend the night in the terminal. This is a last resort and is not offered as an alternative to staying at a hotel.

15 Tracking Inventory This section describes guidance for planning and developing agreements 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 Fort Wayne International Airport organization during an IROPS event. Descriptions of understandings of planned coordination related to sharing of resources are listed in Section Coordinating Existing IROPS Contingency Response Plans. The following table describes specific categories of resources which have been identified as being available for shared use. TASK 2 TABLE 7 - Tracking Resource Inventory *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Inventory Item Description Delta/ United American Eagle Allegiant Airport Concessions INANG 122 nd FW FedEx UPS Atlantic Aviation Tracked in airport database Tracked in airport database Airport will maintain a database of all equipment on the airport. Tracked in airport database Tracked in airport database Tracked in airport database Tracked in airport database Tracked in airport database List will be updated at annual IROPS review Prior to any vendor borrowing a piece of equipment from us, a walk around is done to document any existing damage, and then when equipment is returned, another walk around is down to document any new damage; like how rental car companies do. List will be updated at annual IROPS review. All equipment can be made available upon request depending on its use at the time and length of time it will be needed. List will be updated at annual IROPS review List will be updated at annual IROPS review List will be updated at annual IROPS review List will be updated at annual IROPS review List will be updated at annual IROPS review List will be updated at annual IROPS review

16 Skills Availability This section describes guidance for planning and developing agreements 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 Coordinating Existing IROPS Contingency Response Plans. The following table describes specific categories of skilled personnel which have been identified as being available for shared use. TASK 2 TABLE 8 - Skills Availability *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Skill Description Delta/United Various Each agent is trained on every piece of equipment that is DL/UA owned. We also have trained all agents on AA s equipment. If an agent is uncomfortable with a piece of equipment, then they are encouraged to ask for assistance until they are comfortable themselves to perform the task. American Eagle Allegiant Any skill employees are trained on: loading/unloading aircraft, aircraft parking, lavatory servicing, etc. All employees can be made available for assistance in any area needed. Availability will depend on the current situation and or task they have already assigned to them. Airport Jet Bridge Operation Airport will hold annual training on use of jet bridges. By using a train the trainer approach, airlines will train new hires to ensure all employees are properly trained on jet bridge use. Concessions Various Staff with appropriate training would be called back during an event. INANG Various Equipment INANG personnel will receive training prior to use of any equipment. INANG personnel will train other entities that would have a need to use their equipment. Atlantic Fueling All Atlantic fueling personnel are NATA trained and certified. All are trained and certified on all air carriers that use FWA. Ground handling is limited to availability of equipment on hand.

17 Established Agreements with Concessions Concessions at Fort Wayne International Airport 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 following table describes specific concessions support agreements which have been identified as being available during IROPS events. Appendix C contains copies of specific concession agreements. TASK 3 TABLE 1 - Agreements with Concessions *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Name (Contact) FCC Will accompany needs of sharing supplies as needed. Additional staffing if needed to provide services for IROPS will be called to provide for passenger needs. After hours the general manager needs to be contacted and efforts will be made to accompany passenger needs for concessions. If special needs are identified like special dietary needs and infant needs FCC will make arrangements to get needs for the passengers. The gift shop has diapers and wipes currently available. Menu availability may be limited during irregular operations but every attempt to care for the passengers will be made. PSD will inspect after hour sterile area entry for recalled restaurant personnel. As soon as PSD is notified of a diversion they will make the determination as to if additional resources will be needed. If needed, notification of appropriate personnel will be made by PSD. 2.4 Established Agreements with Ground Transportation Ground transportation organizations at Fort Wayne International Airport 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 following table describes specific ground transportation support agreements which have been identified as being available during IROPS events. Appendix C contains copies of specific ground transportation agreements. TASK 4 TABLE 1 - Agreements with Ground Transportation *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Name (Contact) Organization Name (Contact)

18 Established Agreements with FAA It is recognized that FAA has issued directives to air traffic personnel pertaining to aircraft making tarmac delay requests related to DOT Rules on "Enhancing Airline Passenger Protections". These procedures are in addition to providing access to aircraft flight status. The following table describes Fort Wayne International Airport FAA/ATC facility actions specific to IROPS events. Appendix C contains copies of specific agreements with the FAA. TASK 5 TABLE 1 - Agreements with FAA *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Name (Contact) FAA Air Traffic Control Tower Until otherwise directed by FWACAA, ATC will taxi all IROPS aircraft to the terminal ramp. At FWACAA direction ATC will taxi IROPS aircraft to other designated staging areas to avoid ramp congestion. When a request is made by the pilot-in-command of an aircraft to return to the ramp, gate, or alternate deplaning area due to the Three-hour Tarmac Rule, ATC will coordinate with FWACAA to expeditiously relocate the aircraft for deplaning. Summary In serving our stakeholders during Airport Irregular Operations (IROPS), FWA ATCT (Hereafter referred to as ATC ) is happy to assist our stakeholders within our agency and governmental policies to the maximum extent possible. Our primary responsibility is the operational duty of movement of air traffic; during an IROPS event ATC personnel will be limited in the interaction with other stakeholders due to higher operational priorities. ATC will provide support and advisory information to FWACAA on a work load permitting basis only. (This will take into consideration traffic load, complexity and available recourses.) The information provided may include: 1. Notifying FWACAA that diversion flights are inbound. 2. Establishing with FWACAA irregular parking areas for IROPS aircraft. 3. Advising FWACAA on known ground delay programs that could impact developing or active IROPS.

19 Established Agreements with 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 following table describes (AIRPORT NAME) TSA procedures specific to IROPS events. Appendix C contains copies of specific agreements with the FAA. TASK 6 TABLE 1 - Agreements with TSA *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Name (Contact) (24/7 Contact #) TSA Organization at Fort Wayne International Airport Indianapolis Coordination Center Size, scope and nature of individual airport flight operations determine the hours in which TSA security checkpoints are open for normal screening activity. In the event of irregular flight operations, to include flight diversion(s), upon notification by the affected airline(s) TSA leadership will liaise with airline and/or airport operators to determine the potential impact to the local operation. During regular operating hours when passenger security screening checkpoints are normally staffed, passengers from the diverted flight will have discretion whether or not to leave the sterile area. If that occurs, TSA supervisory staff will ensure that appropriate screening staff is maintained at the airport in order to process the increased influx of passengers back in to the airport sterile area. TSA supervisory staff will brief the screening officers on the situation and inform the TDC as to what boarding passes will be authorized entry in to the sterile area during that period of irregular operations. If irregular operations occur resulting in diverted flights arriving at the airport during a time period when the security screening checkpoint is minimally staffed by TSA, often times for the sole purpose of controlling access to the sterile area while awaiting normally scheduled late flight arrivals, TSA officers will be briefed by airline and/or airport operators to determine the most appropriate course of action under the impending circumstances. Under these circumstances, TSA encourages the airline operator to inform passengers they should remain in the airport sterile area and that should they exit the sterile area, they may be delayed in regaining access to the sterile area which could impact their continuing travel that day. Factors that TSA management will consider during discussions with airlines and/or airport operators in making a determination whether or not to hold over or recall TSA officers to address passenger screening for irregular flight operations include, the size of the airport sterile area, number of flights and passengers affected, anticipated duration of the irregular flight operations, airport amenities in the sterile area to include restrooms and service facilities. If irregular flight operations occur resulting in diverted flights arriving at the airport during a time period when the security screening checkpoint is closed and no TSA officers are present at the airport, airline and/or airport operators should call the 24 hour TSA Coordination Center with details of the irregular flight operation. Airline and/or airport operators should be specific in their request for services and provide information where they can be called back by a TSA management official. Factors that TSA management will consider during discussions with airlines and/or airport operators in deciding whether or not to recall TSA officers to the airport to address passenger screening for the irregular flight operations include, the size of the airport sterile area, number of passengers affected, anticipated duration of the irregular flight operations, airport amenities in the sterile area to include restrooms and service facilities. TSA employees are considered emergency employees and are subject to hold over at the end of their workday or emergency recall. When appropriate, based on the consideration factors discussed earlier in this section, TSA management would have Officers remain on duty at the end of their scheduled shift or call back TSA officers to assist during IROPS.

20 20 TASK 6 TABLE 1 - Agreements with TSA *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Name (Contact) (24/7 Contact #) If irregular flight operations occur resulting in diverted flights arriving at the airport during a time period when the security screening checkpoint is closed the following concepts may be incorporated into ASP amendments to provide a means for the airport to establish a sterile area during IROPS. It would allow for the security and comfort of the passengers, and not necessarily require TSA presence. If passengers are deplaned into a sterile area and remain in the sterile area, they may be re-boarded without additional screening. The airport operator or aircraft operator may establish a sterile area using procedures in the ASP or AOSSP without TSA presence. Procedures may be established to allow for escort of passengers outside the sterile area, such as to vending machines, and return without TSA screening. The second and third bullets above will be the one that need implementation airport by airport. The sterile area can be established by the airport operator, the aircraft operator, or a combination, and different combinations may be suitable for different airports. If the ASP does not already provide for the airport operator establishing the sterile area by sweeping the area and so on, the airport operator may need to establish such procedures in their ASP. For instance, the airport operator will need to determine who will have the responsibility to establish the sterile area, with appropriate training and knowledge by the persons who will do so. If the airport has food and drink in vending machines outside of the sterile area the airport operator may want to establish escort procedures for passengers to take advantage of the machines. The airport operator might want to have some aircraft operator or airport personnel trained to screen incoming food and drink that the aircraft operator may want to provide for the passengers. Irregular operations at airports not regulated under 49 CFR 1542 will be handled on a case-by-case basis and should be coordinated with the closest TSA office covering that geographic area.

21 Established Agreements with 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 following table describes Fort Wayne International Airport CBP procedures specific to IROPS events. Appendix C contains copies of specific agreements with the CBP. TASK 7 TABLE 1 - Agreements with CBP *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Name (Contact) Customs and Border Protection CUSTOMS & BORDER PROTECTION CONTACTS: The airline, charter operator, or pilot of a diverted aircraft, even if pre-cleared, will timely notify the CBP Officer on Duty or CBP Port Director of an intended or actual arrival, whether making an emergency or technical fuel stop, a weather related stop, stops due to illness on board the aircraft, or other emergency stops, including terrorist related incidents or precautions. Notifications to CBP will include the following: Name and contact number of airline representative Flight number Original routing Passenger count ETA and actual block time Reason for diversion, intention of airline, special requests/needs Crew status (how much time crew has before a crew change is required) Additional updates and flight departure time. All passengers and crew must remain on board the aircraft. No new passenger or cargo may be added. Crew changes and servicing aboard an aircraft will be permitted if the carrier has provided 100% Advance Passenger Information (API) prior to the aircraft s arrival. All actions related to the aircraft, persons and cargo onboard will be coordinated with CBP. All international diverted aircraft will be closely monitored by FAA, CBP & PSD. During a protracted stay in excess of two hours, an airline may request permission from CBP to deplane passengers of a diverted aircraft into a sterile and secure holding area. Permission may be granted if the airline communicates with CBP the nature of the diversion and the anticipated length of delay; updates CBP of the status of the diversion and of changes as they occur; and controls the movement of passengers and secures passengers from contact with other domestic or foreign flights. When all airline issues are resolved, passengers will be escorted back to the plane. CBP processing and clearance will take place at the original destination. It is imperative that international flights do not remain on the tarmac at a U.S. airport for more than four (4) hours without allowing the passengers to deplane. If an air carrier s representative or aircraft s pilot states that the aircraft will depart within three 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 aboard the aircraft. If the aircraft lands when the CBP officer is on duty, Airport Operations are to notify. The CBP officer will meet the plane as soon as possible after arrival. If the aircraft is to be refueled, the CBP officer will monitor the refueling and issue a permit to proceed to the aircraft before its departure. The FBO will be allowed to refuel the aircraft, but no person or thing will be introduced or off-loaded onto or from the aircraft, and the aircraft will remain secure. Stairs may be pushed up to the aircraft under CBP supervision for necessary paperwork transfer. Due to FAA requirements, the pilot will be permitted to make a walk-around of the aircraft. If the diversion occurs outside normal business hours, Airport Operations are to call CBP. If there is no answer, they are to call X-SECTOR, and request to speak to the CBP duty officer. On a case by case basis, the permit to proceed and other necessary permissions may be issued telephonically by the CBP duty officer.

22 22 TASK 7 TABLE 1 - Agreements with CBP *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Name (Contact) The location of the secure holding area will be regional holding (gate area 1-4) located on the first floor of the airport terminal. The secure area will be physically blocked off from the rest of the terminal in advance of passengers being deplaned in order to prevent unauthorized entrance or exit. All possible entrances and exits to the holding area will be constantly guarded. The security of the passengers while on board the aircraft or in the holding area will be the responsibility of the airline, but assistance may be rendered by Public Safety & TSA personnel as needed, commensurate with the number of passengers. The secure area has restrooms within it, to which passengers will have exclusive access. The security of the restrooms will be maintained as part of the secure area. Airline personnel may enter the secure area to provide food and water to passengers. International diversions with fifteen passengers or less may be processed and cleared by CPB at the Fort Wayne User Fee Airport. But due to insufficient CBP facilities and personnel at FWA, there is no possibility of CBP processing and clearance of international diverted flights with more than fifteen passengers. It may be possible for CBP at FWA to process and clear the crew of a diverted aircraft, and the aircraft itself, if disabled. But the passengers of said disabled aircraft, if numbering more than fifteen, must proceed for CBP processing and clearance on board an alternate aircraft to a designated airport. CBP processing and clearance will take place at the CBP ramp and office. If there is regulated garbage on board an aircraft with more than fifteen passengers, then it will only be partially cleared by CBP at FWA, which will initiate a CBP Form AI250 to permit de-catering of the aircraft at an alternate designated airport. There is no catering service available at FWA. None of these provisions apply to outbound international flights. But CBP presence may be required if there are deportees onboard.

23 IROPS Coordination Workshop Periodic IROPS coordination workshops are held at Fort Wayne International Airport providing a common format and venue for periodic review and confirmation / update of local IROPS Response plans. The Fort Wayne International Airport will determine the frequency and specific agenda for these meetings, as appropriate. The following table describes Fort Wayne International Airport plans for holding these workshops. Appendix C contains copies of previous workshop summaries which can be referenced. TASK 8 TABLE 1 - IROPS Coordination Workshops *Please modify the table below as appropriate for your needs, and add additional rows as necessary Fort Wayne International Airport IROPS Workshop Lessons learned (after each IROPS activation a committee, consisting of affected airlines, PSD, Operations, Terminal Services, as well as any other entity affected.) Updates from DOT protecting passenger rights in order to ensure compliance with most current regulation/s IROPS operational challenges o Importance of effective and early communication o Situational awareness by ensuring timely sharing of information between affected entities o Reporting and tracking of diverted aircraft Update agencies involved as changes are made, including but not limited to personnel changes, procedural changes, inventory changes, and skills availability Invite subject matter experts from coordinating entities to share experiences or lessons learned at FWA and/or other airports Review coordinating entities best IROPS practices Formulate strategy for future enhancements to the IROPS program Table top exercise following morning review and suggested IROPS changes

24 IROPS Contingency Coordinated Training Periodic coordinated contingency training for IROPS response are held at Fort Wayne International 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. The following table describes Fort Wayne International Airport plans for holding this training. Appendix D contains copies of previous training exercises which can be referenced. TASK 9 TABLE 1 - IROPS Contingency Coordinated Training *Please modify the table below as appropriate for your needs, and add additional rows as necessary IROPS Training Activity (Description) Initial IROPS Training Why IROPS Plan familiarization Trigger points Contact information Skills tracking Effective communication/examples of ineffective communication Recurrent IROPS Training Updates to DOT regulations pertaining to passenger protect IROPS lessons learned from FWA and other airports Feedback/ideas from experiences

25 25 Chapter 3 During an IROPS Event The Joint Actions occurring during an IROPS event are described in the following diagram. The Fort Wayne International Airport IROPS Contingency Response Committee ensures the capability for coordinating shared aircraft status information. Relevant aspects of aircraft status are provided to appropriate aviation service provider organizations during an IROPS event by the Fort Wayne International Airport communication center or point-ofcontact, as appropriate. 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. Joint Actions during an IROPS Event Note to User: Guidance for planning each of the following sections are described as Tasks 10 through 18 in Appendix A of this Model IROPS Contingency Plan and supported with various Tools listed in Part 5 of the Guidebook.. At the discretion of the airport, Appendix A may be deleted after the IROPS Contingency Response Plan has been developed or it may be kept as a reference. It is recognized that agreements for implementing these IROPS response procedures were described in the "Before an IROPS Event" Sections. The corresponding detailed procedure checklists for "During an IROPS Event" are described in the following Sections.

26 Aircraft Status Aircraft status in the air and on the ground is tracked by both airlines and the FAA to provide accurate, complete, and timely information in regard to expected flight delays and developing local situations. The following table describes Fort Wayne International Airport procedure checklists for tracking aircraft during IROPS events. Organization Delta (Delta Global Services) United (Delta Global Services) American Eagle Allegiant (Trego-Dugan) Delta (Delta Global Services) United (Delta Global Services) American Eagle Allegiant (Trego-Dugan) TASK 10 TABLE 1 - Aircraft Status Aircraft Status Actions Diverted Flights Maintains status of aircraft in flight as respect to schedule Determines aircraft requires flight diversion Ensures aircraft diversion notice is communicated to Airport Operations at Diversion Airport Ensures aircraft diversion status is maintained (ongoing) with updated status communicated to Airport Operations at airport where flight was initially planned to arrive Continues tracking and communicating status until flight ultimately arrives at original destination Aircraft on Ground Maintains status of arriving and departing aircraft to determine compliance with "3-Hour Rule" Determines aircraft situation may result in lengthy ground delay Ensures other relevant service providers are notified of possible IROPS related impact and to confirm any related support including gate availability that is potentially needed is available if required Determines aircraft will deplane passengers after lengthy ground delay Ensures other relevant service providers are notified of unplanned passengers arriving in terminal Airport Operations (Diversion Airport) Diverted Flights Initiates monitoring of flight when notified of flight diversion Confirms relevant service providers have been notified of unplanned passengers arriving in terminal Concessions TSA CBP Ground Transportation Airport Operations Aircraft on Ground Tracks status of arriving and departing aircraft to determine compliance with "3-Hour Rule" When notified aircraft will deplane passengers after lengthy ground delay, confirms relevant service providers have been notified of unplanned passengers arriving in terminal Concessions TSA CBP Ground Transportation

27 Implementing IROPS Communications Plans Relevant IROPS information including status and related situational information is communicated among appropriate Fort Wayne International Airport organizations during an IROPS event. The following table describes key elements of Fort Wayne International Airport IROPS communications plans. TASK 11 TABLE 1 - IROPS Communications Plans (Example Checklist - Modify as Appropriate) *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Communications Actions Delta (Delta Global Services) Diverted Flights United (Delta Global Services) Ensures aircraft diversion notice is communicated to Airport Operations American Eagle at Diversion Airport Allegiant (Trego-Dugan) Airport Operations (Diversion Airport) Airport Operations (Diversion Airport) Airport Operations Aircraft on Ground Communicates diversion status to onboard passengers Communicates diversion status to passengers awaiting next segment of flight and to people meeting arriving passengers (in terminal where initially planned to land and externally via electronic notification) Updated status communicated to Airport Operations at airport where flight was initially planned to arrive Continues tracking and communicating status until flight ultimately arrives at original destination Aircraft on Ground Communicates delay status to onboard passengers Ensures other relevant service providers are notified of possible IROPS related impact and to confirm any related support including gate availability that is potentially needed is available if required Communicates delay status to passengers awaiting next segment of flight and to people meeting arriving passengers (in terminal where initially planned to land and externally via electronic notification) Ensures other relevant service providers are notified of unplanned passengers arriving in terminal after lengthy ground delay Diverted Flights Confirms relevant service providers have been notified of unplanned passengers arriving in terminal When notified aircraft will deplane passengers after lengthy ground delay, confirms relevant service providers have been notified of unplanned passengers arriving in terminal

28 Implementing IROPS Passenger Support Plans Support procedures for passengers and other customers at Fort Wayne International Airport during IROPS events include focus while they are on-board aircraft, during their deplaning, in the terminal, and when they need ground transportation. The following table describes procedures at Fort Wayne International Airport for support during an IROPS event TASK 12 TABLE 1 - Passenger Support (Example Checklist - Modify as Appropriate) *Please modify the table below as appropriate for your needs, and add additional rows as necessary Passenger Service Provider Description Location On-Board Aircraft Delta (Delta Global Support for Special Needs passengers Services) Passenger support (status notification, water/food, restrooms, United (Delta etc) per Department Transportation "3-Hour Rule" Global Services) American Eagle Allegiant (Trego- Dugan) On-Board Aircraft Airport Backup (to airlines) passenger support by sharing supplies On-Board Aircraft Concessions Backup (to airlines) passenger support by sharing supplies Deplaning Aircraft Delta (Delta Global Shared gate (as required) Services) United (Delta Global Services) American Eagle Allegiant (Trego- Dugan) Deplaning Aircraft Airport Status for shared gate availability Passenger support for deplaning aircraft at remote parking (provision of mobile stairs, bus transport to terminal, Special Needs lift, etc) Shared equipment support for remotely parked aircraft (mobile stairs, bus transport to terminal, Special Needs lift, etc) In Terminal Delta (Delta Global Periodic status update Services) Re-booking as required United (Delta Global Services) Support for providing accommodations for lengthy delays (including food / lodging as required) American Eagle Allegiant (Trego- Dugan) In Terminal Airport Support for Special Needs passengers Support for after-hours accommodations Agreement with TSA for after-hours secure area Agreement with CBP for after-hours delayed flights Agreement with CBP for support (if airport does not have CBP presence) In Terminal Concessions Support for after-hours operation Inventory support for infants and Special Needs passengers In Terminal TSA Utilization strategy for after-hours secure areas In Terminal CBP After hours support for delayed flights Support to diversion airports not having CBP presence Extended Delay Ground Support for Special Needs passengers Accommodations Transportation After hours transportation to/from off-site accommodations

29 Implementing IROPS Concessions Agreements Concessions at Fort Wayne International Airport have agreed to provide specific support during IROPS events. The following table describes these agreements. TASK 13 TABLE 1 - Implementing IROPS Agreements for Concessions *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Local agreement(s) (24/7 Contact #) Concessions organization #1 Backup (to airlines) on-board passenger support by sharing supplies Implement Concessions IROPS plan Support for special needs passengers Support for infants Support for after-hours service Implement back-up staffing to respond to passenger surge 3.5 Implementing IROPS Ground Transportation Agreements Ground transportation organizations at Fort Wayne International Airport have agreed to provide specific support during IROPS events. The following table describes these agreements. TASK 14 TABLE 1 - Implementing IROPS Agreements for Ground Transportation *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Local agreement(s) (24/7 Contact #) Airport Authority does not have Implement Ground Transportation IROPS plan providing after hours agreements in place with any transportation to/from off-site accommodations private bus company. Below is Support for Special Needs passengers the contact information of Implement back-up staffing/resources to respond to passenger surge known available bus companies.

30 Implementing IROPS Agreements with FAA The FAA/ATC organization at Fort Wayne International Airport has implemented procedures pertaining to tarmac delay requests related to DOT Rules on Enhancing Airline Passenger Protections. The following table describes Fort Wayne International Airport FAA/ATC facility actions specific to IROPS events. TASK 15 TABLE 1 - Implementing IROPS Agreements with FAA *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Local agreement(s) (24/7 Contact #) Local implementation of aircraft ground control procedures per the Department of Transportation "3-Hour Rule" Access to FAA aircraft status related to flight diversions Access to FAA aircraft status related to ground delays during taxi-in Access to FAA aircraft status related to ground delays during taxi-out 3.7 Implementing IROPS Agreements with TSA The TSA organization at Fort Wayne International Airport has implemented procedures concerning establishing and utilizing secure areas using procedures in the Airport Security Program or Aircraft Operator Standard Security Program. The following table describes Fort Wayne International Airport TSA actions specific to IROPS events. TASK 16 TABLE 1 - Implementing IROPS Agreements with TSA *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Local agreement(s) (24/7 Contact #) TSA Re-screening procedures for passengers deplaned due to an extended tarmac delay Contingency plan procedures for after-hours security arrangements 3.8 Implementing IROPS Agreements with CBP Fort Wayne International Airport has implemented agreements with CBP relating to response to IROPS events. The following table describes Fort Wayne International Airport CBP actions specific to IROPS events. TASK 17 TABLE 1 - Implementing IROPS Agreements with CBP *Please modify the table below as appropriate for your needs, and add additional rows as necessary Organization Local agreement(s) (24/7 Contact #) CBP Port Director Implement procedures for unscheduled after-hours International flight CBP Sector Communications arrivals (24 Hr Contact) Implement procedures for diverted International flight into airport with (800) CBP Flight Inspection Station Implement procedures for diverted International flight into airport without CBP Flight Inspection Station Implement procedures for a Technical Stop Implement procedures for Extended Stays / Diversions - Four (4)-Hour Guideline for International flights

31 31 Chapter 4 After an IROPS Event The following tables describe Fort Wayne International Airport procedures for these actions including incorporation of lessons learned into the update of Fort Wayne International Airport IROPS Contingency Response Plan as appropriate. Note to User: Guidance for debriefing of response effectiveness provided during an IROPS event and capturing lessons learned are described as Tasks 18 in Appendix A this Model IROPS Contingency Plan and are supported with various Tools listed in Part 5 of the Guidebook.. At the discretion of the airport, Appendix A may be deleted after the IROPS Contingency Response Plan has been developed or it may be kept as a reference. 4.1 Debriefing After an IROPS event, it is important to have a timely and comprehensive assessment of the event. The Fort Wayne International Airport will coordinate this debriefing meeting and include all aviation service providers, as well as the IROPS Contingency Response Committee. The following table describes Fort Wayne International Airport plans for holding this training. Appendix B contains copies of previous debriefing activities which can be referenced. TASK 18 TABLE 1- Debriefing IROPS Event *Please modify the table below as appropriate for your needs, and add additional rows as necessary Airport Operations (PSD & Review and debriefing with Fort Wayne International Airport Ops) organization management Delta/United (Delta Global Summary Documentation of findings (including any Lessons Learned) Services) American Eagle Allegiant Air (Trego-Dugan) TSA CBP FAA Restaurant (First Class Concessions) Car Rental Parking INANG 122 nd FW FBO (Atlantic Aviation) Fort Wayne International Airport IROPS Contingency Response Committee and recommendations Report sent to Chairperson of Fort Wayne International Airport IROPS Contingency response Committee Consideration if further study is required to fully understand the effectiveness of Fort Wayne International Airport response Results of the review (and study if required) considered to determine if revisions are required in Fort Wayne International Airport IROPS Response Plan Re-distribution of Fort Wayne International Airport IROPS Response Plan (if revised)

32 Lessons Learned As part of the debriefing, it is important to catalog the lessons learned from the individual IROPS events. The Fort Wayne International Airport will coordinate these lessons learned and provide them to the aviation service providers, as well as the IROPS Contingency Response Committee members. The following table describes Fort Wayne International Airport plans collecting lessons learned. Appendix C contains copies of previous lessons learned which can be referenced. TASK 18 TABLE 2 - Capturing Lessons Learned *Please modify the table below as appropriate for your needs, and add additional rows as necessary Airport Operations (PSD & Review and debriefing with Fort Wayne International Airport Ops) organization management Delta/United (Delta Global Summary Documentation of findings (including any Lessons Learned) Services) American Eagle Allegiant Air (Trego-Dugan) TSA CBP FAA Restaurant (First Class Concessions) Car Rental Parking INANG 122 nd FW FBO (Atlantic Aviation) Fort Wayne International Airport IROPS Contingency Response Committee and recommendations Report sent to Chairperson of Fort Wayne International Airport IROPS Contingency Response Committee Consideration if any additional Lessons Learned from examples of coordinated response by Fort Wayne International Airport organizations Compile and distribute any new Lessons Learned Periodic sharing of Lessons Learned with other airports in the general Aviation Community

33 Appendix B Status of Plan Details The following table serves as a working summary of the actions within the current version of the Fort Wayne International Airport IROPS Contingency Response Plan. It is intended that each item in the table will be reviewed periodically for status and outlook by the IROPS Contingency Response Committee. Task - Table Last Update Expected Update Task 1 Table 1 10/3/2011 Task 2 Table 1 10/3/2011 Task 2 Table 2 10/3/2011 Task 2 Table 3 10/3/2011 Task 2 Table 4 10/3/2011 Task 2 Table 5 10/3/2011 Task 2 Table 6 10/3/2011 Task 2 Table 7 10/3/2011 Task 2 Table 8 10/3/2011 Task 3 Table 1 10/3/2011 Task 4 Table 1 10/3/2011 Task 5 Table 1 10/3/2011 Task 6 Table 1 10/3/2011 Task 7 Table 1 10/3/2011 Task 8 Table 1 10/3/2011 Task 9 Table 1 10/3/2011 Task 10 Table 1 10/3/2011 Task 11 Table 1 10/3/2011 Task 12 Table 1 10/3/2011 Task 13 Table 1 10/3/2011 Task 14 Table 1 10/3/2011 Task 15 Table 1 10/3/2011 Task 16 Table 1 10/3/2011 Task 17 Table 1 10/3/2011 Task 18 Table 1 10/3/2011 Task 18 Table 2 10/3/2011

34 Appendix C Reference Documents Development of Contingency Plans for Lengthy Airline On-Board Ground Delays, Developed by the (US Department of Transportation) National Task Force to Develop Model Contingency Plans to Deal with Lengthy Airline On-Board Ground Delays, November 12, 2008 (Note: referred to in this document as the Model Contingency Plan) Airport gate parking configuration ACS Extended On-Board Delay and Diversion Procedures (EOBDD) from Delta Extended Tarmac Delay- Local Station/Airport Plan from United Customer Service Plan- Essential Customer Needs During Extraordinary Delays from American Eagle Customer Service Plan (CSP) and Contingency Plan for Lengthy Tarmac Delays from Allegiant Aircraft characteristic reference Checklists (Airport Operations, PSD, Airlines) Diversion Menu- First Class Concessions EVB Procedures INANG MOA-Use of Equipment Airline Tenant Equipment List

35 Appendix D Compliance Matrix of (AIRPORT NAME) IROPS Contingency Response Plan with DOT Model Contingency Plan Note: The Fort Wayne International Airport IROPS Contingency Response Plan (this document) describes the overall coordination process utilized by the Fort Wayne International Airport 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 Fort Wayne International Airport IROPS Contingency Response 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 utilized by the Fort Wayne International Airport 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)

36 Appendix E - Contact details for Fort Wayne International Airport IROPS Contingency Response Committee and for Points-of-Contact for Agencies during an IROPS Event Contacts during an IROPS Event Organization Name (Contact) Alternate (Contact) Airport Operations Airlines Government Agencies Fixed Base Operations Executive Management Liaison

37 Diversion Checklist for Airlines Before Aircraft Diversion Event (As soon as known): Notify Airport Operations at of the following Identify airline and flight number if available Original departure and destination airports Approximate arrival time Approximate departure time if available Cause of diversion Intentions of diverting aircraft Examples: gas & go, passengers deplaning, extended delay, etc. During Aircraft Diversion Event Continue to communicate aircraft intentions with Airport Operations If Necessary, Airport Operations can Coordinate Accommodations: Aircraft Gate Assignment Passenger Boarding Ramp Food, Transportation, Lodging Security (TSA, PSD, CBP) After Aircraft Diversion Event Airline Supervisor-Obtain feedback from employees about what went well, what did not go well, and changes that could be made to improve the next response Airline Manager and Supervisors join Post Diversion call with Airport Authority

38 Diversion Checklist for Airport Operations Before Aircraft Diversion Event (As soon as known): Remind airline ground handler that Airport Operations ( ) is the point of Contact Obtain all available information from the responsible airline ground handler/aircraft Airline and Flight Number Original departure and destination airports Approximate arrival and departure times Diversion cause Intentions of the diverting aircraft (gas & go, pax deplaning, extended delay, etc.) Determine if diversion aircraft requires specific equipment/resources Stage all needed equipment/resources in advance Relay all known information to PSD Communicate aircraft intentions and impacts with related parties Restaurant, TSA, other airlines, CBP, ATCT, FBO During Aircraft Diversion Event: Continuous communications with airline ground handler (at least every half hour) If necessary, assist airline ground handler: Determine gate assignment Retrieve boarding ramp Food/Beverage needs Transportation/Lodging needs Security (TSA/CBP/PSD) FIDS Update- Immediate update by airlines through daily schedule Social Media updates Communicate to related parties with information updates and offer assistance After Aircraft Diversion Event: Debrief internally with Operations Supervisor/Manager on all available information Debrief with airline ground handler on successes, failures, and areas of improvement If necessary, initiate conference call and disseminate debrief notes with all parties as lessons learned/ actions items

39 Diversion Checklist for Public Safety Before (If notified prior to aircraft landing): Notify Operations Specialist on Duty If operations on duty, notify airline that Operations will be point of contact for all diversion related information Fill out diversion form If warranted, notify additional personnel or entities such as: FCC, FBO, INANG, Etc.* Disseminate EVB-If Necessary ** *If the plan is for the aircraft to have an extended delay at FWA, then determine if resources to accommodate would be necessary. If it is determined they will be necessary, begin call back procedures. ** -If informational EVB only, disseminate to Group 1 and specify that informational only - If additional Airport Authority resources are necessary, disseminate to Group 2 after determining what authority resources would be necessary to provide assistance - Call additional groups as necessary to provide assistance - If social media is needed for dissemination of information, contact Marketing & Administration Manager-Kim Fuhrmann During: If not notified prior to landing, go thru steps in the before stage Obtain additional information about the aircraft Tail Number Time Landed Any other pertinent information Fill out and submit diversion form Inform airlines that if they need assistance, that we can help if requested After: OIC obtain feedback from officers regarding what went well, what didn t and any changes that need to be made (Similar to post incident discussion) OIC join the post diversion conference call and provide input

40 Gate Use/ Parking Plan

41 Airport Irregular Operations (IROPS) Runway use and Taxi Routes The following proposed IROPS runway use and taxi route program covers runway use, staging points, and taxi routes. The limitations of taxiways B, Bl B2, E, and G2, as defined in section 3, must be considered. 1. Runway use. a. Runway 23 offers the greatest flexibility in taxiing and staging a large number of aircraft, with minimal interference to staging points or taxiing. b. Runway 14 offers the similar staging access as runway 23. The use of Runway 14 adds the complication of multiple runway crossings when enroute from the staging points to the terminal. The use of Runway 14 adds the congestion of taxiway Y. With the use of Runway 14 taxiway Y is the route from the staging areas north of taxiway Y to the terminal as well as the route from the terminal to the active runway. c. Runway 5 offers the movement and staging options of runway 23. The use of Runway 5 adds the congestion of taxiway C. With Runway 5 taxiway C is the route from the staging areas of the Air Trade Center and the West Ramp to the terminal as well as the route from the terminal to the active runway. d. Runway 32 has limited runway exiting options for all aircraft. The use of Runway 32 adds the complication of multiple runway crossings when enroute from the staging points to the terminal. The use of Runway 32 adds the potential for blocked aircraft due to the routes from the terminal to the runway and the routes from the staging points to the terminal. 2. Staging points. A staging point is defined as area to be used as an alternate aircraft parking zone when terminal ramp space is at capacity. a. Listed potential staging points: 1). West ramp 2) Fixed Base Operator ramp 3). Ramp space in front of hangers 37, 39, 40 4) Air Trade Center 5) Taxiway B 6) Unused portions of Runway 9/27 7) Taxiway D 8) Taxiway M 9) Skywest maintenance ramp 10) Northwest edge of the Indiana Air National Guard Ramp

42 42 11) Unused Runway (The closing, of crossing runways for staging and parking may be necessary by FWACAA in order to maximize airport capacity.) 12) Portions of taxiway Y not used for routing, aircraft 13) Portions of taxiway C not used for routing, aircraft 3. Primary taxi routes from select staging points based on runway use. Note: the Air traffic control specialist operating the ground control position may elect to use a different route than the ones listed below as the various situations possible may dictate the use of an alternate route. Abbreviations and symbols: TXY = Taxiway RWY = Runway TERM = Terminal Ramp (#) = number of inactive runway crossings. [#] = number of active runway crossings. { }= Insertion of previously stated route Limitations: Taxiways B. B 1. B2. E, and G2 are limited to aircraft with a wingspan less than 79 feet and aircraft weighing less than 50,000 pounds on dual axles. a. Runway 23 in use. 1) From staging point: Air Trade Center Route 1: TXY C to TERM (2) Route 2: TXY C to TXY G to TXY G3 to TERM (2) 2) From staging point: West Ramp Route 1: TXY C to TERM (1) Route 2: 3) From staging point: RYW 9/27 Route 1: TXY D to TXY Y to TXY C or Y5 to TERM (1) [1] Route 2: West on RWY 9:27 to TXY C to {Air Trade Center's Route 1} (1) [1] Route 3: 4) From staging. point: Taxiway B Route 1: East on RWY 9/27 to {RWY 9/27's Route 1} (2) [1] b. Runway 14 in use. 1) From staving, point: Air Trade Center Route 1: TXY C to TERM (2)[1] Route 2: TXY C to TXY G to TXY G3 to TERM (2)[1] 2) From staging point: West Ramp Route 1: TXY C to TERM [1]

43 43 Route 2: TXY G to TXY G3 to TERM [1] 3) From staging, point: RYW 9/27 Route 1: TXY D to TXY Y to TXY C or Y5 to TXY C to TERM [1] Route 2: West on RWY 9/27 to TXY C to {Air Trade Center's Route 1} (2) [1] 4) From staging point: Taxiway B Route 1: East on RWY 9/27 to {RWY 9/27's Route 1} (2) [1] c. Runway 5 in use. 1) From staging, point: Air Trade Center Route 1: TXY C to TERM (1) Route 2: TXY C to TXY G to TXY G3 to TERM (1) 2) From staging, point: West Ramp Route 1: TXY C to TERM (1) Route 2: TXY G to TXY G3 to TERM (1) 3) From staging point: RYW 9/27 Route 1: TXY D to TXY Y to TXY C or Y5 to TXY C to TERM (1) Route 2: West on RWY 9/27 to TXY C to {Air Trade Center's Route 1} (1) [1] Route 3: 4) From staging point: Taxiway B Route 1: East on RWY 9/27 to {RWY 9/27's Route 1} (2) [1] d. Runway 32 in use. 1) From staging point: Air Trade Center Route 1: TXY C to TERM [1] Route 2: TXY C to TXY G to TXY G3 to TERM (1) [1] 2) From staging point: West Ramp Route 1: TXY C to TERM (1) Route 2: TXY G to TXY G3 to TERM [1] 3) From staging point: RYW 9/27 Route 1: TXY D to TXY Y to TXY C or Y5 to TXY C to TERM [1] Route 2: West on RWY 9/27 to TXY C to {Air Trade Center's Route 1} (1) [1] Route 3: 4) From staging point: Taxiway B Route 1: East on RWY 9/27 to {RWY 9/27's Route 1} (2) [1]

44 44