It looks like all the timestamp structs in FlightInfoStatus are returning UTC epoch time for the “localtime” field, UTC
for the “timezone”, and UTC time for the “time”. For example this request:
/json/FlightXML3/FlightInfoStatus?include_ex_data=false&ident=UAL726%401500011100
returns the following:
{
"FlightInfoStatusResult": {
"next_offset": -1,
"flights":
{
...
"filed_departure_time": {
"epoch": 1500011100,
"tz": "UTC",
"dow": "Friday",
"time": "05:45AM",
"date": "07/14/2017",
"localtime": 1500011100
},
"estimated_departure_time": {
"epoch": 1500014820,
"tz": "UTC",
"dow": "Friday",
"time": "06:47AM",
"date": "07/14/2017",
"localtime": 1500014820
},
"actual_departure_time": {
"epoch": 1500014880,
"tz": "UTC",
"dow": "Friday",
"time": "06:48AM",
"date": "07/14/2017",
"localtime": 1500014880
},
"departure_delay": 1620,
"filed_arrival_time": {
"epoch": 1500027300,
"tz": "UTC",
"dow": "Friday",
"time": "10:15AM",
"date": "07/14/2017",
"localtime": 1500027300
},
"estimated_arrival_time": {
"epoch": 1500031380,
"tz": "UTC",
"dow": "Friday",
"time": "11:23AM",
"date": "07/14/2017",
"localtime": 1500031380
},
"actual_arrival_time": {
"epoch": 1500031380,
"tz": "UTC",
"dow": "Friday",
"time": "11:23AM",
"date": "07/14/2017",
"localtime": 1500031380
},
...
}
]
}
}
This seems like a bug. The departure should be in PST and arrival EST.