HM01 running late...

[MDK2]

It's as if Pedro forgot to "fall back." HM01 wasn't on at 1600z at all, but the carrier came up on its 1600z frequency of 11435 at 1650, and it's operating there as if it's intended to be on 1700z now. Since they've always stuck to a UTC schedule and never done a DST shift in the past, AND since yesterday they were on their usual UTC schedule, I'm going to assume human error for now. Will observe over the rest of the daylight hours here and see if it continues to be an hour later than we'd expect.

UPDATE 18:47z: Some time during the 1800 hour, HM01, which began on 11530, QSY'd to 11635.

[shadypyro]

Hmm, wonder if Pedro is sleeping in lol..