AeroNOVA ← SPATIAL EXPLORERBLR / INTEGRATED AIRSIDE OPERATIONS · v0.6BIARDI & DDFS ↗

AeroNOVA Sentient Twin — operational intelligence workspace

New: Airport Manager 2026 - mixed traffic, both runways & terminal plans

ONE SCHEDULE · ONE CLOCK · ONE EVENT STREAM

Every turnaround.
Connected.

Departure-driven simulation with assumed inbound rotations and resource reservations.

PLANNING SIMULATION
Partial 10 October 2026 departure snapshot · no live feed

Provisional Code C stand eligibility • North runway only • Bidirectional mapped taxi paths • Synthetic inbound rotations • Timed taxi-edge reservations. These results do not establish airport capacity or operational clearance.

Preparing mapped routes and stand register…

00:00

Runways: 09L/27R 4,000 × 45 m; 09R/27L 4,000 × 60 m (OSM tags). Markings, lighting, PAPI/LOC and windsocks are illustrative, not surveyed or validated against current AIP. Both runways are displayed; simulated movements use the north runway.

HOS = Head of Stand Road; TOS = Tail of Stand Road. Labelled road overlays and terminal detailing are inferred concepts, not surveyed installations. Parking reference and nose-gear stop share the painted guidance geometry. Landside: mapped road alignments and hotel footprints; estimated upper forecourt and basement levels. Metro and MLCP are schematic. Amber future-terminal extent comes from OSM; approved reservation boundaries are unavailable. Basement X-ray reveals otherwise hidden subgrade structures.

Drag to orbit · wheel to zoom · Aircraft colour: mint baseline / amber selected. Buildings are estimated volumes; © OpenStreetMap contributors. ODbL.

Shared flight board

STD is from the selected demand source; all arrival times, stands, rotations and departure outcomes below are modelled. Select a row to inspect its events.

Flight / destinationSTD ISTStandCurrent stateModelled departureDelay / baseline difference

Event replay

Stand register & boundaries

Mapped positions are retained. Stand aircraft compatibility and terminal allocations need airport validation. Unreachable stands and inferred connectors over 100 m are excluded. Crossings without shared graph nodes, wingspan clearance, real runway rules and south-runway operations remain unvalidated.

The deterministic planner processes rotations in assumed-arrival order and books their full turnarounds. It is conservative and not an optimised dispatcher. Eight teams per service and four tugs are scenario assumptions. Baseline delays may be large; they indicate this model’s constraints, not measured BLR performance.