Epoch is 0 for arrival data

FlightAware AeroAPI
1

Hi,

After retreiving 4 records for IBE2623 I notice that the current flight has epoch 0 which is expected and fine however the
previous 3 flights look like this:

    "filed_arrival_time": {
      "epoch": 1503624600,
      "tz": "PDT",
      "dow": "Thursday",
      "time": "06:30PM",
      "date": "24/08/2017",
      "localtime": 1503599400
    },
    "estimated_arrival_time": {
      "epoch": 1503625485,
      "tz": "PDT",
      "dow": "Thursday",
      "time": "06:44PM",
      "date": "24/08/2017",
      "localtime": 1503600285
    },
    "actual_arrival_time": {
      "epoch": 1503625485,
      "tz": "PDT",
      "dow": "Thursday",
      "time": "06:44PM",
      "date": "24/08/2017",
      "localtime": 1503600285
    },
    "arrival_delay": 885,
    "filed_blockout_time": {
      "epoch": 0
    },
    "estimated_blockout_time": {
      "epoch": 0
    },
    "actual_blockout_time": {
      "epoch": 0
    },
    "filed_blockin_time": {
      "epoch": 0
    },
    "estimated_blockin_time": {
      "epoch": 0
    },
    "actual_blockin_time": {
      "epoch": 0
    },
    "status": "Arrived",
    "progress_percent": 100,

These are all flights that have arrived over 3 days yet all their blockin times are 0, gate to gate time is important for us so I was wondering if this is expected behaviour? If so how can I get the gate to gate time?

Thanks

2

We don’t always receive the blockout and blockin times for international airports. If that data is missing then the field will be set to an epoch of 0.

3

Thanks for the reply, so is the actual arrival and actual departure when the plane started moving away from the gate and when it stops at the destination gate or is it take off and landing time?

4

actualdeparturetime is when the plan takes off and actualarrivaltime is the time it lands. The blockout time is when it pushes back from the gate and blockin time is when it pulls into the gate.