Aircraft
Loading…How To Use This Tool
Compass (left) — shows the antenna bearing in degrees and cardinal direction from Station A to the aircraft, plus the elevation angle you'd need to point straight at it. The bearing updates continuously every second using dead-reckoning — the needle tracks the aircraft's estimated position between ADS-B refreshes, not just the last reported fix. Rotate your antenna to this heading. At typical scatter ranges elevation is usually under 15° and most fixed horizontal beams don't need adjusting for it — the elevation figure turns amber (⚠) when it climbs above that, which usually means the aircraft is closer-in and a beam with no elevation control may not have enough vertical pattern to reach it. Falls back to Emerald if Station A is not set.
Middle panel — shows flight data (altitude, speed, track, distance), possible scatter paths, and a Terrain Profile chart along the Stn A → Stn B path. The chart shows ground elevation with a gold dashed line-of-sight overlay. The red dot (●) marks Station A and the blue dot (●) marks Station B.
Right panel — two boxes stacked vertically:
Radio Horizon — the aircraft's total radio horizon in km, each station's distance, and whether they are ✅ Inside or ❌ Outside the horizon. Ground elevation (metres ASL) is shown for each station from SRTM data. Both stations must be inside the horizon for scatter to be possible — but that alone isn't sufficient: the aircraft also has to sit close to the direct line between the two stations (low scatter skew, shown against each candidate path) for real forward-scatter enhancement. An aircraft can be within horizon range of both stations while sitting nowhere near the path between them.
Line of Sight — checks whether terrain blocks the path from each station to the aircraft using SRTM 30m elevation data. Shows ✅ Clear, ⚠️ Masked (Fresnel zone intrusion) or ❌ Blocked. A masked path may still produce contacts but with reduced signal strength.
Aircraft Star Colours
Altitude sets the starting colour, but a poor scatter skew (aircraft sitting well off the direct line between your two stations) caps it lower regardless of altitude — an aircraft at 35,000ft+ with skew over 20° shows Poor, and over 10° shows no better than Good. Check the skew figure next to each candidate path under "Possible scatter paths" to see why a given colour was assigned.
Antennas
Minimum Height Requirements
About This Tool
Built and designed by Greg Weir VK4GDW for the Central Highlands Amateur Radio Club Inc (VK4WCH), Emerald QLD. This page is a live aircraft scatter geometry calculator for VHF operators in central and eastern Queensland. It uses real-time ADS-B position data from the VK4GDW receiver at Emerald to determine which aircraft overhead are currently in line-of-sight of both a transmitting and a receiving station simultaneously — the basic geometric requirement for aircraft scatter to be possible.
The tool does not predict signal strength or guarantee a contact. It identifies geometry only — whether an aircraft is physically positioned where scatter could occur between two stations on the selected band. Whether a contact is achievable depends on power, antenna gain, mode, and the aircraft's radar cross section.
How Geometry is Determined
For each aircraft the tool performs three checks:
An aircraft that passes all three checks is flagged as being in scatter geometry and appears in the Scatter Paths tab with a flashing icon on the map.
Radio Horizon Formula
The tool uses the ITU standard VHF radio horizon formula with band-specific atmospheric refraction factor k (ITU-R P.452) — 6m uses k=1.60, 2m uses k=1.50, and 70cm uses k=1.33:
Both the aircraft altitude (from ADS-B, converted from feet to metres) and the VK4GDW ground antenna height (9m AGL) are included. At FL350 (10,668m) this gives a radio horizon of approximately 438 km. The result is capped at 430 km — the observed maximum range of the VK4GDW ADS-B receiver (232 nautical miles, predominantly to the north of Emerald) — to avoid flagging geometrically possible but operationally unrealistic paths.
Note: earlier versions of this tool used the simpler formula 1.23 × √(alt ft) × 1.609, which omits atmospheric refraction and antenna height. The current formula is approximately 18% more accurate at typical cruise altitudes.
Scatter Quality Rating
The colour-coded quality rating reflects altitude only, as altitude is the dominant factor in both radar cross section illumination angle and horizon coverage:
Data Source and Refresh
Aircraft position data comes primarily from the VK4GDW FlightAware ADS-B receiver located at Emerald QLD, proxied via a Cloudflare Worker. Positions are updated every 10 seconds. ADS-B altitude is barometric (pressure altitude), which is standard for aviation and consistent with how aircraft scatter geometry is calculated in the literature.
VK4GDW's own receiver has a typical detection range of 160–320 km, with a maximum observed range of 430 km (232 nautical miles), predominantly to the north of Emerald — a hardware limitation, not a software one.
Wider display coverage (added 25 Aug 2026): to show aircraft beyond VK4GDW's own range, the map also pulls from the airplanes.live and adsb.lol community ADS-B networks, covering a corridor down the coast from Cairns to Sydney. This extends what you can see on the map across Queensland and eastern New South Wales — it does not extend the physics of aircraft scatter itself. Scatter-path eligibility (the Scatter Paths tab, quality badges, and skew calculations) is still governed by the actual stations you enter and their real radio horizons, regardless of which network first detected a given aircraft.
Built and designed by Greg Weir VK4GDW for the Central Highlands Amateur Radio Club Inc (VK4WCH), Emerald QLD. ADS-B data courtesy of VK4GDW. Questions or feedback — contact the club.
What is Aircraft Scatter?
Aircraft scatter is a propagation mode where VHF, UHF, and microwave radio signals reflect off the metal fuselage and wings of commercial aircraft, enabling long-distance contacts that would otherwise be impossible by direct line-of-sight. A passing airliner at 35,000 feet can briefly create a communication path of 500–1,000 km or more between two stations on the ground.
The Physics
The physics follows the Bistatic Radar Equation — the same mathematics used in aviation radar, but applied in reverse. Instead of a radar installation detecting an aircraft, two amateur radio stations use the aircraft as an unintentional reflector between them.
The received signal power (Pr) is governed by:
Ptx = Transmitter power · Gtx, Grx = Antenna gains (linear) · λ = Wavelength (m) · σ = Radar Cross Section of aircraft (m²) · Rtx, Rrx = Distance from each station to aircraft (m)
Radio Horizon
This tool calculates the radio horizon using the ITU standard formula for VHF propagation with band-specific k (6m: 1.60 · 2m: 1.50 · 70cm: 1.33):
At FL350 (10,668m) with the VK4GDW 9m antenna, this gives a horizon of ~438 km. A minimum path length of 150 km is enforced — below this, direct VHF is more practical than scatter.
Practical Notes
The key challenge is the double inverse-square law — signal strength drops with the square of the distance twice over. This makes aircraft scatter a weak-signal mode, best exploited with digital modes such as FT8 or MSK144, directional antennas, and aircraft at high altitude near the midpoint of the path.
The contact window is typically brief — 30 seconds to a few minutes as the aircraft transits the optimal scatter zone — so identifying the opportunity in advance is essential.
Aircraft positions from ADS-B receiver at VK4GDW, Emerald QLD. Data refreshes every 10 seconds. | Central Highlands Amateur Radio Club Inc · VK4WCH
Page History
A record of when this page went live and the improvements made since launch. Newest first.
- Root cause of this one turned out to be different from v3.14–v3.16: console logs (WebSocket failure logged as "Page entered Back-Forward Cache") confirmed the browser itself was freezing the entire tab because the screen locked / the laptop slept — not a leak or a hang in this page's own code. That's normal Chrome power-management behaviour for any page left running through a sleep
- The wake-up itself was still worth smoothing out: coming back from a real sleep/lock, this page used to kick off a full data refresh immediately — and since an hour away means essentially every aircraft on screen has changed, that first refresh has to rebuild every marker and card from scratch in one go, right in the same few seconds a machine is typically still catching up from waking. Now: waking from a hide longer than 60 seconds shows a brief "Reconnecting…" status and gives the browser a short moment to finish its own resume work first, before this page's refresh starts. A quick tab switch is unaffected — same as before
- This is a mitigation for a collision, not a fix for a bug in the strict sense — if the "Page Unresponsive" dialog still appears occasionally right after waking a laptop from a long sleep, that may simply be inherent to running a live map+data page through a sleep cycle
- v3.15 (below) fixed a constant per-poll cost problem — this is a different pattern: page was reported still going unresponsive after roughly an hour left running unattended, i.e. fine for a while and then hangs, which points at something that grows over time rather than something that's simply heavy every poll
- The terrain-elevation lookup cache had no upper bound and never removed an old entry — a fast-moving selected aircraft can trigger a fresh line-of-sight recheck (~50 new sample points) every poll or two, so this grew continuously for as long as the page stayed open. It's now capped and clears itself once it gets large; a cache miss just costs one lookup, itself already cached for 30 days at the edge
- The dead-reckoning position tables kept one entry per unique aircraft ever seen, for the life of the page, with nothing ever removing an entry once added — with wide-area traffic cycling through, this also grew without bound over an unattended session. Entries for aircraft no longer in the feed are now dropped every poll
- The terrain profile chart (Station A↔B elevation cross-section) was being fully rebuilt from scratch on every single poll even though it doesn't depend on the aircraft at all and only actually changes when the stations are re-applied — this was pure repeated waste on every render and is now cached until the underlying data actually changes
- Not able to load-test this against a genuine multi-hour live session from here — if it still recurs, the next check is a memory reading from Chrome's Task Manager (Shift+Esc) taken right before it hangs
- v3.14 (below) wasn't enough — the page was still freezing. Two more costs identified as the remaining causes, both fixed here
- The advance scatter prediction walk (added in v3.13) was running its full up-to-18-step lookahead for every tracked aircraft on every 10s poll, even ones nowhere near either station. It's now skipped up front for any aircraft that has no physical way of closing the gap to both stations within the prediction window — the walk itself only runs for aircraft actually close enough for it to matter
- Map markers were being fully torn down and rebuilt from scratch — remove, discard, recreate, reattach — for every aircraft on every poll. They're now moved and re-skinned in place instead, and only created or removed when an aircraft actually enters or leaves the feed
- The fixed distance between Station A and Station B was also being recalculated from scratch on nearly every scatter-geometry check, despite never changing between polls — now computed once when the stations are set
- Fixed the sidebar card lists (and, for the selected aircraft, the terrain profile and compass charts) being fully rebuilt twice every 10s poll when Station A & B were both set — one rebuild is now enough
- Fixed the per-aircraft scatter-geometry check being recomputed 5+ times per poll (once each for the map icon, the sidebar cards, the alert check, and the auto-select pass) against the same unchanged position — it's now computed once per aircraft per poll and reused
- Together these were reintroducing the same "page not responding" symptom v3.12's aircraft-count cap was built to fix, this time via per-aircraft cost rather than aircraft count — most noticeable with both stations set on a busy wide-area poll
- New: advance scatter prediction — once Station A & B are set, each approaching aircraft's current track/speed is projected forward (straight-line, constant altitude, up to 3 minutes ahead) to check whether it's about to enter valid scatter geometry. A thin gold dotted line now shows the projected closing path with an ETA tooltip, before the aircraft actually crosses in — previously the dashed scatter-path line and the 🔔 Alert bell only appeared/rang at the exact moment of entry, with no earlier warning
- 🔔 Alert now also fires a short single "approaching" blip (distinct from the richer two-tone entry bell) the first time an aircraft is predicted to enter — once per approach, not every 10s poll while it closes in
- This is a projection based on current heading and ground speed holding steady, not a guarantee — a turning or descending aircraft can still enter the zone with no advance prediction, or be predicted and then turn away
- Map markers changed from a star/kite shape to a top-down aircraft silhouette that rotates to match each aircraft's heading
- Markers now keep their true Excellent/Good/Poor/None quality colour at all times — previously, once Station A & B were both set, every aircraft outside that specific pair's scatter path was flattened to one grey regardless of its real quality; now only the opacity dims for off-path aircraft, colour stays meaningful
- Added a dark outline/halo to every marker so it reads clearly against any OpenStreetMap tile colour (water, roads, land) rather than relying on fill colour and size alone; marker size increased slightly (20→22px) and the dimmed opacity floor raised (0.55→0.65) so the new outline doesn't wash out on off-path aircraft
- New Metric Alt feature toggle — switches every displayed aircraft altitude between feet and metres. Feet remains the default, since it's the worldwide aviation reporting standard the ADS-B data itself arrives in (used in Australia too, not a US-only convention) — this is a display option, not a correction
- Fixed grounded aircraft (common near the major airports now in range via wide-area coverage) occasionally being processed with a non-numeric altitude, which could contribute to the map appearing to hang
- Capped the number of aircraft actively rendered on busy polls (e.g. near Brisbane/Sydney) to keep the map and sidebar responsive — the busiest, most relevant aircraft for your selected stations are always shown first; the visible count reads "150 of 340" style whenever more traffic exists than is being displayed
- Lightened the map marker colour used for aircraft outside your selected station pair's scatter zone — it previously matched the page's own dark background colour too closely and could read as the whole map going black rather than as dimmed
- The map now shows aircraft across a Cairns-to-Sydney corridor — Queensland and eastern New South Wales — instead of only the ~430km bubble around VK4GDW's own receiver at Emerald. VK4GDW's own feed is still queried and always takes priority for any aircraft it detects itself; the wider area comes from the free, keyless airplanes.live and adsb.lol community ADS-B networks, merged in and de-duplicated by the proxy Worker
- This widens what you can see, not the physics — scatter-path eligibility, quality badges, and skew calculations are unchanged and still depend entirely on the real stations you enter and their actual radio horizons. An aircraft showing on the map from Sydney or Cairns doesn't mean it's usable for scatter unless it also sits near the line between your two chosen stations
- Found and fixed two real bugs while building this: an early version could disproportionately show aircraft in the north while dropping ones further south due to a request-timing bug, and a burst of near-simultaneous requests to the community networks could trip their published rate limits and return nothing for a whole poll cycle. Both are fixed — the proxy now paces requests to respect those limits and caches each area's data briefly so a single slow or failed request doesn't make aircraft flicker on and off the map
- Full technical detail on the proxy-side design and the bugs found along the way is kept in the club's project notes (CHARC-AircraftScatterPhysics-FactCheck-25Aug2026.md) rather than duplicated here
- Fixed a real scatter-geometry bug — reported live: the compass pointed at an aircraft to the southwest while trying to work a station almost due east. Root cause was that the scatter-path matching only checked whether a candidate aircraft was within radio-horizon range of both stations independently — it never checked whether the aircraft was actually near the direct line between them. For a short A-B hop the two horizon circles overlap over a huge area, so an aircraft nearly behind the operator could still pass. Added
scatterSkewDeg()— the true bistatic scattering angle at the aircraft, via the spherical law of cosines — and gated every scatter-path function on it (max 30° skew to appear at all). The reported case measured 161° skew (nearly the opposite direction) and is now correctly rejected. Fixed in all three places this logic existed: the main scatter-path finder (both default and custom Station A/B modes) and the separate Watchlist pair function - Every scatter path now shows its skew angle next to the distance (e.g. "656 km · skew 27°") so the geometry quality is visible, not just asserted
- Quality badge (Excellent/Good/Poor) now factors in skew, not just altitude — a 35,000ft+ aircraft at high skew was previously badged identically to one with near-perfect geometry. Skew over 20° now caps the badge at Poor, over 10° caps it at Good, regardless of altitude. Applied everywhere the badge appears: aircraft cards, map marker colours, the map popup, and the Watchlist tab's best-aircraft badge
- Added an elevation angle to the Antenna Bearing compass — previously azimuth-only, even though the Instructions already told operators to point at "azimuth and elevation." Computed from station ground elevation + antenna height vs. aircraft altitude, with an earth-curvature correction consistent with the existing radio-horizon maths. Turns amber above 15°, the rough point where a fixed horizontal Yagi's vertical pattern may not reach a closer-in aircraft
- Fact-checked the band physics against documented real-world aircraft-scatter contacts (W3SZ paper; a 452km 70cm QSO from 1996; an 850km 1.3GHz QSO from 2006) and corrected the "max scatter" figures that didn't hold up: 6m dropped from an unsupported 1,500km down to 850km (a 30,000ft reflector geometrically can't reach 1,500km — that figure was likely borrowing from unrelated 6m propagation modes like Sporadic-E); 70cm raised from 400km to 500km (the old figure was already beaten by a real 1996 QSO). 2m's 800km was already correct and left unchanged. Relabelled "Max scatter" to "Typical range" on the band buttons since real contacts land on both sides of these figures under good or poor conditions
- Updated the Compass and Radio Horizon descriptions, and the Aircraft Star Colours legend, in this Instructions tab to explain the elevation angle and the skew requirement — the star-colour legend previously described Excellent/Good/Poor by altitude alone, which is no longer the whole story
- Full reasoning, sources, and before/after numbers for all of the above kept in the club's project notes (CHARC-AircraftScatterPhysics-FactCheck-25Aug2026.md) rather than duplicated here
- The selected/pinned aircraft now always sorts to the top of both the Scatter Paths and All Aircraft lists — previously list order was arbitrary (feed order), so the expanded card with the compass could be buried and need scrolling to find
- Remaining aircraft in both lists now rank the same way auto-select judges "best" — size tier first, altitude as the tiebreaker — so the list order matches what the tool considers the better contact
- Terrain profile chart labels moved out of the tiny SVG (where the text was unreadably small) into normal-sized HTML text below the chart — Station A and Station B elevation now shown directly in metres ASL under each coloured dot, plus peak/low elevation, path relief in metres, a plain-language descriptor (Gentle/Rolling/Hilly/Mountainous) and the vertical exaggeration factor
- Terrain chart Y-axis scale replaced twice in testing before landing on this: auto-fit-to-range gave ×400+ exaggeration on long gentle paths and looked like a mountain range; capping exaggeration relative to distance flattened it into an unreadable rectangle instead. Now uses a fixed 1000m reference ceiling — 190m of real relief always reads as a modest ~19% of chart height on any path length, while terrain that genuinely approaches/exceeds 1000m of relief fills the chart for real. Exaggeration for a typical Central QLD route is now ×60–90, not ×25 or ×400+
- Cross-checked the Emerald↔Charters Towers profile against latlonics.com's elevation tool (Copernicus DEM via Open-Meteo) — our SRTM 30m figures (peak ~359m, low ~172m, 187m relief) are internally consistent and reproducible, but latlonics shows a taller peak near the Charters Towers end (~425m) and a lower low (~164m), ~261m relief total. Likely cause: SRTM 30m under-resolving a narrow ridge near Charters Towers that a denser Copernicus DEM sample catches — worth revisiting the Cloudflare Worker's elevation dataset if LoS accuracy near ridgelines matters (outside this file — the dataset choice lives in the Worker, not here)
- Terrain sample resolution is now distance-scaled, up to 100 points along the route (~5km spacing) instead of a flat 40 — narrow ridgelines like the one near Charters Towers are less likely to fall between sample points and get missed. Scales down to 20 points on short paths so short routes aren't over-fetching
- Fixed terrain chart getting stuck on "Loading…" forever when the elevation fetch actually failed — a failed/timed-out request was setting the profile state back to a bare null, and the render logic couldn't tell that apart from "still loading", so a real failure looked identical to a stuck spinner with no way to tell what happened. Failures now show an explicit error message and a Retry link; fetch timeout also now scales with point count (was a flat 10s, tight for a 100-point request)
- Fixed compass rose (and the whole selected-aircraft card) disappearing shortly after clicking an aircraft — auto-select was re-running on every 10s refresh and silently reassigning or clearing the selection out from under a manual click
- Manually selecting an aircraft (card or map star) now pins it — auto-select leaves it alone until you deselect it, click a different aircraft, hit Clear, or the aircraft drops out of the ADS-B feed entirely
- Line of Sight now keeps refreshing for a manually pinned aircraft on every cycle, not just at the moment of selection
- Auto-select "best aircraft" logic was ranking by altitude alone, which could pick a small aircraft over a large one just because it was a little higher — now ranks by aircraft size first (Large > Medium > Small, bigger radar cross-section → stronger scatter return), altitude as the tiebreaker within the same size tier
- Card click in the sidebar now toggles deselect on a second click, matching the map star's existing behaviour
- 📍 Find My Grid modal now includes a zoomable OpenStreetMap map — click anywhere to drop a pin, or drag the pin to fine-tune, for a more accurate station location than the grid square centre
- Map syncs both ways with the search box and manual lat/lon fields — using either one re-centres the map and moves the pin
- Opening the map from a station's LAT/LON button now centres on that station's existing precise location, if one is already set
- 📋 Load Fav dropdown now has a "🗑 Delete All" button in the footer to clear every saved favourite in one go, with a confirmation prompt
- Fixed terrain profile warping when the elevation API returned a null/failed point — previously those points were dropped from the array entirely, which re-indexed every point after the gap and shifted the whole profile along the distance axis (the same failure mode the v2.7 "stale zero-elevation" cache fix only partially addressed)
- Missing points are now interpolated from the nearest valid neighbours instead of being dropped — the distance axis stays correct even when a lookup fails
- Sample resolution doubled from 20 to 40 points along the Stn A → Stn B path (~10km spacing instead of ~21km) for finer terrain detail on longer paths
- Vertical exaggeration factor now shown on the chart (e.g. "×37 vert.") so a gentle rise over a long path isn't misread as a steep one
- Amber warning shown on the chart when any sample point had to be interpolated, so a data gap is visible rather than silent
- Fixed compass needle disappearing and reappearing outside the compass rose
- Root cause: drTick() was holding a stale reference to the needle DOM element after renderCards() rebuilt the card HTML — the old element was detached but still being written to
- drTick() now checks needle.isConnected before updating — skips update if the element has been replaced
- renderCards() now re-applies the current DR bearing to the freshly rendered needle immediately after card rebuild — needle is always correct from the moment it appears
- Terrain Profile removed from the feature toggles row — terrain profile now always visible by default
- Terrain profile toggle was also broken (getElementById lookup failed as the element is rendered fresh each card rebuild) — fixed as part of removal
- Terrain Profile toggle fixed — was looking for a static DOM element ID that doesn't exist; toggle now calls renderCards() which re-renders the card with the correct display state baked in
- Dead Reckoning toggle confirmed working — drTimer interval correctly stopped and restarted; drTick() also has an internal gate as backup
- Hot Area toggle gate moved inside drawHotArea() as the first check — previously only gated at the call site, meaning some code paths could bypass it and redraw the polygon after it was turned off
- Instructions tab updated — Step 10 (Watchlist) and Step 11 (Feature Toggles) added
- Updates tab populated with correct v3.4 and v3.5 entries
- Three-panel selected aircraft card now stacks vertically on mobile instead of overflowing horizontally
- Compass panel goes full-width and horizontal layout on mobile
- Navigation tabs now wrap to a second row on small screens rather than overflowing
- Feature toggle buttons scale down on mobile
- Separate tablet breakpoint (501–800px) added for tab sizing
- New Watchlist tab in the sidebar — monitor two independent station pairs simultaneously
- Each pair has its own callsign and grid square inputs, Set button, and live scatter result display
- Shows aircraft count in scatter zone plus best candidate (flight number, altitude, quality badge)
- Per-pair 🔔 scatter alert bell — rings when a new aircraft enters that pair's scatter zone independently of the main Station A/B alert
- Pair settings (callsigns, grids, alert state) persist to localStorage and restore on page load
- Feature toggle row added below the station bar — five pill buttons to turn individual features on or off
- Hot Area — show/hide the magenta mutual scatter zone polygon
- Dead Reckoning — enable/disable smooth position estimation between ADS-B refreshes
- Labels — toggle map star labels (ready for future label layer)
- Scatter Alert — toggle the audio bell for new aircraft entering the scatter zone
- Terrain Profile — show/hide the elevation cross-section in the selected aircraft card
- Toggle states persist to localStorage and restore on page load
- Bug fix: currentBand variable reference corrected to selectedBand in horizonK() — was causing ReferenceError on every feed refresh, preventing all aircraft markers from displaying on the map
- Callsign, grid square, and antenna height input fields narrowed for a more compact station bar
- Antenna height spinner arrows dimmed at rest (60% opacity) and full brightness on hover — visible without dominating the field
- Antenna tower SVG icon added next to antenna height field — tapered lattice mast with crossbar and guy wires
- LAT/LON button replaces the globe icon next to each station — clearly labelled in blue, opens Find My Grid modal focused on the coordinate entry fields
- 📍 Find My Grid button moved to the left of Station A in the station bar
- Stations can now use a precise GPS location instead of the grid square centre — use Find My Grid (GPS, map click, or town search) and click → Stn A or → Stn B to capture the exact position
- Precise coordinates stored invisibly alongside the grid square — no extra fields in the station bar
- Map marker tooltip shows ★ precise in green when exact coordinates are in use, or (grid centre) when falling back to the midpoint
- Affects all geometry: radio horizon, hot-area polygon, LoS terrain check, and station-to-aircraft distance
- Useful for stations outside the centre of their grid square — e.g. a station 10km outside a town in a 6-character grid
- Precise coordinates cleared when stations are cleared; grid square entry alone continues to use the square centre as before
- Radio horizon calculation now uses band-specific atmospheric refraction factor k, per ITU-R P.452
- 6m (50 MHz) — k=1.60, constant 4.515 — largest radio horizon of the three bands
- 2m (144 MHz) — k=1.50, constant 4.372 — moderate refraction
- 70cm (432 MHz) — k=1.33, constant 4.122 — least refraction, smallest horizon
- Previously a fixed k=4/3 (4.122) was applied to all bands — 6m horizon was understated by ~9%, 2m by ~6%
- Hot-area polygon, scatter zone, and Radio Horizon panel all reflect the corrected values
- Hot-area polygon added to the map — shows the geographic region where an aircraft must be for mutual radio horizon visibility from both Station A and Station B simultaneously
- Calculated as the intersection of the two radio horizon circles, one centred on each station, at the selected aircraft altitude
- Rendered as a magenta semi-transparent filled polygon — the same convention used by AirScout
- Hover tooltip labels the region as the mutual scatter zone
- Only appears when both Station A and Station B are set and an aircraft is selected
- Updates automatically when a new aircraft is selected or the band changes
- Cleared with the rest of the scatter layers when stations are cleared
- Aircraft positions now estimated between 10-second ADS-B refreshes using speed and track from the last fix
- Map stars slide smoothly to their estimated position every second rather than jumping on each data update
- Antenna bearing compass updates continuously — bearing and cardinal direction reflect the aircraft's current estimated position, not just the last ADS-B report
- Extrapolation capped at 60 seconds of travel to prevent runaway drift if ADS-B updates are delayed
- Dead-reckoning pauses automatically when the browser tab is hidden, resuming on return
- Favourite stations added — save up to 10 Station B entries (callsign, grid square, antenna height) to browser storage
- ⭐ Save to Fav button added to the station bar — saves current Station B to the favourites list in one click
- 📋 Load Fav ▾ button added — opens an inline dropdown listing all saved favourites; click any row to load into Station B and recalculate immediately
- Duplicate detection — same callsign and grid square will not be saved twice
- Delete from dropdown — entries can be removed directly from the Load Fav dropdown without switching tabs
- 📍 Find My Grid button moved to the left of Station A for easier access
- Save button removed from station bar — replaced by the Favourites workflow
- Station ground elevation (metres ASL) now fetched from SRTM 30m API when Calculate is pressed — two points, cached 30 days at Cloudflare edge
- Ground elevation now factored into Line of Sight geometry — a station at 180m ASL is correctly treated as 180m above sea level in the LoS maths, not at ground zero
- ASL label now displayed in gold next to each station callsign in the Radio Horizon panel
- LoS recheck threshold lowered from 5km to 2km aircraft movement — fast cruise aircraft no longer get stuck on Checking
- Cloudflare Worker elevation cache versioned to prevent stale zero-elevation entries from flattening the terrain profile chart
- Station A callsign now shown in red in Radio Horizon and Line of Sight panels — matching the red dot on the terrain profile and the red station marker on the map
- Station B callsign now shown in blue in both panels — matching the blue Station B in the controls
- Colour coding is consistent across compass legend, terrain chart, Radio Horizon, and LoS panels
- Scatter path label and station name text brightened to full white for legibility
- Terrain profile legend updated — Station A labelled in red (●), Station B in blue (●), matching the dots on the chart
- Station B dot on terrain SVG changed to blue to match controls legend
- Selected aircraft card restructured into three side-by-side panels — compass (left), middle info+terrain, right data panels
- Middle panel contains flight data, scatter paths, and terrain profile stacked vertically — fills the full available width between compass and right panel
- Right panel retains Radio Horizon and Line of Sight boxes only
- Non-selected cards revert to the compact single-column layout as before
- Station A label shown in red across compass, terrain profile dot, Radio Horizon, and LoS panels — consistent with red map marker
- Station B label shown in blue across all panels — consistent with green map marker
- Terrain profile Station B dot changed from blue to green to match
- Terrain profile moved from the right panel into the centre of the card row between the compass and the Radio Horizon/LoS panel
- Profile SVG widened to fill the available middle column space
- Terrain Profile panel added between Radio Horizon and Line of Sight — SVG elevation cross-section along the Stn A → Stn B path
- 50-point SRTM 30m elevation fetch triggered on Calculate — gold dashed LoS line overlaid, red/blue dots mark each station end
- Profile fetched once per station pair, not per aircraft refresh — cached 30 days at Cloudflare edge
- Station callsign labels in Radio Horizon and LoS panels brightened to full white for legibility
- Selected aircraft card restructured into three side-by-side panels — compass (left), flight data + scatter paths (centre), Radio Horizon + LoS (right)
- Line of Sight panel added — checks terrain between each station and the aircraft using SRTM 30m elevation data via Cloudflare Worker
- Shows ✅ Clear, ⚠️ Masked (Fresnel zone intrusion), or ❌ Blocked per station
- Aircraft size badge added to selected aircraft card header — shows Small Aircraft, Medium Aircraft, or Large Aircraft based on ADS-B emitter category
- Size derived from ADS-B category field: A1/A2 = Small, A3/A6 = Medium, A4/A5 = Large — badge is hidden when category is not available
- Fixed terrain profile SVG rendering NaN coordinates when elevation API returns fewer than 2 valid points — caused screen jitter on slow hardware every 10-second refresh
- Fixed button hover jitter on low-resolution screens — band and altitude buttons no longer cause layout reflow when hovered
- Band selection now applies real physics — changing band genuinely alters scatter geometry, not just display labels
- 6m (50 MHz) — max practical scatter distance 1,500 km, Excellent threshold 30,000ft, lowest path loss
- 2m (144 MHz) — max practical scatter distance 800 km, Excellent threshold 35,000ft, standard aircraft scatter band
- 70cm (432 MHz) — max practical scatter distance 400 km, Excellent threshold 38,000ft, highest path loss requiring closer/higher aircraft
- Scatter path label now shows band-specific max range — e.g. "Possible scatter paths (144 MHz · max 800 km)"
- Quality badges (Excellent/Good/Poor) now use band-specific altitude thresholds — 70cm requires higher aircraft than 2m or 6m
- Band buttons now show a tooltip on hover explaining physics parameters for each band
- Aircraft type (ICAO code), registration, and description added to flight info box and map popup when available from ADS-B feed
- Cloudflare Worker updated with /elevation route — proxies terrain elevation requests to OpenTopoData SRTM 30m dataset
- Elevation results cached at Cloudflare edge for 30 days — repeated requests for the same path return instantly with no external API call
- Line of Sight and Radio Horizon panels in the compass card are now fully operational
- Up to 20 path sample points processed in a single batched request per refresh cycle
- Radio Horizon and Line of Sight moved into a dedicated third panel to the right of the compass — keeps the compass clean and gives terrain data its own space
- Radio Horizon panel shows total horizon distance in km, each station's distance to the aircraft, and whether they are inside ✅ or outside ❌ the horizon
- Rockhampton and Mackay added as default scatter targets — the most realistic contacts from Emerald given ADS-B range
- Charters Towers and Toowoomba added as targets
- All targets reordered by realistic probability from Emerald — Rockhampton, Mackay, Townsville, Charters Towers, Cairns, Brisbane, Gold Coast, Toowoomba, Sydney, Melbourne, Adelaide
- Distance ranges adjusted per city to match actual scatter geometry from Emerald
- Antenna height fields added to Station A and B — default 10m AGL, saves to browser between visits
- Line of Sight check added to compass card — uses terrain elevation data via Cloudflare Worker and OpenTopoData to check both station paths to the selected aircraft
- LoS shows three states per station: ✅ Clear, ⚠️ Masked (Fresnel zone intrusion), ❌ Blocked
- LoS only rechecks when aircraft moves more than 5km — avoids unnecessary API calls
- Fetch timeout added — any stalled network request now aborts after 8 seconds instead of hanging indefinitely
- Load guard added — prevents refresh cycles stacking if a previous fetch hasn't completed
- LoS guard added — prevents concurrent LoS checks running simultaneously
- Polling pauses automatically when the browser tab is hidden and resumes when you return — prevents page hanging after extended idle periods
- Flight data compacted into a single inline info box — Alt, Spd, Trk, Dist on one line, freeing space for the compass panel
- Compass panel widened to 140px, SVG enlarged to 90px, bearing text increased for better readability
- Band selector buttons now correctly deselect the previously active band — clicking 2m then 70cm then 6m no longer leaves all three highlighted simultaneously
- Changing band now also refreshes the map markers and scatter zone calculations to reflect the new frequency
- Antenna bearing compass added to scatter cards — shows compass rose with bearing in degrees and cardinal direction from Station A to the aircraft
- Compass moved to the left of the card and enlarged for better visibility
- Compass falls back to Emerald as reference point when Station A is not set, with clear labelling
- Compass only displays on the selected card — keeps the list clean
- Auto-select — when Station A and B are set, every refresh automatically selects the highest altitude aircraft in the scatter zone and displays its compass bearing
- Auto-select always promotes the best aircraft — if a higher aircraft enters the zone it takes over immediately
- Quality badges (Excellent/Good/Poor) now only display for aircraft geometrically within the scatter zone between Stn A and Stn B — aircraft outside the zone show a neutral grey "Tracking" badge instead
- Aircraft stars on the map are greyed out and dimmed when outside the scatter zone — makes it immediately obvious which aircraft are useful
- Map tiles switched from ESRI World Physical to OpenStreetMap — towns, cities and roads now visible at all zoom levels
- Clicking a selected aircraft star a second time removes the radio horizon ring and deselects it
- Antenna guidance added to Instructions tab — recommended types for 2m, 6m, and 70cm with pointing advice
- Antenna pointing clarified — both stations aim toward the aircraft's azimuth position; beamwidth tolerance means exact tracking is less critical than accounting for Doppler shift
- Minimum height requirements added — antenna height recommendations and aircraft altitude thresholds with colour-coded guidance
- Scatter Alert added — audio bell tone sounds when a new aircraft enters the A↔B scatter zone; uses Web Audio API, no external files required
- Alert toggle sits inline with the Calculate/Find My Grid/Clear buttons for a cleaner layout
- Alert only activates when Station A and B are set; auto-disables when stations are cleared
- Flashing callsign colours updated to match altitude quality colours — green/amber/purple
- Minimum altitude buttons colour-coded — purple (All 15,000ft+), amber (High 25,000ft+), green (Cruise 35,000ft+)
- Altitude button labels updated to All / High / Cruise to clarify minimum threshold behaviour
- Controls bar vertical gap tightened for a more compact layout
- Find My Grid calculator rebuilt — town name search and manual lat/lon coordinate entry replacing unreliable click-on-map
- Radio horizon formula upgraded to ITU k=4/3 standard — includes atmospheric refraction and VK4GDW 9m antenna height, improving accuracy by ~18% at cruise altitudes
- Minimum scatter path distance raised from 100 km to 150 km
- ADS-B receiver max range corrected to 430 km (232 nautical miles), predominantly north of Emerald
- About tab added — full methodology and accuracy documentation
- Updates tab added
- Page subtitle corrected to "central and eastern Queensland"
- CHARC VHF Propagation Tool heading made more prominent
- Find My Grid rebuilt — map removed in favour of town search and manual lat/lon coordinate entry
- Minimum altitude filter buttons colour-coded to match quality scheme — purple (All 15,000ft+), amber (High 25,000ft+), green (Cruise 35,000ft+)
- Flashing callsign colours now match aircraft altitude quality colour — green/amber/purple instead of white
- Altitude filter button labels updated to "All / High / Cruise" to clarify minimum threshold behaviour
- Gold dashed line drawn between Station A and Station B showing path distance
- Flashing star animation — aircraft in valid scatter geometry between saved stations flash on the map with white glow pulse
- Flight number in sidebar flashes in sync with the map star
- Open Graph preview meta tags added for social media link sharing
- Station A/B controls restructured for mobile layout
- Find My Grid calculator added — location search and GPS
- Aircraft Scatter Calculator built and deployed to charc.org.au/aircraft.html
- Live ADS-B feed from VK4GDW Emerald QLD via Cloudflare Worker proxy
- Leaflet map with real-time aircraft positions, colour-coded by altitude
- Scatter path detection for Emerald vs. Rockhampton, Mackay, Townsville, Charters Towers, Cairns, Brisbane, Gold Coast, Toowoomba, Sydney, Melbourne, Adelaide
- Station A/B custom path calculator with Maidenhead grid square input
- Band selector — 2m (144 MHz), 70cm (432 MHz), 6m (50 MHz)
- Minimum altitude filter — 15,000ft / 25,000ft / 35,000ft
- Aircraft data refreshes every 10 seconds
- Statcounter analytics deployed
Built and maintained by Greg Weir VK4GDW · Central Highlands Amateur Radio Club Inc · VK4WCH · Emerald QLD