1 / 10

Departure Scenario 2

Departure Scenario 2. November 14, 2007. Departure Scenario 2. STEP 1 – Entry of ERAU Flight ACTION: ERAU Ops Center enters their flight plan into the ERAU flight dispatch system Flight plan (FP) would be fed into AWIM SYSTEM RESPONSE / VISUALIZATION: ERAU display shows entry of FP

manjit
Download Presentation

Departure Scenario 2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Departure Scenario 2 November 14, 2007

  2. Departure Scenario 2 • STEP 1 – Entry of ERAU Flight • ACTION: ERAU Ops Center enters their flight plan into the ERAU flight dispatch system • Flight plan (FP) would be fed into AWIM • SYSTEM RESPONSE / VISUALIZATION: • ERAU display shows entry of FP • AWIM receives FP and creates a FDO which it adds to the Flight Repository and publishes to all systems connected to AWIM • FP is displayed in the proposed flight lists of EFS, SDSS, FPPP • Benefits: • SWIM flight data distributed to all participants • Flight intent data into the NAS

  3. Departure Scenario 2 • STEP 2 • ACTION: At 5 minutes prior to taxi, the pilot contacts ATC Clearance Delivery to obtain VFR Departure Clearance – delivered by EFS CD controller by voice • Voice readback from pilot to EFS CD controller • EFS CD controller indicates clearance delivered, which is then published to AWIM • SYSTEM RESPONSE / VISUALIZATION: • FP information displayed on Tower CD position EFS display is read to pilot • Pilot reads back cleared FP to ATC • EFS shows flight in ‘Clearance Delivered’ status • Benefits: • Improves accuracy of Out and Off time predictions through use of cleared status for TFM use

  4. Departure Scenario 2 • STEP 3 • ACTION: The aircraft will have a estimated taxi and take-off (OFF) time. Entered in Flight Planning system • Pilot calls ramp and indicates ‘ready-to-taxi’ • Pilot cleared to taxi to the SPOT • SYSTEM RESPONSE / VISUALIZATION: • Not applicable • Benefits: • ATC has awareness of flight’s departure status via AWIM

  5. Departure Scenario 2 • STEP 4 – Aircraft Taxis in Ramp to Spot • ACTION: Pilot calls Ground Control for taxi clearance • SYSTEM RESPONSE / VISUALIZATION: • CARTS displays taxi trajectory • MWS position reporting • Ground Control provides taxi clearance by voice and instructs aircraft to follow SDSS generated surface taxi trajectory • Movement of aircraft is displayed on CAMS and CARTS as unidentified target • Benefits: • Operator (Flt Ops) can now be aware of aircraft status “in the ATC realm” via AWIM

  6. Departure Scenario 2 • STEP 5 Aircraft Identified • ACTION: Aircraft taxies per SDSS generated surface taxi trajectory • Ground Controller sees unidentified track and manually tags the track with the aircraft’s N-number • SYSTEM RESPONSE / VISUALIZATION: • MWS position reporting • Aircraft movement is displayed on CAMS as identified target • CAMS does conformance monitoring of aircraft actual position along taxi route • Benefits: • Increase in safety due to conformance monitoring in taxi

  7. Departure Scenario 2 • STEP 6 • ACTION: Aircraft approaching runway threshold • Flight strip handed off from ground to local on EFS • SYSTEM RESPONSE / VISUALIZATION: • MWS position reporting • Aircraft movement continues to be displayed on CAMS and CARTS • CAMS continues performing conformance monitoring of aircraft • Benefit: • Seamless transfer from ground surveillance to TRACON surveillance

  8. Departure Scenario 2 • STEP 7 • ACTION: CLEAR FOR TAKEOFF entered by Local Controller • Follows taxi trajectory – enters runway according to local controller clearance • SYSTEM RESPONSE / VISUALIZATION: • Operator input into EFS indicating Clear-for-Takeoff • Takeoff clearance transmitted to AWIM • Benefit: • Situational awareness shared

  9. Departure Scenario 2 • STEP 8 • ACTION: Aircraft enters runway and takes off • SYSTEM RESPONSE / VISUALIZATION: • MWS position reporting • Runway is allocated • Runway is deallocated after exceeding height threshold • Benefits: • Taxi trajectory delivers the flight to the runway for departure to meet the airborne trajectory • Smooth entry into the en route system

  10. OEP Initiatives Shown in this Scenario • Surface Decision Support • Shared Situational Awareness • Taxi route calculation and delivery • Tactical Flow Management

More Related