Runway condition, compliance-ready — without the hub-airport price tag.
SnowOps brings RCAM assessment, SNOWTAM/FICON generation, and friction-data ingestion to the ~400 Part 139 regional and smaller airports still running winter ops on paper and Excel — the segment ESRI's free solution leaves behind because it still needs ArcGIS licensing and config capacity they lack.
From contaminant to compliance, in one flow
An inspector observes contaminant type, depth, and coverage on a runway third. SnowOps applies the FAA RCAM to derive a Runway Condition Code (RWYCC 0–6) per third, then generates the compliant NOTAM output — all from the same app the SRE fleet already uses.
RCAM / RWYCC assessor
Contaminant type + depth + coverage → Runway Condition Code (0–6) per runway third, per FAA AC 150/5200-30D and ICAO GRF.
SNOWTAM / FICON NOTAM generator
Machine-parseable ICAO GRF SNOWTAM (8-hour validity) and FAA FICON NOTAMs — ready to file.
Friction ingestion
Tapley/Bowmonk decelerometer and CFME readings — friction mu can downgrade RWYCC automatically.
Part 139 SICP self-inspection
Audit-grade trail for the Snow and Ice Control Plan, with full SRE fleet AVL and material/chemical tracking reused from core.
Zero schema change to reuse the core
The airport capability reuses the core platform's AVL, routing, and material tracking without schema changes — an airport gets the same real-time fleet visibility a municipality does, plus aviation-specific compliance on top.
Where we play (and don't)
Large hub airports run locked-in incumbents (Veovo, SITA, INFORM, PDC). SnowOps targets regional and smaller Part 139 airports instead — and we don't compete on generic GIS, only on aviation-specific compliance workflows.
RWYCC by third — example
Bring your airport off paper and Excel
See RCAM assessment and SNOWTAM generation run against your runways and friction data.
Request a demo →