When an air cargo shipment stops moving, the fastest response is a disciplined one: verify the milestone, identify the responsible handoff, gather evidence, and choose a recovery action. This workflow helps operations teams manage an air cargo shipment delay, customs hold, misroute, or missing scan without relying on assumptions or sending incomplete escalation requests.
Overview
Air freight tracking is useful only when the status is interpreted in context. A shipment may appear inactive because it is between scans, waiting for a connection, undergoing document review, or held at a terminal. The same status can require different actions depending on the planned route, service commitment, customs stage, and last confirmed physical location.
Air cargo exception management begins with the air waybill (AWB), the shipment’s primary reference. Confirm the AWB number, carrier or freight forwarder reference, origin, destination, pieces, weight, flight routing, and expected delivery milestone. Then compare the latest tracking event with the booked plan. Do not treat a lack of a new scan as proof that cargo is lost; treat it as a visibility exception that needs verification.
A practical response has five stages:
- Verify: Check the tracking record, local time, flight plan, and latest confirmed event.
- Classify: Decide whether the issue is a timing gap, documentation problem, customs hold, handling exception, misroute, or potential loss.
- Escalate: Contact the party controlling the next handoff with a concise evidence pack.
- Recover: Request a corrected document, rebooking, warehouse release, delivery change, or investigation as appropriate.
- Communicate: Give stakeholders a time-stamped update, the current risk, and the next checkpoint.
For planning context, compare the exception with the shipment’s original cutoffs, connections, and delivery buffers using the air freight transit time planning guide.
What to track
Record more than the latest status label. A useful exception log shows what happened, when it happened, who confirmed it, and what action is pending.
Core shipment variables
- Identifiers: Master or house AWB, booking reference, purchase order, and internal case number.
- Routing: Origin and destination airports, planned connections, flight numbers where available, and the responsible carrier or forwarder.
- Physical milestones: Pickup, acceptance, tender to the airline, departure, arrival, transfer, breakdown, release, and delivery.
- Exception details: The exact status wording, timestamp, airport or facility, number of affected pieces, and any stated reason.
- Document state: Commercial invoice, packing list, export or import information, permits, certificates, and any corrections requested.
- Commercial impact: Required delivery date, production or customer commitment, replacement options, and whether storage or rebooking costs may arise.
Use the carrier’s tracking page and the forwarder’s portal when both are available, but preserve screenshots or downloaded records with timestamps. Tracking systems can display different events or update at different times. AWB tracking is a starting point, not a substitute for confirmation from the handler, carrier, customs contact, or delivery partner.
Exception evidence checklist
Before escalating, assemble the AWB, booking confirmation, packing list, commercial invoice, proof of pickup, tracking history, photographs of labels or packaging if relevant, and the requested delivery date. For a customs issue, include the classification and shipment description used for the entry. If product classification is uncertain, review the air cargo HS code guide and confirm the correct information with the responsible customs professional.
| Status problem | Next action | Evidence to provide |
|---|---|---|
| No new scan after acceptance | Confirm the last physical handoff and ask whether the shipment is moving under the planned booking. | AWB, acceptance time, booked route, piece count, and latest tracking record. |
| Flight departed but cargo did not move | Ask whether the shipment was rolled, held for capacity, security, documentation, or handling reasons; request the next available routing. | Booking confirmation, flight details, cargo dimensions, and required delivery date. |
| Arrival recorded but no release | Check breakdown, terminal availability, customs status, and delivery appointment requirements. | Arrival event, consignee details, customs documents, and delivery instructions. |
| Held by customs | Identify the exact missing, inconsistent, or review-related item and submit a corrected response through the responsible party. | Invoice, packing list, classification, permits, importer information, and written hold notice if available. |
| Misrouted or wrong destination | Request a location confirmation and recovery routing; do not authorize disposal or return without written instructions. | AWB, labels, intended destination, piece count, and proof of the discrepancy. |
| Piece missing or damaged | Open a formal tracing or irregularity case and preserve packaging, labels, delivery records, and photographs. | Piece-level count, condition report, photographs, AWB, and handoff records. |
Cadence and checkpoints
Set checkpoints before a shipment becomes urgent. At booking, record the planned milestones and the latest acceptable time for each one. At pickup, confirm piece count, labels, dimensions, and documents. After airline acceptance, verify that the shipment is assigned to the expected movement. Around each connection, check whether the cargo departed, arrived, and was transferred. At destination, monitor customs release, terminal availability, delivery appointment, and proof of delivery.
The right review frequency depends on the shipment’s service and risk. A routine shipment may need checks at planned milestones, while time-sensitive, regulated, high-value, or temperature-sensitive cargo may justify more frequent monitoring. Use local operating hours and the carrier’s stated response channels when setting deadlines; avoid assuming that a status will update continuously.
When escalating, include one clear request and a response deadline. For example: “Please confirm the physical location, reason for the missed connection, next routing, and revised delivery estimate by [time and time zone].” Send the request to the party controlling the current handoff, then copy the commercial or account contact if no response arrives within the agreed window.
Maintain a simple exception worksheet with these fields: last confirmed event, current status, suspected cause, owner, action requested, evidence sent, next checkpoint, customer update time, and closure date. This prevents multiple people from repeating the same inquiry and creates a record for later review.
How to interpret changes
Separate a normal timing variation from a material exception. A short gap between routine scans may not require recovery action if the shipment remains within its planned buffer. A missed flight, unconfirmed handoff, customs request, or destination mismatch requires a specific investigation.
Look for patterns across events rather than reacting to a single label. “In transit” may cover several stages, so compare it with the last airport and the planned connection. “Arrived” may mean arrival at the airport, not release to the consignee. “Exception” is not a complete diagnosis; ask who has custody, what action is blocked, and what information would clear it.
Classify the cause into one of four working groups:
- Visibility gap: The cargo may be moving, but a scan or data transmission is missing.
- Capacity or routing issue: The planned flight or connection was not used, requiring rebooking or a revised route.
- Documentation or compliance issue: Information, permits, packaging, or classification requires correction or review. For specialized cargo, consult the relevant preparation guidance, such as the lithium battery air-shipping checklist.
- Physical handling issue: Cargo is damaged, short, inaccessible, or at an unexpected facility.
Communicate facts separately from estimates. State the last confirmed event, the open question, the action underway, and the next update time. Avoid promising a delivery date until the carrier or forwarder confirms a viable routing. If service recovery is required, compare rebooking, alternate airport, airport-to-airport collection, door-to-door delivery, partial shipment, or replacement inventory against cost, customs requirements, and operational risk.
When to revisit
Review this workflow monthly for active operations and at least quarterly as a formal playbook update. Refresh carrier status terminology, escalation contacts, terminal instructions, customs-hold examples, service commitments, and recommended response windows whenever procedures change. Contact details that worked for one shipment may not be suitable for another airport, service type, or destination.
After each significant incident, conduct a short review within the next operating cycle. Ask:
- Which milestone first showed the exception?
- Was the status visible early enough to act?
- Which document, handoff, or contact caused the longest delay?
- Did the team have the required evidence immediately?
- Was the customer or internal stakeholder updated at the promised time?
- Would a different route, buffer, packaging method, or service level reduce recurrence?
Track recurring causes by lane, carrier, airport, commodity, service, and document type. A monthly count of delays is useful, but the operational value comes from identifying preventable patterns: repeated invoice corrections, missed cutoffs, weak connection buffers, incomplete labels, or unclear ownership after arrival. Use those findings to update booking instructions and escalation thresholds.
Before the next shipment, save the current AWB workflow, confirm the escalation list, and attach the appropriate document checklist. For broader preparation, see the air freight customs documents checklist and the guide to booking air cargo online and managing the AWB workflow. A repeatable log, scheduled review, and clear owner turn an air freight tracking problem from a reactive scramble into a manageable operations process.