NorthSky AERO / ProductsAeroGround
● Ready to deploy

Every turn, seen.
Every event, logged.
Every minute, shared.

15+ turnaround events per flight, captured at the edge from camera + sensor. One record across airport, airline, handler — reconciled by construction. Production-tested. Deploy in weeks.

Outcome
On-time turn
Capture
15+ events per turn
Coverage
Per-stand · apron FOD
Stream
Events into ATOMS

The apron today
is a wall of clipboards.

◆ WHY AEROGROUND
ONE TURN · MANY LOGS · NONE RECONCILE

Handler, airline, airport — three records, three clocks, no shared evidence. When TOBT slips, next morning's meeting has three different stories.

◆ TODAY
Three logs. One slot lost.
  • 70+ events per turn — manual or untracked.
  • Three records, no neutral clock.
  • Apron FOD — six-hour shift-change blind spot.
  • Reconciliation is a meeting.
◆ WITH AEROGROUND
One stand. One record.
  • Every event detected from camera + sensor at the edge.
  • One record across all three parties — reconciled by construction.
  • Apron FOD continuous; GSE + ramp safety surfaced.
  • Into ATOMS — TOBT variance predicted, not reported.

Four layers.
One stand watched.

◆ HOW AEROGROUND WORKS
CAMERAS · SENSORS · EDGE · EVENTS

See. Confirm. Fuse. Record. Each layer reuses what's already on the apron.

LAYER 01

Cameras.

What's visible

6–8 cameras per narrow-body stand. Existing CCTV first; NorthSky fills the gaps.

CCTV-first Day · night · monsoon
LAYER 02

Sensors.

What the camera can't tell

Weight-on-wheels, aerobridge, fuel flow, door contact. Sensor confirms; camera shows.

Reads existing systems No new BMS
LAYER 03

Edge AI.

Inference at the stand

Edge box per stand. Sub-second detection. Tower outage doesn't blind the stand.

< 1 s latency Outage-tolerant
LAYER 04

Structured events.

Onto the ATOMS bus

Timestamp, tail, stand, class, confidence, evidence clip, audit hash. Events, not raw streams.

ATOMS bus Audit by construction

Three companies.
One record.

◆ THE APRON IS A SHARED EVENT
A SHARED RECORD · UNTIL NOW

One operational record. Same clock, same evidence, all three parties.

PARTY 01
Airport operations
Allocates, releases, manages exceptions against the operating record.
Sees: per-stand SLA · network · exception queue
PARTY 02
Airline operations
Acts from ops centre, not after the schedule breaks.
Sees: per-flight timeline · TOBT variance · delay attribution
PARTY 03
Ground handler
Defends performance with evidence, not anecdote.
Sees: per-team performance · per-event evidence · audit
"The chock didn't go on at 14:32 because the handler was late" stops being an argument. It's a frame.

Inside the airport.
Three views, one feed.

◆ DESK-BY-DESK
OPS · HANDLER · SAFETY
ROLE 01
Airport ops
Allocates, releases, manages exceptions against the live operating record.
LIVE SHIFTper-stand SLA · exception queue
ROLE 02
Ground handler
Defends crew performance with evidence, not anecdote.
PER-CREWperformance · evidence · SLA
ROLE 03
Ramp safety
Continuous safety: apron FOD, GSE zone violations, PPE, vehicle–aircraft conflicts. Audit-ready.
CONTINUOUSsafety register · per-handler trend · audit log

Zoom in. Fifteen events,
every turnaround.

◆ THE EVENT CATALOG
EVIDENCE + CONFIDENCE PER EVENT · A-CDM ALIGNED
T+0 · BLOCK ON
T+10
T+20
T+30
T+40
T+45 · OFF-BLOCK
11CREW & STAFF · CONTINUOUS
ARRIVAL
01At gate
CHOCKS
02Chocks on
AEROBRIDGE
03Aerobridge
CARGO
04Belly door
BAG OFFLOAD
05Baggage unloading
BAG LOAD
06Baggage loading
FUEL
07Fuel vehicle
CATERING
08Catering vehicle
CLEANING
10Cabin cleaning
WATER
12Water & lavatory
EXCEPTION
13GSE alert
TUG
Tug09
OFF-BLOCK
Push14
15APRON FOD & FUEL SPILL · CONTINUOUS

Built to the operating standards.

◆ COMPLIANCE POSTURE
APRON SAFETY · A-CDM · REGULATOR
ICAO
ANNEX · 14
Annex 14 aligned
● ALIGNED
Apron-safety reporting · evidence retention · FOD posture.
REF · ICAO/A14/2026.Q3
IATA
AHM
AHM aligned
● ALIGNED
15-event taxonomy maps to AHM milestone definitions.
REF · IATA/AHM/2026.Q3
EUROCTRL
A-CDM
A-CDM aware
● AWARE
Emits TOBT & TSAT events back to your A-CDM platform.
REF · EC/ACDM/2026.Q3
DGCA
INDIA
Aerodrome safety
● ALIGNED
Timestamped record matching DGCA airfield-inspector format.
REF · DGCA/IN/2026.Q3

Common questions.

◆ FOR OPERATIONS & SAFETY
WRITTEN FOR PROCUREMENT
BRIEFING 001SCOPE
Do I have to take ATOMS to run AeroGround?
No. Standalone — 15 events, per-stand SLA, apron FOD, three-way record. Add ATOMS for the AOCC bus; AeroResolve for closed-loop safety.
BRIEFING 002COVERAGE
Does this include runway and taxiway FOD?
No. AeroGround covers apron FOD on each stand. Airfield-wide FOD is AeroFOD — dedicated hardware, three modes. Customers running both see one dispatcher console.
BRIEFING 003HARDWARE
What hardware per stand?
Existing CCTV first; NorthSky fills gaps. Typical: 6–8 cameras per stand, one edge box per pier of 8–12 stands.
BRIEFING 004DEPLOY
How long does a deployment take?
One pier (8–12 stands) goes live in ~6 weeks from civil-works clear. Template ships — first stand slowest, the rest replicate fast.

Start with one pier, scale to the network.

Templates production-tested. One pier live in ~6 weeks from civil-works clear.

Talk to us→

Bring AeroGround
to your apron.

A 30-minute walkthrough on your stand layout, CCTV coverage, and top turnaround frustrations.

Request a demo→ See ATOMS → See pricing