Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Approved by: AMC/A3TK Effective Date: 16 Apr 07 Version: 2.0.

Similar presentations

Presentation on theme: "1 Approved by: AMC/A3TK Effective Date: 16 Apr 07 Version: 2.0."— Presentation transcript:

1 1 Approved by: AMC/A3TK Effective Date: 16 Apr 07 Version: 2.0

2 2  Think Of It as, Text Messaging With Controllers  Advantages?  Clear Communications  No Language “Issues”  Direct Line to Controller  Better Surveillance  Automatic Position Reporting

3 3 ACARS – Aircraft Communications Addressing And Reporting System (Character-Based) ADS – Automatic Dependent Surveillance ATS – Air Traffic Service AFN – ATS Facilities Notification AOC – Airline Operational Control ATSU – Air Traffic Services Unit CDA – Current Data Authority CMU – Communications Management Unit

4 4 CPDLC – Controller Pilot Data Link Communications D-ATIS – Digital ATIS FANS-1/A – Future Air Navigation System FOM – FANS-1/A Operations Manual IMFD – Interactive Multi-function Display HFDL – HF Data Link NDA – Next Data Authority OOOI – Out, Off, On, In SATCOM – Satellite Communication VDL – VHF Data Link

5 5 8.33 Radios SATCOM/HF/VHF CPDLC RNP – 30 vs. 100 NM RVSM – 1000 vs. 2000 ft FM Immunity ADS Mode S TCAS CategoryComponentsGoal Communication Digital Radios to Handle Reduced Channel Spacing and Datalink Navigation Better Horizontal/Vertical Position Accuracy to Enable Reduced Separation Surveillance Enhanced Situational Awareness, Collision Avoidance, Automatic Position Reporting C C N N S S ATMATM ATMATM Air Traffic Management Transition from ATC to ATM With the Ultimate Goal of Free Flight

6 6  Controller Pilot Data Link Communications (CPDLC)  Air Traffic Service (ATS) Facilities Notification (AFN) - Logon  Automatic Dependent Surveillance (ADS)  Airline Operational Control (AOC)  Air Traffic Services (ATS) – D-ATIS, Oceanic Clearance

7 7

8 8

9 9 Guidance And Procedures In Civilian Operating Manuals  Guidance And Procedures In Civilian Operating Manuals  FANS-1/A Operations Manual (FOM)  Guidance Material for ATS in NAT Airspace  Area Planning Documents  Regional AIPs  NOTAMs  Centers Upgrading ALL the time! CPDLC? ADS? First Call Procedures?

10 10 NOTAMS webpage

11 11 FAA Oceanic Procedures Branch

12 12  SEE GP Chapter 4  RWXYJ IDKLOT HUV/PD (B40)  RWXYJ IDKLOT HUV/SD (B40.2)  P – Mode S Including PA, But No ID  S – Mose S and Aircraft ID  D – ADS Capability  J – Datalink, K – MLS Equipment


14 14

15 15  AFN Logon  Normally 15-45 Minutes Before Airspace Entry  Required for a CDA To Be Established  Does Not Establish Your Current Data Authority (CDA)  Can Also Be Done “Automatically” Via Address Forwarding

16 16  Wrong Center Name (KZAK vs. KZOA)  Flight ID Does Not Match Call Sign  1801 REG Does Not Match APM Number  For KC-135: Last Digit Of Year Plus Last Four Of Tail Number Plus An S (i.e. 80093S for tail Number 58-0093 or 44835S of 64-14835)  If You Change Aircraft: Call Dispatch To Change On 1801 (AFN) And Tell Command Post To Change C2IPS (AOC)

17 17

18 18  Get Organized!  IMFD / CDU Displays  Flight Plan Log (Rounds Time)  SELCAL Page  CPDLC Position Report Page (truncates time)  Compulsory / Non-compulsory Points  Don’t Access Position Report Early  Reported Point In The Position Report Is The Last Waypoint Sequenced By The FMS

