The runway is
your most expensive
asset.
+2–4 movements/hour, recovered. Predicted ROT, sequencing optimiser, configuration recommender, runway-incursion classifier. Fuses A-CDM, ATC, SMR, runway-end optics, weather. Events into ATOMS.
Every hour the runway
under-delivers, the airport
loses a slot it could have sold.
Slots, fees, throughput, OTP — all bounded by what the runway delivers per hour. The gap between declared and delivered at a typical hub is 2–4 movements/hour. Most is recoverable.
From spreadsheet
to operating record.
- ROT sampled by hand, not measured.
- Sequencing decided one aircraft at a time, by intuition.
- Configuration changes called when the wind already shifted.
- Utilisation reports arrive a month late in a slide deck.
- ROT measured per movement, attributed to tail, RET, weather.
- Sequencing advisor surfaces the wake-category gain right now.
- Configuration change proposed 20 min ahead of the wind, with queue cost.
- Utilisation reports generated on the same record, daily, audit-ready.
Data we fuse.
Models that learn.
Events on the bus.
We collect.
A-CDM for intent, ATC log for the call, SMR + MLAT for position, runway optics for touchdown/rollout/exit. AeroTaxi hands over pushback; AeroFOD publishes detections. Weather + friction close the loop.
The AI learns.
ROT predictor — expected occupancy before final. Sequencing optimiser — wake-category gain. Config recommender — flip ahead of the wind. Incursion-risk classifier — flags before read-back.
We emit events.
Each inference becomes an event on the ATOMS bus. Tower sees config recs; duty controller sees sequencing gain; CEO sees delivered-vs-declared; DGCA sees a continuous record.
The watch manager's view.
Arrival
Touchdown → vacate
Departure
Line-up → airborne
RET
Rapid-exit taxiway
Event
On ATOMS bus
What the CEO tracks.
Who gains, and how.
The largest capacity gain available without pouring runway.
- +2–4 movements/hour recovered — sequencing, RET, configuration.
- Unscheduled-closure minutes down — AeroFOD-found, AeroRunway-cleared.
- Continuous operating record — daily, audit-ready, signed.
A runway that publishes its intent, not one read about in a delay code the next morning.
- Predicted ROT per arrival and departure.
- RET briefing to the pilot before short final.
- Slot adherence tracked per tail, audit-ready.
Built to the operating standards.
Common questions.
Do we need AeroTaxi or AeroFOD to run AeroRunway?
No. Standalone. With AeroTaxi, the pushback bookend is exact. With AeroFOD, every FOD-cleared-without-closure becomes a CEO-visible value metric.
Will the AI take decisions away from the tower?
No. Every model output is an advisory event on screen. Duty controller and watch manager retain authority. Acceptance rates climb to 85–90% once they see the predictions land against the live shift.
How is the throughput gap calculated?
Delivered movements counted on the ATC log + surveillance. Declared capacity from your published slot model. Gap attributed by cause (sequencing, configuration, weather, closure). Methodology signed off during commissioning.
How long until we see the +2–4 movements/hour?
ROT predictor and configuration recommender start producing within weeks. Full gain characterised during commissioning against the published baseline.
Start with one runway, scale to the system.
Integrations production-tested. Scoped in days, integrated in weeks, characterised in a month.
Bring AeroRunway
to your runway.
A 30-minute walkthrough on your runway configuration and current throughput gap.