1 departure scenario 1 november 14, 2007. 2 scenario overview entry of flight data into awim...

1

Departure Scenario 1Departure Scenario 1

November 14, 2007November 14, 2007

2

Scenario OverviewScenario Overview

• Entry of Flight Data into AWIM SystemEntry of Flight Data into AWIM System– Embry Riddle Instructional FlightEmbry Riddle Instructional Flight– Delta Flight from Daytona Beach to AtlantaDelta Flight from Daytona Beach to Atlanta

• Pre-Pushback ActivitiesPre-Pushback Activities– Clearance DeliveryClearance Delivery– Aircraft Fueling, Pre-Flight, Start and PushbackAircraft Fueling, Pre-Flight, Start and Pushback– Departure Release CoordinationDeparture Release Coordination

• Push-BackPush-Back– Immediate Push-Back for Embry Riddle FlightImmediate Push-Back for Embry Riddle Flight– Gate Hold for Just-in-Time Delivery to the Runway for Delta FlightGate Hold for Just-in-Time Delivery to the Runway for Delta Flight

• TaxiTaxi– Digital Taxi ClearancesDigital Taxi Clearances– Surface Taxi Trajectories in Surface AutomationSurface Taxi Trajectories in Surface Automation– Taxi Conformance MonitoringTaxi Conformance Monitoring

• Take-OffTake-Off

• All Flight Data Objects are Shared between Local Systems through AWIMAll Flight Data Objects are Shared between Local Systems through AWIM– And with the Rest of the NAS and Flight Operators through SWIMAnd with the Rest of the NAS and Flight Operators through SWIM

3


• STEP 1a – Entry of ERAU FlightSTEP 1a – Entry of ERAU Flight

• ACTION: ERAU Ops Center enters their simulated flight plan into the ACTION: ERAU Ops Center enters their simulated flight plan into the ERAU flight dispatch systemERAU flight dispatch system– Flight plan (FP) is transmitted to AWIMFlight plan (FP) is transmitted to AWIM

• SYSTEM RESPONSE / VISUALIZATION:SYSTEM RESPONSE / VISUALIZATION:– ERAU display shows entry of FPERAU display shows entry of FP– AWIM receives FP and creates a FDO which it adds to the Flight AWIM receives FP and creates a FDO which it adds to the Flight

Repository and publishes to all systems connected to AWIMRepository and publishes to all systems connected to AWIM– ERAU FP is displayed in the proposed flight lists of applications ERAU FP is displayed in the proposed flight lists of applications

connected to AWIM:connected to AWIM:• EFS, SDSS, CARTS, FPPP and FltWindsEFS, SDSS, CARTS, FPPP and FltWinds

• Benefits:Benefits:– AWIM flight data distributed to all participantsAWIM flight data distributed to all participants– Flight intent data into the NASFlight intent data into the NAS

4


• STEP 1b – Entry of Commercial FlightSTEP 1b – Entry of Commercial Flight

• ACTION: Simulated Delta Airlines Ops Center enters their flight plan into the ACTION: Simulated Delta Airlines Ops Center enters their flight plan into the Flight Plan Pre-Processor (FPPP)Flight Plan Pre-Processor (FPPP)– Airline receives constraint feedback on 4-D trajectoryAirline receives constraint feedback on 4-D trajectory

• Based on Special Activity AirspaceBased on Special Activity Airspace• Airspace and airport congestionAirspace and airport congestion

• SYSTEM RESPONSE / VISUALIZATION:SYSTEM RESPONSE / VISUALIZATION:– FPPP display shows entry of Flight PlanFPPP display shows entry of Flight Plan– AWIM receives FP and creates a Flight Data Object which it adds to the Flight AWIM receives FP and creates a Flight Data Object which it adds to the Flight

Repository and publishes to all systems connected to AWIMRepository and publishes to all systems connected to AWIM– Delta FP is displayed in the proposed flight lists of applications connected to Delta FP is displayed in the proposed flight lists of applications connected to

AWIM:AWIM:• EFS, SDSS, CARTS, FPPP and FltWindsEFS, SDSS, CARTS, FPPP and FltWinds

• Benefits:Benefits:– SWIM flight data distributed to all participantsSWIM flight data distributed to all participants– Flight intent data into the NASFlight intent data into the NAS– Value of constraint feedback to the airlineValue of constraint feedback to the airline

5


• STEP 2 – Clearance Delivery for Delta FlightSTEP 2 – Clearance Delivery for Delta Flight

