UPS Flight Forward has been quietly moving from regulated pilot projects toward operational BVLOS flights, and the latest rounds of tests underline a pragmatic, incremental path to scaled drone logistics. The company is running Matternet M2 systems under FAA-authorized BVLOS frameworks and is using a Remote Operations Center model to manage flights, which together point to a near-term commercial role for drones in last mile and intra-campus logistics rather than broad consumer doorstep delivery overnight.
The technical setup that UPS and its partners are using is worth unpacking because it shows how the industry is solving the core safety problem for BVLOS. The Matternet M2 is a small, purpose-built delivery quadcopter that has been certified and type-approved by regulators. UPS Flight Forward received specific FAA authorization allowing BVLOS operations using Matternet systems, and the operator is relying on ground-based surveillance sensors to reduce the need for human visual observers. The Matternet release describing that authorization explains how ground radar or similar sensors can scan the skies and feed alerts back to a remote pilot in command. That surveillance approach reduces costs and makes longer routes practical when the infrastructure covers the operational footprint.
Those approvals have not been purely theoretical. UPS Flight Forward and Matternet recorded what the companies describe as true BVLOS delivery flights in the United States during late 2024, with operations run from a remote operations center in Kentucky. The milestone referenced by Matternet notes November 17, 2024 as the date UPS completed BVLOS flights using the Matternet M2 with remote management from Fisherville, Kentucky. That matters because it moves BVLOS from isolated waiver testing toward routine operations under Part 135 authorizations.
Regulators have been deliberate but constructive. The FAA publicly authorized UPS Flight Forward and others to conduct BVLOS operations in 2023, making clear that ground-based surveillance plus a rigorous safety case can be an acceptable risk mitigation strategy. The FAA announcement highlighted the role of ground-based detection systems and signaled that data from these early programs will inform broader rulemaking. Reuters reporting at the time also noted that UPS planned flights in multiple states and that the Remote Operations Center concept is central to how the company intends to scale.
What are the operational implications of these tests? First, the ROI case is strongest for high-value, time-sensitive payloads and point-to-point hops that bypass road traffic. That is why much of the commercial drone delivery work to date, including UPS and Matternet, has emphasized medical samples, lab-to-lab shuttles, and healthcare logistics. Second, the use of ground-based sensors combined with centralized remote pilots enables a single pilot to supervise multiple aircraft, sometimes described as a small fleet-to-pilot ratio. That economy of scale is a prerequisite for financially sensible operations, but it also shifts the reliability burden onto sensors, communications networks, and software. The Matternet authorization specifically mentions centralized mission control and multi-aircraft supervision as a route to better economics.
There are several technical and policy gaps that these tests expose, and those need fixing if BVLOS delivery is to expand safely. The first is surveillance coverage. Ground-based radar and optical sensors are effective when sited and networked properly, but they require shared access models when multiple operators want to operate in the same airspace. That means regional, interoperable surveillance services or UTM capabilities are essential. The FAA BEYOND initiatives and Phase 1 Phase 2 work are explicitly aimed at turning the ad hoc waiver world into a rules-based regime with performance standards for surveillance, detect-and-avoid, and communications. Continued data sharing from operators like UPS will be central to that rulemaking.
The second gap is contingency management. BVLOS flights remove the remote pilot or observer from the immediate visual scene, so robust failover behaviors, hardened command and control links, and clear procedures for bent-wire scenarios are mandatory. Tests to date emphasize safe recovery logic, geo-fencing, and automated return-to-base or loitering fail-states, but those behaviors must be stress tested against a wide range of real world conditions including low altitude GA traffic, birds, and urban clutter.
Finally, community acceptance remains a social constraint. Noise, privacy, and perceived safety are not solved by approvals alone. Operators will have to publish safety data, route density, complaint handling metrics, and measurable targets for noise reduction and privacy protections if they want broad local support. The business model that is emerging, and that UPS appears to be pursuing, relies first on healthcare and business-to-business corridors where stakeholders are clear and benefits are tangible, rather than on generalized consumer last-mile.
Bottom line: UPS testing BVLOS packages under Matternet systems and FAA-authorized frameworks is a practical step rather than a giant leap. The partnership model, ground-based surveillance, and remote operations center approach collectively demonstrate a path to scaling safe, repeatable drone logistics for specific use cases. That path is contingent on sharing operational data, interoperable surveillance infrastructure, and sensible, performance-based rules from regulators. For engineers and operators the technical hurdles are tractable. For the industry at large the harder work is regulatory harmonization and community trust, which will determine whether these tests turn into reliable, widespread services.