Every turn, seen.
Every event, logged.
Every minute, shared.
Apron, stand, and gate monitoring. 15+ turnaround events per flight captured at the edge — chocks, aerobridge, fuelling, catering, baggage, cleaning, pushback — plus real-time apron FOD, GSE positioning, ramp safety. Events stream into ATOMS; airport, airline, handler reconcile from the same record. Production-tested. Deploy in weeks.
The apron today
is a wall of clipboards.
Handler logs what they see, airline notes what their crew did, airport tracks SLA from radio chatter. Three records, three time-bases, no shared evidence. When TOBT slips and the slot is gone, next morning's meeting has three different stories.
- 70+ events per turn, tracked manually or not at all.
- Three companies, three records — no neutral clock.
- Apron FOD at shift change — every-six-hours visibility on a hazard.
- Reconciliation is a meeting — argumentative, usually inconclusive.
- Every event detected from camera + sensor at the edge; one platform clock.
- One shared record across airport, airline, handler — reconciliation by construction.
- Apron FOD continuous; GSE positioning automatic; ramp safety surfaced.
- Events stream into ATOMS — TOBT variance predicted before the milestone slips.
Four layers.
One stand watched.
Cameras see what's visible. Sensors confirm what's happening. Edge AI fuses both into events. Platform writes them to the shared record. Each layer reuses what's already installed where possible.
Cameras.
A narrow-body stand carries 6–8 cameras — overview, aerobridge, cargo, fuel zone, catering, pushback. Existing CCTV reused where adequate; NorthSky fills gaps.
Sensors.
Confirm what vision alone can't. Weight-on-wheels, aerobridge state, fuel flow, cargo door contact. Sensor confirms, camera shows.
Edge AI.
Edge box per stand or pier. Sub-second detection. Tower outage doesn't blind the stand; bandwidth back to platform stays light (events, not raw streams).
Structured events.
Each detection becomes a structured event — timestamp, tail / stand / class, confidence, evidence clip, audit hash. ATOMS consumes; airline + handler + regulator subscribe.
Three companies.
One record.
Today airport, airline, and handler reconcile from three systems after the fact. AeroGround gives all three the same operational record, in real time, with the same evidence behind every event.
Three roles.
One record, three views.
Airport ops.
Live exception queue across every stand. Allocates, releases, manages exceptions against the operating record.
Ground handler.
Per-crew performance against the procedure book. Defends performance with evidence, not anecdote.
Ramp safety.
Continuous safety record — apron FOD, GSE restricted-zone violations, ramp PPE non-compliance, vehicle-aircraft conflicts. Audit-ready format.
Zoom in. Fifteen events,
every turnaround.
Built to the operating standards.
Common questions.
Do I have to take ATOMS to run AeroGround?
No. AeroGround is standalone — 15-event capture, per-stand SLA, apron FOD, three-way operating record. Add ATOMS when you want events on the AOCC bus alongside taxi and runway. Add AeroResolve for closed-loop safety.
Does this include runway and taxiway FOD?
No. AeroGround covers apron FOD on each stand. Airfield-wide FOD (runway / taxi / apron) is the standalone product AeroFOD with dedicated hardware in three modes. Customers running both see one dispatcher console.
What hardware per stand?
Existing CCTV is primary where adequate; NorthSky fills gaps. Edge box per stand or pier. Typical: 6–8 cameras per stand, edge box per pier of 8–12 stands.
How long does a deployment take?
Configuration template ships. A single pier (8–12 stands) goes live in roughly 6 weeks from civil-works clear. First stand slowest; subsequent stands replicate quickly.
Start with one pier, scale to the network.
Templates production-tested. One pier live in ~6 weeks from civil-works clear.
Bring AeroGround
to your apron.
A 30-minute walkthrough on your stand layout, CCTV coverage, and top turnaround frustrations.