How Do You Track Cargo and ULD Management for a Part 121 Airline?

Part 121 airlines track cargo and ULD (unit load device) management by giving every can, pallet, and container a unique serial number tied to a live location and status, then recording weight, load position, and custody signatures against the specific flight leg it moves on. That chain — registry, load manifest, and custody log — is what lets you answer where a ULD is, what's loaded on a given tail, and who is accountable for a shipment at any point from acceptance to delivery.

Cargo and ULD tracking is really three connected records: a ULD registry (what you own or lease and where it currently sits), a load manifest per flight (what's on this tail, in what position, at what weight), and a custody log (who touched the shipment and when). Airlines that run this on paper or in disconnected spreadsheets lose ULDs between stations, mis-load weight and balance, and can't answer a claims adjuster fast. The goal is one system where cargo data, load planning, and dispatch all reference the same flight and ULD records instead of three versions of the truth.

Why the answer is what it is

Give every ULD a registry entry, not a paper tag

Track serial number, ULD type (LD3, LD6, pallet, etc.), owner or lessor, current station, and condition/damage status for each container. A registry beats a paper tag because it survives the ULD moving to a different station or airline.

Tie cargo to the load manifest for that specific flight leg

Every ULD and loose-loaded shipment needs a weight, a load position, and a destination recorded against the tail number and leg it's flying on. That manifest is what load planning and dispatch both need to agree on before departure.

Log custody at acceptance, loading, and delivery

A signature or scan at each handoff — acceptance at origin, loading onto the aircraft, and delivery at the destination — is what lets you reconstruct what happened to a shipment when something goes missing or a claim comes in.

Reconcile ULD inventory by station on a schedule

Don't wait until a can is missing to count them. A regular station-by-station reconciliation against the registry catches ULDs stuck at the wrong station before they become a shortage that delays the next load.

Build cargo and ULD re-manifesting into your IRROPS process

When a flight cancels or a tail swaps, cargo and ULDs need to be re-routed and re-manifested along with crew and passengers. This is the step that gets missed when cargo tracking lives in a separate system from crew and dispatch recovery.

What to look for

  • Assign a unique serial/tracking ID to every ULD in your fleet or lease pool
  • Record ULD type, owner/lessor, and current station location at all times
  • Log weight, load position, and destination for every ULD and shipment on each flight's manifest
  • Capture custody signatures or scans at acceptance, loading, and delivery
  • Reconcile ULD inventory by station on a set schedule, not just when one goes missing
  • Add a cargo/ULD re-manifest step to your IRROPS recovery playbook
  • Keep cargo and ULD records exportable for claims, interline reconciliation, and audits

Related questions

What is a ULD in airline cargo operations?

A ULD (unit load device) is a standardized container or pallet — like an LD3 can or an A-series pallet — used to consolidate cargo and baggage so it loads into an aircraft's belly or cargo hold as a single unit instead of loose pieces. Airlines and ground handlers track ULDs by serial number because they're valuable, get shared across interline partners, and need to be accounted for at every station.

How do airlines track ULDs between interline partners?

Most airlines participate in industry ULD control programs that log ULD movements, ownership, and station balances across carriers, since a container loaded by one airline often gets unloaded and returned by another. That only works if your own ULD registry and load manifests stay current — the shared system is only as accurate as what each airline reports into it.

Does AviationAlley track cargo and ULD management?

Yes. AviationAlley is built as one operations platform scoped to the FAR Part you operate under, including Part 121 airlines, and its IRROPS Recovery & Cargo feature area is built for cargo and ULD management alongside explainable legal re-crew and tail-swap recovery. AviationAlley is pre-launch and opening to a founding cohort, so this describes what the platform is built to do rather than an in-market track record.

How Roffik addresses this

The platform for FAA-approved Part 142 training centers — simulator scheduling, FAA compliance records, client-account billing, and SWIFT wire reconciliation. Learn more about AviationAlley.

Keep exploring