Altert Reply actual_blockout_time

FlightAware AeroAPI
1

We learned from support that it is also possible to setup alerts for more than the categories mentioned in your documentation:

estimated_blockin_time
filed_blockin_time
actual_blockin_time
estimated_blockout_time
filed_blockout_time
actual_blockout_time

our question is: how would an alert response look like for those alerts?

thanks

2

Alerts based on actual times can be enabled by including {split_block_times 1} in the channels parameter when using SetAlert. This would result in a an example channels parameter value of {16 e_departure e_arrival} {split_block_times 1}. An event must still be specified int he “16” portion along with the additional block time value.

3

thanks for the reply. Actually I am surprised. I have an email from April from FlightAware, telling me that I am able to SetAlerts for

estimated_blockin_time
filed_blockin_time
actual_blockin_time
estimated_blockout_time
filed_blockout_time
actual_blockout_time

individually. But as I understand your reply it is only possible to add

{split_block_times 1}

meaning to get the actual offblock and onblock time? So every flight would trigger exactly two pushs? Or did I understand it wrongly?

4

@dogrock I would really appreciate an answer by today since tomorrow I am meeting our programmers and discuss ways to implement your API

5

The split_block_times would trigger up two to alerts for the actual times, if they are available.

If receiving all the estimated time updates, as well as additional information like gate and terminal updates, as they happen is a requirement then Firehose may be a better solution.

6

@dogrock thank you. Could you please provide me with a split_block_times alert reply example to have an idea on what we would get out of it?

What do you mean with „if they are available“? Are there cases when you don’t have the info even for major carriers?

7

For major airlines and airports block event coverage is very good. For smaller airlines or more remote locations block event reports may be more sporadic.

Here’s an alert sample:

{
“long_desc”:“American Airlines #1630/N889NN is at the gate at Hartsfield-Jackson Intl (KATL) at 15:32 EDT, arriving from Dallas-Fort Worth Intl (KDFW)\n\nDestination (Hartsfield-Jackson Intl / KATL): Terminal N, Gate E8”,
“short_desc”:“AAL1630/N889NN is at the gate at KATL, arriving from KDFW”,
“summary”:“AAL1630/N889NN at the gate at KATL, arriving from KDFW”,
“eventcode”:“onblock”,
“alert_id”:35644780,
“flight”: {
“ident”:“AAL1630”,
“aircrafttype”:“B738”,
“origin”:“KDFW”,
“destination”:“KATL”,
“filed_ete”:“01:41:00”,
“route”:“FORCK2 FORCK ELD MEI DUUCK ORRKK HOBTT2”,
“faFlightID”:“AAL1630-1598244312-airline-0336”,
“reg”:“N889NN”,
“filed_altitude”:370,
“filed_airspeed_kts”:452,
“filed_time”:1598244312,
“filed_departuretime”:1598463900,
“estimatedarrivaltime”:1598469600,
“actualarrivaltime”:1598469600,
“actualdeparturetime”:1598463839,
“estimated_blockin_time”:1598470140,
“filed_blockin_time”:1598471460,
“actual_blockin_time”:1598470200,
“estimated_blockout_time”:1598463300,
“filed_blockout_time”:1598463300,
“actual_blockout_time”:1598463000,
“filed_arrivaltime”:1598469960
}
}

8

thank you for your help