Embed Size (px)
DESCRIPTION
Understanding Role of Flight Data Processing Across NAS Operational Domains. Elvan McMillen August 24, 1999. Organization: F062 Project: 02991204-O5. Context. Presentations such as this can be used: For developing an understanding of the current operations in order to establish a baseline - PowerPoint PPT Presentation
Citation preview
Understanding Role of Flight Data Processing Across NAS Operational
Domains
Elvan McMillen
August 24, 1999
Organization: F062Project: 02991204-O5
2
Context
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
Flight Plan Info
Domestic Flight Plan Filing
Flight Plans
ErrorIndication
Flight Plans
HOCSR FDP:Performs format and logic checksDetermines if any PARs or PDRs are applicablePerforms route conversion and posting determinationPerforms initial fix time calculations
Flight Plans
Flight Plans
Flight Plans
Weather and ATC briefings,NOTAMs
Flight Plans
Weather Briefings
Flight Plans
Flight Plans
ErrorIndication
Weather and ATC briefings,NOTAMs
Flight Plans
Flight Plans
ErrorIndication
Weather and ATC briefings,NOTAMs
NOTAMs
NOTAMS from FDC
NOTAMS from FDC
Flight Plans
Direct User AccessTerminal Service
(DUATS)
Controllers
Bulk Store Files
Airline Pilot
Military Pilot
ARTCC responsible for the departure airport
Host and Oceanic Computer
System Replacement (HOCSR)
Flight Data Processor (FDP)
AutomatedFlight
Service Station(AFSS)
PrivateWeather Service
Flight Data Center
(Wash, DC)
GA Pilot
Neighboring ARTCCs
HOCSR
FDP
Airline Operation Centers (AOC)
MilitaryOperations
ETMS
ARTS
TRACONs
5
Flight Plan Info
HOCSR FDP:Sends flight information
to ARTS and assigns transponder code ~30 min prior to departure
Departure Phase of Flight
Marked-up Flight Strip
Marked-up Flight Strip
Marked-up Flight Strip
Clearance Delivery Controller:Checks facility directives to verify the route of flight and altitude requestedRestricts altitude if necessaryDelivers clearance: "as filed" or modified, includes altitude, departure control frequency, transponder code, any changes
Departure Clearance
Ground Controller:Issues taxi instructionsCoordinates active runway crossing with the local controller to prevent runway incursion
TaxiClearance
Departure Controller:Radar identifies the aircraftAdvises pilot of the radar identificationVerifies altitudeVectors aircraft to the route of flight
VectoringInstructions
Flight Strip Info
Departure Clearance
Departure Airport Tower
En Route Sector(s)
ARTCC TRACON
HOCSR FDP ARTS
Clearance Delivery
Ground Control
Local Control
Departure Control
Predeparture Clearance W/S
ETMS
Departure, Beacon
Code Info Track Info
Printed again when the departure
message is received
Local Controller:Ensures runway separation with other arrivals and departuresAssigns heading that keeps the aircraft within the departure airspaceDelivers take off clearanceInstructs pilot to contact departure control (at the frequency given by clearance delivery)
Takeoff Clearance
(w/heading)
Flight Strip
Flight Strip
Flight Strip
Printed ~30 minutes prior to departure
Sent when the SSR detects the transmission from aircraft's transponder
Departure Message
7
High Altitude Sector
ARTCC Low Altitude Sector (Departures)
Traffic Management Unit
Low Altitude Sector (Arrivals)
ATCSCC
HOCSR
Departure Control
TRACON
ARTS ETMS
WARP
Neighboring ARTCC
Traffic Management
Advisor
Traffic Situation Display
Center Weather
Service Unit
InitiateHandoff
InitiateHandoff
Handoff Indication
En Route Phase of Flight
Altitude Clearances
Handoff
Handoff
Altitude Clearances
Traffic Information
Traffic Information
En Route Controller:Accepts handoff from departureProvides separationGives altitude clearancesHands off to next sector
En Route Controller:Accepts handoff from low sectorProvides separationGives altitude clearancesHands off to next sector
En Route Controller:Accepts handoff from high sectorProvides separationGives altitude clearances,Prepares to handoff to arrival
Flight Strips
Flight Strips
Printed ~30 minutes prior to sector entry
Coordination
Weather Information
Weather Data
Handoff Accepted
Accept Handoff
Accept Handoff
Departure Controller:Vectors aircraft toen route airspaceInitiates handoff toen route sector
VectoringInstructions
Track, Amendment, Boundary Crossing Information
Flight plans are forwarded ~30 minutes prior to boundary crossings. Interfacility handoffs take place in accordance with facility directives
Position report processing, fix time
updates, association checking
9
Arrival Phase of Flight
Handoff
Vectoring Instructions
Arrival/Final Controller:Radar identifies the aircraftProvides radar separationDescends aircraft while coordinating with departure controlSequences aircraft, coordinatingwith other arrival controllers for ILS approachEnsures spacing using speed adjustment instructionsAdvises pilot to monitor local control
LandingClearance
Local Controller:Ensures runway separation with other arrivals and departuresRedirects if necessaryClears aircraft for landingAdvises pilot to contact ground control
Coordinate
For sequencing
Speed Adjustments
For spacing
Coordinate
For descent
clearances
En Route Controller:Provides separation and vectors aircraft to coordination fixAchieves metering objectives and spacing with speed restrictionsHands off to arrival controller
MeteringLists
Includes sequence of a/c, assigned
time of arrival, delay information
Metering
Functions
To achieve metering
delays
Speed Restrictions
Beacon Terminated
Arrival Info
Track Info
Flight Strip
Flight Plan Information
Arrival Airport Tower
HOCSR
FDP
ARTCC TRACON
Low Altitude Sector
Arrival/Final Control
Departure ControlLocal Control
Ground Control
ARTS
TMU
Arrival Control
ETMS
Speed Restrictions
Ground Controller:Issues taxi instructionsCoordinates active runway crossing with the local controller to prevent runway incursion
TaxiClearance
Flight Strip
Flight Strip
Printed ~30 minutes prior to entry
11
IFR Flight Example
Reference: Fundamentals of ATC, M.S. Nolan, Chapter 10, Operation in the NAS
Three flight legs
- From Lafayette, IN to Champaign, IL
- From Champaign, IL to Indianapolis, IN
- From Indianapolis, IN to Lafayette, IN 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 ExampleFlight Plan Filing
Terre Haute
Pilot Flight Data Control
FDP
ZID ARTCC LAF Tower
AFSS Computer
ZAU ARTCC
FDPPurdue
Low SectorFSS
Specialist
InformationRequest
Weather Briefing
Flight Plan(1st leg)
Flight Plan Entry
Flight Plan (2nd leg)
Flight Plan (1st and 3rd leg)
Error Indication
Error Indication
Corrected Flight Plan
Corrected Flight Plan
Flight Plan(2nd leg)
Flight Plan(3rd leg)
Flight StripFlight
Information (verbal)
Printed 30 minutes prior to proposed departure time. Transponder code is allocated at this time
13
IFR Flight ExampleLafayette to Champaign - Departure
Contact (ready to taxi)
Departure Clearance
Taxi Instructions
Flight Information
(verbal)Flight Strip (manually
updated)
Pilot Local Control
LAF Tower
Ground Control
LAF Terminal
Approach/Departure
East ArrivalPosition
CMI TRACON
Flight Data Controller
Coordination (verbal)
Coordination (verbal)
Approved
Approved
For coordination fix, altitude, and use of route
14
IFR Flight Example Lafayette to Champaign - Departure (cont’d)
Contact (ready to take
off)
Takeoff Clearance (heading)
Contact Departure
Contact
Vectoring instructions
Contact Champaign Arrival
Pilot Local Control
LAF Tower LAF Terminal
ARTS
CMI TRACON
Approach/Departure
Flight Data Controller
FDP
ZID ARTCC ZAU ARTCC
Purdue Low Sector
FDP
Request to depart a/c
DM message
Coordination
Approved
For airspace usage
Flight Information
Flight Information
Includes Beacon Code
Flight Strip
15
IFR Flight Example Lafayette to Champaign - Arrival
Altitude Clearance
Vectoring Instructions
Speed Restrictions
Monitor Local Control Frequency
Vectoring Instructions
Landing Clearance
Contact Ground Control
Contact
Taxi Clearance
Local Control
CMI TowerCMI TRACON
East Arrival Control Ground ControlARTSPilot FDP
ZAU ARTCC
Drop Flight
Drop Flight
Beacon Terminated
Coordinate
For active runway crossing
Contact
Radar Contact Advisory Contains
initial runway assignment
Final Approach Fix Crossing Report
ILS Approach Clearance
Informs pilot of distance to final approach fix, heading for intercepting ILS course, altitude to maintain, and the clearance for the runway
16
IFR Flight Example - Champaign to Indianapolis
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 ExampleChampaign to Indianapolis - Departure
Pilot Local Control
CMI Tower
Ground ControlARTS
CMI TRACONZAU ARTCC
FDP Clearance Delivery
Flight Information
Flight Strip
Flight Strip (manually updated)
Contact (ready to taxi)
Taxi Clearance
Contact (ready to take off)
Take off Clearance
Heading Instructions
Contact Departure Control
Departure Message
Flight Strip
Approved
Coordination (verbal) For active
runway crossing, in some facilities
Contact (ready to depart)
Departure Clearance
Contains restricted altitude, transponder code, departure frequency
18
IFR Flight ExampleChampaign to Indianapolis - Automated Handoff
Flight Information
Flight Strip
Contact
Radar Contact Advisory
Altitude Clearance
Initiate Handoff
Initiate Handoff
Handoff Indication
Handoff Indication
Handoff Accepted
Handoff Accepted
Handoff Accepted
Handoff Accepted
Altitude Clearances
Altimeter Setting
Pilot
ZID ARTCC
Terre Haute Low SectorARTS
CMI TRACONZAU ARTCC
HOCSRDeparture
Control HOCSRArrivalControl
IND TRACON
ARTS
Flight Information
Flight Strip
Contact Indianapolis ARTCC
19
IFR Flight ExampleChampaign to Indianapolis - Arrival
Initiate Handoff
Handoff Accepted
Contact Indianapolis
Arrival Contact
Vectoring Instructions
Landing Clearance
Contact Ground Control
Contact
Pilot FDP
ZID ARTCC IND TRACON
Terre HauteLow Sector
East ArrivalControl
Departure Control
Local Control
IND Tower
Ground ControlWest ArrivalControl
Taxi Clearance
Coordination (verbal)
Approved
For descent from 10,000 ft to 7,000ft
Coordination (verbal)Approved For sequencing
Speed Adjustments
For spacingILS Approach Clearance
Altitude Clearance Descent to
11,000 ft
Altitude Clearance
Final Approach Fix Crossing Report
Monitor Local Frequency
20
IFR Flight Example - Champaign to Indianapolis
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 ExampleIndianapolis to Lafayette - Departure
Pilot Local ControlFDP
ZID ARTCC IND Tower
Ground Control
IND TRACON
Flight Data/Clearance Delivery
Approach
LAF Terminal
ARTS
Flight Information
Flight Strip
Contact (ready to depart)
Departure Clearance (altitude restriction, transponder code,
departure frequency)
Markup Strip
Marked up StripContact (ready to taxi)
Taxi Clearance
Contact (ready to take off)
Take off Clearance
Contact Departure Control
Marked up Strip
Coordination (verbal)
Approved (with restriction) For entry point
Flight Information (verbal)
22
IFR Flight ExampleIndianapolis to Lafayette - Arrival
Pilot Local Control
LAF Tower
Approach Ground Control
LAF TerminalIND TRACON
Departure Control
Radar Identification
Vectoring Instructions (heading, altitude)
Contact
Clearance (to pass coordination fix)
Clearance (for ILS landing)
Monitor Tower Frequency
Landing Clearance
Contact Ground Control
Contact
Taxi Clearance
Contact Lafayette Approach
Also indicates termination of radar service
Contact
![Unmanned Aircraft Systems (UAS) Integration in the ...info.publicintelligence.net/NASA-UAS-NAS-Integration.pdf · FY13 APG [Project ID 3265] Complete flight evaluations to assess](https://img.pdfslide.us/doc/110x75/6001f364f797c21cc110a7ed/unmanned-aircraft-systems-uas-integration-in-the-info-fy13-apg-project-id.jpg)
