Containers

Define cargo container types for container-based aircraft operations.

Staff
Last verified: January 30, 2026

Containers define the cargo Unit Load Devices (ULDs) available for container-based aircraft. When a fleet is configured as "Passenger & Containers" or "Cargo - Containers", pilots select which containers to load during dispatch rather than specifying cargo by weight alone.

Accessing Containers

In Orwell, go to Payload → Containers. You need the Manage Containers permission.

Understanding Container Units

Container-based cargo operations use a unit system rather than raw weight. Each aircraft has a Container Units capacity (set on the fleet or aircraft), representing available cargo positions.

Think of it like parking spaces in a car park:

  • The aircraft has 12 "spaces" (container units)

  • An LD3 container takes 2 spaces

  • A pallet takes 4 spaces

  • Pilots can load any combination that fits the available spaces

This models real-world constraints where physical space - not just weight - determines what can be loaded.

Real-World ULD Examples

ULD Type

Typical Use

Approximate Size

LD3

Lower deck, narrow-body/wide-body

Small (1-2 units)

LD6

Lower deck, wide-body

Medium (2-3 units)

LD11

Lower deck, wide-body

Large (3-4 units)

Pallet (PMC)

Main deck freighters

Large (4-6 units)

Half Pallet

Smaller cargo loads

Medium (2-3 units)

Your container unit sizes don't need to match real-world exactly - choose values that create interesting loading decisions for your pilots.

Container Properties

Field

Description

Name

Display name shown to pilots (e.g., "LD3 Main Deck"). Should be unique for easy identification.

Type

Container type identifier (e.g., "LD3", "Pallet", "LD-4"). Helps group similar containers.

Unit Size

How many container units this container occupies (1-9999). Must fit within aircraft's Container Units capacity.

Weight

Loaded weight in kilograms. Used for weight and balance calculations.

Notes

Optional notes visible to pilots when selecting containers.

Incompatible Containers

Containers that cannot be loaded together with this one.

Container Assignment

Containers must be assigned to Airports or Routes to appear in dispatch. Without assignment, pilots cannot select them.

Assignment Priority

Departure Airport

Route

Result

Has containers

Has containers

Route containers used

No containers

Has containers

Route containers used

Has containers

No containers

Airport containers used

No containers

No containers

No containers available

Route assignments always override airport defaults.

Assignment Strategy

Use Airport defaults when:

  • Most routes from an airport use the same containers

  • You want consistent container options across a hub

  • You're modelling real-world airport cargo facilities

Use Route overrides when:

  • Specific routes have unique cargo requirements

  • Charter or special flights need different container options

  • You want to restrict containers on certain routes

Recommended Approach

Set up containers at your major hubs first, then add route-specific overrides only where needed.

Assigning to Airports

In Orwell, go to Airports → Airports, select an airport, then open the Load Management tab. The Containers field sets the default containers for flights departing from this airport.

Assigning to Routes

In Orwell, go to Routes → Routes, select a route, then find the Containers section. Containers assigned here override the departure airport's defaults.

Container Incompatibility

Some containers cannot be loaded together due to physical constraints or operational rules. When you mark containers as incompatible:

  • The relationship is bidirectional (marking A incompatible with B also marks B incompatible with A)

  • During dispatch, selecting an incompatible container disables conflicting options

  • Pilots cannot bypass these restrictions

Use cases for incompatibility:

  • Containers requiring special handling equipment that can't be used simultaneously

  • Hazmat containers that cannot travel with certain cargo types

The Dispatch Flow

When a pilot dispatches a container-capable flight:

  1. Load factors calculate limits - Cargo (Weight) and Cargo (Volume) load factors determine maximum weight and units

  2. Containers become available - Based on route or airport assignment

  3. Pilot selects containers - Choosing types and quantities

  4. System enforces limits - Weight, volume, and incompatibility rules apply

  5. Generate Random Payload - Optional auto-fill within constraints

What Pilots See

During dispatch on container-capable aircraft, pilots see:

  • Available containers with their type, weight, and unit size

  • Any notes you've added to help with selection

  • Current weight and volume usage as containers are selected

  • Quantity input for each selected container type

  • Remaining capacity for both weight and volume

The Generate Random Payload button automatically fills containers within the aircraft's weight and volume limits, respecting incompatibility rules. This is useful for pilots who want realistic loads without manual selection.

Integration with Other Systems

SimBrief

Container weights are included in the payload sent to SimBrief for flight planning. The OFP reflects the actual container load.

SimBrief may offload cargo to meet MTOW, MLW weights - vAMSYS will not update with offloaded containers.

PIREPs

Container loads are recorded in the PIREP, showing what cargo was carried on the flight.

Load Factors

Containers work alongside Load Factors:

  • Cargo (Weight) load factor sets the maximum total container weight

  • Cargo (Volume) load factor sets the maximum container units

  • Pilots must stay within both limits

Tips

  • Use descriptive names - Include position or purpose (e.g., "LD3 Forward Hold", "Pallet Main Deck")

  • Set unit sizes realistically - Match your aircraft's actual ULD positions

  • Add notes for special handling - Help pilots understand when to use specific containers

  • Use incompatibility for conflicts - Prevent impossible loading configurations

  • Assign at airport level first - Use route overrides only for specific operational requirements

  • Create variety - Offer different container sizes so pilots can optimise their loads

  • Consider your fleet types - Only container-capable fleets use this system

Troubleshooting

Pilots can't see any containers:

  • Check containers are assigned to the departure airport or route

  • Verify the fleet type is "Passenger & Containers" or "Cargo - Containers"

Containers appear greyed out:

  • They're incompatible with an already-selected container

  • Weight or volume limits have been reached

Weight/volume limits seem wrong:

  • Check Cargo (Weight) and Cargo (Volume) load factors

  • Verify aircraft container unit capacity

Related

Was this article helpful?