I’ve known for a long time that FA removes leading zeros from flight numbers, albeit for reasons I don’t understand. Up until recently it’s never been a problem and you’d get the same results whether you searched with the 0 or without it.
This no longer appears to be the case. Southwest’s new Max N8713M testing as BOE013 no longer works. If you search in the BFI departures listings http://flightaware.com/live/airport/KBFI/departures?;offset=50;order=actualdeparturetime;sort=DESC you will find that it shows the following - (times are UTC)
(29th) BOE013 B738 Grant Co Intl (KMWH) Fri 16:31 Fri 18:01 Fri 17:54
(26th) BOE013 B738 Grant Co Intl (KMWH) Tue 16:56 Tue 17:57 Tue 17:52
But when you search for the flight number you get this :
No mention of the flights from 26th or 29th. They definitely departed as a friend of mine watched them fly and the callsigns on the radio were as reported.
If you try forcing a 0 into the URL to make it BOE013 the site doesn’t allow you and defaults backs to BOE13.
What is causing this issue and can it be fixed by your techies?