• ACTION: At 10 minutes prior to pushback, the ERAU and Delta pilots each ACTION: At 10 minutes prior to pushback, the ERAU and Delta pilots each receive clearance via data linkreceive clearance via data link– Departure clearance displayed on pilot’s cockpit displayDeparture clearance displayed on pilot’s cockpit display– Pilots responds by acknowledging the data link messagePilots responds by acknowledging the data link message

• SYSTEM RESPONSE / VISUALIZATION:SYSTEM RESPONSE / VISUALIZATION:– Flight Data Object is updated automaticallyFlight Data Object is updated automatically– EFS shows flight in ‘Clearance Delivered’ statusEFS shows flight in ‘Clearance Delivered’ status– Clearance Delivery Controller passes strip to Ground ControllerClearance Delivery Controller passes strip to Ground Controller

• Benefits:Benefits:– Reduced operational errors due to digital communication of clearanceReduced operational errors due to digital communication of clearance

• No chance for voice/interpretation errorsNo chance for voice/interpretation errors– Improves accuracy of Out and Off time predictions through use of cleared status Improves accuracy of Out and Off time predictions through use of cleared status

for TFM usefor TFM use

6


• STEP 3 – Departure ReadinessSTEP 3 – Departure Readiness

• ACTION: The aircraft has a planned door closed / ready to pushback ACTION: The aircraft has a planned door closed / ready to pushback (OUT) time entered in Flight Planning system(OUT) time entered in Flight Planning system

• SYSTEM RESPONSE / VISUALIZATION:SYSTEM RESPONSE / VISUALIZATION:

– SDSS computes initial Off TimeSDSS computes initial Off Time

– Initial Out and Off Time updated in the Flight Data Object and shared Initial Out and Off Time updated in the Flight Data Object and shared with AWIMwith AWIM

– Flight Ops enters updated flight status as the phases of turnaround Flight Ops enters updated flight status as the phases of turnaround proceedproceed

• Benefits:Benefits:

– ATC has awareness of flight’s turnaround status via AWIMATC has awareness of flight’s turnaround status via AWIM

7


• STEP 4 – Departure Release CoordinationSTEP 4 – Departure Release Coordination

• ACTION: Ramp controller sends request for release to En Route SDSSACTION: Ramp controller sends request for release to En Route SDSS– En route TMC enters the release time into SDSSEn route TMC enters the release time into SDSS

• SYSTEM RESPONSE / VISUALIZATION:SYSTEM RESPONSE / VISUALIZATION:– En Route SDSS shows flight that is subject to APREQEn Route SDSS shows flight that is subject to APREQ– Show entry of Release TimeShow entry of Release Time– SDSS recalculates OUT, OFF times as neededSDSS recalculates OUT, OFF times as needed– EFS displays APREQ release timesEFS displays APREQ release times

• Benefits:Benefits:– Better information to ATC - Earlier request for departure release – Better information to ATC - Earlier request for departure release –

possibly capture earlier slot – reduce delaypossibly capture earlier slot – reduce delay– Just-in-time delivery to the runway end for departureJust-in-time delivery to the runway end for departure– Reduced emissions – reduced fuel usageReduced emissions – reduced fuel usage

8


• STEP 6 – ERAU Power Up and Taxi StartSTEP 6 – ERAU Power Up and Taxi Start

• ACTION:ACTION:

– ERAU ramp clears flight for push-backERAU ramp clears flight for push-back

– Aircraft starts taxiingAircraft starts taxiing


– Aircraft starts generating ADS-B reportsAircraft starts generating ADS-B reports

– Movement of aircraft is displayed on SDSS, LCSS and CARTSMovement of aircraft is displayed on SDSS, LCSS and CARTS

– FDO updated to state ‘Ramp Taxi Out’FDO updated to state ‘Ramp Taxi Out’

9


• STEP 7 – ERAU Approaches SpotSTEP 7 – ERAU Approaches Spot

• ACTION: Tower Ground Controller evaluates taxi route on EFSACTION: Tower Ground Controller evaluates taxi route on EFS

– Ground Controller modifies taxi route from SDSS which is shown on Ground Controller modifies taxi route from SDSS which is shown on EFSEFS


– Taxi Route Change initiates full taxi trajectory update in SDSSTaxi Route Change initiates full taxi trajectory update in SDSS

– Updated taxi route displayed on EFSUpdated taxi route displayed on EFS

– Taxi route changes can be datalinked to the pilot or sent by voiceTaxi route changes can be datalinked to the pilot or sent by voice


– Automation assistance in generation of taxi routesAutomation assistance in generation of taxi routes

– Allows for electronic version of taxi route for conformance monitoringAllows for electronic version of taxi route for conformance monitoring

10


• STEP 7 – ERAU Approaches Spot (cont.)STEP 7 – ERAU Approaches Spot (cont.)

