PrimeFlight Buys StratAir Handling: Who Owns the Cargo Exception After the Sale?

An air cargo warehouse can change owners in a day. The open damage claims, security holds, missed connections, and unlocated pieces inside it do not reset at closing.

That distinction matters after PrimeFlight Aviation Services acquired StratAir's cargo-handling operations. FreightWaves reported that the transaction includes a 120,000-square-foot warehouse and workforce at Miami International Airport, plus ground-handling operations in Richmond, Virginia, and San Juan, Puerto Rico. PrimeFlight already served more than 200 locations and provided cargo services in 10 domestic markets; the acquired operation is therefore joining a much larger service network.

The deal may create scale, but it also creates a cutover point at which an exception can fall between organizations. Airlines, forwarders, and handlers need to decide who owns every unresolved shipment before systems, operating procedures, email addresses, or escalation paths change.

Closing the deal does not close the exception

FreightWaves said StratAir's operations would initially retain their current brand and transition to PrimeFlight over time. That staged change is sensible commercially, yet it can complicate operations. A warehouse employee may still wear one brand while using a new reporting line, a legacy cargo system, and a customer contract that has not been fully migrated.

The safest rule is simple: the party controlling the freight when an exception is discovered owns containment and communication until a named party accepts the handoff. Contractual liability can be resolved separately. Customers should never wait while two companies determine which agreement applies.

Four common exceptions require explicit ownership:

1. Damage: The discovering handler photographs the freight, records packaging condition and location, preserves CCTV or scan evidence, and prevents further movement when required. The claim owner may ultimately differ, but evidence collection cannot wait.
2. Missed connection: The handler controlling the freight confirms its physical location and status. The airline owns the revised flight decision, while the forwarder communicates the commercial impact and downstream plan to the shipper.
3. Security or regulatory hold: The regulated party placing the hold controls release. The handler must preserve the hold code, authority, timestamp, screening evidence, and authorized-release identity rather than converting the event into a generic delay.
4. Unlocated freight: The last party with a verified custody event leads the search until a documented transfer is proven. An electronic status message alone is not proof of physical handoff.

This separation between operational response and final liability is crucial. A 2026 change to air-waybill guidance illustrates how quickly responsibility can become disputed. FreightWaves described the change as a significant reallocation of risk for forwarders involving misdeclared goods, concealed dangerous goods, and unsafe packaging. Industry groups warned that airlines could implement the framework differently. During an acquisition, ambiguous contracts layered onto changing operational control make a shared exception record essential.

Transfer the history, not just the shipment

A clean acquisition cutover needs a shipment-level exception ledger. Migrating customer names and active air waybills is insufficient. For every open exception, the transfer package should include:

• master and house air-waybill numbers, piece count, weight, commodity, and special-handling codes;
• every physical scan with local time, time zone, device, user, facility, and exact location;
• planned and actual flight, truck, dock, and unit-load-device assignments;
• custody changes, including the releasing and receiving individuals or organizations;
• damage photographs, inspection notes, seal numbers, CCTV references, and packaging condition;
• security, customs, temperature, dangerous-goods, or other hold codes and release authority;
• customer notifications, promised update times, escalation contacts, and current owner;
• claim status, reserves or stated value where authorized, documents received, and response deadlines.

Preserve the original event IDs and timestamps. Re-creating old records in a new system can make a six-hour gap appear like a fresh scan and destroy the sequence needed to investigate a claim. The new operator should append events rather than overwrite the legacy timeline.

Data quality deserves special attention because air cargo infrastructure records are already uneven. A Government Accountability Office study covered by FreightWaves found federal airport-warehouse data incomplete, untimely, and inaccurate, with many warehouses missing. It also found that air cargo data in the Freight Analysis Framework relied on only two sources, one with known sampling error. If industry-level data has blind spots, operators cannot afford the same weakness in shipment-level custody records.

Run a 30-day post-close exception review

The first month should be managed as an operational stabilization period, not a routine reporting cycle.

Before cutover, reconcile all freight physically on hand against system inventory. Assign one accountable owner and one next action to every open exception. Airlines, the outgoing operation, the acquiring handler, and affected forwarders should approve a shared escalation matrix.

During days 1-7, hold a daily review of aged freight, unlocated pieces, missed connections, open holds, damage cases, and scans rejected by interfaces. Compare exceptions by legacy versus new workflow, facility, airline, shift, and customer. Any record without a next-update time is incomplete.

During days 8-14, test the evidence chain. Sample closed cases and verify that a reviewer can reconstruct custody, decisions, notifications, and release authority without searching personal inboxes. Confirm that claim documents and images remain accessible to authorized partners.

During days 15-30, measure whether the transition is stabilizing. Track exception rate per 1,000 shipments, time to acknowledge, time to assign an owner, time to locate, missed promised updates, claim-cycle age, and reopened cases. A falling case count can be misleading if teams are simply coding issues differently, so definitions must remain constant through the review.

At day 30, the parties should formally accept remaining cases or extend enhanced oversight. No legacy exception should become an orphan merely because the brand transition advanced.

Make ownership visible across the handoff

Acquisitions expose a basic truth about air cargo: customers experience one shipment journey even when several companies and contracts participate in it. The best protection is a common operational record that identifies the current custodian, exception owner, required next action, and complete history.

CXTMS gives freight teams a shared workflow for milestones, documents, exceptions, responsibilities, and customer communication across organizational boundaries. Request a CXTMS demo to see how structured exception management can keep cargo accountable through a handling transition.