● Ready to deploy

Every turn,
end to end.

ATOMS — Airside Turnaround Operations Management — is the turn-cycle product for airports. One operational record that follows a flight from its origin, through the air, into touchdown, off the runway, across the taxiway, onto the stand, off the stand, and back into the sky. Three companies, one record. Production-tested. Deploy in weeks.

Status
Ready to deploy
Scope
End-to-end turn cycle
Opt-in packs
3 hardware packs
Transparency
Airport · airline · handler

The turn cycle,
from origin to wheels-up.

◆ ONE FLIGHT · ONE RECORD
EIGHT PHASES · EVERY EVENT
NOT JUST THE GATE

A turnaround doesn't start when the chocks go on. It starts when the inbound leaves its origin and ends when it's wheels-up on the outbound. ATOMS captures the whole arc — every phase, every event, every actor — on one operational record.

PHASE 01INBOUND
Origin departure
OFF-BLOCKWHEELS-UPEOBT VARIANCE
PHASE 02OVER THE AIR
En route & descent
ETA UPDATEHOLDDESCENTHANDOFF
PHASE 03RUNWAY
Touchdown
TOUCHDOWNLANDING ROLLRUNWAY EXIT
PHASE 04TAXI-IN
Taxi to stand
RWY-TWYTAXI ROUTEHOT-SPOT CROSSINGIN-BLOCK
PHASE 05GATE · TURN
On stand
15 EVENTSGROUND HANDLINGAPRON FOD
PHASE 06TAXI-OUT
Pushback & taxi
OFF-BLOCKPUSHBACKTAXI ROUTEHOLD QUEUE
PHASE 07RUNWAY
Line-up & roll
LINE-UPTAKE-OFF ROLLRUNWAY EXIT
PHASE 08DEPARTURE
Wheels-up
WHEELS-UPCLIMBNEXT-CYCLE START

Phases 1–4 use third-party feeds (ADS-B, AODB, DCS, ATC). Phases 5–7 are captured by NorthSky hardware packs — opt-in below. Phase 8 closes the record and opens the next cycle.

Three opt-in packs.
Take one. Or all three.

◆ HARDWARE WHERE YOU NEED IT
EVENTS WHERE YOU WANT THEM
SAME ATOMS RECORD · SAME DASHBOARD

ATOMS core gives you the turn record across phases 1, 2, 3, 4, 6, 7, and 8 — fed by your existing feeds. Phases 5–7 are where NorthSky hardware adds the events. Pick the packs that match your priority. Light them up later if you start with one and decide to grow.

● Ready to deploy
PACK 01 · DEDICATED PAGE →

Ground Handling Optimisation

Apron cameras + sensors + edge processing. Captures fifteen turnaround events per flight on the stand — from aerobridge connect through pushback — with evidence clips and confidence scores.

  • 15-event catalog per turnaround — see below.
  • Real-time apron FOD — fuel spills, small objects.
  • Per-stand procedure-book compliance.
  • GSE positioning & restricted-zone alerts.
  • Staff identification for compliance logs.
Hardware: Per-stand camera + edge box. Uses existing CCTV where coverage allows; NorthSky cameras fill gaps. Read the deep dive →
● Ready to deploy
PACK 02

Taxi-time Optimisation

Surface-movement capture across the taxiway network. Not one flight — every flight. Heatmaps of where time is lost. Bottleneck identification at hot-spot intersections. Per-stand taxi-out and per-runway taxi-in distributions.

  • Fleet-level taxi heatmap — see where the network bleeds time.
  • Hot-spot identification — intersection-level wait analysis.
  • Per-stand taxi-out distribution by terminal, by hour.
  • Per-runway taxi-in patterns — congestion by direction.
  • Fuel-burn estimates from movement track history.
Hardware: Taxiway sensor network + ADS-B feed. Long-range optics at hot-spot intersections; passive sensors at junctions.
● Ready to deploy
PACK 03

Runway Utilisation Optimisation

