Announcement

Collapse
No announcement yet.

Wrong Arrival Times showing - defaults to Sched. time?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wrong Arrival Times showing - defaults to Sched. time?

    I have noticed recently that the arrival times are not always accurate. For example using my local airport Birmingham (BHX/EGBB) :-

    flight ZB903 from Dalaman due at 15:40 is showing on FR24 as "landed 15:40" with a yellow dot against it, indicating it arrived late, so how could it be showing as landed on time? On checking airline/airport websites etc.. the official landing time for the flight was 15:59, so an arrival time discrepancy of 19 minutes.

    so far today 12 flights arriving at BHX show on FR24 as having landed as the same scheduled arrival time, when in fact these 12 flight actually arrived early or late.

    It appears that for some reason FR24 sometimes publish the scheduled landing time instead of the actual land time. Is this a default setting in the FR24 system, or is this an issue that FR24 needs to look at?

    Has anyone else noticed this problem too?

  • #2
    Matt995,

    I seem to recall seeing something on a forum thread recently where the arrival/departure times on FR24 are runway to runway where as on airline/ airport sites is gate to gate. If I can find it I'll post it here.



    Regards,
    Gregg
    Last edited by fungus; 2017-05-22, 02:59.
    YSSY2/T-YSSY4 [SBS-1 Basestation w/- SSE-1090 SJ Mk2 Antenna (Thanks Delcomp) ] [Uniden UBCD996T w/- 16 element Wideband Discone VHF/UHF Antenna, and tuned 108MHz-137MHz Airband Antenna] [Trialing a home-brew 1090MHz collinear antenna]

    Comment


    • #3
      Hi Fungus, thanks for that but it not connect to that.

      for example, today :-

      2017-05-22 Ibiza (IBZ) Birmingham (BHX) B738 (G-JZHZ) 18:55 CEST 20:13 20:35 BST Landed 20:35

      if you look at this flight, it departed Ibiza 1hour 18 minutes late, and has the red dot next to the landed time, indicated late/delayed, yet the FR24 arrival time gives 20:35!! a flight of only 1 hour 22 minutes!!!
      impossible!!

      017-05-22 Girona (GRO) Birmingham (BHX) B738 (G-JZHN) 19:40 CEST 21:17 21:00 BST Landed 21:00

      same again, departed 1 hour 37 minutes late, arrived on time!!! a flight time of only 1hour 20 minutes, and again a red delayed dot against the landed time!

      out of 187 arrivals into BHX today, FR24 says 70 have arrived on exactly the scheduled arrival time, so approx 40% of flight arrived dead on time!! again not possible, something has to be wrong with the FR24 arrival times!!

      are other airports the same too??

      Comment


      • #4
        I noticed the same issue with a different airport. Consider BE7326 from MXP to HAJ on 8 June:

        08 Jun Milan (MXP) Hannover (HAJ) DH8D (G-ECOD) - 7:25 PM 10:31 PM 9:10 PM
        Landed 9:10 PM

        The actual departure was at 10:31 PM, but the web site shows me "Landed 9:10 PM" - so at -1h, that's a very fast flight Yet the color shown on the page is red, indicating severe delay. So the color is correct, but the time is not.

        On flightaware com, the arrival is indicated at 11:56PM, which seems plausible to me.

        If I check the raw data for this flight in developer tools (URL: api flightradar24 com /common/v1/flight/list.json?query=be7326&fetchBy=flight&page=1&limit =100&token=[REMOVED]), we see something interesting:

        - The relevant section of the JSON is .result.response.data[14].time
        - Under real.arrival I have a timestamp equal to Thu Jun 08 2017 21:10:00 GMT+0200 (CEST)
        - This is equal to the entry under scheduled.arrival and matches what is shown in the web site.

        - However, under the "other" section, there is information that seems more correct:
        -- other.eta = Thu Jun 08 2017 23:57:57 GMT+0200 (CEST),
        -- other.updated = Fri Jun 09 2017 00:19:31 GMT+0200 (CEST)
        - When downloading the CSV for the flight, the last entry is:
        -- 1496958866 2017-06-08T21:54:26Z BEE249J 52.481827,10.006074 3000 206 278

        Moral of the story:
        - The displayed actual arrival time is certainly wrong
        - The "other.eta" time in the JSON file is probably close to being correct
        - The "updated.eta" time is even later - is this gate time? Or something to discard?
        - The CSV file invalidates the info shown on the web site (because by 21:54 UTC, the flight was still mid-air), but also does not have the complete landing record.

        @flightradar24 - can you help us out with this problem?

        Comment

        Working...
        X