RangerTrak: Free Offline Field-Report Mapping for Radio-Only Teams

TL;DR: RangerTrak is a free, open-source (AGPL v3) browser app that turns voice radio reports into a sortable log, a live map and printable ICS forms. One scribe types each call into a laptop at the command post. It runs offline once installed, needs no account, and keeps your mission on your own device. It’s still in beta, so keep the paper log beside it.


Anyone who has sat at a net control table during an exercise knows the scene. Teams call in over the radio, someone scribbles on a Form 309, someone else tries to remember which grid square “Team 4” last mentioned, and twenty minutes later nobody can say with confidence where each team was or who has gone quiet. The radios work fine. The picture in the room is the problem.

Most “modern” answers to this assume data on the field end: phones with cellular coverage, tracker apps, a server somewhere. That is exactly what you can’t count on in a canyon, a wildfire perimeter or a storm-damaged county. For CERT, ACS/ARES, SAR and wildland-fire support teams that are reachable only by voice radio, the realistic workflow is still a human at a table writing down what comes over the air.

RangerTrak (rangertrak.com for the project site, rangertrak.org for the app itself) keeps that workflow and fixes what paper can’t do: it plots every report on a map, shades overdue teams red, and prints the forms ICS expects. This article covers what it is, how it works, how to set it up, where it falls short, and how it compares with the alternatives.

Last updated: November 2026.


What Is RangerTrak?

RangerTrak is a free, open-source field-report log and map, built for voice-radio teams, that runs entirely in a web browser with no server and no account. A scribe transcribes each radio report into a simple form (who, where, when, what), and RangerTrak stores the record and plots it on a map.

It is written and maintained by John Cornelison, copyright 2019 to 2026, licensed under the AGPL v3, with the source on GitHub under SteadyEOC/RangerTrak. The project describes itself as “completely free and always will be”.

Key design decisions that set it apart:

  • Built for the person at the table. The user is the scribe, not the ranger in the field. Teams keep calling in exactly as they always have.
  • No phones, accounts or installs for rangers. Nothing changes on the radio side.
  • Offline first. Install it once on a connection, save your map area, and it works with no Internet.
  • Your data stays on your device. There’s no server. The app only reaches out for map images and address lookups when you are online.
  • Paper stays. The project explicitly recommends keeping the paper log going alongside it as the backup.

Release Status (as of Writing)

Milestone Date
Alpha 29 September 2026
Beta 28 October 2026 (97 releases in four weeks, per the release notes)
Beta 2 8 November 2026
Beta 3 13 November 2026
Beta 4 “this week” per the site
1.0 target End of November 2026

The author is honest about this: it is “ready for drills, not yet a real call-out”. I would treat it the same way. Run it in exercises, break it, and report what you find.


The Problem: Paper Logs Are Reliable but Blind

The ICS Form 309 Communications Log is simple, proven and needs no power. Everyone knows how to use it. The limits are just as well known:

  • It can’t show where anyone is.
  • It’s only as legible as the handwriting.
  • There’s one copy.
  • Sorting or filtering means reading every line.

RangerTrak doesn’t replace it. It adds what paper can’t:

Capability Paper Form 309 RangerTrak
Works with no power Yes No (laptop needed)
Shows team positions No Yes, on a map
Legible entries Depends on the scribe Always
Sort, filter, correct No Yes
Overdue-team warning Memory Green to amber to red shading
Multiple copies Photocopy Backup file, spreadsheet, prints
Shared view at command post One sheet Optional read-only RangerView

How It Works: The Command Post Workflow

  Rangers / teams in the field
        |  voice radio (unchanged)
        v
  +-----------------------------+
  |  Scribe at command post     |
  |  one laptop, RangerTrak     |
  +-----------------------------+
        |            |             |
        v            v             v
   Radio Log       Map        Printed forms
  (sortable)   (tracks, red)  309 / 213 / 213RR / 214

Each call is one row of a familiar form. The default Easy menus show only the everyday workflow. The extras (tactical call signs, photos, field phones, the printed map sheet) appear in Full menus, one button away.

Entering Reports

  • Position in whatever format the radio gives you. RangerTrak takes USNG/MGRS or latitude/longitude as it is read out. The project blog also covers UTM, Maidenhead and Plus Codes, all converted on the device with no signal.
  • Pin-in-the-water check. A small map beside the form shows where the report landed. If the pin is in a lake, read the coordinates back over the radio.
  • Submit now, fix later. Don’t hold the radio to correct a report. Log it, then fix it in the Radio Log. Changing a latitude or longitude moves the pin.
  • Operator stamp. Each report records who was at the keyboard, and that never changes, so a shift change doesn’t reassign earlier entries.
  • Time sanity check. The entry screen warns if a report’s time is more than a few minutes in the future.

Watching the Mission

  • The Radio Log. Every report in one table you can sort, filter, reorder and correct. A strip names every active filter so nobody forgets rows are hidden.
  • Every team at a glance. Each ranger or team gets its own marker colour and shape. On the topographic map, lines join each team’s reports oldest to newest, so you can see which way they’re moving.
  • Overdue check-ins. Set the expected check-in interval. The map, roster and log shade time since last contact from green through amber to red. Nothing beeps, so someone has to be looking.
  • Thinning a crowded map. Hide places or entries, turn on ranger paths, a heat map or range rings, or show only each ranger’s latest report. A strip lists whatever is hidden.

The Forms It Prints

RangerTrak prints onto the forms people already use:

  • ICS-309 Communications Log, with mission and operational period on every page
  • ICS-213 General Message (tick “Also generate an ICS-213” on a report)
  • ICS-213RR Resource Request, up to nine items with priority and delivery details (Full menus only)
  • ICS-214 Activity Log, on FEMA’s own form
  • Printed map sheet with a legend listing every team and its entry count

