Do flight monitoring sites have problems adjusting to AEDT?

[Melburnian1]

The otherwise useful site Flightradar24.com - Live flight tracker! seems to have a problem adjusting to the start of daylight saving in Australia's southeast.

As one example, QF9 has naturally been retimed from today to depart MEL at 1625, an hour later than previously. This allows it to arrive at LHR at the same time as in the non daylight saving time half of the year.

It left late today - at about 1653.

However, the above website incorrectly shows QF9 as timetabled to depart at 1525, but actually departing a claimed four minutes early at 1521.

Wouldn't such sites adjust UTC-related timings automatically, just like many smartphones and tablets?

This was far from the only example today, with many Australian domestic flights also depicted incorrectly.

 

[bass_ke]

Oh dear, could it be like the millennium bug? Big problems due to some Australian states being retimed?

 

[mono88]

There are so many of these time changes around the world that these sites should be able to get it right.
Clearly some of them don't think it is a priority.

 

[Mal]

Well BA forgot about a DST change in Morocco earlier this year... Total clack up. (Myself and another AFF member were there for the weekend). Flight was delayed until checkin "should" have originally closed. Very understanding pilot basically... Decided to stick around whereas head office seemed to have more of a 'ditch them and run' attitude.

Basically there will always be time zone and DST issues. Not everyone gets it right and keeping track of it is a nightmare.

 

[Melburnian1]

I agree that it must be extremely difficult to keep track of, particularly if jurisdictions make sudden changes or vary the dates from year to year. For instance, the AEDT changover is 'first Sunday morning in October at 0200' which may not be as simple as '3 October at 0200' from a programmer's viewpoint.

 

[Boris spatsky]

I agree that it must be extremely difficult to keep track of, particularly if jurisdictions make sudden changes or vary the dates from year to year. For instance, the AEDT changover is 'first Sunday morning in October at 0200' which may not be as simple as '3 October at 0200' from a programmer's viewpoint.

That is why aviation schedules generally work on UTC. Doesn't necessarily translate to the passenger front end of the business though.

 

[Melburnian1]

VA1332 (operated by 738 VH-VOX) which was due out of MEL at 1940 is now southeast of the city, but Flightradar24.com - Live flight tracker! has it shown as departing at '2141.' The site incorrectly claims that the flight will arrive in HBA at 2248, which is not remotely close to actuality.

How can this otherwise excellent site get these 'real timings' so wrong? It's not a time difference of an hour (AEST to AEDT conversion either way) so it's a mystery to me.