Military Airfields / SCN

SCN

Secondary Crash Net activation records with per-agency notification logging.

The problem

A commo check only counts if the record shows every agency answered

The Secondary Crash Net only works if every agency on it is actually reachable when it matters, which means a routine check has to prove each one answered, not just that someone tried to call the list. A check that skips an agency, or one where nobody wrote down who came back No Response, isn't a check anyone can point to later.

That record also has to hold up on its own two cadences, daily and monthly, without the two getting confused with each other.

How it works

The roll call, logged agency by agency

  1. 01

    Two cadences, tracked separately

    Daily and monthly checks each get their own card on today's view (Complete once logged, Start Check when it's due), so the two never get run together or mistaken for each other.

  2. 02

    Work through the roll call, mark every agency

    Step through the agency list and mark each one Loud & Clear, No Response, or Out of Service. An Out of Service call requires a note before it can be logged.

  3. 03

    Every check lands in the same history

    Completed checks file into a Past 30 Days history, attributed and timestamped, so a specific day's check is easy to find again.

  4. 04

    A monthly matrix, ready to submit

    Export the month's checks as a matrix PDF (every day, every agency, one page) instead of assembling it by hand at month's end.

Secondary Crash Net check log for a demo airfield
The Secondary Crash Net module for a demo airfield: Daily and Monthly Back-up SCN Check cards both awaiting today's roll call, a Monthly Report picker for July 2026 with Download PDF, and a Past 30 Days history logging one daily check with 7 agencies not clear.

The benefit

What it automates

No agency gets skipped quietly

The roll call steps through every configured agency by name. An Out of Service call requires a note, so a check can't be logged clean with a gap nobody explained. Completion and notes are automatically logged in the daily events log upon completion.

Daily and monthly stay two different records

Each cadence has its own card and its own history, so a completed daily check and a completed monthly check are never confused for one another.

One export, not a month of reassembly

The matrix PDF pulls straight from the logged checks. Nobody reassembles a month of roll calls into a report by hand.

Related

Works alongside

FAQ

Straight answers

Is this where a real crash net activation happens?

No. This module is the communications-check record: a routine roll call confirming every agency on the net is reachable, logged daily and monthly. It's not a live activation control.

What happens if an agency doesn't answer?

Mark it No Response or Out of Service. An Out of Service call requires a note, so a gap in the roll call is explained in the record, not just left blank.

Are the daily and monthly checks the same record?

No. Each has its own card and its own history, so a completed daily check and a completed monthly check never get mixed up.

Can I produce a report covering a full month of checks?

Yes. Export a matrix PDF covering every day and every agency for the month, built from the logged checks rather than assembled by hand.