It’s not browser related, which is why I didn’t ask about the browser in my first reply. Some changes were made recently to the flight tracker box and I’ve asked the developer responsible to look into it on Monday.
Rgr that Mark. Any jobs going for ‘glitcher’ or ‘quality tester’ ? 
This has been resolved.
I concur. What was causing it just out of interest? 
Recently we re-wrote backend code that handles flight ident validation as frontend code. We like to do this whenever it will improve the user experience and/or the response time of the request.
However, the front-end language is different, and the code had to be written in a slightly different way, a so there was some room for error. One part of the code translates airline flight idents; from DAL4444 to SKW4444, for example. The problem was that the new code was translating flight numbers that are not supposed to be translated.
Thank you for discovering this bug!!!