Summary

  • The Metropolitan Airports Commission says it plans to share MSP's private 5G connectivity with airlines, concessionaires and other partners.
  • An operating network already exists. The next question is how independent users obtain access and who answers when their needs conflict with airport operations.

An airport can decide which of its own vehicles joins its network. Giving an airline or concessionaire the same connectivity introduces a different relationship: another organisation has its own devices, support staff and expectations. That is the commercial significance of the Metropolitan Airports Commission's latest private 5G announcement at Minneapolis-St. Paul International Airport.

In its 9 September disclosure, the commission, or MAC, describes an Ericsson Private 5G network serving a five-square-mile campus. Cameras, ticketing equipment and mobile vehicles are among the uses. It also says it plans to share connectivity with airlines, concessionaires and other airport partners. The latter is a plan, not evidence that all those organisations have joined or signed a paid service agreement.

The new boundary is between organisations

The immediate rationale is practical. MAC describes private wireless as an alternative to extending Wi-Fi or installing more fibre for these operational uses. Tram video monitoring is an early example. Its official's claim of continuous video access is useful customer testimony, not an independently measured availability guarantee.

Nor should this announcement be read as the network's first day of life. An Insight case study dated 31 October 2025 already described the project. It named Insight Public Sector for end-to-end delivery and Pierson Wireless for installation, and stressed the importance of maintaining the system over time. The September news adds a current account from the airport; it does not establish a new procurement date.

Extending the service to separate organisations changes what has to be managed. A shared radio footprint might spare each user a separate connectivity project. But someone must still decide whose equipment is admitted, who may change its permissions and where an incident is escalated. Those are service obligations, even if the airport never charges a separate connectivity fee.

A dashboard cannot settle the bargain

Ericsson's product documentation describes a cloud-based management portal covering provisioned devices and role-based access rights, alongside an on-premises controller. Such capabilities offer tools for administering a network. They do not tell a concessionaire which rights it will receive at MSP or give it authority over an airport-critical application.

The distinction matters most when interests diverge. A tenant wants predictable service for its own work; the airport must protect its wider operation. Clear decisions about access, priorities and support could make a shared network more valuable than a collection of point solutions. Without those decisions, adding users could also add disputes over who owns a fault.

No tenant tariff, contract term, revenue-sharing model or service-level commitment is disclosed in the reviewed airport announcement. Private 5G is therefore an operating platform with a proposed wider user base, not yet evidence of a new wholesale revenue line.