Shared Sky · planned-operations engine · runs in your browser

Shared Sky Lab

Set up a Houston-style build-out of Wing, Zipline and Amazon delivery sites using their FAA-filed flight profiles, choose the heights and rules, and run it. Your runs are computed live in your browser by the same engine used for the published studies; the two example runs shown first were computed with it when this page was built.

Start from

Airspace
Heights (metres)
Shared flight-plan check
When something goes wrong

Being re-checked (22 Nov 2026): the engine undercounts conflicts for drones that change their plan in flight, so off-plan results are provisional.

Ready.
Plan viewcounted area, 10 × 10 km
Side vieweast–west, height × 40
WingZiplineAmazonPlanned conflict between companies
minute 0 of 60
Planned conflicts by company pairwithin 30 m and 10 m

Lab runs use a 24 km area, 1 hour and one seed, so they are faster and noisier than the published studies (the headline uses real 68–80 km layouts, 2 measured hours and 10 seeds, with 95 % ranges). Expect the same direction and similar size of effect, not the same numbers. Try a few seeds before reading much into one run.

Your runs

Run log

ScenarioPlanned conflictsTightFlights delayedAvg waitOff-plan eventsConflicts per 100 eventsTime
Published studies

Download the scorecard as a spreadsheet (CSV): one row per study with its question, result and how many registered predictions passed.

Study record

Since 22 Oct 2026 every study was written down with its predictions and fingerprinted before any code or run. Exceptions: VALLOC, VALLOC2 and ROBUST were committed together with their results, and FLEET’s analysis came after its runs. Failed predictions stay in the record.

StudyQuestionResultPredictions