PROJ EQUIRECTANGULAR
180°W ⟷ 180°E
Airline Operations · Digital Twin
Every slot, delay, and diversion — modeled to the tick.
AeroTwin is a deterministic digital twin of an airline's operations center. Schedules, weather, irregular operations, cost — direct the whole operation, reproducible to the cent.
What it is
A simulation only worth running if it's honest.
The closer the twin gets to a real operations center, the more its decisions — and their costs — actually mean something.
Run the operation.
A serious airline-operations simulation, not a tycoon game. Schedules and slots, aircraft and cost, weather that turns. Irregular operations arrive without warning, and you make the cancel, delay, and recovery calls a real ops controller lives with.
Modeled to the tick.
Underneath: A-CDM flight timing, weather from a seeded stream, integer-cent money. The same mechanics a real ops center runs on — reproducible to the cent, replayable from the command log.
Domain fidelity
It speaks the operation's language.
Not a weather-and-money abstraction wearing airline paint. The model is built around the artifacts an ops center actually works from — and it keeps moving toward the ones it doesn't have yet.
- A-CDM flight timing — the milestone clock an ops center runs on
- A seeded weather stream that drives delays and disruption
- Slots, schedule, and cancellations under pressure
- Integer-cent cost attached to every decision
- IATA SSIM schedule ingestion
- Adverse-weather scenarios from historical METAR / TAF
- SID / STAR and airspace constraints
- BADA-style aircraft performance
- Fuel price, and LCC-vs-FSC P&L
How it holds up
Built on a backbone that doesn't drift.
Deterministic core
Same seed, same command log, same world — down to the last cent. Every run is replayable and auditable, not a one-off you can never reproduce.
Irregular operations
Weather, delays, and cancellations arrive from a seeded stream — disruptive but reproducible. They cascade through the schedule and the cost line exactly as they would in a real operation.
Open core
The simulation engine is open source. Inspect the model, run it headless with nothing but cargo test, and write plugins against a semver-stable ABI.
Why deterministic matters
Replayable isn't a technicality. It's the whole point.
"Same seed, same world" reads like an engineering footnote. In an operation it means the counterfactual is exactly reproducible — the one thing a real ops center never gets.
The snowstorm that paralyzed the hub — the same weather, the same schedule, waiting for you. Try your recovery, watch it cascade, rewind, and take a different call. As many times as it takes.
Post-mortem the cancel-versus-divert decision against identical conditions every run, and read the cost of each path to the cent. A sandbox where the what-if is reproducible, not an anecdote.
The backbone, in spec
Determinism, spelled out.
tick: u64
producer, tick)
replay
Models in the loop
Frontier models, wired into the operation.
Not a chatbot bolted to the side. Language models drive the parts of an operation that are messy, human, and never the same twice — so the pressure on the desk feels real.
Snags & comms
Pilot-reported snags and virtual-ATC exchanges, written in the voice of the moment — the ambiguous, incomplete inputs a controller actually has to act on.
Passenger fallout
When a bank collapses, models read passenger sentiment and weigh rebooking cost against the clock — so an IRROPS call carries its human and financial weight.
Your choice of model
Bring the frontier model you trust — plug it into the loop and see how it holds up under an operation that doesn't wait.
Early access
Be in the tower when it opens.
We're building in public. Join the waitlist for first access, the dev log, and the opening set of operation templates.
NO SPAM · DEV LOG + LAUNCH ONLY · UNSUBSCRIBE ANYTIME