• ACTION: Aircraft taxis in ramp to spotACTION: Aircraft taxis in ramp to spot

– Ground Control provides clearance and instructs aircraft to follow SDSS Ground Control provides clearance and instructs aircraft to follow SDSS generated surface taxi trajectorygenerated surface taxi trajectory


– Aircraft continues generating ADS-B reportsAircraft continues generating ADS-B reports

– Movement of aircraft is displayed on SDSS, CAMS and CARTSMovement of aircraft is displayed on SDSS, CAMS and CARTS


– Operator (Flt Ops) can now be aware of aircraft status “in the ATC Operator (Flt Ops) can now be aware of aircraft status “in the ATC realm” via AWIMrealm” via AWIM

– Reduced controller workload due to less frequency interactionReduced controller workload due to less frequency interaction

11


• STEP 8 – Delta Aircraft power upSTEP 8 – Delta Aircraft power up

• ACTION: Aircraft powers up based upon SDSS generated OUT timeACTION: Aircraft powers up based upon SDSS generated OUT time


– Aircraft begins generating/broadcasting ADS-B position reportsAircraft begins generating/broadcasting ADS-B position reports

– ADS-B surveillance data is displayed on SDSS, CAMS and CARTSADS-B surveillance data is displayed on SDSS, CAMS and CARTS

• Benefit:Benefit:

– Just in time power-up – reduced fuel usage and emissionsJust in time power-up – reduced fuel usage and emissions

12


• STEP 10 – Delta Push BackSTEP 10 – Delta Push Back

• ACTION: Aircraft pushes back ACTION: Aircraft pushes back



– Movement of aircraft is displayed on SDSS, CAMS and CARTSMovement of aircraft is displayed on SDSS, CAMS and CARTS

– FDO updated to state ‘Ramp Taxi Out’FDO updated to state ‘Ramp Taxi Out’

• BenefitsBenefits

– Just-in-time delivery to the runway end for departureJust-in-time delivery to the runway end for departure

– Reduced emissions – reduced fuel usageReduced emissions – reduced fuel usage

13


• STEP 11 – Delta Hand Off to Tower Ground ControlSTEP 11 – Delta Hand Off to Tower Ground Control

• ACTION: Tower Ground Controller evaluates taxi route on EFSACTION: Tower Ground Controller evaluates taxi route on EFS

– Ground Controller approves the taxi route from SDSS which is shown on Ground Controller approves the taxi route from SDSS which is shown on EFSEFS


– Taxi route displayed on EFSTaxi route displayed on EFS

– Taxi route changes can be datalinked to the pilot or sent by voiceTaxi route changes can be datalinked to the pilot or sent by voice


– Automation assistance in generation of taxi routesAutomation assistance in generation of taxi routes

– Allows for electronic version of taxi route for conformance monitoringAllows for electronic version of taxi route for conformance monitoring

14


• STEP 12 – Delta Approaches SpotSTEP 12 – Delta Approaches Spot

• ACTION: Aircraft taxis in ramp to spotACTION: Aircraft taxis in ramp to spot

– Ground Control provides clearance and instructs aircraft to follow SDSS Ground Control provides clearance and instructs aircraft to follow SDSS generated surface taxi trajectorygenerated surface taxi trajectory



– Movement of aircraft is displayed on SDSS, LCSS and CARTSMovement of aircraft is displayed on SDSS, LCSS and CARTS


– Operator (Flt Ops) can now be aware of aircraft status “in the ATC Operator (Flt Ops) can now be aware of aircraft status “in the ATC realm” via AWIMrealm” via AWIM

– Reduced controller workload due to less frequency interactionReduced controller workload due to less frequency interaction

15


• STEP 13 – Both Flights Follow Surface Taxi TrajectorySTEP 13 – Both Flights Follow Surface Taxi Trajectory

• ACTION: Aircraft taxies per SDSS generated surface taxi trajectory ACTION: Aircraft taxies per SDSS generated surface taxi trajectory

– EFIS/CDTI/MFD displays taxi clearanceEFIS/CDTI/MFD displays taxi clearance


– Aircraft movement is displayed on SDSS, CAMS and CARTSAircraft movement is displayed on SDSS, CAMS and CARTS

– SDSS is performing conformance monitoring of aircraft actual position SDSS is performing conformance monitoring of aircraft actual position with respect to the assigned surface trajectorywith respect to the assigned surface trajectory


– Redundancy of taxi conformance monitoring (ground system and Redundancy of taxi conformance monitoring (ground system and aircraft)aircraft)

16


• STEP 14 – ERAU Flight Taxi DeviationSTEP 14 – ERAU Flight Taxi Deviation

