Understanding Role of Flight Data Processing Across NAS

Understanding Role of Flight Data Processing Across NAS Operational Domains Elvan Mc. Millen August 24, 1999 Organization: F 062 Project: 02991204 -O 5

2 Context l Presentations such as this can be used: - For developing an understanding of the current - operations in order to establish a baseline As a tool to derive the impact of known alternatives such as ICAO flight plan processing, and flight objects on baseline processes to develop future requirements As a focal point for discussion to identify additional issues that may become requirements drivers To draw the boundaries of FDP functionality

3 Domestic Flight Plan Filing Weather and ATC briefings, NOTAMs Private Weather Service Flight Plans Weather Briefings NOTAMS from FDC Flight Plans GA Pilot Airline Operation Centers (AOC) Weather and ATC briefings, NOTAMs Direct User Access Terminal Service (DUATS) Flight Plans ARTCC responsible for the departure airport Error Indication Automated Flight Service Station (AFSS) Host and Oceanic Computer Flight Plans System Replacement (HOCSR) Error Indication Flight Plans Military Pilot NOTAMS from FDC Controllers Flight Plans Error Indication Weather and ATC briefings, NOTAMs Flight Plans Flight Data Processor (FDP) NOTAMs Flight Data Center (Wash, DC) HOCSR FDP: Performs format and logic checks Determines if any PARs or PDRs are applicable Performs route conversion and posting determination Performs initial fix time calculations Military Operations Flight Plans HOCSR FDP Neighboring ARTCCs Bulk Store Files Flight Plan Info ETMS Flight Plans ARTS TRACONs

5 Departure Phase of Flight ARTCC TRACON ETMS HOCSR FDP: Sends flight information to ARTS and assigns transponder code ~30 min prior to departure En Route Sector(s) Flight Strip Departure, Beacon Code Info HOCSR FDP Sent when the SSR detects the transmission from aircraft's transponder Departure Message Flight Strip Printed ~30 minutes prior to departure Clearance Delivery Predeparture Clearance W/S Flight Strip Info Departure Clearance Delivery Controller: Checks facility directives to verify the route of flight and altitude requested Restricts altitude if necessary Delivers clearance: "as filed" or modified, includes altitude, departure control frequency, transponder code, any changes Departure Airport Tower Departure Control ARTS Flight Plan Info Flight Strip Printed again when the departure message is received Track Info Departure Controller: Radar identifies the aircraft Advises pilot of the radar identification Verifies altitude Vectors aircraft to the route of flight Vectoring Instructions Marked-up Flight Strip Departure Clearance Taxi Clearance Marked-up Flight Strip Local Control Takeoff Clearance (w/heading) Marked-up Flight Strip Ground Controller: Issues taxi instructions Coordinates active runway crossing with the local controller to prevent runway incursion Ground Control Local Controller: Ensures runway separation with other arrivals and departures Assigns heading that keeps the aircraft within the departure airspace Delivers take off clearance Instructs pilot to contact departure control (at the frequency given by clearance delivery)

7 En Route Phase of Flight TRACON Neighboring ARTCC Departure Control Low Altitude Sector (Departures) Departure Controller: Vectors aircraft to en route airspace Initiates handoff to en route sector High Altitude Sector En Route Controller: Accepts handoff from low sector Provides separation Gives altitude clearances Hands off to next sector En Route Controller: Accepts handoff from departure Provides separation Gives altitude clearances Hands off to next sector Handoff Initiate Handoff Accepted Handoff Indication Flight plans are forwarded ~30 minutes prior to boundary crossings. Interfacility handoffs take place in accordance with facility directives Printed ~30 minutes prior to sector entry Accept Handoff Flight Strips ARTS Vectoring Instructions Altitude Clearances Initiate Handoff Accept Handoff Track, Amendment, Boundary Crossing Information HOCSR Position report processing, fix time updates, association checking Flight Strips Low Altitude Sector (Arrivals) Altitude Clearances En Route Controller: Accepts handoff from high sector Provides separation Gives altitude clearances, Prepares to handoff to arrival Traffic Information Handoff Traffic Management Advisor Center Weather Service Unit ETMS Traffic Situation Display Traffic Information ATCSCC Coordination Weather Information Weather Data Traffic Management Unit WARP

9 Arrival Phase of Flight TRACON ARTCC TMU Metering Functions Arrival Info Metering Lists HOCSR To achieve metering delays En Route Controller: Provides separation and vectors aircraft to coordination fix Achieves metering objectives and spacing with speed restrictions Hands off to arrival controller Ground Controller: Issues taxi instructions Coordinates active runway crossing with the local controller to prevent runway incursion Arrival Airport Tower ARTS Flight Strip Printed ~30 minutes prior to entry Flight Strip Handoff Vectoring Instructions Speed Adjustments Speed Restrictions Low Altitude Sector Ground Control Arrival/Final Controller: Radar identifies the aircraft Provides radar separation Descends aircraft while coordinating with departure control Sequences aircraft, coordinating with other arrival controllers for ILS approach Ensures spacing using speed adjustment instructions Advises pilot to monitor local control Flight Plan Information Flight Strip Speed Restrictions Arrival/Final Control Track Info Beacon Terminated FDP Includes sequence of a/c, assigned time of arrival, delay information ETMS For spacing Taxi Clearance Landing Clearance Local Controller: Ensures runway separation with other arrivals and departures Redirects if necessary Clears aircraft for landing Advises pilot to contact ground control Local Control Coordinate For descent clearances Departure Control Coordinate For sequencing Arrival Control

