Flytrex and Wing, two competing U.S. drone delivery operators, flew simultaneously over the same Dallas Fort Worth suburbs using an automated airspace coordination system built by a multi operator consortium.
In two Dallas-Fort Worth suburbs 1.36 miles apart, rival drone delivery operators Flytrex and Wing flew simultaneously for most of January and February 2026, sharing more than 10 hours of low-altitude airspace on 30 of 31 active days. The two operators say the combined ~10,000 overlapping flights ran without an airspace conflict, and the more interesting story is what kept the drones from running into each other: not a human controller, not a single vendor's proprietary system, but an automated airspace-coordination layer run by a multi-operator consortium.
The setup matters more than the headline number. Flytrex and Wing are competitors in a U.S. drone delivery market that has spent years bumping into the same wall: each operator wants to fly delivery drones over suburban yards, but low-altitude airspace has no real equivalent of the radar-based air traffic control that governs manned aviation. Under the FAA's experimental rules for beyond-visual-line-of-sight (BVLOS) drone operations, multiple operators have historically had to coordinate flights manually or fly in segregated zones. That does not scale.
The mechanism that handled the Dallas-Fort Worth overlap is a software service called Unmanned Traffic Management (UTM): automated systems that let operators exchange flight plans in real time and reroute before a conflict occurs, rather than relying on a human controller to separate aircraft. The deployment runs on a framework developed through US UTM Implementation, a consortium of 17 drone operators, including Flytrex and Wing, that governs shared-airspace rules and interoperability. In plain English: when one operator plans a delivery, the other operator's planned route is visible, and if two flight paths would cross at the same altitude and time, the system reconciles them before takeoff or in flight.
Flytrex product manager Shai Karassikov, who co-chairs the US UTM Tech Committee, framed Dallas-Fort Worth as "a proof of concept for the entire industry", and the numbers support the framing for the narrow test he is describing. Between January and February 2026, Flytrex and Wing logged roughly 8,000 deliveries from sites 1.36 miles apart in Little Elm and Wylie, Texas, with combined monthly flights approaching 10,000. The two operators flew simultaneously on 30 of 31 active days, often sharing airspace for more than 10 hours per day. Combined flight volume grew 215% month over month, per Flytrex, which suggests the operators were not throttling themselves to avoid conflicts.
The regulatory pathway behind the milestone matters because it does not depend on a single operator's technology. In November 2024, ANRA Technologies secured the first FAA Letter of Acceptance for a non-vertically-integrated UTM, meaning a third-party software vendor (not an operator's own internal system) could be accepted as the coordination layer for critical-infrastructure drone flights. That approval sits inside the FAA's broader UTM framework, which gives operators a defined route: a UTM Operational Evaluation (UTM OE) and the Notice to Air Missions (NTAP) process under a Letter of Authorization. The Dallas-Fort Worth test is the first commercial deployment of automated UTM for shared delivery airspace in the United States, and it was built on that regulatory spine, not on ad-hoc coordination.
Wing has positioned the work as a strategic flight-coordination milestone, and the trade press has framed it as a long-running problem finally cracking. The framing is half right. The operators have shown that a multi-operator coordination layer can run without a human separating flights in real time, and they have done it at a scale that already produces thousands of overlapping flights per month. The conflict-free figure is real, but it is also self-reported: it is the operators' own metric for what their UTM software caught and rerouted, not an FAA or independent safety determination. The FAA is described as watching the deployment, which fits the UTM OE process: this is operator-coordinated airspace sharing operating inside an FAA framework, not regulator-issued certification of conflict-free operations.
What the Dallas-Fort Worth test does not yet prove is the harder version of the question. Two operators in two adjacent suburbs is a meaningful test of the coordination software, but it is not evidence that the model scales to dense urban cores, to a third or fourth operator sharing the same patch of sky, or to airspaces shared with manned aircraft and helicopter traffic. The 215% growth figure shows demand for the airspace, not capacity of the system under load. Whether the same UTM framework holds when a city has half a dozen operators and not two, and whether the FAA's UTM framework extends to airspaces shared with crewed aviation, are the open questions that will determine whether Dallas-Fort Worth is a proof of concept or a template.
The watch item is whether other operators join the shared-airspace deployments and whether the FAA formalizes the Dallas-Fort Worth model beyond the current UTM OE process. If a third operator begins coordinated deliveries in the same region without incident, the consortium-governance argument moves from plausible to load-tested.