Wing and Walmart Just Named Seven New Drone Delivery Metros. Here Is the Airspace and Approval Work Each One Will Need.

By Wesley Alexander • June 11, 2026 • 8 min read

Tactical Summary

On June 8, 2026, Wing and Walmart announced seven new metro markets for their drone delivery partnership: Memphis, New Orleans, Philadelphia, Phoenix, San Diego, the San Francisco Bay Area, and Salt Lake City. That brings the planned footprint to nearly 20 U.S. markets, on top of routes already flying in Dallas-Fort Worth, Metro Atlanta, and Greater Houston, and previously announced launches in Orlando, Tampa, Charlotte, St. Louis, Cincinnati, Los Angeles, and Miami. The companies are still pointing at the same January 2026 target: more than 270 locations reaching over 40 million Americans by 2027.

The retail framing writes itself. Sixty-mph drones, tether delivery to the driveway, orders in 30 minutes, over one million commercial deliveries completed. What the press release does not spell out is the regulatory production line that has to run behind every one of those seven city names, and what the rest of us operating in those metros should expect as it does.

The Approval Pattern Is Now Repeatable, and That Is the Story

Wing is not waiting for Part 108 any more than anyone else gets to. Each market expansion runs on the toolbox that exists today: Part 135 air carrier authority, exemptions, operating specifications amendments, and site-by-site environmental review under NEPA. We walked through exactly what that looks like in practice when the FAA opened comment on Wing's Houston environmental assessment: up to 75 nests, 24 aircraft per nest, 400 deliveries per operating day per site, all evaluated as a metro-scale network rather than a demonstration route.

Houston was the template. Seven new metros means running that template seven more times, each with its own environmental assessment, its own airspace coordination, its own community engagement cycle, and its own operating specifications work. Wing's stated approach is a phased rollout with local-leader engagement before each launch, which tracks with how Houston was handled.

For operators, the takeaway is that metro-scale BVLOS delivery is no longer a one-off science project getting bespoke treatment. It is a repeatable approval pipeline, and the FAA is processing it as one. When the Part 108 framework does land, the companies that built these pipelines under Part 135 will convert fastest, because the safety cases, data, and community track record already exist. Everyone still operating purely on waivers and exemptions should be studying that playbook, not just the rule docket.

Look at the Airspace These Seven Names Actually Sit In

This is where the operator read diverges hardest from the retail read. The seven new metros are not easy airspace:

Philadelphia: PHL Class B, dense Northeast corridor traffic, and proximity to the Washington-New York flow. Low-altitude integration here is a different problem than suburban Texas.
Phoenix: PHX Class B plus one of the busiest general aviation and flight-training environments in the country. Deer Valley and Falcon Field generate constant low-altitude VFR traffic exactly where delivery routes want to live.
San Diego: SAN Class B layered with extensive military airspace, naval helicopter operations, and a coastal terrain squeeze that concentrates everything into narrow corridors.
San Francisco Bay Area: three Class B and C primary airports in close proximity, marine layer weather that compresses usable VFR altitudes, and terrain.
Salt Lake City: SLC Class B against mountainous terrain, with strong seasonal winds and density altitude swings that matter for small aircraft performance.
Memphis: the FedEx superhub. Overnight cargo banks make this one of the most schedule-critical pieces of airspace in the world, and low-altitude operations near the hub will be scrutinized accordingly.
New Orleans: MSY Class B plus the Gulf helicopter ecosystem and hurricane-season operational realities.

None of this makes the expansion unworkable. Wing's model flies typically below 400 feet AGL in defined service areas, and the Houston assessment shows how the FAA evaluates that envelope. But cumulative low-altitude density is becoming a real planning factor in these metros. Police and medical helicopters, news aviation, flight training, existing Part 107 operators, and now recurring delivery traffic are all sharing the same urban volume. If you fly commercially in any of these seven markets, the practical effects to anticipate are more structured UTM-style coordination, more attention on Remote ID compliance across the board, and less tolerance for operators who treat the airspace as empty because it looks empty.

What Operators in These Markets Should Do Now

If you run a drone program, a public-safety unit, or a commercial operation in one of these seven metros, the expansion is actionable before the first nest is installed:

Track the environmental assessment when it publishes for your metro. The Houston EA comment window was the moment to put noise, routing, and deconfliction concerns on the record. Each new market should get its own review cycle, and substantive comments get written responses. That is leverage, and most local operators never use it.
Map your operating areas against likely nest geography. Wing sites nests in commercially zoned retail property with roughly a six-mile service radius. If your inspection routes, DFR launch points, or training areas sit inside plausible service circles, plan deconfliction now rather than after routes are active.
Get your own house in order on Remote ID and documentation. As delivery networks scale, low-altitude airspace gets more visible to regulators, not less. Sloppy compliance that nobody noticed in 2024 becomes conspicuous when an Alphabet subsidiary is flying structured routes overhead and logging everything.
Watch community sentiment, because it transfers. Delivery drones are about to become the most visible drone operations in these cities. When an incident happens, as it did when an Amazon MK30 came down on a Texas apartment complex, public reaction does not stay neatly contained to the company involved. Every operator in the metro inherits the trust climate.

The Scaling Question Nobody Should Skip

One number worth holding onto: 270+ locations serving 40 million Americans by 2027 is infrastructure-scale aviation, run by a Part 135 certificate holder, sited in shopping center parking lots. The aviation system has never absorbed distributed, neighborhood-adjacent air operations at this density before. The Houston EA's maximum planning values (tens of thousands of theoretical daily flights in one metro) were the first official look at what regulators are being asked to evaluate. Seven more markets means seven more versions of that question, each in more complicated airspace than the last batch.

That is also why this expansion matters beyond delivery. The data Wing generates across 20 metros, on detect-and-avoid performance, C2 link reliability in urban RF environments, noise complaints per thousand flights, and community acceptance, will shape what Part 108 compliance looks like in practice for every BVLOS operator. The delivery companies are running the experiment. The rest of the industry will operate under the rules written from its results.

If your organization operates in one of these markets and needs the airspace coordination picture, comment-window strategy, or BVLOS authority path mapped before the nests arrive, that is exactly the kind of work UAVHQ does.

Sources

Wing Walmart drone delivery expansion Part 135 BVLOS Part 108 environmental assessment Class B airspace Remote ID UTM Memphis Philadelphia Phoenix San Diego Bay Area Salt Lake City New Orleans