A 23-year-old remote pilot named Trevor Wischnewsky spends his shifts watching a screen full of blinking icons over Dallas-Fort Worth, each one a delivery drone from a different company. On a busy afternoon he tracks up to 10 aircraft at once, flown by four separate operators that, on paper, compete for the same airspace and the same customers. According to a October 9, 2026 report from MIT Technology Review, Wischnewsky works as a remote pilot in command, or RPIC, for FlyTrex, a hexacopter delivery company that operates within a three-mile radius of its hubs. His job did not exist five years ago. It is also, oddly enough, a preview of a much bigger problem now taking shape 240,000 miles away, where NASA engineers are racing to build a traffic-control system for the Moon.
Those two stories, one grounded in suburban Texas and one orbiting the lunar poles, share the same underlying challenge: how do you keep multiple autonomous or semi-autonomous vehicles from colliding when there is no human controller watching every inch of the route. The drone industry is solving it today, in real airspace, with real packages. NASA is solving it on paper and in simulation, ahead of a problem that will arrive the moment more than one spacecraft needs to loiter near the same lunar outpost. Both point to the same conclusion: traffic management, not propulsion or payload capacity, is becoming the hardware-and-software bottleneck of the next decade of flight.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
A New Job Title: Delivery Drone Traffic Controller
Wischnewsky’s role did not exist in any job posting a decade ago. As MIT Technology Review described it, he coordinates traffic involving FlyTrex, Zipline, Amazon, and Alphabet’s Wing delivery drones over the Dallas area, a metro region that has quietly become the densest multi-operator drone delivery test zone in the United States. The outlet quoted him describing how he got into the field: “It was super fascinating,” he said, and after being exposed to the industry, “I just immediately wanted to be a part of it.” Of his actual function in the system, he offered a simple summary: “You’re there as a safety net.” Reporting is careful on one point of terminology: his formal title is remote pilot in command (RPIC), and “drone air traffic controller” is a descriptive comparison used in coverage rather than a confirmed Flytrex job title.
That safety-net framing matters because it describes a hybrid role, not a classic air-traffic-controller job. Wischnewsky is not issuing clearances over radio the way a Federal Aviation Administration controller would at a staffed tower. Instead, he is monitoring an automated system that is already doing most of the deconfliction work in software, stepping in only when something falls outside the expected pattern. Supplementary reporting on the Dallas-Fort Worth drone corridor indicates that FlyTrex and Wing alone logged roughly 8,000 deliveries between January and February 2026 in overlapping airspace around Little Elm and Wylie, two DFW suburbs, with the shared system reportedly deconflicting all submitted flight intents during that stretch without a reported airspace conflict.
Police departments are starting to lean on the same low-altitude drone fleets for very different purposes. In Colorado, Commerce City recently deployed four drones to help track down a wrong-way driver after an I-76 crash, a reminder that the same airspace-sharing problem facing delivery companies is starting to show up in public-safety operations too, where multiple agencies increasingly fly in the same limited low-altitude corridor.
That is the headline number worth sitting with: zero conflicts across thousands of flights from four independent, commercially competing drone fleets sharing the same low-altitude airspace. It is the kind of statistic that regulators and competitors alike are watching closely, because it is effectively a real-world proof point for whether autonomous airspace sharing can scale past a single operator.
How the Dallas-Fort Worth Drone Testbed Actually Works
The Dallas-Fort Worth area has become, in effect, a live testing ground for what the industry calls unmanned aircraft systems traffic management, or UTM. The core idea is that participating drones share their flight coordinates in real time, rather than relying on a single centralized control tower the way commercial airliners do. Instead of one authority issuing instructions to every aircraft, each operator runs its own UAS Service Supplier, or USS, and those separate USS systems exchange flight-intent data with each other through a shared protocol.
That interoperability layer reportedly follows the ASTM F3548-21 standard, an industry specification built specifically to let independent drone operators swap operational data without needing to merge their underlying fleets or software stacks. In practice, that means a FlyTrex hexacopter delivering a food order near Wylie can “see” that a Wing aircraft is inbound on a crossing path, and the system automatically adjusts one of the routes, altitude bands, or timing windows to keep the two apart. Coordination reportedly spans four dimensions: route, altitude, timing, and whatever operational constraints each flight carries, rather than relying purely on static no-fly zones.
It is worth being precise about what counts as hardware in this picture, because there is no single physical control box that each drone plugs into. The real hardware layer is distributed: each operator’s onboard avionics, navigation sensors, communications radios, telemetry links, and ground infrastructure such as FlyTrex’s rooftop docking stations, Wing’s curbside AutoLoader pickup points, and Zipline’s restaurant-side loading zones called Zipping Points. The “traffic controller” in this system is mostly a software-and-network service layer sitting on top of that distributed hardware, with a human like Wischnewsky watching for edge cases the automation was not built to resolve alone.
Who’s Flying Over Dallas: The Four Operators Compared
Each of the four companies sharing DFW airspace has taken a different hardware approach, and the differences matter for how the shared traffic system has to behave. FlyTrex runs small hexacopters rated for roughly 6.6 pounds, or 3 kilograms, of payload per flight, and has leaned into pre-positioning infrastructure: its Flytrex Dock lets a drone land and sit at a merchant location before an order even comes in, cutting the time between order and liftoff. Amazon’s current delivery aircraft, the MK30, is reported at around 5 pounds of payload, an 83-pound maximum takeoff weight, a top speed near 73 mph, and a service radius of about 7.5 miles. Wing flies hybrid hover and fixed-wing aircraft cruising near 65 mph, with a network reportedly reaching about 75% of the DFW-area population from its existing hubs. Zipline, known for its longer-range medical delivery heritage, uses dedicated loading points at partner restaurants ahead of launch.
| Operator | Aircraft Type | Reported Payload | Reported Speed / Range | Ground Infrastructure |
|---|---|---|---|---|
| FlyTrex | Hexacopter | ~6.6 lb (3 kg) | 3-mile operating radius | Rooftop “Flytrex Dock” pre-positioning |
| Amazon Prime Air | MK30 multirotor | ~5 lb | ~73 mph top speed, ~7.5-mile radius | Hub-based launch sites |
| Alphabet’s Wing | Hybrid hover/fixed-wing | Reported in low single-digit lbs | ~65 mph cruise | Curbside “AutoLoader” pickup |
| Zipline | Fixed-wing / P2 platform | Reported up to 8 lb (P2) | Longer-range medical-delivery heritage | Restaurant “Zipping Points” |
What stands out is that none of these companies share a hardware platform, yet their aircraft fly the same corridors every day. That is only possible because the traffic coordination happens above the hardware layer, in the shared data exchange, rather than inside any single company’s flight computer. It is a markedly different model from how commercial aviation handles shared airspace, where aircraft from different airlines still answer to one unified ground-based control authority.
From Suburban Skies to Lunar Orbit
Now zoom out, literally, to about 240,000 miles above that same Texas airspace. NASA is working through a strikingly similar problem for a much higher-stakes environment: the near-rectilinear halo orbit, or NRHO, that will host the agency’s Gateway space station and the spacecraft visiting it during the Artemis program. Diane Davis, an associate professor of space engineering at Texas A&M who worked on the traffic-management research, put the stakes plainly: “Collisions and serious damages could happen. To ensure crew safety and mission success, effective traffic management in the NRHO is crucial.”
The parallel to Dallas-Fort Worth is not perfect, but it is instructive. Where DFW has four commercial drone operators sharing low-altitude airspace, Gateway’s NRHO will eventually have NASA’s Orion crew capsule, uncrewed logistics vehicles carrying supplies, and crewed lunar landers all needing to arrive, loiter, and depart from the same narrow orbital corridor. Unlike a drone hovering over a parking lot, a spacecraft in NRHO cannot simply stop and wait in place. The orbit itself is dynamically unstable, meaning both Gateway and every visiting vehicle has to perform regular station-keeping maneuvers just to stay on their intended path, according to CNET’s reporting on the lunar traffic-control research.
The “String of Pearls” Solution
The traffic-management concept that researchers simulated for NRHO works less like an air-traffic radar screen and more like a parking queue. Rather than letting visiting spacecraft drift independently and hope for the best, the system assigns each vehicle a calculated loiter position ahead of or behind Gateway, holding it there until its turn to dock or depart arrives. The Week’s coverage of the research describes the resulting pattern as a “string of pearls” arrangement, with spacecraft strung out along the orbit at timed intervals rather than clustered together.
That queuing system reportedly underwent extensive simulation testing, running through scenarios involving multiple spacecraft loitering near Gateway at once while accounting for realistic failure modes such as thruster malfunctions and navigation uncertainty, rather than assuming every vehicle behaves perfectly. Nautilus magazine’s account of the simulations frames the work as treating Gateway less like a single destination and more like the first spaceport design problem humanity has had to solve for deep space, where the usual assumption of empty, uncontested orbit no longer holds once multiple programs start sending hardware to the same orbital neighborhood.
Testing of the concept is expected to get its first real-world exposure with the Capstone 02 mission, with additional validation planned for NASA’s next crewed Artemis mission, targeted for 2027. That timeline means the “moon traffic control” system Dallas-area headlines compare to earthbound drone coordination will remain largely theoretical for at least another year, even as the underlying math has already been simulated extensively on the ground. It also arrives alongside a broader scramble over the hardware that will support deep-space missions, including SpaceX’s reported push to secure roughly $40 billion in NVIDIA chips for orbital AI workloads, underscoring how much compute and coordination infrastructure now rides alongside any crewed lunar mission.
Terrestrial Drones vs. Lunar Orbit: A Side-by-Side Comparison
Laying the two traffic-management problems side by side shows how much harder the lunar version is, even though both are described using the same vocabulary of coordination, deconfliction, and shared situational awareness.
| Factor | Dallas-Fort Worth Drone UTM | NASA NRHO / Gateway Traffic Management |
|---|---|---|
| Vehicles coordinated | FlyTrex, Zipline, Amazon, Wing aircraft | Orion, Gateway, logistics craft, landers |
| Status in 2026 | Operating with reported zero conflicts across thousands of flights | Simulated; first live test expected via Capstone 02 |
| Human role | Remote pilot monitors automation as a “safety net” | Mission planners design loiter windows pre-flight |
| Core coordination method | Real-time flight-intent sharing via USS network (ASTM F3548-21) | Pre-planned loiter slots in a “string of pearls” sequence |
| Biggest technical obstacle | Multi-operator interoperability at low altitude | Orbital instability requiring constant station-keeping |
| Next milestone | Scaling beyond ~8,000 monthly flights in one metro | Capstone 02 test, further validation targeted for 2027 Artemis mission |
The comparison also exposes a key difference in risk tolerance. A drone deconfliction failure in Dallas means a near-miss, a delayed delivery, or at worst a damaged aircraft and a customer complaint. A deconfliction failure in NRHO means a potential loss of a spacecraft and, depending on timing, a crew. That asymmetry is exactly why NASA’s team, as Davis described it, has spent years running thousands of simulated scenarios before putting any part of the concept near an actual crewed mission, where the drone delivery industry has been comfortable iterating in live airspace with paying customers’ food orders riding along.
Historical Context: From Air Traffic Control to Autonomous Airspace
Commercial aviation’s air traffic control system took decades to mature into the centralized, radar-and-radio model flyers rely on today, built up gradually as passenger volume grew and near-misses forced regulatory change. Drone delivery is compressing a similar maturation curve into a handful of years, but through a fundamentally different architecture: distributed software coordination instead of a single central authority. Reporting between October 6 and October 21, 2026 indicates the UK may be moving the same way, away from a single-ANSP or “monolithic” UTM model toward federated and decentralized service provision.
The growth curve behind that compression has been steep. According to McKinsey & Company research, global drone deliveries increased by more than 80% from 2021 to 2022, reaching almost 875,000 deliveries worldwide, with healthcare accounting for 45% of all drone deliveries in 2022 and rising to 54% of deliveries in the first half of 2023. A separate McKinsey analysis found that more than 2,000 commercial drone deliveries were occurring every day worldwide as of early 2022, with over 660,000 total commercial deliveries completed in the three years leading up to that point. Those figures predate the current DFW multi-operator milestone by several years, but they show the trajectory that made a job like Wischnewsky’s inevitable: once delivery drone volume crosses a certain density threshold in a single metro area, informal coordination between competing operators stops being viable, and some kind of shared traffic-management layer becomes mandatory rather than optional.
Space traffic management has its own, much older history, dating back to Cold War-era satellite tracking, but coordinating human-rated vehicles that loiter and rendezvous near a shared outpost in deep space is a genuinely new category of problem, distinct from tracking debris or monitoring satellite collision risk in Earth orbit.
Market Impact: Why Investors and Regulators Are Paying Attention
For the drone delivery sector, the Dallas-Fort Worth deconfliction numbers function as a credibility test. Amazon, Alphabet’s Wing, Zipline, and FlyTrex have all raised capital or committed corporate resources on the premise that drone delivery can scale into dense metro airspace without constant human intervention. A reported record of zero conflicts across thousands of flights is the kind of operational data point that can unlock expanded Federal Aviation Administration approvals for beyond-visual-line-of-sight, or BVLOS, flight, which remains one of the biggest regulatory bottlenecks limiting how far and how densely these companies can fly.
On the lunar side, the market impact is more structural than immediate. NASA’s Artemis program depends on multiple contractors, including spacecraft and lander providers, trusting that the agency has a credible plan for keeping their hardware safe once more than one vehicle is operating near Gateway simultaneously. A validated traffic-management framework is effectively an insurance policy for every company with hardware riding on an Artemis mission, reducing the operational uncertainty that would otherwise complicate mission insurance, crew safety certification, and launch scheduling around Gateway’s increasingly busy manifest.
The Regulatory Picture: FAA Rules Still Catching Up
Even with a working technical system in Dallas-Fort Worth, the regulatory framework around it is still being written in real time. The FAA’s public safety notices portal remains a key channel through which operators and the agency communicate evolving rules for drone operations, and BVLOS authorization continues to be granted on a case-by-case basis rather than through a single blanket rule covering multi-operator UTM deployments like the one running in DFW. That means the entire shared-airspace model currently depends on a patchwork of individual waivers rather than a settled national standard, which is itself a form of regulatory risk for every company involved. Regulators elsewhere are signaling that this layer matters: NATS described UTM as a critical next step on October 16, 2026, particularly as drone demand grows in busy airspace.
A similar regulatory gap exists for lunar traffic management, except there the open question is not which domestic agency has jurisdiction but which international framework, if any, will govern lunar orbital slots as more countries and private companies send hardware toward the Moon over the next decade. That regulatory lag is not unique to drones and spacecraft, either; self-driving trucks recently won a five-year federal beacon exemption in the United States, another sign that autonomous-vehicle rulemaking across every domain, air, road, and orbit, is still playing catch-up with the hardware already operating in the field.
Competitive Landscape: Four Companies, One Shared System
What makes the Dallas-Fort Worth case unusual in tech competition terms is that FlyTrex, Zipline, Amazon, and Wing are direct rivals for the same delivery customers, yet they are relying on the same underlying coordination standard to keep their aircraft apart. None of the four has a proprietary traffic-management moat here, because the deconfliction layer is explicitly built to be interoperable across operators rather than locked to one company’s fleet.
That is a notably different competitive dynamic than, say, cloud computing or chip design, where vendors fight to keep customers inside a proprietary stack. Here, every operator benefits from a shared, open coordination layer, because a deconfliction failure involving any one company’s drone would almost certainly trigger regulatory scrutiny for every other operator flying in the same airspace. Competing on drone range, payload, delivery speed, and ground infrastructure, as the table above shows, while cooperating on shared safety infrastructure, may become the template other autonomous-vehicle industries follow as they scale past single-operator pilots.
What Comes Next: Five Predictions
- More U.S. metro areas will likely see multi-operator drone delivery testbeds modeled on the Dallas-Fort Worth deconfliction framework within the next 12 to 18 months, as operators push the FAA for expanded BVLOS approvals using DFW’s safety record as supporting evidence.
- The “remote drone traffic controller” job description will likely expand beyond single-operator monitoring into formal cross-operator coordination roles, as the number of simultaneous flights per monitored zone grows past the current reported peak of around 10.
- NASA’s NRHO traffic-management concept will likely see its first operational validation tied to the Capstone 02 mission before the broader framework is applied to the crewed Artemis mission targeted for 2027.
- Pressure will likely grow on the FAA to replace the current waiver-by-waiver BVLOS approval process with a standardized national framework, particularly if other metro areas replicate the DFW zero-conflict track record.
- Expect closer public comparisons between terrestrial UTM and lunar traffic-management research, as both fields borrow vocabulary and, in some cases, personnel from each other’s technical communities.
The Bigger Picture: Traffic Management as Infrastructure
Neither story, taken alone, looks like a hardware story in the traditional sense. There is no new chip, no new GPU, no flagship device launch here. But both the Dallas-Fort Worth drone corridor and NASA’s lunar orbit research point to the same underlying truth about where autonomous-vehicle hardware is heading next: the bottleneck is no longer building the vehicle, it is building the shared infrastructure that lets many vehicles, built by many different companies, occupy the same space safely at the same time.
That infrastructure, whether it is a USS network exchanging flight-intent data over Wylie, Texas, or a simulated loiter-slot schedule for a lunar Gateway station, is becoming as commercially and strategically important as the vehicles it coordinates. Reports describing the lunar system as the Moon’s “first airport” are not just a colorful framing; they reflect a genuine shift in how engineers are starting to think about orbital real estate, treating it less like empty space and more like a finite, schedulable resource that needs active management the moment more than one serious operator shows up. It is the same shift already visible in other high-speed autonomous hardware programs, including SpaceX’s Starship Flight 15, where analysts are watching payload and cadence numbers as closely as engineers once watched raw thrust figures, and in NASA’s own history of extreme-speed vehicles, where the Space Shuttle’s Mach 25 reentry speed, eight times faster than the SR-71, still stands as a benchmark for how far flight-control systems have had to evolve to keep up with vehicle performance.
What This Means for the Drone Delivery Industry
For FlyTrex, Zipline, Amazon, and Wing specifically, the near-term implication is that reliability data, not raw delivery volume, is becoming the currency that matters most to regulators. A company that can point to a clean safety record inside a shared, multi-operator airspace has a much stronger case for expanded BVLOS authorization than one still operating under single-operator restrictions. That shifts competitive pressure away from simply flying more drones and toward flying more drones safely inside systems other companies also depend on, a subtle but important change in how these companies will likely pitch themselves to regulators and investors through the rest of 2026 and into 2027. Flytrex’s own site says it is delivering across Dallas-Fort Worth, with new metros coming in early 2027.
Frequently Asked Questions
What does a delivery drone traffic controller actually do?
A delivery drone traffic controller, or remote pilot in command, monitors an automated airspace-deconfliction system and intervenes when a flight pattern falls outside what the automation is built to resolve on its own, functioning more as a safety monitor than a traditional air traffic controller issuing manual clearances.
Which companies share drone delivery airspace in Dallas-Fort Worth?
Reports describe FlyTrex, Zipline, Amazon, and Alphabet’s Wing as the four operators flying delivery drones in overlapping Dallas-Fort Worth airspace, coordinated through a shared unmanned aircraft systems traffic management framework.
How many drones can one remote pilot monitor at once?
According to MIT Technology Review’s reporting, FlyTrex pilot Trevor Wischnewsky monitors up to 10 drones simultaneously during his busiest shifts across multiple operators’ fleets.
What is NASA’s near-rectilinear halo orbit traffic management system?
It is a simulated traffic-management concept for spacecraft operating in the near-rectilinear halo orbit around the Moon, where Gateway and visiting vehicles like Orion, logistics craft, and landers would be assigned timed loiter positions, described by researchers as a “string of pearls” arrangement, to avoid collisions.
When will NASA’s lunar traffic-management system be tested?
The concept is expected to receive an initial test tied to the Capstone 02 mission, with further validation planned for NASA’s next crewed Artemis mission, currently targeted for 2027.
Why is coordinating spacecraft near the Moon harder than coordinating drones on Earth?
Unlike a drone, a spacecraft in near-rectilinear halo orbit cannot simply stop and wait, because the orbit is dynamically unstable and requires continuous station-keeping maneuvers, and a deconfliction failure risks a crewed spacecraft rather than a delivery drone.
What standard do drone operators use to share flight data in Dallas-Fort Worth?
Reporting describes the interoperability framework as based on the ASTM F3548-21 UAS Service Supplier standard, which lets independent operators exchange real-time flight-intent data without merging their underlying systems.
Is drone delivery traffic management the same as commercial air traffic control?
No. Commercial air traffic control relies on a single centralized authority directing aircraft, while drone UTM in Dallas-Fort Worth is built as a distributed system where each operator’s software shares data with the others, and a human remote pilot monitors the results rather than issuing direct clearances.