11 IFR Flight Example l Reference: Fundamentals of ATC, M. S. Nolan, Chapter 10, Operation in the NAS l Three flight legs From Lafayette, IN to Champaign, IL From Champaign, IL to Indianapolis, IN From Indianapolis, IN to Lafayette, IN l Characterization of the flight from Lafayette to Champaign No FDIO equipment in the departure tower and terminal facilities Arrival airport is in neighboring ARTCC’s airspace Flight travels through terminal airspace only -

12 IFR Flight Example Flight Plan Filing Terre Haute FSS Specialist Pilot ZAU ARTCC AFSS Computer FDP ZID ARTCC LAF Tower Purdue Low Sector FDP Flight Data Control Information Request Weather Briefing Flight Plan (1 st leg) Flight Plan (2 nd leg) Flight Plan (3 rd leg) Flight Plan Entry Flight Plan (1 st and 3 rd leg) Flight Plan (2 nd leg) Error Indication Printed 30 minutes prior to proposed departure time. Transponder code is allocated at this time Corrected Flight Plan Flight Strip Flight Information (verbal)

13 IFR Flight Example Lafayette to Champaign - Departure LAF Tower Pilot Ground Control Local Control LAF Terminal CMI TRACON Flight Data Controller Approach/ Departure East Arrival Position Contact (ready to taxi) Departure Clearance Taxi Instructions Flight Information (verbal) Flight Strip (manually updated) For coordination fix, altitude, and use of route Coordination (verbal) Approved

14 IFR Flight Example Lafayette to Champaign - Departure (cont’d) LAF Tower Pilot ZID ARTCC LAF Terminal Approach/ Departure Local Control Purdue Low Sector ZAU ARTCC FDP CMI TRACON Flight Data Controller ARTS Request to depart a/c DM message Includes Beacon Code Flight Information Contact (ready to take off) Coordination Approved Takeoff Clearance (heading) Contact Departure Contact Vectoring instructions Contact Champaign Arrival For airspace usage Flight Strip

15 IFR Flight Example Lafayette to Champaign - Arrival CMI TRACON East Arrival Control Pilot CMI Tower ARTS Local Control ZAU ARTCC Ground Control FDP Contact Radar Contact Advisory Altitude Clearance Vectoring Instructions Speed Restrictions ILS Approach Clearance Contains initial runway assignment Informs pilot of distance to final approach fix, heading for intercepting ILS course, altitude to maintain, and the clearance for the runway Monitor Local Control Frequency Final Approach Fix Crossing Report Vectoring Instructions Landing Clearance Contact Ground Control Drop Flight Beacon Terminated For active runway crossing Contact Coordinate Taxi Clearance Drop Flight

16 IFR Flight Example - Champaign to Indianapolis l Characterization of the flight from Champaign to Indianapolis - Both facilities are FDIO equipped - Arrival airport is a high activity airport in neighboring - ARTCC’s airspace Flight travels through terminal and en route airspace

17 IFR Flight Example Champaign to Indianapolis - Departure ZAU ARTCC Pilot FDP ARTS CMI Tower CMI TRACON Clearance Delivery Ground Control Local Control Flight Information Flight Strip Contact (ready to depart) Departure Clearance Contains restricted altitude, transponder code, departure frequency Flight Strip (manually updated) Coordination (verbal) Approved Contact (ready to taxi) Taxi Clearance Flight Strip Contact (ready to take off) Take off Clearance Departure Message Heading Instructions Contact Departure Control For active runway crossing, in some facilities

18 IFR Flight Example Champaign to Indianapolis - Automated Handoff ZAU ARTCC Pilot HOCSR CMI TRACON Departure Control ARTS IND TRACON ZID ARTCC HOCSR Terre Haute Low Sector Flight Information Flight Strip Contact Radar Contact Advisory Altitude Clearance Flight Information Initiate Handoff Flight Strip Handoff Indication Handoff Accepted Contact Indianapolis ARTCC Altitude Clearances Altimeter Setting ARTS Arrival Control

19 IFR Flight Example Champaign to Indianapolis - Arrival IND TRACON ZID ARTCC Terre Haute Low Sector Pilot East Arrival Control West Arrival Control FDP IND Tower Departure Control Local Control Initiate Handoff Accepted Altitude Clearance Contact Indianapolis Arrival Descent to 11, 000 ft Contact Coordination (verbal) Approved Altitude Clearance Vectoring Instructions Coordination (verbal) Approved Speed Adjustments ILS Approach Clearance For spacing Monitor Local Frequency Final Approach Fix Crossing Report Landing Clearance Contact Ground Control Contact Taxi Clearance For sequencing For descent from 10, 000 ft to 7, 000 ft Ground Control

20 IFR Flight Example - Champaign to Indianapolis l Characterization of the flight from Indianapolis to Lafayette - No FDIO equipment in the arrival tower and terminal - facilities Flight travels through airspace within a single ARTCC’s jurisdiction Flight travels through terminal airspace only

21 IFR Flight Example Indianapolis to Lafayette - Departure ZID ARTCC Pilot IND TRACON FDP IND Tower Flight Data/ Clearance Delivery ARTS Ground Control LAF Terminal Local Control Approach Flight Information Flight Strip Contact (ready to depart) Departure Clearance (altitude restriction, transponder code, departure frequency) Flight Information (verbal) Coordination (verbal) Approved (with restriction) Markup Strip Contact (ready to taxi) Marked up Strip Taxi Clearance Marked up Strip Contact (ready to take off) Take off Clearance Contact Departure Control For entry point

22 IFR Flight Example Indianapolis to Lafayette - Arrival IND TRACON LAF Terminal Departure Control Pilot Approach Contact Radar Identification Vectoring Instructions (heading, altitude) Also indicates termination of radar service Contact Lafayette Approach Contact Clearance (to pass coordination fix) Clearance (for ILS landing) Monitor Tower Frequency Landing Clearance Contact Ground Control Contact Taxi Clearance LAF Tower Local Control Ground Control