19 19  AFN LOGON: Accepted By KZAK (Oakland) When Near FIR. No New Operator Input Required  CPDLC: CDA is KZAK (CPDLC Enabled) (CPDLC Enabled)  DISCONNECT Prompt for CPDLC Available

20 20  Non-NAT - After Entering Oceanic Airspace or Crossing FIR Boundary:  Send a CPDLC Position report – FIRST!  Informs ATSU That They Are The CDA  HF Call With SELCAL Address And Stating That You Are Data Link Equipped  Oakland Example: “Beak 96, CPDLC, Origin KSKA, Destination YBBN, Request SELCAL Check on JMQR”

21 21  NAT- After Entering Oceanic Airspace Or Crossing FIR Boundary:  DO NOT Send a CPDLC Position Report  HF Call With a CDA and ADS Contract - “RCH XXX, C-P- D-L-C, Shanwick Next*, Request SELCAL Check XXXX”  HF Call ADS Contract Only - “RCH XXX, A-D-S, SCROD VALIE*, Request SELCAL Check XXXX”  Continue to Add CPDLC or ADS After Call Sign on HF * If flight will exit current FIR into oceanic airspace, include the name of the next FIR. If exiting into domestic airspace, include track name if on the organized track system or last two fixes in the cleared route of flight if not on the OTS.

22 22  Replaces HF Position Report  Course Offsets And/Or Block Altitudes Will Not Be Reflected On Position Reports  Do Not Use Page 3 To Attach Free Text  Controllers Don’t Normally Access  Do Not Send A Separate Free Text  Controllers Expect You To Adhere To Previous Clearance Until You Report Otherwise  No Feedback - Controller Will Not Respond

23 23

24 24

25 25  Can You Break Down This Message To Determine:  Reported Position?  Next Position?  Next + 1 Position?  Anything Else Here?

26 26  Only TWO Connections Possible  Current Data Authority (CDA)  You’re In Their Airspace  Has Exclusive Communication  Next Data Authority (NDA)  Determined by CDA  No Communications Capability  Usually The Next FIR You Will Be Entering

27 27  Also Referred To As, “AFN LOGON Triggered By Address Forwarding”  Failure To Close All Uplink Messages Will Cause A Termination Of Both CDA And NDA Connections  Downlink Messages Do Not Affect The Transfer Process

28 28 Process is AUTOMATIC – Usually  CDA Will Send An END SERVICE Message To Aircraft  If END SERVICE msg Failed You Will Need to DISCONNECT From CDA  If No NDA Appears, A Manual LOGON To The Next Center Will Be Required

29 29  AFN LOGON: Forwarding in Progress  CPDLC: CDA and NDA

30 30  AFN LOGON: Accepted by Tokyo  CPDLC: No Change to CDA and NDA

31 31  CONTACT Message Combined With END SERVICE Message  Most Common  CDA Disconnects And NDA Becomes CDA Upon Downlink Of WILCO Response

32 32  AFN LOGON: Accepted by Tokyo  Note 7-Letter ATSU Identifier  CPDLC: NDA Has Become CDA

33 33

34 34  WILCO – Instruction Understood And Will Be Complied With  UNABLE – Instruction Cannot Be Complied With  STANDBY – Wait For A Reply, Short-term Delay (<10 min)  REQUEST DEFFERED – Request Received But Deferred, long-term delay (>10 minutes)  ROGER – Message Received And Understood Only Correct Response To Free Text Uplink  AFFIRM – Yes  NEGATIVE – No

35 35  Standard set of messages  Consist of Elements and Variables  “CLIMB TO AND MAINTAIN FL360”  “CLIMB TO REACH FL340 BY 0300”  Most Messages Open a Dialogue  Messages Are Linked If A Response Is Required  Message Exchange Between ATS and Aircraft Involves Message # and Variable Value

36 36  Messages are “Open” until “Closed” by Appropriate Response…System Knows!  Pilot Responses: Three levels  WILCO or UNABLE For Clearance Changes  AFFIRM or NEGATIVE For Inquiries  ROGER For Information Requiring A Response “Message Received”

