Two commercial drone delivery operators flew roughly 8,000 overlapping flights above the same Texas suburbs in January and February, on 30 of 31 active days, often sharing the sky for more than ten hours at a stretch. Every operational intent was deconflicted. There were no airspace conflicts.
There was also no way for either of them to tell the other that an aircraft was in trouble.
That is the part worth understanding about the arrangement Wing and Flytrex have built over Little Elm and Wylie, in the Dallas-Fort Worth metroplex. It is a real achievement and it is narrower than the air-traffic-control framing suggests.
What they actually built
The two companies began exchanging flight intent data in May 2025, the first time two commercial delivery operators in the US ran unmanned traffic management technology in daily operations over shared airspace. Each system publishes where its aircraft intend to fly; the other adjusts automatically. No human at Wing calls a human at Flytrex.
It runs on ASTM F3548-21, the USS interoperability standard, under the FAA’s UTM Operational Evaluation. The point of using a published standard rather than a private integration is that any operator implementing it can join, which is what makes the Dallas arrangement interesting beyond Dallas.
The scale-up is the news. Combined daily operations rose 215% between January and February, and Flytrex now reports approaching 10,000 overlapping flights a month with other operators. In under a year the pattern went from a handful of coordinated flights to thousands.
Strategic, not tactical
Here is the distinction the announcements tend to blur.
What Wing and Flytrex have is strategic deconfliction: aircraft exchange intended routes before flight and adjust so they never need the same piece of sky at the same moment. It works, and the Dallas numbers show it works at volume.
What it is not is tactical deconfliction — the thing that happens when an aircraft stops doing what it intended. There is no in-flight emergency broadcast between the two operators. If a Flytrex aircraft loses GPS, suffers a failure or has to put down unexpectedly, Wing’s system is not automatically told. Each operator runs its own emergency and contingency landing procedures under its own separate FAA approvals.
That is the inverse of how conventional air traffic control earns its keep. Routine separation is the routine part. The reason controllers exist is to clear everyone else out of the way when one aircraft is in trouble.
Why the gap matters more as this scales
The failure cases in this industry are not hypothetical. Amazon’s MK30 collided with a crane in Arizona in October 2025, an incident that drew NTSB and FAA scrutiny.
An unshared emergency state is survivable when one operator has the sky largely to itself. It gets harder to defend as a design choice when three or four operators are flying the same suburb at commercial density — which is the explicit direction of travel. Wing is heading for 270 Walmart locations by 2027. Zipline has signed with Uber Eats. DoorDash has its own Part 135 certificate now.
Strategic deconfliction assumes aircraft do what they said they would. That assumption holds on almost every flight, and the exceptions are exactly the moments when coordination is worth the most.
None of this makes the Dallas work less significant. Building a standards-based system that two competitors run in daily commercial operation, without manual coordination, is the harder organisational problem and they solved it. It is a foundation that a tactical layer can be built on, which is more than the industry had eighteen months ago.
What to watch
Whether tactical coordination gets added to the same standards track is the question. ASTM F3548-21 governs strategic coordination between USS providers; the emergency-state problem sits outside it, and no equivalent commercial implementation has been announced.
The FAA’s Part 108 rule may force the issue. It went to the Office of Information and Regulatory Affairs on 10 July, the last stop before publication, and would replace site-by-site BVLOS waivers with a standing framework. A standing framework means more operators in more shared airspace, faster. Whether the rule addresses multi-operator contingency handling — or leaves it to each operator’s individual approvals, as now — is one of the more consequential details to look for when it publishes.
