When I go to Awards and click on the States the record shows an unconfirmed contact for Kansas on 20 meters but no contact for Indiana. The fact is the unconfirmed contact is actually Indiana. I have never had any contact in Kansas on 20 meters.
Your screenshot shows Bloomington IN in the comments. If you open that QSO, you'll see the operator's logged location is Kansas.
Digging deeper, his license location says Bloomington Indiana, but his logbook operating location shows Pittsburg Kansas. You'll need to check with him to see if that's an error in his logbook or if he was operating portable.
He kept saying "You're 59 into Indiana" so I would assume that's where he was operating from. I sent an email so we'll see what he says. Larry
It's a common error: someone moves and doesn't update their logbook operating location. If he confirms it is an error, he will need to correct his logbook properties to make newly logged QSOs correct, AND edit any existing QSOs that are wrong. Revising settings only affects new QSOs.
Well it happened again today, for the third time in a couple of weeks. Right now I am working on a goal of contacting, and confirming, all 50 states but this is now the third contact where the location on the sender's page doesn't match their actual location and all three were POTA contacts or a special event. One was for a Carolina event but the sender was located in the state of Washington. Another was an apparent contact in Indiana but it turns out the sender was actually in Kansas or so it says. The third was apparently a contact in Georgia but it turns out the sender was actually in TN. We were able to get one fixed but not the other two. No disrespect to the POTA folks but from now on if I hear POTA I'll pass, I don't need the hassle of trying to get the QSO fixed even if I can actually make email contact with the sender which I have not been able to do in one instance. Sorry if that sounds petty but at 84 I don't have time to waste on trying to fix problems I didn't create.
I mostly accept an op's data on QRZ.com, log it, and move on. Errors seem to cause a few percent "overhead" of wrong QSLs. Hams who don't QSL also cause overhead. My solution is to get back on the radio. More contacts in whatever location will eventually lead to a confirmation. This probably means I don't spend sufficient time troubleshooting each log entry. That will continue except when someone contacts me asking for help.