37 37  ACCEPTED and CLOSED Signify “Closed” Messages  CONN ENDED Results From Termination of CDA With Open DOWNLINK Message

38 38  If A Message Has Multiple Elements That Require A Different Response, Highest Order Response Will Close Message  Example: Descend To And Maintain FL220, Report Level FL220  Descent Requires: WILCO  Report Level Requires: ROGER  WILCO Will Close Message And The ‘System’ Will Display WILCO or UNABLE Only

39 39  Do Not Send Multiple Request Message After Receipt Of A STANDBY Uplink  Use “WHEN CAN WE EXPECT _____”  Close All Identical Messages, If Applicable

40 40  “CLIMB TO AND MAINTAIN FL330” Opens Dialogue (Clearance)  STANDBY, WILCO or UNABLE Are Selectable  If Pilot Chooses STANDBY – Dialogue Remains Open…  “WILCO” – Dialogue Closed, Pilot Begins Climb  “EXPECT CLIMB AT WALZA” Opens Dialogue (Information) ROGER Displayed on MCDU  “ROGER”– Dialogue Closed

41 41  REQUEST DIRECT TO [position]  Present Position To Specified Position  REQUEST [route clearance]  Amendment To Current Clearance  REQUEST CLEARANCE  Request For Pre-departure Or Route Clearance  Clearance Will Load In Alternate Flight Plan Before Allowing You To “Execute” To Active Flight Plan  Print Out Route Clearances To Ensure You See The Whole Clearance!!

42 42

43 43  Avoid multi-element requests  “Request climb to FL350 and request direct HUMOR” Responses easily confused – stick to standard message sets!  Answer all messages in a timely manner  Respond with “roger” to all free text uplinks before composing response message  Uplinks MUST be closed prior to FIR transition or…

44 44  Do Not Rename Waypoints In The FMS  Customized Names Will Replace Original Point Description In Downlinked Reports  Technique: Use Alternate Flightplan With Overlay For User-defined Points

45 45  Why not just use FREE TEXT ??  No Dialogue established, No Required Response From ATC, No Linked Response Available To Controller  Time Intensive – Type Manually (Typos), Send, Read By ATC, Type An Answer, Send To Airplane, Pilot Reads  Language (e.g. Korean Airlines Pilot Typing in English???)  Interpretation by ATC

46 46  Should Only Be Used When There Is No Other Available Message Option  Use Standardized Free Text When Able  WAKE DEV [direction]  REVISED ETA [position]  Reference Regional Operating Manuals For Additional Guidance

47 47  See Sample Messages In AMC Enabling Concept  Uses Standard Message Set With Free Text Elements, Where Possible  Still Not Pre-coordinated With Most ATSUs  ATSUs Responding With Free Text  AFFSA Working To Have Them Accepted As Standardized Free Text In The FANS-1/A Message set

48 48  Use The Message Set Correctly  Limit Use Of Free Text – Ensure There Is No Appropriate Message In Message Set  Read All Parts/Pages Of Messages  Received Messages May Be More Than 1 pg.  Sent Messages May Be More Than 1 Page (i.e. Position Report)  Print Out Route Clearances  Ensure You Understand All Parts Of Message – Your Transmit Button Still Works

49 49

50 50  Surveillance – Information Sent From Aircraft Without Pilot Involvement  ADS Armed When Power Applied  Each Center Establishes Their Own Contract  You Can See If A Contract Has Been Established With You (Unlike Many Commercial Aircraft).

51 51  Three Types Of Contracts:  Periodic – Every XXX Seconds  Set By Controller  Can Be Modified  May see 0/0 = No Periodic Requested  Event – Waypoint Change (Next Or Next+1), Climb, Descent Or Other Certain Events Occur  Demand – When Desired

52 52 ADS Connection  1 With Tokyo  Periodic – Every 320 sec (5 min 20 seconds)  Event – Yes, but you don’t know what kind

