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.
More on the topic:
- More: US expands CPDLC coast-to-coast
- More: Ops Deep Dive: Private Flights to the US
- More: Ops in Europe vs USA: The Differences
- More: Optimise your Descent
- More: Datalink in Europe: What Are The Rules?
- Latest: Asia Airspace Risk: Why North Korea’s Lastest Launch Matters…
- Latest: Navigating the NOPAC Redesign Project
- Latest: US expands CPDLC coast-to-coast
- Safe Airspace: Risk Database
- Weekly Ops Bulletin: Subscribe
- Membership plans: Why join OPSGROUP?
Departing JFK for the atlantic crossing, when a northern track is filed where the entry point is in the canadian airspace, we also did log-on with Moncton center first.
In JFK, with a filed FPL, log-on to KUSA was possible only when we had J4 added to J1 and J5 in the aircraft equipment block of the flight plan
been in TEB for an flight to Europe. No CPDLC and no PDC possible with an active and loaded flightplan. First CPDLC log in with Moncton.
In Houston Bush KIAH on Nov. 1. Did not have an active flight plan and could not login KUSA until we filed.
I’m a airline Pilot and very interested in aviation news!!!