BizJet Brief
Thursday, November 19, 2026
BizJet Brief

Thursday, November 19, 2026

Tech

Texting With ATC: A Practical CPDLC and FANS Data Link Guide for Business Jet Crews

How CPDLC, FANS 1/A and ADS-C work, what the North Atlantic data link mandate requires of Part 91 operators, and crew habits that prevent errors.

Texting With ATC: A Practical CPDLC and FANS Data Link Guide for Business Jet Crews
File photo: Matti Blume / Wikimedia Commons, CC BY-SA 4.0 — flight deck of Bombardier Global 6000 N835GL at EBACE 2019; full frame shown on a blurred background from the same photo

For many business jet crews, the first real taste of controller-pilot data link communications comes at a busy airport, when the departure clearance shows up on the screen instead of in the headset. The second comes over the ocean, where texting with air traffic control is no longer a convenience but a condition of entry.

This refresher covers how CPDLC works, what the rules say for Part 91 operators, and the habits that keep a text from becoming a clearance you did not mean to accept. It draws on the FAA's Advisory Circular 90-117, Data Link Communications, the FAA's Data Communications guidance page, and ICAO's NAT Doc 007, the North Atlantic operations manual, edition V.2026-1. Your flight manual and avionics maker's guide come first.

The alphabet soup, decoded

CPDLC means controllers and pilots exchanging ATC messages as data rather than voice. Controller messages normally follow a standard format and usually require a response, the FAA says.

FANS 1/A is the avionics standard most business jets use for oceanic data link. It rides on the ACARS network, and messages can travel over VHF, satellite or HF data link depending on the aircraft's equipment and what is available. The "+" in FANS 1/A+ means a newer version with a monitor that flags old messages that may no longer apply.

ADS-C works alongside CPDLC. After you log on, the ground system sets up a "contract" with the aircraft and receives automatic reports of position, altitude, speed and upcoming waypoints, without pilot input.

Is it required?

Inside the United States, no. The FAA says its regulations presently do not require data link in the National Airspace System, and Part 91 operators do not need operational authorization to use data link domestically. Where it is used, CPDLC is an acceptable way to deliver and accept an ATC clearance under 14 CFR 91.123. It does not replace the required voice radios.

Over the North Atlantic, the answer changes. NAT Doc 007 says the NAT Data Link Mandate requires aircraft to be equipped with, and operating, FANS 1/A CPDLC and ADS-C over Inmarsat or Iridium satellite communications from FL290 to FL410 inclusive. There are exceptions, including airspace north of 80 degrees North, the New York Oceanic East flight information region, and certain areas with radar or ADS-B surveillance plus VHF voice coverage.

For Part 91 operators flying oceanic or remote routes, or into countries that require specific data link approval, the FAA says operators may apply for a letter of authorization, known as LOA A056. A Part 91 operator must hold that authorization before filing the J5 through J7 satellite CPDLC codes for oceanic and remote continental airspace.

For the tightest oceanic spacing, NAT Doc 007 says operators also need state authorization to file RCP 240 and RSP 180 performance to use the designated PBCS tracks, which are spaced 23 nautical miles apart between FL340 and FL400.

Logging on

Most first-time problems happen here. AC 90-117 gives the basics:

  • Domestic departures: Log on to KUSA, the single U.S. data authority, about 30 minutes before proposed departure. The departure clearance is sent to the aircraft automatically once the controller approves it. You do not have to ask for it.
  • Oceanic entry: Log on 10 to 25 minutes before entering data link airspace, and make sure ADS-C is armed first. NAT Doc 007's sample oceanic checklist repeats the same window.
  • Match the flight plan exactly. The aircraft identification, registration or aircraft address, and airports entered must match what was filed. The FAA notes that "ABC3" does not match "ABC003," and a mismatch is the first reason it lists for a failed logon.
  • Don't keep retrying. Too many logon attempts in a short time can put an aircraft on a block list. If that happens, contact clearance delivery or your operations center.

Leaving U.S. airspace, the handoff from KUSA may not happen automatically; if not, the pilot must end the connection and log on to the next facility manually.

Reading the screen like a crew

The most useful part of the advisory circular may be its crew resource management guidance. With two pilots aboard, the FAA says each should read every uplinked message individually, and silently, before discussing it or responding. Reading it aloud, the AC warns, can bias the other pilot into "reading" what was said rather than what is displayed.

That matters most for conditional clearances, such as a climb that begins only at a certain fix or time, so a crew does not send WILCO and then fail to comply.

A few more rules of the road from AC 90-117:

  • Respond to CPDLC by CPDLC and to voice by voice. If a message is unclear or conflicts with something else, clarify by voice, then close the data link exchange.
  • If you cannot comply with any part of a multi-part message, reply UNABLE to the whole message. Avoid stacking several requests in one downlink.
  • Use STANDBY if you need time to decide, and free text only when no standard message fits.
  • Keep listening. Pilots must keep monitoring VHF or HF, or maintain a SELCAL watch, while using data link.

When it breaks

If a downlink fails to send, the FAA says the crew should end the connection and log on again with the current facility, then revert to voice if it fails a second time. The suggested phrase is "CPDLC failure, continuing on voice." Degraded data link performance must be reported to ATC as soon as practical.

Over the North Atlantic, NAT Doc 007 says a data link failure inside mandate airspace must be reported to ATC immediately. The flight may be re-cleared out of that airspace. If the equipment fails before departure, the flight should refile to stay clear of the mandate airspace.

In an emergency, sending a MAYDAY or PAN PAN downlink also switches ADS-C into emergency mode, and crews may go back to voice whenever they are able, the FAA says.

Sources

  1. FAA Advisory Circular 90-117, Data Link Communications (status page)
  2. FAA AC 90-117 (PDF)
  3. FAA Flight Operations Group: Data Communications (DataComm) guidance
  4. ICAO NAT Doc 007, North Atlantic Operations and Airspace Manual, V.2026-1