53 53  Altering flight plan (next or next+1) sends out a Waypoint Change Event report  Reports update flight plan info at ATSU  Used for conformance monitoring  ADS Emer can only be turned on by pilot  No restriction on non-compulsory reporting points in flightplan

54 54

55 55  CPDLC “MAYDAY” Message Automatically Places The CPDLC And The ADS Functionality Into Emergency Mode  The Crew Can Also Select ADS Emergency Mode Independently of CPDLC  Emergency Mode Can Only Be Initiated by The Crew And Can Only Be Cancelled by The Crew

56 56  Mayday or Pan Messages Do Not Require a Response  Most ATSUs Will Respond To Confirm Situation And Provide Positive Feedback To The Crew  ATSU Will Attempt To Send An “ON DEMAND” Contract And Increase Periodic Contract Reporting Rate

57 57

58 58  IN ALL CASES, If You Have A Problem/ Emergency And Need Immediate Resolution, Contact The ATSU by ANY Means Available  If the CPDLC Connection is lost  “NO ATC COMM” Will Be Displayed  Lose CDA  Attempt Re-logon to ATSU  May Need To Call The ATSU To Have Them Log You Off Their System, If Unable to Re-logon

59 59  A > Annunciation Indicates Loss of data link communications  BE PATIENT. SATCOM Should Reconnect Within A Short Period Of Time And > Annunciation Will Be Displayed  You Should Not Lose The Established CDA or ADS Contract(s)  Revert To Voice If Unable To Regain Data Link Connectivity

60 60  Data Link Opens Up Your Active Flight Plan And Aircraft Parameters To Hackers Any Time Power Is On The Aircraft And DL:ON Is Selected  Turning Off the ADS Closes the Door Slightly  TACC Has The Capability To Pull Information From Your System Without Your Knowledge

61 61  Turning DL:OFF Will Shut Down VDL, SATCOM (Including Voice), And HFDL  NO LINK On All Media, Squitters Off  Need To Manage Active Flight Plan When Flying Missions With Unclassified And Classified Legs On The Same Sortie  Consider Pulling CMU 1 & 2 Circuit Breakers to Disable Data Link, But Leave SATCOM available (DL:ON)

62 62  Used To Collect Data On Specific Observations  Confusion About a Clearance  Inappropriate Use Of Abbreviations/Acronyms  Any Other Abnormal Event/Observation  What To Include In The Report  Date, Time, FIR, Detailed Description  Error Report in AMC Datalink Concept of Employment (CONEMP)  All AMC reports submitted to TACC

63 63

64 64 SCENARIO  Call Sign – Astra 13  Tail number – 57-1435  Reg number – 71435S  You Are 30 Minutes Out From Entering Oakland FIR (KZAK) QUESTIONS 1. What Do You Enter In The Logon To Field? KZAK 2. What Goes In The FLT ID Field? Your call sign – ASTRA 13 3. What Happens After Both Fields Are Populated? The SEND LOGON Prompt Appears at VLSK 2L

65 65 QUESTIONS 1. What Do You Expect To See As You Approach The Fir Boundary? a. AFN Logon By Address Forwarding To PPTCDYA b. NDA Field Will Populate With NTTT 2. What Do You Do After Boundary Crossing? Standard FIR entry procedures: CPDLC position report and SELCAL check 3. What Actions Will You Take In Airspace? None, Assuming Tahiti Accepts ADS Reports In Lieu Of CPDLC Position Reporting SCENARIO You Are In The Oakland FIR (CPDLC-only) And Approaching The Tahiti FIR (NTTT) Note: Tahiti Has Both CPDLC and ADS

66 66 Data Link Training Course End GATM Approved by: AMC/A3TK Effective Date: 23 Apr 07 Questions: Contact OPR Maj Schroeder, DSN 779-3645

Download ppt "1 Approved by: AMC/A3TK Effective Date: 16 Apr 07 Version: 2.0."

Similar presentations

Ads by Google