Runway throughput, separation, and slot adherence analytics. Touchdown-to-touchdown distributions. Line-up to wheels-up timings. Runway occupancy by direction, by hour, by weather window.

  • Per-runway throughput stats — movements per hour, by direction.
  • Separation analytics — inter-arrival and inter-departure gaps.
  • Runway occupancy time per landing and per departure.
  • Slot adherence — scheduled vs actual.
  • Weather-window analysis for capacity planning.
Hardware: Runway-end optics + ATC/AODB integration. Capture line-up, take-off roll, touchdown, runway exit at both ends.

Runway foreign-object detection is a separate product — AeroFOD → — because it needs a dedicated sensor installation alongside the runway. Apron FOD lives inside Pack 01.

Fifteen events,
every turnaround.

◆ INSIDE PACK 01 · GROUND HANDLING
CAPTURED FROM APRON CAMERAS & SENSORS

Each event is detected from camera vision + sensor signal, time-stamped at the edge, and written to the shared turnaround record. Every event carries an evidence clip and a confidence score. Catalog is configurable per airline and per stand.

EVENT 01ARRIVAL
Flight at gate
Aircraft on stand, engines spooling down. Anchors the start of the turn.
EVENT 02SAFETY
Chocks on / off
Wheel chocks placed and removed. Critical safety and timing event.
EVENT 03PASSENGER
Aerobridge connect / disconnect
Passenger bridge engaged with the door and released.
EVENT 04CARGO
Belly door open / close
Cargo and baggage hold doors opened and closed.
EVENT 05BAGGAGE
Baggage unloading
Inbound baggage offload — start and end.
EVENT 06BAGGAGE
Baggage loading
Outbound baggage onload — start and end.
EVENT 07FUEL
Fuel vehicle arrival / depart
Bowser or hydrant truck on stand. Anchors the fuelling window.
EVENT 08CATERING
Catering vehicle arrival
Galley truck on stand and at the aircraft door.
EVENT 09PUSHBACK
Pushback tug arrival
Tug positioned at the nose gear, ready for pushback.
EVENT 10CLEANING
Cabin cleaning on / off
Cleaning crew entry and exit through the service door.
EVENT 11STAFF
Crew & staff identification
Handler, fuelling, catering, security presence — for compliance logs.
EVENT 12WATER
Water & lavatory service
Service vehicle on stand and connection time at the aircraft.
EVENT 13EXCEPTION
GSE in restricted zone
Equipment crossing into a no-go area. Alert with evidence.
EVENT 14DEPARTURE
Pushback commence
Tug applies push. Anchors the off-block time.
EVENT 15SAFETY
Apron FOD & fuel spill
Foreign objects on the apron in real time. Alert + evidence + coordinates.

Three companies.
One record.

◆ THE TURNAROUND IS A SHARED EVENT
BUT THE PEOPLE RUNNING IT DON'T SHARE
A RECORD · ATOMS DOES

An apron turnaround is run by three different companies — the airport, the airline, the ground handler. Today they reconcile from three different systems, often after the fact, often in dispute. ATOMS gives all three the same operational record, in real time, with the same time-stamps and the same evidence.

PARTY 01
Airport operations
Sees turnaround compliance across every stand, every airline, every handler. Allocates resources, releases stands, manages exceptions against the operational record.
Sees: per-stand SLA · network view · exception queue
PARTY 02
Airline operations
Sees their flight's turnaround in real time — every milestone, every delay factor, every variance from plan. Acts on it from the ops centre, not after the schedule breaks.
Sees: per-flight timeline · delay attribution · TOBT variance
PARTY 03
Ground handler
Sees their team's performance against the procedure book — chocks on, GSE positioning, fuelling, catering. Defends performance with evidence, not anecdote.
Sees: per-team performance · per-event evidence · audit trail
"The chock didn't go on at 14:32 because the handler was late" stops being an argument. It's a frame.

What changes when
the record is shared.