• ACTION:ACTION:

– ERAU Flight taxis to wrong intersection off of taxiway NERAU Flight taxis to wrong intersection off of taxiway N


– Aircraft movement is displayed on SDSS, CAMS and CARTSAircraft movement is displayed on SDSS, CAMS and CARTS

– SDSS performs conformance monitoring of aircraft positionSDSS performs conformance monitoring of aircraft position

• Taxi conformance alert will be shown on SDSS and CARTSTaxi conformance alert will be shown on SDSS and CARTS


– Alerting of taxi deviation immediately upon missing taxi turn – rather than Alerting of taxi deviation immediately upon missing taxi turn – rather than waiting to be approaching runwaywaiting to be approaching runway

17


• STEP 15STEP 15

• ACTION: Aircraft approaching departure queue / run-up areaACTION: Aircraft approaching departure queue / run-up area

– Flight strip handed off from ground to local on EFSFlight strip handed off from ground to local on EFS


– Aircraft movement continues to be displayed on SDSS, CAMS and Aircraft movement continues to be displayed on SDSS, CAMS and CARTSCARTS

– SDSS continued performing conformance monitoring of aircraft actual SDSS continued performing conformance monitoring of aircraft actual position versus the surface trajectoryposition versus the surface trajectory

18


• STEP 16 – Both ERAU and Delta Line Up for Take Off in SequenceSTEP 16 – Both ERAU and Delta Line Up for Take Off in Sequence

• ACTION: CLEAR TAKEOFF issued by voice by Local ControllerACTION: CLEAR TAKEOFF issued by voice by Local Controller

– Flight enters runway according to local controller clearanceFlight enters runway according to local controller clearance


– EFS Status Indicates Take-Off Clearance IssuedEFS Status Indicates Take-Off Clearance Issued

19


• STEP 17 – Flights Take-off in SequenceSTEP 17 – Flights Take-off in Sequence

• ACTION: Aircraft enters runway and takes off ACTION: Aircraft enters runway and takes off

• SYSTEM RESPONSE / VISUALIZATION:SYSTEM RESPONSE / VISUALIZATION:– ADS-B and MWS position reportingADS-B and MWS position reporting– OFF status identified automatically by SDSS and CAMSOFF status identified automatically by SDSS and CAMS– As aircraft passes a parameter height or time after ‘OFF’ runway is deallocatedAs aircraft passes a parameter height or time after ‘OFF’ runway is deallocated– CARTS will “auto acquire” aircraft on departure and generate a Departure CARTS will “auto acquire” aircraft on departure and generate a Departure

Message that is used by the enroute system to initiate its processingMessage that is used by the enroute system to initiate its processing– CARTS will show aircraft on departure routeCARTS will show aircraft on departure route

• Benefits:Benefits:– Taxi trajectory and airborne trajectory are consistent – taxi trajectory delivers the Taxi trajectory and airborne trajectory are consistent – taxi trajectory delivers the

flight to the runway for departure to meet the airborne trajectoryflight to the runway for departure to meet the airborne trajectory

20

Scenario SummaryScenario Summary

• Entry of Flight Data into AWIM SystemEntry of Flight Data into AWIM System– AWIM flight data distributed to all participantsAWIM flight data distributed to all participants– Flight intent data into the NASFlight intent data into the NAS

• Pre-Pushback ActivitiesPre-Pushback Activities– TFM has awareness of flight’s turnaround status via AWIMTFM has awareness of flight’s turnaround status via AWIM– Better information to ATC - Earlier request for departure release – possibly Better information to ATC - Earlier request for departure release – possibly

capture earlier slot – reduce delaycapture earlier slot – reduce delay• Push-BackPush-Back

– Just-in-time delivery to the runway end for departureJust-in-time delivery to the runway end for departure– Reduced emissions – reduced fuel usageReduced emissions – reduced fuel usage

• TaxiTaxi– Automation assistance in generation of taxi routesAutomation assistance in generation of taxi routes– Assigned taxi route available in surface automation for conformance monitoringAssigned taxi route available in surface automation for conformance monitoring– Alerting of taxi deviation immediately upon missing taxi turn – rather than waiting Alerting of taxi deviation immediately upon missing taxi turn – rather than waiting

to be approaching runwayto be approaching runway• Take-OffTake-Off

– Taxi trajectory and airborne trajectory are consistent – taxi trajectory delivers the Taxi trajectory and airborne trajectory are consistent – taxi trajectory delivers the flight to the runway for departure to meet the airborne trajectoryflight to the runway for departure to meet the airborne trajectory

1 departure scenario 1 november 14, 2007. 2 scenario overview entry of flight data into awim...

Documents