Flood-Net
Investigations
Write-ups of strange data and what was behind it. Each one is dated, says how sure it is, and keeps the exports
and the script that drew its figures in the repository, so anyone can check it or run it again on new data.
02 · 29 October 2026 · Toowoomba AL ·
Open: Toowoomba implicated, site fault not yet found
Toowoomba AL's repeater stopped transmitting at 04:35 on 25 October, 78 minutes after its rain counter reset to
0. On its channel, 151.525 MHz, corrupted copies fell from 53 to 19 per 1,000 at that moment, on the same
traffic, back to the early-October level. Neither our receiver's update the day before nor anything else at our
end caused it. Toowoomba's own carrier had been sending corrupted copies twice as often as the other repeaters
on its channel, and it looks to have been failing since 15 October.
01 · 27 October 2026 · Billaboo AL and Blackdown Tableland AL ·
Open: cause narrowed, not confirmed
The crosses climbing above the rainfall line are second copies of real reports, damaged as they were relayed.
Each arrives about a second after a clean copy, with its upper bits changed. Old ALERT frames have no checksum,
and their check bits can't see damage in the last byte, so it gets through and reads high. The same fault
explains Blackdown Tableland's odd-looking reset, and Emerald Radar is the only repeater both stations share.
Adding one
- Take the next number and a short name, as
<year>-<month>-<what>. The page
goes here as investigations/<name>.html, its data under
data/investigations/<name>/, and the script that computes its figures under
tools/investigations/.
- Keep it to two printed pages. Lead with the answer, then the evidence, and say what is established, what is
likely and what is still open.
- Add it to the top of this list, and to
sitemap.xml.
- Never quote site codes or landholder contact details. They stay in the inspection records.