Air Impending Arrival Report (AIRIAR) Business Rules

​​​​ Message Mapping

User Data Dictionary

AIRIAR - Messaging Rules

1. The valid Message Function Codes for an AIRIAR are
   1. Original (9)
      
   2. Change (4)
   3. Withdraw (50)
2. AIRIAR messages must quote a unique Sender Reference. The ICS will use this number and the associated version number to ensure duplicate messages are not processed.
3. The version number for an Original (9) message must be set at 1 or greater.
4. Before the AIRIAR message is processed at the application level
   1. All leading and trailing blanks will be stripped;
   2. Multiple spaces will be compressed;
   3. Illegal characters will be removed; and
   4. All nulls will be converted to blanks.
5. Any errors in an AIRIAR message will be reported in an AIRIAR Response message (AIRIARR).
6. Any advice messages resulting from the AIRIAR message will be reported in an AIRIAR Response message.
7. The maximum number of errors and advices that can be reported will be 50. No further errors or advices will be processed once the maximum number allowed for the AIRIARR has been reached.
8. A Change to an AIRIAR will be rejected if there is no difference between the Original and the Change AIRIAR.
9. Each Change AIRIAR message will be considered to be a new version of the message. For each version of a message the senders reference version number must be unique and incremented from the previous version.
10. Change or Withdraw AIRIAR messages for which no original exist will be rejected by the ICS.
11. The Withdrawal of an AIRIAR is for the entire record.
12. Once an Impending Arrival Report has been created, amended or withdrawn online through the ICS, future processing via EDI will not be permitted.
13. Where the Message Function Code is 9 (Original), the valid Line Action Code is I (Insert).
14. Where the Message Function Code is 4 (Change) and the Line Action Code is populated, the valid codes are I (Insert), A (Amend) or D (Delete).
15. To create a new line record, the Message Function Code is 4 (Change) and the Line Action Code is I (Insert).
16. To amend a line record, the Message Function Code is 4 (Change) and the Line Action Code is A (Amend).
17. To delete a line record, the Message Function Code is 4 (Change) and the Line Action Code is D (Delete).

AIRIAR - Processing Rules

1. The AIRIAR is used by a Carrier or Service Provider to report the expected arrival details of an aircraft.
2. The reporting of the Impending Arrival must be made no earlier than a specified time before the estimated date/time of arrival of the aircraft. See Import Cargo Reporting Timeframes for more detail.
3. An AIRIAR is linked to an AIRAAR by the
   1. Airline Code;
   2. Flight Number;
   3. Port of Arrival; and
   4. Estimated Date of Arrival.
4. The AIRIAR will also be linked to one or more Air Cargo Reports (AIRCR). The link will be established using the:
   1. Airline Code;
   2. Flight Number;
   3. Estimated Arrival Date; and
   4. Port of Arrival.
5. An AIRIAR is uniquely identified by
   1. Airline Code;
   2. Flight Number;
   3. Date of Departure from Last Overseas Port; and
   4. Last Overseas Departure Port.
6. The unique identifiers within an AIRIAR cannot be amended. The existing AIRIAR must be withdrawn and a new AIRIAR submitted with the new identifiers supplied.
7. The Line Identifier for an AIRIAR is identified by the Port of Arrival.
8. The Unique Line Identifier will consist of a combination of the Report Identifier and the Line Identifier.
9. The AIRIAR will be rejected if more than 9 Codeshare Flights are reported within the one message.
10. An AIRIAR cannot be amended or withdrawn by an external user if a Border Force Officer has created or amended the record online.
11. At a minimum, the following attributes are required to withdraw an AIRIAR
    1. Document Name;
    2. Sender Reference;
    3. Sender Reference Version;
    4. Owner Site Id;
    5. Message Function Code;
    6. Airline Code;
    7. Flight Number;
    8. Last Overseas Port of Departure; and
    9. Date of Departure from Last Overseas Port.
12. For all amendments to an AIRIAR, the full report with all attributes is required.
13. If the withdrawal of an AIRIAR is successful, an Advice is sent to the AIRIAR reporter in an AIRIARR message confirming the successful withdrawal.
14. All port references are to be supplied in UNLOCODE format.
15. If a codeshare flight is reported within the AIRIAR along with the primary flight, a single AIRAAR can be reported to arrive both flights.
16. If a codeshare flight is reported in a separate AIRIAR to the primary flight, a separate AIRAAR must be reported for the codeshare and primary flights.
17. When the Cargo Discharge Indicator is set to Yes for a port of arrival, the Discharge CTO Identifier must be supplied.
18. If the Country Code for the Port of Arrival is not equal to AU then the AIRIAR will be rejected.
19. The Port of Arrival specified must be the same as the Port Code for the Discharge CTO Identifier.
20. The Responsible Party Client ID is mandatory for an Original AIRIAR. This is the ABN/CCID of the owner of the information, not the ABN/CCID of the document sender (note that the owner and sender may be the same client).
21. The Responsible Party Client ID cannot be changed. The AIRIAR must be withdrawn and a new AIRIAR submitted.
22. Up to nine CTO Establishment Ids can be reported for each line however each of these must be reported on separate AIRAAR reports.

Data Dependency Tables

Data Dependency Table for Original and Change

The following table models the data elements of the Air Impending Arrival Report Document where the document Message Function Code is considered a "Original" or "Change".

Data Dependency Tables - Withdrawal

The following table models the data elements of the Air Impending Arrival Report Document where the document Message Function Code is considered a "Withdraw.

NOTE: for further details in relation to a Business Term, refer to the User Data Dictionary.

V2.3 17 SEP 2004