Mission desk

Features

Everything on this machine: missions, radio log, ICS 214, roster, channels, official print, and a copy you can take to another computer.

PageWhat it does
Dashboard Active mission, A–F designators, recent traffic, watch bill, Zulu and local clocks.
Missions Create, open, and close missions. Import a saved JSON pack. Sample SAREX on first launch so the desk can be clicked through immediately.
Radio Log Fast CAPF 110 hot log: date, HHMM, call, channel A–F, remarks. Stamp now. Mark a line for ICS 214. Search the communications log.
ICS 214 Activity Notable activities, decisions, equipment issues, and shift changes. Radio lines marked ICS 214 plus dedicated notes print on Form 214 block 7.
Roster Watch bill (name, CAPID, ICS position, time in/out) plus ICS 214 block 6 resources assigned with home agency.
Channels CAPF 110 designators A–F (CC1, Air 1, Guard, TAC 1, Telephone, Liaison) plus a CAP mission channel strip.
Print Forms On-screen official-form preview. Print CAPF 110, ICS 214, or both. Save as PDF from the browser print dialog for WMIRS.
Reference ICAO phonetics, CAP mission radio procedure, and which traffic belongs on 110 versus 214.
Settings Operator, CAPID, wing, unit, default Zulu or local. Full backup and restore. Mission packs under data/missions/.
DATA

On disk

SQLite database at data/logbook.db. JSON mission packs under data/missions/. No required Python packages beyond 3.10+. Port 8770 so it can run next to Moonraker Logbook® on 8765.

TIME

Zulu first

Default is Zulu (UTC). Note the time zone on the first log line of each day, as CAPF 110 requires. Switch a mission to local time if that is how the IC is running the period.

RETENTION

Keep it with the mission file

Logs that include mission activity should be kept with the mission file per CAPR 100-1 and CAPR 10-2. Saving a mission writes a timestamped pack plus a latest copy named after the mission number, and downloads the same file.