Opening Bay 01

0%

Pods

Drag to orbit · Pinch or ⌘-scroll to zoom · Tap a number

Full breakdown

00 · Aerial platform

Autonomous Aerial Mobility System

Quad-rotor aerial platform navigating on optical flow rather than satellite fix, with a four-bay underslung rack. It holds position and completes a route in the places GNSS does not reach: between buildings, under structure, inside plant.

Rated payload
100kg
Maximum take-off mass
~300kg
Thrust-to-weight at MTOW
≥ 1.4
Hover endurance at MTOW
≥ 15min
Usable pack energy
9.9kWh
Independently released
4bays

01 · Features

Design features

01 · Nav

Optical-flow primary navigation

Downward-facing flow and range sensing hold position without a satellite fix. GNSS is a cross-check, not a dependency.

02 · Sensing

Mast-mounted LiDAR and gimbal

A top-mounted scanning dome for structure, a stabilised gimbal below for inspection and tracking.

03 · Rack

Four-bay modular pod rack

Independently released bays. One route, up to four separately addressed drops.

04 · Link

Multi-radio C2

Cellular, a licensed command link and satellite fallback, arbitrated live against what is actually working.

02 · Launch · Corridor · Drop

One sortie, end to end

Rooftop launch, corridor transit, marked-pad drop and re-ascent, flown as one continuous flight.

PhaseLAUNCH
Alt000 m
Range0.00 km

Provisional profile

03 · Four-bay rack

Payload configuration

The rack takes one, two or four pods. Every bay releases independently, so a single sortie can serve up to four separately addressed drops without returning to base.

Slung mass is the constraint that matters. Range and endurance fall with it, and the planner solves the route against what is actually fitted, not against the empty-aircraft figure.

Pods fitted
Slung mass
0kg
Range
0km
Endurance
0min
Drops per sortie
0×

Provisional model. Linear mass penalty pending flight test. Linked to the 3D bay above.

04 · GNSS-denied

Navigation without a fix

Between buildings, under structure and inside plant, the satellite constellation is not available. The platform does not treat that as a failure case. It never depended on it.

GNSS Cross-check only

  1. 01 · Track

    A downward-facing sensor tracks ground features frame to frame.

  2. 02 · Scale

    The displacement of those features, scaled by measured height, gives velocity.

  3. 03 · Integrate

    Integrate velocity and you have position, computed onboard, at rate, with no external signal in the loop.

  4. 04 · Cross-check

    GNSS, where it is available, is folded in as one more input to the estimator. It cross-checks the solution. It does not carry it.

05 · By subsystem

Technical specification

01

Airframe & mass

4 parameters
Rotor count / configuration
4, quad rotor with folding arms
Rated payload
100 kg
Maximum take-off mass
~300 kg
Thrust-to-weight at MTOW
≥ 1.4
02

Flight performance

5 parameters
Hover endurance at MTOW
≥ 15 min
Hover throttle at MTOW
≈ 70 %
Hover bus power
34 kW
Usable pack energy
9.9 kWh
Rotor-out (OEI) behaviour
Controlled hover at reduced margin, safe landing
03

Navigation & sensing

1 parameter
Primary navigation
Optical flow + range, GNSS-independent
04

Payload rack

2 parameters
Bays
4, independently released
Release
Electromechanical, per bay
05

Compute, links & compliance

2 parameters
Compute
OmegaMTL stack, real-time safety tier
ESC telemetry bus
CAN-FD, ≥ 100 Hz

Product requirements and design allocations from the current definition baseline, not measured field results.

06 · Where it flies

Deployment.

  1. 01

    Medical and diagnostic transfer

    Sample and consumable movement between facilities on a fixed corridor, measured in minutes rather than traffic.

  2. 02

    GNSS-denied inspection

    Structure and asset survey between buildings, under decks and inside plant where satellite fix is unusable.

  3. 03

    Multi-drop urban delivery

    Four separately addressed pods released across one route without returning to base.

  4. 04

    Disaster response

    First-look survey and small-payload resupply into areas the ground network cannot reach.

07 · Next step

Fly a corridor.

Send us the two endpoints and the payload. We will come back with a sortie profile and what a first deployment looks like.