Short answer: Every Cabrillo QSO line carries a date and a time in UTC. A contest that runs across one or more midnights in UTC gives the date a chance to go wrong: a computer that works in local time, a logger that changes the day at the wrong moment, or a manual edit that moves the clock. Wrong dates can put QSOs outside the contest period or in the wrong day of a two-day event. Set the computer to UTC or verify the offset, watch the first minutes after 00:00 UTC, and check the dates in the exported file.
Why midnight is special
Most HF contests are described in UTC, and many of them start or end at 00:00 UTC or run through it. A weekend contest such as the ones on the Contest Analyzer contests page begins on a Saturday and ends on a Sunday, so the date in the log changes at least once, and sometimes at a surprising moment for you. For a station in Europe, midnight UTC is already the middle of the night, when you are tired and busy with a good low-band opening. If the logger does something unexpected at that moment, you are unlikely to notice.
The date and the time are separate fields in the QSO line, but they are related. A QSO at 23:59 on Saturday and a QSO at 00:01 on Sunday are two minutes apart, but their dates differ. If the logger changes the time but forgets the date, or the other way round, the line is wrong even if every other field is right. The result may be a QSO that appears two days earlier or twenty-four hours later than it should.
Common causes of rollover errors
- The computer clock is set to local time. The logger shows a time that looks reasonable to you, but it is not UTC. The date then changes at your local midnight instead of 00:00 UTC.
- Daylight saving changes. If the computer follows local time and the clocks change near a contest weekend, the offset between local time and UTC moves by an hour. A log that is mixed between the two offsets has a gap or an overlap.
- Manual date entry. Some loggers allow you to type the date for a QSO. A typing error at midnight, or a date copied from the previous line, leaves one wrong date in a long log.
- Time zone settings in imports. A log merged from several computers, or imported from an older file, may carry a different offset on part of the QSOs.
- Midnight written as 2400. Some people write the end of a day as 2400 instead of 0000 of the next date. The Cabrillo format expects the time as four digits, and a nonstandard value can confuse a program that reads the file.
What a rollover error looks like in a log
The easiest sign is a QSO that falls outside the contest period. If the contest starts at 00:00 UTC on Saturday and a QSO has a Friday date, it is clearly wrong, because nobody could have worked a contest QSO the day before. The article on QSOs outside the contest period explains why these lines matter. A date error can also place a QSO inside the period, but on the wrong day, which is harder to see.
Look at the order of the QSOs. In a normal log the times grow from the first line to the last. A block where the time jumps back by a day, or where the date goes forward and then backward, is a rollover problem. Another sign is a sudden gap of almost exactly twenty-four hours, or of exactly one hour, which points to a time zone or daylight saving issue. For other kinds of time faults, see wrong PC clock and UTC errors.
Set the clock before the contest
The cleanest solution is to run the logging computer on UTC for the whole contest. Many contesters set the operating system time zone to UTC, or use a utility that shows UTC next to local time. Check the setting at least a day before the contest, not in the last hour. After you change the time zone, restart the logger and open a test log to see that the time shows UTC and that the date is right.
Synchronise the clock with a network time source, and test it again. A clock that drifts by several seconds is not a problem for the date, but a clock that is wrong by an hour or a day is. The more general advice is in the article about computer time sync, which also covers contest computers that are not on the internet.
Watch the first minutes after 00:00 UTC
If your contest passes through midnight UTC, make a small habit of looking at the log at that time. Take ten seconds to see that the date in the new QSO line has changed and that the time is correct. If you work with a second computer, check both. This is a cheap test, and it is easier to repair a wrong date after a few QSOs than after two hundred.
For multi-operator stations the habit should belong to the operator who is on the radio at the time. Write it into the shift plan: at 00:00 UTC, one person verifies the date. If you merge logs from several computers, verify the date on each of them before the merge, because the combined file is hard to repair if only one computer was wrong. The article on multi-op log merge errors shows what can happen.
Check the exported file
When you export the Cabrillo file, open it in a text editor, not only in the logger. Look at the first and the last QSO line, and look at the lines around midnight. Do the dates follow the order of the contest? Is the first QSO on the first day, and the last one on the last day? Are there lines with a date that does not belong to the contest at all? A few minutes here saves you from a submission that is rejected or reclassified.
A log checker can also help. Contest Analyzer marks QSOs outside the contest period, so a date that moves a QSO outside the window will show up in the report. You can then correct the line in the table and download the corrected Cabrillo file. The contests page lists the period of each supported contest, which makes it easy to compare with your file.
Operating habits that reduce the risk
Some habits make rollover errors less likely without extra effort. Do not pause the logger or close it at midnight, because a restart is exactly when a clock setting can change. Do not edit QSO times by hand during the contest, even when a time looks odd; mark the line with a note and deal with it afterwards. If you use a paper backup for a short period, write the full UTC time and the date on the sheet at the day change, so you can reconstruct the order later.
It also helps to keep one reference clock in view. A cheap UTC clock on the desk, or a clock on a second screen, costs nothing and gives you a quick comparison with the logger. When the two disagree, you notice it in the first minute and not in the last hour. That simple comparison has saved many logs from a wrong offset that nobody saw for two days.
Finally, remember that the first hour of the contest is the best time to catch a clock problem. Compare the logger time with your UTC reference when you work the first QSO, and again after the first hour. If something is wrong, you have only a handful of QSOs to correct.
If you find an error, fix it with care
When you find a wrong date, think about why it happened before you change it. If the whole log is offset by one hour, a single correction may fix all the lines, but only if you are sure about the offset. If only a few lines are wrong, correct them one by one and write down what you changed. Do not guess: if you cannot be sure of the right time of a QSO, a recording or a paper note may help.
After the correction, check the rate by hour. A repaired log should show a normal curve without an empty hour or a double hour at the point of the change. That is a good way to confirm that the repair is right.
Related reading
The bottom line
Midnight UTC is a small moment that can cause a big mistake. Run the logger on UTC, watch the date at the day change, read the exported file around midnight and fix what you find with care. For general questions about what a log check covers, see the FAQ.
FAQ
What time zone does a Cabrillo log use?
Contest logs use UTC for the date and time of each QSO. Check the rules of the contest if you are unsure.
My log has QSOs with the wrong date. Is the whole log wrong?
Not necessarily. If only a few lines are affected, correct those. If every line is offset, look for a time zone or daylight saving cause.
Is 2400 a valid time?
Use 0000 on the next date. Write the time as four digits and avoid 2400 so that every program reads the file in the same way.
Can a log checker find rollover errors?
It can mark QSOs outside the contest period, which will show many date errors. It cannot know the right time for a QSO inside the period.
Should I change the date manually in the logger?
Avoid it. Set the clock correctly and let the logger create the date from the clock.



