Cambridge, UK · Route validation for drone operations

Prove the route
before you fly it.

Locust tests a proposed drone operation in a simulator of the real city before anyone buys aircraft or asks for airspace. You get a proceed, redesign or stop recommendation, with every assumption behind it written down.

Built around Drone operators Councils and site owners Assurance teams
Example: Cambridge delivery scenario Simulation online
Operations hub
Priority corridor
Modeled cost£4.32per delivery
Modeled range2.8 kmaverage route
Fleet state 24 aircraft modeled
AirspaceCambridge Airport FRZ
Open console ↗
619deliveries / day
34%modeled contribution margin
89%on-time in current run
65 Whenergy / delivery

Example output from the Cambridge delivery scenario. These are simulation results. No Locust flights have taken place. Method and limitations [12]

What Locust does

One question per engagement: should this operation fly?

Operators, councils and site owners bring a mission: a route, an aircraft and an operating window. Locust models it against the city, the weather and the failure cases, and reports what it would take to fly it safely and economically. Locust does not build aircraft, run hubs or operate drones.

Scope a route assessment ↗
01
↗

Route model

Model the route, aircraft, airspace, energy reserve, weather limits and contingency landing options in a simulator of the real city.

  • Route and aircraft definition
  • Weather, failure and reserve cases
  • Cost and demand scenarios
02
◎

Evidence

Each finding traces to a scenario that can be re-run with the same seed and inputs and give the same result.

  • Assumptions and data sources
  • Deterministic re-runs
  • Gaps the operator still has to close
03
△

Re-runs

When the aircraft, route, demand or rules change, the same scenarios run again and the report shows what moved.

  • Change impact reports
  • Pilot gate tracking
  • Updated recommendation
What the customer receives

A decision, the evidence behind it, and the gaps.

Each engagement ends with a proceed, redesign or stop recommendation. The work is useful even when the correct answer is to keep the mission on the ground.

Decision

Proceed, redesign or stop

A recommendation for the route and aircraft as proposed, and the changes that would alter it.

  • Route and aircraft verdict
  • Weather and time windows
  • Energy reserve at the worst case
  • Contingency landing coverage
  • Cost per completed mission
Evidence

A versioned report

Findings with the scenario, seed and inputs that produced them, so a reviewer can reproduce each one.

  • Scenario register
  • Assumptions and data sources
  • Failure and contingency results
  • Sensitivity to key inputs
  • Model limitations
Gaps

What still has to be proven

The items simulation cannot settle, named so the operator can plan the flight tests and approvals that close them.

  • Items needing flight data
  • Items for the operator's safety case
  • Items for the site owner or council
  • Suggested acceptance gates
  • Re-run triggers
Built to learn before we spend

Model first.
Pilot second.
Scale on evidence.

Our Cambridge model combines OpenStreetMap buildings and roads, Census 2021 population, the Cambridge Airport flight restriction zone, synthetic merchant demand, battery behavior and weather limits. UK BVLOS operations require an appropriate CAA Operational Authorisation; simulation does not provide one.1

Launch interactive model ↗
01

Map the operating area

Population under the route, restricted airspace, demand, hubs and recovery points are modeled together.

02

Stress-test the service

Run weather, outage, battery, demand and fleet scenarios before field operations.

03

Recommend

Report proceed, redesign or stop, with the scenarios and assumptions behind the call.

04

Re-run as it changes

Repeat the same scenarios when the aircraft, route or demand changes, and show what moved.

Decision-grade evidence

A pitch is not proof.
So we expose the assumptions.

Every headline number is tied to a route, fleet, demand, tariff and staffing assumption. The current sweep covers 270 physical scenarios and 810 cost evaluations; it contains no Locust flight measurements.12

Example output: unit economicsCambridge · 24-drone scenario
Revenue / delivery£6.54
−
Cost / delivery£4.32
=
Contribution / delivery£2.22
Maintenance & fleetCore
Operations & labourVariable
InfrastructureShared
Insurance & complianceControlled

Scenario output changes with utilization, route length, pricing and fleet assumptions. Figures exclude financing and tax.

For councils and site owners

See the evidence
before you commit public space.

Before any trial is approved, Locust can model the proposed operation over your area: its routes, hours, payloads, weather limits, reporting and pause conditions. The authorised operator remains accountable for the operation and CAA approval.2

See the cooperative compact ↗
01

Restricted by design

Geofenced routes avoid sensitive sites and can be changed before deployment.

02

Community visibility

Publish operating windows, routes, contacts and plain-English performance reports.

03

Measurable public value

Compare road miles, delivery time, energy use, noise and service access.

04

Agreed stop conditions

Weather, safety, noise and incident thresholds pause operations automatically.

A first engagement

A route assessment should end in a decision.

Your routeYour aircraftNamed assumptionsA clear verdict
Partners wanted: Cambridge

Operators and manufacturers: test a Cambridge route before you commit to it.

We bring the city model and the route, risk and economic analysis. You bring the aircraft data and operating experience. Together that gives a council and the CAA a reviewable case to assess. We are looking for drone manufacturers and BVLOS operators who want to evaluate a Cambridge operation before they commit to one.

If you build or operate delivery, inspection or logistics drones and have a route in mind, we would like to model it.

Partner with Locust ↗
Aircraft / OEMBVLOS operatorCambridge siteLogistics partner
Proposed pilot acceptance gates

Expand only when the evidence clears every owner.

Thresholds are agreed with the operator, customer and council before operations. A miss triggers redesign or pause rather than retrospective justification.

Decision areaMeasureProposed evidenceDecision owner
SafetyNo uncontained loss of control or reserve breachFlight logs, occurrence record, contingency reviewAuthorised operator
ServiceCompletion and on-time performance against agreed route targetAccepted, completed, delayed and cancelled missionsCustomer
Public impactNoise, complaints and privacy events remain within agreed limitsAcoustic measurements, complaint log, data auditCouncil / site owner
EconomicsMeasured cost and labour per completed delivery beat the agreed alternativeLabour, maintenance, energy and infrastructure ledgerCustomer / Locust
DemandEnough eligible orders accept the service without unfair pricingQuotes, accepts, abandonments and basket mixCustomer / council
Work with us

Bring us a route,
a neighbourhood,
or a hard question.

We want to hear from drone manufacturers and BVLOS operators, councils, landowners, logistics teams and early-stage investors.

Contact Locust ↗
Route assessmentOperator partnershipCouncil briefingInvestment