Enter a callsign to pull the last known position from APRS.fi. This auto-fills your latitude and longitude so members with APRS trackers don't need to type coordinates.

Bearing intersection — Members with a directional antenna (Yagi, quad, beam) report the compass bearing toward the strongest signal. The app draws lines from each station along those bearings and finds where they converge. Three or more bearing reports gives an excellent fix — often within a city block.

Signal-strength weighting — Without bearing data the app uses S-meter readings as a distance proxy: stronger signal = closer to the source. The result is a weighted centroid biased toward the loudest reporters. Less precise than bearings but still useful for a first estimate.

Shared database — All reports are saved to localStorage in the browser. For true club-wide sharing, host this file on a simple web server or use a service like Netlify Drop — all members visiting the same URL will share the same report pool.

APRS import — Members with APRS trackers can look up their last beacon position automatically, or paste a raw APRS packet for instant coordinate parsing.

• Spread reporters in different compass directions around the suspected area
• Yagi or quad loops give bearing data — rubber ducks give none
• Report while the interference is active, not after it stops
• Multiple reports from the same direction don't improve accuracy
• Note if the signal seems mobile — strength will drift more than a fixed source
• Three or more crossing bearing lines narrows the source to within a few blocks

This file works fully offline in any browser. To share with club members so everyone sees the same reports in real time, upload it to any static web host (Netlify, GitHub Pages, your club website) and share the URL. All members on the same hosted page share a common report store.