Civilian Airports / Airport Operations Map
Airport Operations Map
One airport map everyone shares, drawing runway status, closures, work orders, parked aircraft, construction, and Part 139 conditions as layers.
Request a demoThe airport picture lives on too many screens
Runway status, open work orders, closures, wildlife activity, parked aircraft, and construction each live in their own place. Building the day’s picture means opening every one of them and holding the rest in your head.
The Airport Operations Map draws the records the airport already keeps as layers over satellite imagery, so the operation reads the airport from one page. Every record lives once, so everyone with the same layer on sees the same thing.
Choose the layers, read the airport
Open a view
Start from a built-in view, including the Part 139 compliance view, a view you saved, or one a manager saved for the whole airport. A view keeps which layers show, never data.
Turn on layers from your modules
Layers cover the airport (areas, runway status, lights and signs), operations (closures, work orders, wildlife), parking, planning (construction, imaginary surfaces, obstruction evaluations), and Part 139 (conditions, compliance actions, ARFF access roads, fuel facilities, and inspection routes).
Click a record for its facts
A runway shows its status, surface condition, closures, open work orders, and inoperative lights. Any other record opens a short dialog with a link to the record in its own module.
Close an area as a condition record
Pick or draw an area, mark it Closed or Restricted, and write how it reopens. At a Part 139 airport the closure opens an airport condition and drafts its restriction for a second person to authorize.
What it automates
One page for the whole operation
Runways, closures, work orders, aircraft, and construction read together.
Compliance on the same map
The Part 139 view adds conditions, compliance actions, access roads, fuel facilities, and inspection routes.
Always the current record
The map refreshes on its own when a record changes anywhere at the airport.
Straight answers
Does the map keep its own copy of the records?
No. It draws the records other modules keep, and each dialog links back to the record in its own module.
Can a closure reopen on its own?
No. A closure stays active until a person reopens it, and its reopen sentence reads the same on the map, the Airport Status board, the kiosk, and the log.
Who sees each layer?
A layer appears only for people whose role opens its source module at that airport. Layers drawn from airport setup are offered to everyone who can open the map.
Can we place response items during an incident?
Yes. Place fire, police, and medical resources, cordons, and hazard pins, linked to an open incident if you choose, and draw your own layers.
Connected modules
Airport Status
Live field, NAVAID, and surface-condition status your whole operation works from.
Field Conditions
Runway assessments, draft FICON wording, and a condition ledger with recorded dissemination, restrictions, and restoration.
Discrepancies & Work Orders
Airfield discrepancies routed to maintenance and tracked to verified closure.
Construction
Every airport construction job from design through warranty: design reviews, phases, closures, cranes, NOTAMs, notices, and the CSPP record.