Starting April 23rd, 2018, Changi Airport (WSSS) will begin giving departure clearance (DCL) via datalink, on certain routes. The idea is to clear up voice communications when DCL can be used. Full details listed in CAAS AIP SUP 013/2018.
To use this, you’ll need ACARS, and be compliant with EUROCAE ED85-A. You’ll login to the ground system at WSSS.
The departures are as below:
– Destinations in Peninsular Malaysia via ATS Routes A457 and B466
– Destinations in Thailand via ATS Routes B466 and B469 / M751
– Destinations in Indonesia via ATS Route A457, R469 and B470
– Destinations in Australia and New Zealand via ATS Route B470
– Flights with allocated Calculated Take-Off Time (CTOT) under Bay of Bengal Cooperative Air Traffic Flow Management (BOBCAT)
A few other notes:
-The DCL message will not include requested crusing levels and final cruising levels. Your planned flight level in 15b will be used, and ATC will give cruise FL when airborne. Sounds like they won’t entertain any requests for a different FL while on the ground.
-No revisions allowed over datalink, all changes must be made by voice comms.
-Make your request with RCD message (see format in attached AIC) no more than 20 minutes before TOBT. If you’ve got a CTOT under BOBCAT, you’l need to put that in the message. If you’re routing via ANITO B470, list your FL at ANITO crossing.
If your DCL is rejected, you’ll get a “revert to voice procedures” message. A few auto-rejects:
-Flight routes not applicable.
-RCD message doesn’t comply with ED-85A or inaccurate data.
-When required due to flow restrictions.
Operating out of WSSS soon? CAAS AIP SUP 013/2018 is worth a read.
It’s time for everyone’s favourite topic – DATA LINK MANDATE! New things are happening on December 7th. Don’t worry, we’ll help.
Right Now, if you’re using the NAT tracks, between FL350-390, you’re mandated to use data link services. Simply put, you must be equipped with CPDLC and ADS-C (FANS 1/A ready and able).
On December 7th 2017, the data link mandate will expand to the entire ICAO NAT Region between FL350-390, with a few exceptions. We’ve got the image below showing you the area. White routes are exempt, as well as the grey border areas (we like the Big Fish).
-Everything north of 80°North
-New York Oceanic East FIR (was previously all of NY Oceanic)
-Routes T9, T213, T13, T16, T25. (see: The Tango Routes)
-The Blue Spruce Routes (white lines)
-Areas that currently have radar, multilateration (is this a word?) and/or ADS-B. (the grey areas)
Note: If any of the NAT Tracks go into the grey areas, you won’t be exempt while on the tracks.
Be ready, January 30th, 2020, all of the NAT ICAO Region will have the Data Link Mandate, above FL290, including the Tango Routes as well as those little grey areas.
To figure out where you are welcome on the NAT, depending on what equipment and training you have, check out our quick and dirty guide here.
For more details about the datalink mandate, you can read the UK AIC in full here.
In case you missed the several hundred Notams this week, KUSA is the new identifier for all datalink logons in the US, including CPDLC-DCL, and enroute, which came into use on October 22nd. Now, the only logon you need is KUSA.
For all you could possibly want to know about Datalink operations in the US, take a peek at the new AC90-117, ” an overview of data link communication operations for U.S. domestic
operations and in oceanic and remote continental airspace”, which we’ve uploaded here.
More readable is the FAA’s CPDLC-DCL guide, uploaded here.
There are some comments that it doesn’t work properly if you don’t have an active FPL in the box, let us know your experiences on that in the comment section below.
Update 03Oct: The FAA has released AC_90-117, which is their updated overview of Data Link Communications.
- The United States ATC system transition to a National Single Data Authority (NSDA) is here.
- The changeover will take place on 22Oct at 0330Z
- A single CPDLC logon ID (KUSA) will be provided for domestic US airspace.
- The initial phase is set up to issue departure clearances only
- En-route CPDLC communications within US airspace will be implemented at a later time.
- More details about the transition process are found here NSDA – Data Comm Program
- We’ll post further information as it becomes available