Civilian Airports / Visual NAVAIDs
Visual NAVAIDs and Lighting Outage Detection
Every light and sign plotted on satellite imagery, with outages evaluated against your selected standard the moment they're reported.
Outage math kept in someone's head, or in a spreadsheet that breaks
A lighting outage is never just one light. What matters is whether the system as a whole still meets its serviceability threshold, and answering that by hand means knowing every fixture on the system, what percentage is out, and whether adjacent lights are dark at the same time.
Most airports keep that math in a spreadsheet that breaks the moment the data changes, held together by the one person who knows every circuit. The evaluation has to survive that person leaving.
The airport, fixture by fixture
Your lighting depicted on satellite imagery
Every light and sign sits at its position on a satellite map of your airport, each a feature with its own type, status, and system, brought in with Import Features or placed with the in-app editor.
Click the fixture, report the outage
Reporting happens on the map, not in a form. Pick the fixture, mark it out, add a note. Done from a vehicle on the field on a phone, tablet, or desktop.
Evaluated against your standard the moment you report
The Outage Engine recomputes the system's outage percentage and its spatial pattern against the standard your airport selects (FAA Part 139 thresholds from AC 150/5340-26C, or ICAO Annex 14), and flags conditions on a four-tier alert scale.
The follow-up starts itself
An outage that exceeds its threshold auto-creates a discrepancy assigned to maintenance, and the alert carries the required actions and Lighting NOTAM wording that match the standard you operate under.
What it automates
Threshold detection on every report
The evaluation runs the second an outage is logged, percentage and adjacent-fixture patterns both, so a condition that trips a threshold is flagged before anyone does math.
The response matches the standard
Alerts carry the required-action checklist and NOTAM wording for the standard your airport selected, not another authority's vocabulary.
The program survives turnover
System layouts, thresholds, and outage history live in the platform, not in one person's memory or a spreadsheet only they can maintain.
Straight answers
How does the airport map get built?
Import Features brings fixtures in from existing data, or place them manually with the built-in editor. Either way the result is your airport: real imagery, fixtures at their real positions. Audit Mode handles bulk work like sequential labeling and fixture ID generation.
Which outage standard applies?
It's a per-airport setting. A Part 139 airport defaults to the FAA standard, and ICAO Annex 14 can be selected instead. Thresholds, required actions, and NOTAM wording all follow the selection.
Does an outage create a work order?
An outage that exceeds its threshold auto-creates a discrepancy assigned to maintenance, so the fix starts moving the moment the condition is known.
What about CAT II/III runways?
Flagging a system CAT II/III tightens its thresholds where the selected standard says so; under the FAA standard, runway edge lights tighten from 15 percent allowable to 5. The option appears only on system types the selected standard covers.