Operations Plan

The Operations Plan (OP): The OP is a plan for management of the NAS and is formulated, developed, and maintained by the Air Traffic Control System Command Center (ATCSCC) Planning Team (PT) in collaboration with FAA and customer weather forecasters, ATCSCC personnel, Air Route Traffic Control Center (ARTCC), District Traffic Management Officers (TMO) or designees, terminals, airline planners, international facilities, military, general aviation planners, and other FAA field facility management personnel. The Operations Planning Webinar (PW) is conducted via a web-based application to include an audio dial-in capability.

Advance Plan (AP): The AP is for advanced (next day or later) management of the NAS. The AP is developed by the PT after collaboration with the same personnel as the OP.

Trigger: A specific event/critical decision window (CDW) that causes a specific traffic management initiative (TMI)/time‐based management (TBM) operation to be implemented or modified.

A trigger is for planning purposes and is intended to reduce coordination when implementing or modifying the specified TMI/TBM operation.

All en route facilities impacted by the TMI/TBM operation must be contacted prior to implementing the TMI/TBM operation in response to the trigger.

En route facilities must relay TMIs/TBM operations to affected terminal facilities within its area of jurisdiction.

All triggers will be identified by “IF, THEN” clauses in the OP.

The OP will specify:

Terminal constraints: facilities where delays are expected to be 15 minutes or greater.

En route constraints: facilities where expanded miles-in-trail, deviations, and tactical reroutes may be required.

The PT provides operational same day analysis and support, advanced planning, and historical review to provide greater predictability and reliability in managing NAS performance. Responsibilities include:

Deliver a detailed Advance Plan (AP) to identify the next day's potential NAS impacts and TMIs/TBM operations as well as multi-day outlooks containing potential constraints and initiatives.

Identify aviation system efficiencies while using historical NAS performance data and trends to develop effective advance planning strategies.

Provide historical data analysis, demand projections, and potential mitigation strategies for future constraint management.

Use post‐event analysis and lessons learned to define and implement future strategies and operational triggers based on past performance and outcomes.

Gather and share timely and continuous feedback with operational personnel to provide increased data, weather knowledge, and tools for analytical use and planning.

The ATCSCC PT must:

Lead the development of the OP.

Formulate the OP through coordination with PT members using the OP timeline.

Brief the National Operations Manager (NOM), National Traffic Management Officer (NTMO), and other ATCSCC operational elements on the OP.

Post the OP on the ATCSCC website and issue as a numbered advisory.

Document agreed-upon triggers in the OP.

Maintain the PW.

The NOM must:

Direct the NTMO, ATCSCC operational units, and personnel on implementation of the OP.

Coordinate with and provide direction to FAA facilities on implementation of the OP.

The District TMO or designee must:

Provide input to the AP.

Participate via the PW in formulation and development of the OP when stated in the previous OP, when requested later by the ATCSCC, or when issues within the facility warrant participation.

Provide input on:

Equipment outages having an operational impact;

Internal initiatives;

Terminal constraints;

Route closure/recovery information;

Anticipated use of airborne rerouting;

Anticipated use of TBM;

Anticipated TMI; or

Other issues which may impact operations (i.e., staffing, special events, etc.). (See FIG 18-21-1, Operational Planning Webinar Checklist.)

Brief and direct facility Operational Supervisors, Traffic Management Supervisors, Traffic Management Units, and operational personnel on the implementation of the OP and gather additional information for the next conference.

Coordinate with and provide direction to underlying facilities on the implementation of the OP.

Monitor and assess the OP, notifying the ATCSCC of problems that may impact the OP.

Provide operational feedback for use in post-operational evaluation of the OP.

Terminal Facility Management must:

When notified by the District TMO or designee, or ATCSCC PT, participate in the PW.

Brief and direct facility operational personnel on actions required by the OP.

Monitor and assess the OP, notifying the ATCSCC of problems that may impact the OP.

Participate in the AP when necessary or notified.

The PW participants are FAA and customer weather forecasters, FAA District TMO or designee, other FAA field facility management personnel, airline strategic planners, ATCSCC personnel, international facilities, and military and general aviation system customers.

The ATCSCC is delegated the authority to direct the operation of the PW for the FAA.

The ATCSCC will notify those FAA facilities required to participate as part of the PW.

Military, international, and general aviation entities will be included as necessary.

The PT collaborates on the formation of the OP. The OP is continuously evaluated, and updated or amended, as necessary.

Weather information provided by National Weather Service meteorologists will be used in the conference. If there is a collaborative product of weather information, developed by both government and industry meteorologists, it will be used as the primary source for the PW.

OP timeline (all times local/Eastern): The OP Timeline provides a continuous process and method for group decision-making and collaboration in dealing with system constraints. Modification of the timeline, participation, and scheduling is done at the discretion of the PT and as directed by the ATCSCC. The PT conducts and facilitates the PW with FAA field facilities and NAS customers beginning at 7:15 a.m. Eastern time, then every 2 hours, unless otherwise coordinated, with the last Webinar usually being conducted at 9:15 p.m. Webinar duration should be less than 30 minutes. Discuss recurring issues (e.g., VIP movements, overnight cargo operations) as necessary.