A Logbook That Lies Less

Read enough logbooks and a pattern shows up that has nothing to do with propagation. Entries written the same night tend to be plain: a frequency, a time, a rough sense of how the signal came and went. Entries copied over a week later, or reconstructed from memory on a slow Sunday, drift. The weak carrier that faded in and out for ninety seconds becomes, in hindsight, a solid catch. The station that never quite resolved into readable audio becomes logged, full stop. None of this is dishonesty in any deliberate sense — it is just what memory does to a signal once the receiver is off and the desk has gone quiet.

The shape of a log entry

A useful entry earns its keep on five fields: date and time in UTC, frequency, mode, a note on the signal, and whatever actually identified the station — a call sign, an announcer's language, a piece of music that matched a known schedule. Miss any one of them and the entry turns decorative rather than useful. It becomes a memory aid for someone who was already there, not a record that can stand on its own months later when a card finally shows up asking to be matched against it.

Where memory cheats you

One night in April, something thin and steady sat on 17.870 MHz a little after local dark. No pad was within reach, so nothing got written until the next morning. By then the recollection had firmed up into something more confident than the listening session actually was — a clean signal instead of a marginal one, a definite identification instead of a probable one. The frequency was still correct. Almost everything else about that entry had been quietly upgraded overnight, without any intention to mislead anyone, including the person doing the upgrading.

The five-minute rule

The fix that has held up on this desk is dull: log during the session, not after it. A pad sits next to the radio, and the entry gets written the moment an identification is reasonably confirmed — not at the end of the evening, not the next morning over coffee. Waiting even twenty minutes is enough time for a fade to become a "strong opening" in memory. Writing at the moment of hearing keeps the entry closer to what the receiver did, rather than what a tired brain later decided it must have done.

The log is not a trophy case. It is a record of what the receiver actually did, written by someone who was in the room.

What belongs in the log, and what doesn't

Observed fact and interpretation are easy to blur on paper, and worth keeping apart on purpose. "Frequency drifted roughly 200 Hz over the session" is an observation. "Probably a low-power relay transmitter" is a guess, however reasonable. Both are worth writing down, but only one belongs in the same column as the time and frequency. A separate line for notes and theories keeps the factual spine of the log from absorbing every hunch that seemed plausible at the desk that night.

The same discipline applies to what gets left blank. An unfilled field is honest; it says the information wasn't captured. A field filled in weeks later from a vague memory of "probably around nine at night" looks identical to one written in real time, and that is exactly the problem — nothing in the page distinguishes a fact from a reconstruction unless the habit of writing at the time is kept without exception.

A stricter field, row by row

Cross-checking against the card

Every confirmation that eventually arrives is a small audit. Comparing the date and time on a mailed card against the corresponding logbook line catches transcription slips that would otherwise sit uncorrected for years — a time entered an hour off, a frequency mistyped by five kilohertz. One card took four months to arrive, long enough that the original entry had to be located rather than recalled, which is exactly the point of keeping it precise the first time. A log that can only be trusted by the person who wrote it, on the night they wrote it, isn't doing the job a log is for; the record is what accumulates value, not any single entry in isolation.

A short checklist has done more for accuracy here than any amount of good intention:

• Log during the session, not after it ends.
• Record UTC time to the minute, at the moment of identification.
• Keep what was heard separate from what was assumed.
• Note the antenna and radio in use — a fade might be the equipment, not the sky.
• When a card arrives, check it against the entry, not against memory.

A format that resists flattery

None of this makes a logbook more impressive to read. If anything, a stricter format produces fewer standout entries and more ordinary ones — faded signals recorded as faded, uncertain identifications left marked uncertain. That plainness is the point. A logbook is not competing with anyone else's; it only has to hold up against what actually came through the wire, months or years after the session ended, when the only witness left is the page itself.