It can’t always be sombody elses fault when some of the errors are so blatent.
Take this example, 14 March 2013, Flight UAE35 from OMDB to EGNT. Departure time, according to Emirates timetable is 03:40UTC actual departure time as observed by me on FlightRadar24 was 04:33UTC. Flight aware sent me a departure alert of 04:24UTC which was close, it was in the zone but still 9 minutes difference. Then I received another alert headed ‘flight information has changed’ telling me that UAE35 had actually departed at 03:48UTC a full 36 minutes earlier than the first alert and 45 minutes ahead of the observed departure time seen on Flight Radar24.
I am trying to research and collate data for my thesis as part of my Phd in Statistical Analysis and I really do need to have accurate data or my submission will be shut down in flames, if I were not so far in I would probably change my subject matter from aviation to railways time-keeping.
This is not in any way intended as a flame on FlightAware or anyone associated with FlightAware. it is a frustrated cry for help. The example I have given is not an isolated one, its happening all too frequently and I don’t understand why, with all the technology and resources available today, FlightAware is publishing data that is so blatently wrong.