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

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

image-20260406-191657.png

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.

LDM import fills operational data without manual editing, improving cargo data consistency and speeding up flight preparation.

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

image-20260406-192832.png

 

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 LDM column, where you can configure the loading points:

image-20260406-185044.png
image-20260406-190405.png

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

Important: If you want to record load distribution in the OPS Checklist, go to Checklist Configuration, enable the “Load distribution” item, and set it to “Auto add to leg”.

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 → LDM, 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.

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.