Air Cargo Load Planning Software
Plan the load before the flight is released.
Build aircraft-specific cargo load plans with piece, weight, volume, dimension and compartment information. FlightStratix evaluates the configured limits, records plan revisions and connects load readiness to the cargo flight's dispatch checks.
Load information cannot live in a disconnected worksheet
Flight operations needs to know which plan is current, what changed and whether cargo constraints have been checked. The plan should stay linked to the operating flight and shipment allocations.
Built around the way you work
Each capability is part of the connected FlightStratix workspace.
Aircraft cargo configurations
Set effective-dated aircraft configurations with maximum payload, volume, compartment dimensions, door limits and permitted cargo attributes using operator-supplied approved data.
Build the flight load plan
Add cargo items with piece count, weights, volumes, dimensions and compartment assignment, including eligible shipment-linked allocations.
Review checks and revisions
Inspect plan findings; finalisation requires a nonempty plan with no FAIL or UNKNOWN check result. Reopen a final plan with a reason.
Record what was actually loaded
Capture loaded weight and offloaded items after planning, keeping a history of the operational change.
From start to finish
Cargo aircraft configuration, load checks and actual uplift
Load decisions need current aircraft limits, actual pieces and a versioned plannot a separate spreadsheet.
Use a configured aircraft loading profile
Define effective-dated aircraft cargo configurations with maximum payload and volume, compartments, door dimensions, maximum piece length and dangerous-goods permissions. These values come from the operator's supplied approved data and must be maintained accurately.
Build a load from eligible cargo items
Select an aircraft configuration for the cargo flight, add eligible pieces with planned compartment, weight and volume, and keep shipment-linked allocations connected to their source shipment record.
Checks that distinguish unknown from cleared
Review plan evaluations before finalising. Empty plans and checks returning FAIL or UNKNOWN cannot be finalised as if safe. Revisions carry expected version checks, and staff may reopen a final plan with a reason.
Record actual load and offloads
After planning, enter actual loaded weight or record offloaded items. The dispatch release service checks cargo-plan status and current evaluation, helping stop an incomplete plan from being mistaken for a released flight.
Plan the load against actual aircraft constraints
Start with an operator-maintained configuration
Each aircraft cargo configuration can have effective dates, reference details, maximum total payload and total volume. Compartments record weight and volume limits, door width and height, maximum piece length and whether dangerous goods are permitted. These are operational inputs maintained by the operator; the application does not certify that they match the aircraft's approved loading manual. A clear load-planning page should make that responsibility visible rather than implying that any entered value is automatically approved.
A load item has real dimensional requirements
The flight plan holds load items with number of pieces, weight, volume, dimensions and planned compartment. These details answer more than 'how many tonnes are on board': a piece may fit within total payload but not through a compartment door, or it may be unsuitable for a location based on its handling classification. The system evaluates planned items against the saved configuration and returns checks that the load planner needs to review.
Missing data must not look like spare capacity
The finalisation workflow requires a nonempty plan and does not accept FAIL or UNKNOWN results. That distinction is useful in operations where incomplete shipment dimensions or a missing configuration might otherwise look like zero additional load. The plan also uses expected revisions to stop stale updates from overwriting later work, and it records a reason for reopening a final plan.
After loading, keep planned and actual weight separate
When a plan is finalised, actual loaded weight can be recorded for relevant items, or items can be marked offloaded. Shipment-linked items should be changed through the cargo shipment workflow so the booking and allocation records remain aligned. A changed load can affect NOTOC currency and flight dispatch readiness. The load page should link to shipment management and Cargo Ops rather than attempting to own their wider search terms.
Cargo readiness contributes to flight release
For a cargo flight, dispatch release checks require a suitable cargo plan and passing cargo checks in addition to the configured aircraft, crew and station conditions. A plan finalised earlier cannot be assumed current after material cargo amendments. This is an operational cross-check, not a claim that the software independently replaces authorised load control, weighing equipment or aircraft manufacturer's approved documentation.
Review the planned load against its source data.
Keep the shipment allocation visible
Review which shipments are assigned to the flight and the loading information associated with them. Keep changes connected to their source records so the team can understand what has changed before preparing the next plan.
Explore cargo shipment recordsUse validated aircraft and loading information
The planning workflow depends on the aircraft and loading data entered by the team. Review the plan under your approved operating procedures and keep the resulting operational events connected to the shipment history.
Connect shipment event tracking- Select configurationChoose aircraft type and limitsComplete
- Add cargoAssign pieces to compartmentsComplete
- 03Evaluate checksReview weight/volume limitsIn review
- 04Finalise planLock the approved loadPending
- 05Record actualsCapture loaded and offloaded itemsPending
- 06Review readinessCheck against dispatch releasePending
See it in context
Load checks find an unsuitable compartment
A large piece is proposed for a compartment with insufficient door clearance. The planner reviews the check result, moves the piece to an eligible location or removes it from the planned flight and evaluates again. After finalisation, the team records actual weight and any offloaded items. If dangerous goods are affected, the NOTOC is reviewed and updated as required before the release is accepted.
An operational example
A flight receives several pieces for two compartments. The load planner selects the applicable aircraft configuration, allocates pieces and reviews a weight-volume conflict. The plan remains unfinalised until corrected; after loading, actual weights and offloads are recorded before dispatch release is reviewed.
Where it fits in FlightStratix
Frequently Asked Questions
Does the system supply aircraft-approved loading limits?
The operator enters the applicable data; approval of that data is not established by the product reference.
Can an incomplete plan be finalised?
The documented service blocks empty plans and checks marked FAIL or UNKNOWN.
Can I finalise a plan with missing weight information?
No. The documented finalisation rules reject unknown or failing checks and empty plans.
Can a released plan be changed?
It can be reopened with a reason and maintained as a revised plan; any affected operational release must be reviewed under the airline/cargo rules.
Explore FlightStratix solutions
Keep cargo load readiness part of flight readiness.Book an Fx Cargo Ops demo.
Book a 30-minute walkthrough tailored to your operation.