The runway is your
single most expensive
asset. Run it like one.
AeroRunway is the runway-operations monitoring, throughput, and optimisation product. It fuses A-CDM milestones, the ATC clearance log, surface-movement radar, runway-end optics, the AeroTaxi pushback events, the AeroFOD detection events, weather, and friction — and lets the AI predict runway occupancy time per movement, recommend configuration changes ahead of the wind, optimise sequencing for wake-category gain, and quantify every minute of capacity delivered against capacity declared. Structured events stream into ATOMS. The operating record is continuous, gate-to-gate-and-back.
Every hour the runway
under-delivers, the airport
loses a slot it could have sold.
The runway is the single binding constraint on the whole airport business. Every other metric — slots sold, fees collected, passenger throughput, on-time performance — is bounded by what the runway delivers per hour. Yet the gap between declared capacity and delivered capacity at a typical hub is two to four movements an hour, every hour, every day — and most of that gap is recoverable. Better RET utilisation, smarter wake-category sequencing, configuration changes called twenty minutes earlier, closure windows that don't bite the peak. None of it is new physics. All of it is new visibility.
From spreadsheet
to operating record.
- ROT is sampled by hand, not measured by the runway.
- Sequencing is decided one aircraft at a time, by the controller's intuition.
- RET choice is the pilot's habit, not the airport's optimisation.
- Configuration changes are called when the wind already shifted.
- Closure windows are scheduled by the maintenance team without operations weight.
- Incursion risk is read after the event, in the safety review.
- Utilisation reports arrive a month late, in a slide deck, in a meeting.
- ROT measured per movement, attributed to the tail, the RET, the weather.
- Sequencing advisor surfaces the wake-category gain available right now.
- RET recommendation briefed to arriving pilots before short final.
- Configuration change proposed twenty minutes ahead of the wind, with the queue cost.
- Closure windows optimised against the schedule and the forecast.
- Incursion risk classified per intersection, surfaced before the event.
- Utilisation reports generated on the same record, every day, audit-ready.
Data we fuse.
Models that learn.
Events on the bus.
We collect.
A-CDM milestones (AOBT, ATOT, ALDT, AIBT) give us the intent. The ATC clearance log gives us the call. Surface radar and MLAT give us position. Runway-end optics confirm touchdown, rollout, and exit. AeroTaxi hands over the pushback; AeroFOD publishes the detections that change runway availability. Weather, friction, and the AODB closure schedule close the loop.
The AI learns.
A runway-occupancy predictor publishes the expected ROT per movement before the aircraft is on final. A sequencing optimiser finds the wake-category re-order that adds a movement an hour. A configuration recommender proposes the runway flip ahead of the wind. A closure-window optimiser schedules maintenance for the lowest revenue impact. An incursion-risk classifier flags the intersection before the read-back.
We emit events.
Every inference becomes a structured event on the ATOMS bus. The tower watch manager sees the configuration recommendation. The duty controller sees the sequencing gain. The CEO sees the throughput delivered vs declared on the same dashboard the next morning. The DGCA inspector sees a continuous, timestamped operating record at audit. One taxonomy. One clock. One audit trail.
What we plug into.
AeroRunway rides on the systems already running your runway. Where a signal is missing, we bridge it; where you also run AeroTaxi or AeroFOD, the events arrive on the same bus and the operating record is continuous.
Five models.
One operating record.
Predicted occupancy.
A per-movement runway-occupancy-time predictor publishes the expected duration from touchdown to vacate, or from line-up to airborne, before the aircraft is on final. Inputs include the aircraft type, the wake category, the pilot's RET preference, the surface state, and the time-of-day pattern. Output is a number with a confidence band, on the ATOMS bus.
Wake-category gain.
A sequencing optimiser evaluates the current queue against wake-turbulence separation tables — and surfaces the re-order that adds a movement an hour without breaking any separation rule. The controller decides; the AI assembles the option set.
Flip before the wind.
A configuration recommender reads the wind forecast, the queue length, the LVP probability, and the noise quota — and proposes the runway flip with a queue-cost estimate twenty minutes ahead of when the wind would force it. The watch manager accepts or overrides.
Quiet windows.
A closure-window optimiser finds the maintenance windows that bite the schedule least — and converts the maintenance team's request list into a calendar that aligns with the forecast and the historical traffic pattern.
Risk per intersection.
An incursion-risk classifier learns the airport's hot intersections by time-of-day, configuration, and traffic mix — and raises an event on the tower screen when the live state crosses the learned threshold.
Delivered vs declared.
A utilisation analyser rolls every movement into the per-runway, per-direction, per-weather-window throughput record — and surfaces the gap between what the airport said it could move and what the airport actually moved, with attribution by cause.
Events into ATOMS.
AeroRunway publishes every inference as a structured event on the same bus the AeroTaxi taxi events and the ATOMS turnaround events flow on. The tower, the AOCC, the airline, the maintenance team, the CEO's dashboard, and the regulator audit log each subscribe to what they care about. The operating record is continuous and reconciled by construction.
One bus. One operating record.
Every AeroRunway event lands on the same platform bus the ATOMS turnaround events and the AeroTaxi taxi events flow on. AOBT in ATOMS, TSAT advisory from AeroTaxi, ROT from AeroRunway, AIBT back in ATOMS — same clock, same audit trail, same dashboard. Gate-to-gate-and-back.
The watch manager's view.
Arrival
Touchdown → vacate
Departure
Line-up → airborne
RET
Rapid-exit taxiway
Event
On ATOMS bus
What the CEO tracks.
Delivered vs declared.
By the hour.
The FOD event that didn't close the runway.
Every FOD detection on the movement area is an event in AeroRunway. Some force an ATC hold; many are cleared during a natural gap because the detection happened in time. That distinction — closed vs cleared-without-closure — is one of the most valuable metrics on the airport CEO's screen. AeroRunway counts it explicitly, attributes it to AeroFOD, and quantifies the slot-minutes preserved. See AeroFOD for the detection product across runway, taxiway, and apron.
Who gains, and how.
The single largest capacity gain available without pouring runway — recovered from the gap between declared and delivered, shift by shift.
- +2–4 movements per hour recovered from the throughput gap — sequencing, RET, configuration.
- Unscheduled-closure minutes down — AeroFOD-found, AeroRunway-cleared.
- Configuration changes called earlier — the queue absorbs the flip.
- Continuous operating record for the regulator audit — daily, audit-ready, signed.
- CEO dashboard — delivered vs declared, by runway, by hour, on the same screen the AOCC runs.
The dispatch and the OTP team get a runway that publishes its intent, not one they read about in a delay code the next morning.
- Predicted ROT per arrival and departure — block fuel and crew clock decisions get tighter.
- RET briefing to the pilot — the runway expects this exit, at this speed.
- Avoided fuel-burn in holds when the closure is cleared in a natural gap.
- Slot adherence tracked per tail, per shift, audit-ready for the airline's performance team.
- OTP gain — the queue at the holding point shrinks because the runway moves faster.
Built to the operating standards.
Common questions.
Do we need AeroTaxi or AeroFOD to run AeroRunway?
No. AeroRunway is standalone. If you also run AeroTaxi, the pushback bookend is exact and the configuration recommender gains a powerful input. If you also run AeroFOD, every FOD-cleared-without-closure becomes a CEO-visible value metric. All three pair natively; each runs alone.
Will the AI take decisions away from the tower?
No. Every model output is an advisory event on screen — sequencing gain available, configuration change proposed, RET recommended. The duty controller and the watch manager retain authority. Acceptance rates climb to 85–90% once the controllers see the predictions land against the live shift.
How is the throughput gap calculated?
Delivered movements per hour are counted on the ATC log and confirmed against surveillance. Declared capacity is read from your published slot model. The gap is the difference, attributed by cause — sequencing, configuration, weather, closure, or AOCC operating posture. The methodology is signed off during commissioning.
What about runway incursions?
AeroRunway's incursion-risk classifier learns the airport's hot intersections by time-of-day and configuration. It does not replace the incursion-warning systems (RWSL, ARIWS) where they exist; it surfaces the risk on the operating record so the safety register has a continuous, structured input.
Does it report to the regulator automatically?
Yes — UTILISATION_REPORT_DAILY is generated on the same record every morning, in the format your regulator requests. The audit log is continuous and tamper-evident.
How long until we see the +2–4 movements/hour?
The ROT predictor and the configuration recommender start producing within weeks of integration. The full throughput gain is characterised during commissioning, against the airport's published declared-capacity baseline, and reported back to the operating committee.
Start with one runway, scale to the system.
The data integrations, the AI commissioning, and the operating-record handover are production-tested. A typical first runway is scoped in days, integrated in weeks, characterised in a month. The CEO dashboard and the regulator audit log are continuous from day one; the throughput recovery compounds from week three.
Bring AeroRunway
to your runway.
A 30-minute walkthrough on your runway configuration, your current throughput gap, your top three operating constraints. We'll send a phased proposal — pilot runway, integration plan, characterisation timeline — within a week.