The push manifest and ad-hoc push are both manual methods for transmitting passenger and crew data to destination authorities. However, the appropriate option depends on the specific scenarios explained below.

While passenger and crew data is typically submitted automatically, operators can choose to send additional messages manually. This may be necessary if data is updated and the operator wants to verify authorization statuses before the final automatic transmission—ensuring that all passengers and crew are cleared to board.

Important: Some countries enforce strict deadlines for final data submission. Any updates must be sent before the country’s designated last submission time. If this isn’t possible, we recommend postponing the flight, as late submissions may result in penalties or fines.

Push Manifest

The push manifest sends all passenger and crew data to the destinations state authority.

Ad-hoc Push

The ad-hoc push differs from the push manifest in that it allows for sending individual messages—for example, only for passengers, only for crew, or, as in the case of the UK shown above, for specific messages like UPT (boarding statuses) or API (GAR submission for passenger and crew data). The options available vary depending on the destination country.

If the results don’t appear immediately after performing a push manifest or ad-hoc push, click the refresh icon in the top-right corner to update the statuses.

⚠️ Unless specific messages must be sent, we recommend using the push manifest option.