Yes, I see the B check has been performed.
So, these random missed checks are happening. It is not happening with every swap, though, which is making it hard to pin down. I have had it happen about 20 times in the last year, some I caught others I didn't and it has cost me about a half dozen ramp checks. If the system is working right, this shouldn't happen. Ever.
There is a simple solution to this problem that has been suggested in other threads covering this subject. It would involve the system checking a schedule when a swap occurs. If A and B checks are scheduled, it would prevent the newly swapped aircraft from receiving any warning or ramp check violations, regardless of how overdue maintenance may be, for a period of 9 days, the maximum amount of time it would take for scheduled checks to complete. If the system as its programmed works properly 99% of the time, this becomes nothing more than a safety net.
Otherwise, I would be happy to spend a couple hours on the test server tomorrow with my GW1 airline just swapping planes to see if I can recreate this. Maybe it is a specific string of clicks, maybe it's a glitch that doesn't always show up, but something triggers this and I would really like to figure out what so it doesn't happen again.