The WestJet Strike Is a Belly-Cargo Contingency Test for Canadian Shippers

Passenger-airline disruption is also a freight disruption. When a passenger flight disappears from the schedule, the lower-deck space carrying urgent parts, medical products, perishables, and e-commerce shipments disappears with it. The brief WestJet flight-attendant strike delivered a sharp reminder that Canadian shippers need a belly-cargo contingency plan before the first cancellation.

The dispute moved quickly. Flight attendants issued a 72-hour strike notice on July 30. WestJet began cancelling flights before the walkout, the strike started on August 2, and a tentative agreement was announced on August 3. Reuters reported that approximately 250,000 travellers had flights cancelled over Canada's three-day holiday weekend. The union represented about 4,400 flight attendants.

For cargo planners, the important fact is not that the stoppage ended quickly. It is that an airline network can progress from formal warning to cancellations and grounded aircraft inside one normal freight-planning cycle.

The 72-hour notice is an operational clock

A strike notice should not trigger a general request to “monitor the situation.” It should start a timed sequence of decisions tied to shipment urgency and network exposure.

At the 72-hour mark, planners should identify every booked or planned shipment touching the affected carrier during the risk window. That inventory needs more than airway bill numbers. It should include required-delivery time, product shelf life, temperature requirements, customer priority, alternative airports, customs status, and the latest time at which the freight can be diverted without missing service.

When pre-strike cancellations begin, exposure becomes an exception-management problem. Booked capacity is no longer reliable merely because the flight still appears in an earlier confirmation. Teams should require a fresh operating-status check and obtain alternative capacity for shipments approaching their decision deadline.

Once aircraft are grounded, the objective changes again. Planners must stop waiting for the original itinerary and execute the best recoverable option. The sequence matters: companies that delay action until the strike formally starts compete for the same limited replacement uplift as everyone else.

Passenger cancellations remove freight capacity

Belly cargo is easy to overlook because airlines publish passenger impacts first. But each cancelled narrow-body or wide-body departure also removes a scheduled link from a time-sensitive logistics network. The loss is particularly difficult on regional lanes where freighter service is limited and passenger schedules provide the practical air bridge.

The effect reaches beyond freight already tendered. A cancellation can strand cargo at origin, interrupt connections at a hub, or leave goods cleared at an airport that no longer offers a viable onward departure. Restored passenger operations do not instantly restore cargo flow either. Aircraft, crews, and passengers must be repositioned, while accumulated freight competes with new demand for the first available space.

That is why a one-day stoppage can produce a longer cargo recovery tail. Reuters reported on August 3 that WestJet had begun resuming operations after a tentative agreement, but shippers still needed to validate each routing rather than assume the network had immediately returned to normal.

Build four triggers into the contingency plan

An executable plan defines who acts, what data they need, and which event authorizes additional cost.

1. Rebooking trigger

Rebook when the probability-adjusted arrival of the original itinerary exceeds the customer's latest acceptable delivery time. Formal cancellation is an obvious trigger, but it is too late for premium freight. Other signals can include a strike notice, progressive schedule reductions, a missed acceptance cutoff, or an itinerary with no protected onward capacity.

2. Truck-air substitution trigger

Move freight by truck to another airport when the drive plus handling time produces a safer arrival than waiting locally. From western Canada, that could mean testing alternative Canadian or U.S. gateways depending on product admissibility, customs readiness, available uplift, and total transit time. The calculation must include border crossing, security screening, terminal cutoff, and recovery—not just line-haul mileage.

3. Alternative-gateway trigger

Activate a gateway only after confirming capacity, ground handling, customs brokerage, and final-mile recovery. A quoted flight with no realistic acceptance slot is not a solution. Approved gateways should be ranked in advance by lane, commodity, regulatory restrictions, and the shipper's ability to tender freight there.

4. Customer-notification trigger

Notify customers when the risk crosses a defined threshold, not after service fails. A useful message states the affected shipment, current status, decision deadline, available alternatives, incremental cost, and revised delivery range. Early notification turns disruption into a commercial choice; late notification turns it into an apology.

Rank recovery options by service risk

The cheapest replacement quote can be the most expensive decision if it relies on an uncertain connection or misses a production shutdown deadline. Contingency selection should score the full route across several dimensions:

• probability of confirmed uplift and connection success;
• expected arrival and variability around that estimate;
• handling, customs, temperature, and security risks;
• additional transport cost and potential failure cost;
• customer priority and inventory consequence.

CXTMS can bring affected shipments, alternative routes, carrier responses, cutoffs, and customer commitments into one exception workflow. Planners can compare options using service-risk scores, record why an option was selected, issue the revised routing, and notify stakeholders from the same operational record. That creates a repeatable response instead of a collection of calls, inbox threads, and spreadsheets.

The WestJet disruption ended faster than a prolonged strike scenario, but that does not make the test less valuable. A 72-hour warning, pre-emptive cancellations, a grounded network, and a staged restart exposed every decision point a shipper should automate. The next disruption may involve weather, maintenance, cyber risk, or another labor action—and may offer less warning.

Want to turn disruption alerts into ranked, executable recovery plans? Request a CXTMS demo and see how shipment exceptions, alternatives, approvals, and customer updates can run in one workflow.