Negative time in V3 for arrival_time for FlightInfoStatus


#1

Hello,

I get a negative time for “estimated_arrival_time”, “actual_arrival_time” for FlightInfoStatus (XML V3) and ident N542LM:



       "filed_arrival_time": {
          "epoch": 1501876440,
          "tz": "AKDT",
          "dow": "Freitag",
          "time": "11:54VORM.",
          "date": "04.08.2017",
          "localtime": 1501847640
        },
        "estimated_arrival_time": {
          "epoch": -1,
          "tz": "AHST",
          "dow": "Mittwoch",
          "time": "01:59NACHM.",
          "date": "31.12.1969",
          "localtime": -36001
        },
        "actual_arrival_time": {
          "epoch": -1,
          "tz": "AHST",
          "dow": "Mittwoch",
          "time": "01:59NACHM.",
          "date": "31.12.1969",
          "localtime": -36001
        },
        "arrival_delay": -150187644

“filed_arrival_time” seem to be correct. Is this a bug or is there a misunderstanding from my side?

Thanks,
Stefan


#2

It’s a bug in FlightInfoStatus. If the estimated_arrival_time or actual_arrival_time are not known it’s supposed to put an epoch of 0, but in some cases a -1 is being set. For right now just treat an epoch of -1 as unknown (ie the flight hasn’t departed or arrived) and I’ll update on the forums when that is fixed.


#3

But why is there an actual arrival time on the website for N542LM and how do I get this value?

de.flightaware.com/live/flight/N542LM


#4

Looks like there is a bug related to this flight because we have a diverted entry on that same flight_id as well. I’ve filed a ticket for it and we’ll look into why FlightInfoStatus is not displaying both results (the diverted flight and the complete flight).