I discussed unintended spots with KU6J three days before this happened to N1EU. If one extends his/her alert with S+, then the alert is cached by the RBNGate machine and can not be countermanded by the posting station using any technique whatsoever. One climber used S+192 for an eight day hike, and he was locked in for the full eight days. Another guy accidentally used S+ in listing alternate frequencies in his alert, and the machine locked him in. The ordinary non-extended three hour alerts are downloaded to the machine every five minutes, not cached, so one who returns home before the expiration of the standard three hours can cancel his alert, wait five minutes for the machine to refresh, and call CQ with impunity.
I don’t know if there was an alert for W2/GC-002 using a call similar to N1EU and a weak skimmer misinterpreted what it heard, but EU has nothing logged in June or July. He has been on that peak more than once, though. One time I posted an alert with the wrong year. When it didn’t appear, I posted it again. A year later, the bad alert dutifully showed up and I didn’t show up… bad. Maybe someone on the MT can look at the alerts for N1EU last Sunday, if any. Then this mystery will go away.