FEA/FCA Quick Reference Guide Back Cover Reference Material 31March2005 Prepared by FCA/Reroutes Work Group
Contents Forward FEAs/FCAs show areas where the traffic flow should be evaluated or where initiatives should be taken due to severe weather or volume constraints. A Flow Evaluation Area (FEA)is a two-dimensional line or three-dimensional volume of airspace, along with filters and time boundaries, used to identify flights associated with a potential (or actual) constraint. FEAs can be built by Traffic Management Coordinators (TMCs) at Traffic Management Units (TMUs), Traffic Management Specialists (TMSs) at the Air Traffic Control System Command Center (ATCSCC), or by flight dispatchers at various flight operations centers (using CCSD). A Flow Constrained Area (FCA)is a two-dimensional line or three-dimensional volume of airspace, along with filters and time boundaries, used to identify flights subject to an actual constraint. FCAs are built by the ATCSCC and require a traffic management initiative (TMI); for example, a reroute. This document offers some brief examples of how FEAs and FCAs are actually being used in the field today. The goal of this document is to share information to encourage further use of FEAs/FCAs and promote new ideas.
ORD FEA to monitor arrivals from CZY ORD FEA to monitor arrivals from ZDV Internal/Private FEA to monitor ORD Depts • 1. Restrictions/Miles In Trail • Use FEAs to justify and manage TMIs • ATCSCC requests and monitors FEAs to help determine MIT need • ATCSCC builds FEAs or FCAs when issuing TMI • Example: ATCSCC NTML Log Entries: Restriction being monitored/supported via FEAs • 02/16/2004 00:00 22 Log Entry 0106 • PHX 2324 RSTN. CHECKED WITH ZAB ON PROGRESS AND ZAB INFORMS RSTN IS WORKING SUFFICIENTLY FOR THEM. WILL CONTINUE TO MONITOR WITH FEA. • 01/22/2004 00:00 24 Area Log 2344 • ZFW CALLED BACK AND ADVISED THAT THE SECTOR IS NOW WELL OVER CAP OF 13 FOR 30 CONSECUTIVE MINUTES AND THEY ARE UNABLE TO COME OFF THE RESTN. A FEA IN ADDITION TO THE MAP SUPPORTS THE MIT RESTRICTION. IAH ADVISED. • Example: • Saved ORD arrival FEAs to determine when to pass back MIT restrictions.
Example: • FEA built to monitor flights affected by an area of Wx, and which might need reroutes. • 2. Weather Avoidance • Use FEAs to help manage weather constraint events. • Draw FEA around Wx area • Review FEA Dynamic List and Timeline to determine impact and necessary actions • Example: These NTML log entries show FEAs led to successful collaboration to resolve Wx problems • 05/22/2004 00:00 Sever Wx Area Log 2115 • ZDV CALLED TO CONFERENCE ZMP REGARDING FEA ZDVWX. ZMP TACTICALLY ROUTED SIX FLIGHTS SOUTH TO GLD OR HLC TO AVOID WEATHER NORTH OF DEN. - LNK: ZDV/ZMP • 05/22/2004 00:00 Sever Wx Area Log 1414 • Shift Summary: DAY SHIFT- DUE TO UNEXPECTED ZKC WX. ALSO CREATED A PUBLIC FEA TO ADDRESS ANY OTHER TRAFFIC ON J80 REQUESTING THAT THEY FILE SOUTH OF J80. THE USERS DID A GOOD JOB OF TAKING APPROPRIATE ACTIONS TO AVOID THE CONSTRAINED AREA IDENTIFIED IN THE FEA.
2. Weather (cont.) • FEAs adjacent to Weather Constraint • Build FEAs adjacent to severe Wx areas to determine how deviating flights will affect traffic flow/volume in sectors just adjacent to the weather. • Example: See figure to the right. • FCA first built around actual Wx to show flights that needed to be moved. • Straight line FEAs then drawn on the north and south side of the Wx to evaluate volume impact in those adjacent sectors. • Example: • Adjacent sector impact FEAs
Area of Wx problems • 2. Weather (cont.) • UPT Caution • When routing traffic around an area of Wx, consider when and how the traffic merges back into a needed flow • Example: See figure to the right. • In the example at right, UPT led to an unorganized, random route filing for ORD Arrivals. Arrival routes crossed each other and ORD departure flows. • A better solution may have been to UPT the traffic to a specific fix, then assign a preferred arrival route from there. Example: UPT Caution An area of crossing/ conflicting traffic for rerouted flights.
Example: • Chokepoint route monitoring with FCA. • 3. Route Monitoring • Use FEAs to help monitor route compliance and route changes • Process: • Draw an FEA. • Monitor the FEA to ensure flights conform to required routing • Example: Chokepoint FCA • ATCSCC draws FCA line to include J584, J70, J16 in ZOB airspace. • FCA is filtered for JFK & EWR arrivals excluding ZOB/ZID/ZAU departures • FCA is examined by numbers list and bar graph to determine peaks and valleys • The peak issues are reviewed on Planning Telcons to agree on MIT times • Note: There is a misconception that all flights to EWR/JFK must be on chokepoint routes. Chokepoints only apply to traffic transiting ZOB. Flights on routes that already miss ZOB do not have to be moved. Chokepoint FCA line Timeline shows how many flights are due to cross the Chokepoint FCA line in each 15-minute time segment. Bar chart also shows how many active (red) and proposed (yellow) flights are due to cross the Chokepoint FCA line in each 15-minute time segment.
Example: All inclusive FEA at ZOB to capture traffic needing reroutes to DFW/IAH • 3. Route Monitoring (cont.) • FEAs to help manage reroute requirements • Use FEAs and their associated dynamic lists to ensure flights are on the correct route when leaving your Center’s airspace. • Example: See figure to the right from ZOB. • Draw a quick FEA is over the ARTCC’s entire airspace or at the boundary • Filter the FEA for traffic destined to restricted airports to ensure they all have proper new routes
ZOB CXR Arrival FEAs 8 1 7 2 6 3 5 • 4. Traffic Flow Monitoring • Use FEAs for basic traffic flow/volume monitoring • Process: • FEAs present dynamic picture of given flows of traffic for TMUs to monitor • ATC/Traffic Mgt personnel adjust flows strategically with planned initiatives • Example: Saved FEAs at ZOB recalled daily to monitor traffic flows into local airports or along the busy NY – ORD corridor. • The FEAs at right (#s 6, 7, 8) are recalled to monitor CLE arrivals over CXR. • Note: Multiple canned FEAs can lead to a problem of clutter on the TSD if not carefully managed. • Example: • ZOB daily FEA to monitor CLE arrivals over CXR
5. Arrival/Departure Flow Management • Use FEAs to monitor and manage departure flows and arrival flows • Process: • Build FEAs to capture arrival or departure flows • Use FEA timeline data to determine if/when action may be necessary • Example: • ZOB FEAs at ZOB to monitor arrival flow into ORD. • TMC can determine from FEA timeline data for the three arrival fixes where or when action may be taken to restrict or balance traffic. Example: ZOB ORD arrival flow FEAs
5. Arrival/Departure Flow Mgt. (cont.) • Example: Dynamic Sector Flow Monitoring for LAX Arrivals • FEAs built to dynamically monitor LAX arrival traffic from Mexico over two fixes. • FEAs for both flows allows TMCs to compare projected sector volume, both airborne and scheduled, and determine dynamically which sector is the best fit to handle arrivals at any given time. Example: Two FEAs built to assist in real-time route selection LAX Arrivals from Mexico
5. Arrival/Departure Flow Mgt. (cont.) • Example: Flight Operations Centers may also build FEAs with CCSD to monitor Arrivals or Departures. • Below is an FEA built by an airline to monitor arrivals into MSP from the east. • Ops Center personnel then monitor dynamic lists/timelines (see figure at right) to determine if proactive flight plan changes can mitigate potential problems. Example: CCSD Dynamic FEA Flight List
Example: ZMP FEA at Crypts MOA • 6. Military SUA AirspaceManagement • Some TMUs are experimenting with FEAs to manage SUAs • Process: • Build FEA by selecting MOA as a NAS element • Use FEA timelines/flight lists to monitor and coordinate • Example: • ZMP FEA built around Crypts\ • Timelines and lists then used to coordinate dynamic sharing of airspace when possible FEA Timeline can be monitored to show periods of greatest impact FEA Flight List for flights intersecting the FEA can be pulled for any airport.
Example: FEAs created with CCSD to monitor MOA and restricted areas • 6. MOA Mgt. (cont.) • Example: NAS Customers also build FEAs with CCSD to monitor SUA • In the “Maps” Menu, select “Overlays” to display MOAs, etc. • Then create an FEA over the SUA • Monitor the flights affected • Take appropriate flight planning action
7. Special Events Handling • Use FEAs to plan and manage air traffic associated with various seasonal or special events • Process: • Build FEA • Use FEA timelines/flight lists to monitor and coordinate routes, restrictions, etc. • Examples: • FEAs/FCAs for Snowbird Traffic: TMUs and the ATCSCC use FEAs/FCAs to monitor traffic to and from Florida during the busy winter season (see figure at right). • FEAs for Ski Country Traffic: FEAs/FCAs used to help manage ski country traffic flows in the winter. • FEAs for Sporting Events or ‘Fly-Ins’: To monitor and manage traffic inbound to small airports for events such as the Masters Golf Tournament or NASCAR races. • FEAs to manage equipment-related issues: To help manage traffic around equipment issues. Example: Snowbird6 FEA/FCA ‘Snowbird6 FEA to route traffic away from busier east coast area of FL.
8. How to Build an FEA • Building an FEA with TSD • Step 1: Open the Create FEA/FCA Dialog Box • Select <FEA/FCA> from TSD header bar • Select < Create FEA/FCA > from the drop down menu.
8. Building an FEA with TSD (cont) • Step 2: Use the Create FEA/FCA Dialog Box to define desired FEA/FCA Parameters • Select < Polygon, Circle or NAS Element > to draw the FEA/FCA. • Select a short, descriptive NAME for your FEA (FCAs named automatically) • Enter Start and End Time for the FEA/FCA • Enter ALTITUDE RANGE for the FEA/FCA • Enter MOVING PARAMETERS if FEA/FCA will be moving • Enter Domain: - Private: Your own use only - Shared: To explicitly share with other TMUs - Public: ATCSCC to share with all TSD/CCSDs) • Type: Preset to FEA unless you are an ATCSCC user • Select a Reason from the drop down menu • Select an easily viewable Color for the FEA/FCA • Undo will delete the last line drawn • Erase will erase the entire drawn FEA/FCA
8. Building an FEA with TSD (cont) • Step 3: Draw the FEA/FCA you have defined • Click two points or more to draw a line or polygon. • For a Circle: Click <Circle>, then click and drag, or enter Circle Parameters (Lat/Long) • For a NAS element: Click NAS, then select the type of NAS element you want for the FEA/FCA from the Category: drop down menu (e.g., Fix, TRACON, Sector, SUA, etc.). Then, select the Name of the element you want from the drop down that will appear (or, type in the name of the specific NAS element). • Step 4: Apply the FEA/FCA you have defined/drawn • Press < OK > to apply the function and close the dialog box. • Press < Apply > to apply the function and allow the box to remain open.
8. Building an FEA with CCSD • Building an FEA with CCSD • Step 1: Open the Create FEA/FCA Dialog Box • Select <FEA/FCA> from CCSD header bar • Select < Create FEA/FCA > from the drop down menu. • Step 2: Name your FEA(Do not use “CA” in the name.)
8. Building an FEA with CCSD • Step 3: Create filters to select flights of interest for your FEA • Click <Fliters> at the top of the Create FEA box to open Primary or Secondary Filter Boxes. • Create filters in the same manner as described below in Tab 9 (using radio buttons plus Arrivals/Departures and other filters desired for your FEA). • Step 4: Save the Information and Close the Filter Box • Click < OK > to save the FEA information • Then, click < Close the Window > 1 2 5 3 4
Point and click until you have completed your FEA. • 8. Building an FEA with CCSD • Step 5: Draw and Save the FEA • Draw the FEA on the CCSD using point and click steps until you have completed the FEA. • Then Click < OK > at the bottom of the Create FEA box to save the FEA. • You will receive a Confirmation notice, which you subsequently close.
9. How to Filter an FEA/FCA • Using Primary and Secondary Filters • Assume an FEA is built using ZHUIAH (I90) TRACON as a NAS Element. • Step 1: Use the Primary Filters Tab to select airports, times and other filters to apply to the FEA/FCA. • Examples: • The Primary filter could include selected airports • To exclude arrivals: Set Departure/Arrival Time Range to DEPARTURE and the time to correspond with the FEA time. • If only IAH and HOU departures were needed, IAH and HOU would be entered in the Departs from any of: line. • If IAH and HOU were to be excluded, click the down arrow button at the end of that line to change the choice to Departs from none of:. • NOTE: If a Secondary Filter is to be used, the Primary filter must encompass the traffic to be displayed in the Secondary Filter. Traffic not included in the Primary Filter cannot be displayed by the Secondary Filter.
9. How to Filter an FEA/FCA (cont) • Step 2: Use the Secondary Filters Tab to filter for each Departure Gate • The Departure fixes that correspond with the gate would be entered in the Traverses any of: line. • Each gate would have a Secondary Filter with the departure fixes listed in the Traverses any of: line
9. How to Filter an FEA/FCA (cont) • Step 3: Use the filtered FEA to pull Timelines and Lists of those flights you desire to see. • Examining the FEA would bring up a Timeline that shows the number of flights proposed to depart all of the airports in the I90 airspace for the time range selected. • From that Timeline a Dynamic List could be displayed that show the route of flights for the selected filter(s).
1. Choose Select FEA/FCA 10. How to Save and Recall an FEA/FCA There are many times when information from an FEA/FCA is needed on a recurring basis. It is an easy process to save and recall FEA/FCAs. Saving an FEA/FCA Step 1: Choose SelectFEA/FCA from the FEA/FCA Menu Step 2: Select the number of the FEA/FCA to be saved 2. Select FEA/FCA to be saved
10. How to Save and Recall an FEA/FCA Step 3: Click on Save FEA/FCA File from the File menu Step 4: Enter the name of the FEA/FCA to be saved if other than the current name (the current name will show up in the Name window). Step 5: Then Click < OK >. 3. Select Save FEA/FCA File from the File menu 4. Enter the name of the FEA/FCA
10. How to Save and Recall an FEA/FCA Recalling an FEA/FCA Step 1: Choose RecallFEA/FCAFile from the FEA/FCA Menu Step 2: Enter the name of the FEA/FCA file to be recalled Step 3: Click OK . 1. Choose Recall FEA/FCA File 2. Select or Enter name of FEA/FCA to be recalled