Nothing is retyped between the log and the forms.


Offline Maps and the Readiness Dot

Offline operation is the whole point, so the preparation matters. A device that has never loaded the app gets nothing in the field.

Before You Deploy

  1. Open rangertrak.org once on a connection and install it like any app.
  2. Name the mission and set the operational period.
  3. Load a real roster.
  4. Save the map area on screen. The app keeps it plus two closer zoom levels.
  5. Download the alternative map, a second offline map with a low-detail world map built in. Demo missions carry street detail for their own area, and you can load a map file for yours.
  6. Protect storage so the browser doesn’t evict your data.

A coloured readiness dot at the top of every page checks six things: mission named, real roster loaded, operational period current, map tiles saved, alternative map downloaded, storage protected. Hover or tap it to see what is missing. It never stops you working.

On the topographic map the layers box adds a USNG/MGRS grid that works offline, plus satellite view, marked trails and terrain shading when you are online.

Test it properly: the project’s own advice is an airplane-mode test on your own device before any drill. I would add: do it on the actual laptop you will use, not your workstation.


Shift Changes and the After-Action Side

A mission outlasts a scribe’s energy, so RangerTrak handles the hand-off.

  • Operational periods. Set the next period on the Mission page. The header counts time elapsed and left, and both the 309 and the map sheet print the period, so Op 1 and Op 2 paper can’t be mixed up.
  • SitRep. A situation report generated from the radio log: totals, messages per hour, traffic by team, counts by station, operator, status and source, entries needing attention, and AAR notes. It only reads the log. Run it at each shift change as the brief and again at the end. It isn’t your EOC’s SitRep or an ICS-209.
  • Hand over to another scribe. One file carries the people, places and every entry. The receiving device merges it in. Nothing is replaced, corrections come across, and merging twice creates no duplicates.
  • AAR notes. Record something to improve in one line without leaving what you’re doing. At the debrief, add an area, recommendation, owner and optionally a HSEEP capability element (Planning, Organization, Equipment, Training or Exercise), then print an improvement-plan table or export a spreadsheet.

More Than One Device (All Optional)

One laptop and a radio is the whole basic setup. For larger operations the project offers extras, none needing the Internet:

Option What it does Notes
Field phones A ranger’s own phone files reports in field mode, with or without signal Reports sent later as a Report Packet; urgent traffic still by radio
Report Packet One file of unsent reports for email, text, AirDrop or Nearby Share Merging only adds reports it lacks, so sending twice is harmless
Receipts A small file listing report numbers, sent back so the phone marks them Received Not a replacement for “received, over”
Station letters Each laptop gets a letter so message numbers (B001, C001) never collide Vashon ACS ran three scribes this way
Display / Pop out Look-only big-type views for a projector or second monitor No server needed
RangerView Mini web server on one laptop so others on the same Wi-Fi watch the log read-only Advanced; roster never goes to it; see rangerview.org

Copies don’t sync by themselves. Devices share by files you send on purpose, or by looking at a read-only view.


RangerTrak vs the Alternatives

Feature Paper Form 309 RangerTrak Live GPS tracking (e.g. APRS, TAK)
Needs hardware on rangers No No Yes
Needs Internet/cellular No No (after install) Often network or RF infrastructure
Plots positions No Yes, from spoken reports Yes, automatic
Position accuracy n/a As good as what was read out GPS-accurate
Printable ICS forms Form 309 only 309, 213, 213RR, 214 Varies
Cost Free Free, AGPL v3 Hardware plus infrastructure
Best for Backup Voice-only teams, drills, CERT/ACS Teams with trackers

These are complements, not rivals. If your teams already carry APRS trackers or run a TAK server (see my OpenTAKServer Docker article), you have automatic positions. RangerTrak fills the gap for everyone who only has a handheld and a voice.


Honest Limitations

  • Beta software. Not yet for a real call-out. Keep paper.
  • Positions depend on the human chain. A mis-read grid reference is still a wrong pin. The pin-in-the-water check helps but doesn’t fix everything.
  • Nothing alerts you. Overdue shading is passive. Someone must watch the screen.
  • No automatic sync. Each browser keeps its own copy. Clearing site data or working in a private window loses the mission, so back it up.
  • Install needs the Internet once. Do it before you leave home.
  • Map downloads. Offline map detail is only what you saved beforehand.
  • Not a dispatch system. It logs and maps. Urgent traffic still goes by voice.

Who Should Try It

  • CERT and ACS/ARES groups running drills and wanting better situational awareness for the same effort.
  • SAR and wildland-fire support teams that are reachable only by voice radio.
  • Net controllers who keep a 309 and want a map and legible record without changing field procedure.
  • Exercise planners who want HSEEP-shaped AAR notes without retyping.

The project site includes a built-in Grand Canyon demo mission with invented people, and a guided Tour at rangertrak.org/tour. That’s the fastest way to evaluate it: about ten minutes, per the project’s own Field Notes series.


Why It Matters

Amateur radio and EmComm have spent years chasing sophisticated digital links, yet the bottleneck at most command posts is still the human at the table. RangerTrak is a refreshingly pragmatic answer: leave the radio workflow alone, make the record legible, put it on a map, print the right forms, and be upfront about what it can’t do. It is free, open source and runs offline in a browser, which is hard to argue with for a drill budget of zero.

Try the demo mission, run an airplane-mode test, then take it to your next exercise with the paper log still next to it. If something breaks, tell the author on GitHub. That feedback is how a beta becomes a 1.0.

73 de 9M2PJU.


Sources and Further Reading

Post Comment