Cargo — LDM message import and automatic in-flight data saving

The Cargo module in Leon enables automatic import of LDM (Load Message) contents and saves the extracted data directly to the relevant flight. It reads, parses, and maps key fields (e.g., total cargo weight, ULD, number of pieces, C/B/M codes, notes) into the Flight Watch.

Key benefits

• Automatic completion of Cargo and Load Distribution fields in a flight based on the LDM standard.

• Fewer manual transcription errors and faster OPS checklist completion.

• Audit trail in message history and integration logs.

Configuration

1) Mailbox - LDM intake channel

• Configure the LDM message Mailbox in the Settings → https://leonsoftware.atlassian.net/wiki/x/xxdt2w.

• Use the LDM Mailbox in the CARGO CONFIGURATION:

2) Fleet and Cargo configuration

Ensure that in Settings → Fleet for the given registration you have defined the weight units, Cargo mass limits (BASIC tab of the aircraft configuration window), and — optionally — loading points in the ULD Bay column (opens the ULD bay configuration window), where you can configure the loading points:

LDM message import can fill Cargo fields and, when the message contains suitable data, reflect the distribution by loading points.

How it works — LDM processing

Leon scans the mailbox every 10 minutes, parses Load messages, and saves cargo, mail, baggage, and passenger data directly in Flight Watch for matching flights.

1. Leon receives an LDM message from the configured Mailbox.

2. Leon identifies the flight based on flight number, registration, date, and airports (ADEP/ADES).

3. Cargo mass, ULD (identifier and weight), C/B/M codes, and notes are extracted from the LDM structure.

4. Cargo summary (total cargo mass in the fleet unit) is displayed in Flight Watch.

5. When the LDM includes a breakdown and loading points are configured in Fleet → ULD Bay, ULD-level items are populated in Load Distribution.

6. In OPS → Flight details and in the “Load distribution” checklist item (EDIT button) you can review the imported fields.

Load distribution from LDM (non-standard usage)

Normally, load distribution across an aircraft's loading points/compartments is sent via a CPM message. Some operators, however, send this breakdown through the LDM message instead — providing the mass per loading point rather than a ULD identifier. Leon now reads this distribution from the LDM and saves it to the flight's ULD model, matched against the loading points (ULD Bays) configured for the aircraft.

Leon matches each entry from the message to a loading point using two methods, in order of priority:

• By track and point ID — the letter in the message (e.g. P, L, R) is treated as the track identifier and the remaining part as the loading point ID. For example, both P10 and 10P are matched to the point on track P with ID 10.

• By point ID only — if no match is found by the first method, Leon takes the whole identifier from the message and looks for a loading point with that ID on the aircraft, ignoring the track.

Validations

• No flight match: the message goes to the error queue; verify flight number/airports/dates or link it manually.

• Inconsistent units: Leon uses the weight unit defined in Fleet. When they differ, the parser performs conversion.

• Duplicate LDMs: a subsequent message may overwrite/supplement items according to the channel rules (recommended: "last write wins" or merge by ULD ID).

• Limit exceedance: if the total load violates limits (e.g., max Cargo, MZFW), OPS will display warnings according to fleet policy.

• Incomplete ULD data: items without mass/ID may be flagged for manual correction in Load Distribution.

• Load distribution present in LDM but no ULD Bays configured: the distribution part is skipped; only the Flight Watch data is saved.

• Configured ULD Bays don't match the message: unrecognized points are not saved, but the rest of the import (Flight Watch data and any recognized points) still completes.