◆ OUTCOMES
FOR AIRPORT · AIRLINE · HANDLER
◆ FUEL & CO₂
Less burn.
Earlier off-block, fewer holds on taxiway, less APU running on stand. Fuel burn reduction shows up in the airport's environmental report and in the airline's fuel bill.
◆ DELAY
Fewer misses.
When the bottleneck is visible in real time — catering late, GSE in the wrong place, chocks delayed — someone can fix it before the slot is gone. Delay is anticipated, not reported.
◆ SAFETY
Cleaner apron.
Apron FOD detected in real time prevents engine damage, slips, and ramp incidents. Safety logs auto-generated with evidence retained for ICAO Annex 14 and DGCA review.
◆ TRUST
No more arguments.
When all three parties — airport, airline, handler — see the same time-stamps with the same evidence, the after-the-fact reconciliation goes from blame to operations.

How ATOMS sees
the airport.

◆ TECHNOLOGY SHAPE
NO RIP-AND-REPLACE
◆ AT THE SURFACE
Cameras & sensors.

Existing infrastructure first. Apron CCTV, taxiway optics, runway-end cameras — ATOMS works with what's already on site. Where coverage gaps exist, NorthSky supplies cameras, edge boxes, and passive sensors to fill them. No requirement to rip out a working camera network.

◆ AT THE EDGE
Edge processing.

Detection runs on edge boxes at the stand, the taxiway hot-spot, or the runway end. Inference happens where the camera is — sub-second latency, low bandwidth. Stand-level resilience: a tower outage doesn't blind the apron.

◆ AT THE PLATFORM
One shared record.

Events stream to the NorthSky platform. Airport ops, airline ops, and the ground handler each see their own view of the same record. Audit trail by design. Inference in India. Read AI governance →

Plugs into the
systems you already run.

◆ INTEGRATIONS
STANDARDS-BASED · OPEN

Inbound feeds

  • ADS-B for over-the-air position and timing.
  • AODB for the flight schedule and the operational plan.
  • DCS for departure-control events.
  • BHS for baggage milestones at depth.
  • Ground handler dispatch for handler-side operational events.
  • Existing CCTV / VMS for camera feeds where available.
  • Tower / ATC feeds for runway events.

Outbound flows

  • Airport operations centre dashboard — full network view.
  • Airline operations centre — per-flight timeline with delay attribution.
  • Ground handler dispatch — per-team performance and exception queue.
  • A-CDM network manager feeds where the airport is A-CDM aligned.
  • BI / data warehouse exports for reporting and modelling.
  • Safety system events for ICAO Annex 14 reporting.
  • Open REST & webhooks for everything else.

Common questions.

◆ DEPLOYMENT & SCOPE
WRITTEN FOR OPERATIONS & PROCUREMENT

Do I have to take all three packs?

No. Each pack is independently licensed and independently deployed. Most customers begin with one — typically Ground Handling — and light the others up later as priorities and budget allow. ATOMS core works with any combination.

What if we don't have apron CCTV today?

NorthSky supplies cameras and edge boxes where coverage gaps exist. We've designed the hardware for typical apron lighting conditions (day, night, monsoon). A stand-by-stand survey precedes deployment.

How does the airline get its view?

Per-flight timelines stream to the airline's operations centre via REST APIs, webhooks, or A-CDM feeds — depending on what the airline is already plumbed into. Read access is scoped to that airline's flights only.

Who can see the ground handler's performance data?

The handler themselves, the airport ops centre, and any airline whose flights they handle. Sharing is governed by the deployment contract; the audit trail is preserved across all parties.

Does this replace our A-CDM system?

No. ATOMS feeds A-CDM where it exists — TOBT updates, milestone time-stamps, hand-offs to the network manager. If you're not yet A-CDM aligned, ATOMS can be the operational record that gets you there.

What about runway foreign-object detection?

Runway FOD is a separate product, AeroFOD — different sensor installation, different optics, different operational profile. Apron FOD (fuel spills, small objects on the stand) is covered by ATOMS Ground Handling pack.

Ready to deploy.

Production-tested. The configuration template ships with ATOMS — procedure book, event catalog, per-stand camera mapping. Pilots are typically scoped in days and live in weeks. Active design partners welcome on Pack 02 and Pack 03 in particular.

Talk to us

Bring ATOMS
to your airport.

A 30-minute walkthrough on your real stands, your real taxiways, your real runway throughput. We'll show you what each pack would surface and propose a deployment scoped to your priorities.

Request a demo See AeroFOD (runway)