Shared Sky · Dallas–Fort Worth

Three delivery companies. One sky.

Two hours of modelled drone deliveries over a 12 × 12 km patch of Dallas–Fort Worth. Each arrow is a drone (a ring while it hovers). Red marks are planned conflicts between drones of different companies.

planned conflicttap a name to hide it
Heights
Day
0:00:00
Personal simulation project from public data; not affiliated with Wing, Zipline, Amazon or the FAA; not flight data or advice. Heights and speeds come from FAA filings; the sites are a modelled build-out, not real locations, the low blocks under the drones are a stand-in, and the downtown towers are real buildings from OpenStreetMap (© OpenStreetMap contributors), shown as a backdrop outside the simulated area. Heights are drawn 10× taller so the layers show. Drag to turn; right-drag, Shift-drag, two fingers or arrow keys to move around; double-click to fly there; scroll or pinch to zoom; tap a red mark for details. Drones are drawn as arrows many times their real size.
Shared Sky · drone traffic simulation

With Amazon at its best-sourced heights, sharing out heights cuts planned conflicts between drone companies by 73%.

Where Amazon flies decides it. Amazon told Richardson council it flies out at about 69 m (225 ft); its FAA filings for Florida, Detroit and Kansas City put the return trip anywhere in 85–115 m, which includes Zipline’s 101 m cruise. Only if Amazon came home near the 400 ft (122 m) maximum in its filings, a height above every FAA-filed return band (at most 377 ft) that only an informal Amazon staff remark supports, would the benefit fall to about 35%. The 73% (95% interval 66–80% across 10 random layouts of Wing and Zipline sites, not model error; Houston 72%) assumes 10 m of height between companies is enough; if 15 m were needed it would be 45%. The headline uses the filed DFW site counts, with Amazon’s real sites and Wing and Zipline sites placed at random; the animation below is a denser test patch: sites every 3 km, about 9 times as tightly packed as the filed layout, so it shows roughly 75 times more planned conflicts per square km than the headline study (77 in 2 hours over 144 km² against 22.2 an hour over 6,400 km²; Zipline’s DFW filing is 400 flights a day per site, under half its Houston figure).

A model of a possible future build-out, not today’s traffic. Which DFW sites fly today is not public; the question is what happens as the companies build out. Six of Amazon’s seven DFW sites are real, geocoded locations; Wing’s and Zipline’s are placed at random because their full site lists are not public. The model flies planned paths only; it does not simulate collisions or avoidance. A “planned conflict” means two planned paths of different companies within 30 m sideways and less than 10 m vertically, with no coordination between companies. Some operators already share flight plans before take-off (ASTM F3548 is the industry standard): in Little Elm and Wylie, Wing and Flytrex reported about 8,000 overlapping flights in January–February 2026 with zero conflicts between their plans (Flytrex is not modelled here). So this is a reference point for how much height sharing removes, not a picture of today’s practice. The shared-out layers are 10–20 m apart, so the cut assumes 10 m between companies is enough (see Results for 15 m and 20 m).

Personal showcase. A personal, unaffiliated simulation project, built for learning and as a portfolio piece, using only publicly available FAA filings and public reports. Not affiliated with, endorsed by or reviewed by Wing, Zipline, Amazon or the FAA. Results come from a model, not real flight data, and are not safety, operational or legal advice.

Built with the Shared Sky engine · studies written down before they ran (since 22 Oct 2026), failed predictions reported · forgottenl5
0planned conflicts between drone companies so far
A simulation from public FAA filings over a modelled build-out, not real traffic. Not affiliated with Wing, Zipline, Amazon or the FAA.
Loading 2 hours of flights… (a few MB the first time)