In short: IATA Resolution 753 requires airlines to track every bag at acceptance, loading, transfer and arrival. The check-in and reclaim ends of that journey are well-instrumented, but the airside leg — across the apron, on the ramp, in the transfer tunnel — is where the data goes dark. That gap is a connectivity problem before it is a baggage problem, and it is the part private 5G is best placed to close.
Key Takeaways
- The four tracking points split across two networks — acceptance and arrival sit inside the well-cabled terminal, while loading and transfer happen airside on the apron, where coverage is thin and the data goes dark.
- A mishandled bag is a measurable cost, not an abstraction — SITA puts the global bill for mishandling in the billions each year, and most of the failures cluster at the transfer and loading points that airside tracking is meant to catch.
- Apron handheld scanners need real coverage, not goodwill — ramp agents scanning bags into a container under an aircraft are exactly where terminal WiFi and public 4G both fail, and where one managed private 5G layer pays for itself.
In a nutshell
A regulation that quietly redrew the connectivity map
IATA Resolution 753 has been in force since June 2018, and on paper it is simple: member airlines must be able to demonstrate delivery of baggage by maintaining an accurate inventory through acquisition of tracking data. In practice it obliges the industry to know where every bag is at four moments in its journey — at passenger handover (acceptance), when it is loaded onto the aircraft, at any transfer between flights, and on arrival at the destination. The bag must be tracked, and the data must be shareable between the carriers and ground handlers who touch it along the way.
What is interesting about 753, from where we sit, is that it is not really a baggage regulation at all. It is a data-availability regulation that happens to be about bags. To comply, an airport and its handlers must capture a scan or a read at four points and move that data, in something close to real time, into shared systems such as SITA WorldTracer or the carrier's own departure-control system. Two of those four points sit comfortably inside the terminal, on infrastructure that has been cabled and re-cabled for decades. The other two sit airside — on the apron, on the ramp, in the transfer tunnels — where the connectivity story is a great deal less settled.
This post is about that second half: why the airside tracking points are the hard ones, why the existing networks struggle with them, and why we think a managed private 5G layer across the airside footprint is the cleanest way to close the gap.
The four points, and where each one lives
Take the four tracking points in turn and notice which side of the terminal wall each one falls on.
Acceptance happens at the check-in desk or the bag-drop kiosk. This is the most thoroughly solved point in the whole chain — fixed scanners, a wired network, a conveyor that takes the bag away under continuous belt-side instrumentation. Nobody loses a bag here.
Loading happens on the stand, under the aircraft, often in poor weather and frequently against the clock of a tight turnaround. A ramp agent scans each bag or unit-load device (ULD) as it goes into the hold or the container. This is airside, mobile, and outdoors.
Transfer happens in the bowels of the baggage hall and out across the apron between stands, as a bag from an inbound flight is rushed to a connecting departure. Transfer is where most mishandling originates, and it is a mix of automated sortation indoors and manual, mobile handling outdoors.
Arrival happens at the reclaim belt, back inside the terminal, on fixed infrastructure again.
So the pattern is clear. Two of the four points — acceptance and arrival — are indoors, fixed and well-served. The two that actually decide whether a bag makes its flight — loading and transfer — are airside, mobile and comparatively starved of reliable connectivity. The regulation treats all four points as equal. The network underneath them does not.
Why the apron defeats the obvious answers
The instinctive response is to ask why this needs anything special. Surely the terminal WiFi reaches the stand, or a public 4G SIM in the scanner does the job? In our experience, both answers fall over for the same physical reasons.
Terminal WiFi is engineered for the concourse — high density, indoors, a predictable ceiling height to mount access points on. The apron has none of those features. It is a vast outdoor expanse with large metal aircraft moving across it continuously, each one a moving radio obstacle. A ramp agent crouched between a tug and a container, scanning bags into the hold, is frequently in the radio shadow of the very aircraft they are loading. Access points mounted on the terminal façade simply do not reach reliably to the far stands, and mounting enough of them across an open apron to guarantee coverage is neither cheap nor practical.
Public 4G and 5G fare a little better outdoors but bring their own problems. Coverage at a busy airport is contended — tens of thousands of passengers are using the same macro cells — and a handler cannot get a service-level guarantee on a consumer network. More to the point, the data a 753 scan generates is operational data the airport and handler want to own, route and secure on their own terms, not push out over a public network and hope it comes back through an API in time to matter.
The result, at a great many airports, is a quiet workaround: agents scan into a handheld that buffers the reads locally and syncs them in a batch when the device next finds signal — back at the office, or when the agent walks past a working access point. That satisfies the letter of 753 because the data eventually arrives. It does nothing for the real-time picture that makes the regulation operationally useful, and it is precisely the lag in which a transfer bag misses its connection.
The cost sitting behind the compliance line
It is worth grounding this in numbers, because mishandled baggage is one of the few airport problems with a well-measured price tag. SITA's annual baggage reports have for years put the global cost of mishandling in the billions of dollars, with the rate measured in mishandled bags per thousand passengers. The proportion attributable to transfer — a bag that arrives at the airport fine but misses its onward flight — has consistently been the single largest category. Loading errors and ramp delays sit close behind. In other words, the failures cluster almost exactly at the two airside tracking points where the connectivity is weakest.
That alignment is the whole argument. Resolution 753 was written on the premise that if you can see every bag at every point, you can intervene before it goes wrong — pull a transfer bag forward, flag a mis-load before the hold closes, redirect a container before the tug leaves the stand. But you can only intervene in real time if the data arrives in real time. A batch-synced scan that lands twenty minutes later tells you, accurately and compliantly, about a bag you have already lost. Closing the airside connectivity gap is what turns 753 from a record-keeping exercise into an operational tool.
What a private 5G layer actually changes
A managed private 5G network sized for the airside footprint changes the picture in a specific, unglamorous way: it gives every handheld scanner, every ULD tag reader and every tug a live, owned, guaranteed connection from the moment it leaves the building to the moment it returns. The ramp agent's scan at the hold door reaches the departure-control system before the next bag is lifted. A transfer bag's read on the apron updates WorldTracer while there is still time to act on it.
The same layer carries more than baggage data, which is what makes it justifiable. Ground service equipment reports position and status continuously, so the operations room knows where the tugs and loaders are. Apron cameras feed stand-allocation and turnaround monitoring. The cargo sheds next door — increasingly the busier operation at regional airports — get the same coverage for ULD tracking and temperature-controlled freight. Baggage tracking is rarely the use case that pays for a private network on its own; it is the use case that makes the network's value legible to the people who sign off baggage SLAs, riding on infrastructure that a dozen other airside functions also need.
There are trade-offs, and we would rather name them than gloss over them. A private network is capital up front, against a public SIM that is operating expenditure spread thin. It needs spectrum — in the UK, Ofcom's Shared Access licence framework makes that genuinely straightforward, but it is still a step. And it needs the handheld and tag estate to support it, which for an airport mid-way through a device refresh is a question of timing rather than principle. The case is strongest where the airside footprint is contained, the handler relationships are owned by one or two parties, and the mishandling cost is already showing up on the operations dashboard.
Where this lands for UK airports
For UK operators the regulatory direction is only tightening. IATA's broader baggage-tracking work is pushing from the four-point minimum of 753 towards modern, message-based bag tracking and richer real-time visibility, and the move from older barcode reads towards RFID-tagged ULDs makes continuous airside reads not just possible but expected. Every one of those steps assumes a network that reaches the bag where the bag actually is — on the apron, under the aircraft, in the transfer tunnel — rather than where the cabling happens to run.
We think the regional airports are the natural first movers here, for the same reasons they are the natural first movers on airside private 5G generally: a contained footprint, a short list of ground-handler concessions, and a single operations team that owns both the baggage SLA and the network decision. The hubs will get there too, but with more vendors and more terminals to reconcile. Either way, the conclusion is the same. Resolution 753 drew a line that runs straight through the apron, and the airports that close the airside half of it — rather than batch-syncing their way to nominal compliance — are the ones that will actually stop losing bags.