The MCDU Datalink Pages

Of the three cockpit interfaces (article 1), the MCDU is the "build/manage/edit" side: sending notifications, managing connections, building requests, consulting reports, checking status, browsing records — all on the MCDU datalink pages, while the DCDU (article 8) only "reads one, answers one". This article does not walk every line key (that is a manual look-up); it lays out the navigation structure and functional grouping of the MCDU datalink pages, so you know where to go for a given task.

1. Navigation structure — the ATSU DATALINK page and its four branches

The entry to the datalink pages. Per FCOM DSC-46-10-40-30:

The MCDU MENU page enables access to datalink pages when the flight crew selects ATSU. [...] The ATSU DATALINK page provides a subsequent access to: AOC MENU pages [...] ATC MENU pages, COMM MENU pages, DATALINK STATUS page.

The four branches: ATC MENU (dealings with the controller: connection/notification/request/report/emergency/ATIS), COMM MENU (communication configuration: media/VHF3 mode/scan), DATALINK STATUS (which media are available), and AOC MENU (dealings with the company, operator-customised).

2. Functional grouping of the pages

The ATC MENU pages, grouped by "what do I want to do" (page names per the FCOM DSC-46-10-40-30 page tree):

To do this	Go to
Notify an ATC centre	NOTIFICATION
Check/disconnect a connection, check ADS-C status	CONNECTION STATUS
Request a lateral change (re-route/DIR TO/SID/STAR)	ATC LAT REQ
Request a vertical change (level)	ATC VERT REQ
Negotiate (when can we accept a level/speed)	WHEN CAN WE EXPECT
Request clearance / own separation / voice contact	ATC OTHER REQ
Build/edit reports, arm automatic position report	ATC REPORTS
Manual position report	POSITION REPORT
Send an emergency message, switch ADS-C emergency	EMERGENCY
Request airport information	ATIS MENU (also receives the report, article 6)
List connected ADS-C centres	ADS-C DETAIL

One line: request (LAT/VERT/OTHER/WHEN), report (REPORTS/POSITION), connection (NOTIFICATION/CONNECTION STATUS), emergency, ATIS — sort the task into a group and you know the page.

3. The DATALINK STATUS page — which media are available

The page to read in operations and abnormals — the datalink status of each medium (integrative, per FCOM DSC-46-10-40-30 DATALINK STATUS): for VHF 3 / SATCOM / HF, two lines each —

Line 1, datalink status: DLK AVAIL (established and available) · DLK NOT AVAIL (not established) · INOP (not operative) · NO NETWORK (inhibited, VHF3) · VOICE (operating in voice mode, VHF3/HF) · NOT INSTALLED (SATCOM/HF);
Line 2, application availability: ATC / AOC · ATC ONLY · AOC ONLY.

Per FCOM DSC-46-10-40-30, for example:

VHF 3 Line 1 Displays datalink status: DLK AVAIL The datalink communication is established and available.

[!note]- DATALINK STATUS is the datalink "signal bars" This page is the datalink's signal bars: at a glance, which of VHF 3 / SATCOM / HF can carry datalink now, and whether it can carry ATC or AOC. VOICE warns that a medium has been switched to voice (e.g. HF to voice, so its datalink drops, article 1); NO NETWORK = inhibited; INOP = failed. Diagnosing a datalink fault (article 11) and checking media before oceanic entry (article 10) both read this page. The ATSU auto-selects the best medium (VHF→SATCOM→HF), but you need to know which one it is using and which is left to take over.

4. MSG RECORD — the archive of closed messages

Where do finished messages go? Into the MSG RECORD (article 6 source). Per FCOM DSC-46-10-30-70:

The Message Record application enables to store datalink messages. [...] When the flight crew closes a message on the DCDU, the message is stored and disappears from the DCDU. The messages are stored in chronological order and grouped by flight number. When the maximum number of stored messages is reached (up to 99 messages), any new message will be stored and the oldest message will be deleted. [...] Note: 3. The ADS-C reports are not stored.

[!note]- Three points about MSG RECORD (1) CLOSE a message = archive it into the MSG RECORD (article 8); within 5 minutes you can still RECALL it on the DCDU, after that browse the MSG RECORD page. (2) Up to 99 messages, grouped by flight number, rolling over the oldest. (3) ADS-C reports are not stored in the MSG RECORD (they are background surveillance data, not "messages", article 5) — so to review clearances/requests you sent, come here; to see what ADS reported, it is not here. Printable and fully erasable.

Self-test

[!note]- Q1. Where do the datalink pages start, and what are the ATSU DATALINK page's four branches? MCDU MENU → ATSU → ATSU DATALINK, branching to ATC MENU, COMM MENU, DATALINK STATUS, and AOC MENU.

[!note]- Q2. Which pages do you use for a lateral request, a vertical request, negotiation, position report, and emergency? ATC LAT REQ, ATC VERT REQ, WHEN CAN WE EXPECT, POSITION REPORT, and EMERGENCY.

[!note]- Q3. What does the DATALINK STATUS page show, and what do VOICE / NO NETWORK / INOP / ATC ONLY mean? Per-medium datalink status and application availability. VOICE = switched to voice; NO NETWORK = inhibited; INOP = failed; ATC ONLY = only ATC applications available.

[!note]- Q4. What does MSG RECORD store, how many, grouped by what, and which is not stored? Closed datalink messages, up to 99, grouped by flight number, rolling over the oldest; ADS-C reports are not stored.

Key takeaways

Point	Detail
Navigation	MCDU MENU → ATSU → ATSU DATALINK → ATC MENU / COMM MENU / DATALINK STATUS / AOC MENU
Grouping	Request / report / connection / emergency / ATIS — sort task to group to page
DATALINK STATUS	Per-medium DLK AVAIL/VOICE/INOP/NO NETWORK + ATC/AOC availability — the "signal bars"
MSG RECORD	CLOSE archives it; ≤ 99, grouped by flight number; ADS-C not stored

References

FCOM DSC-46-10-40-30 — ATSU DATALINK four branches, ATC MENU page tree, DATALINK STATUS per-medium availability.
FCOM DSC-46-10-30-70 — MSG RECORD: CLOSE archives, ≤ 99 grouped by flight number, ADS-C not stored, printable/erasable.

Independent study material, not an Airbus publication and not endorsed by the manufacturer. Always defer to the current operator FCOM, FCTM, and QRH for operational use.