Air Actual Arrival Report (AIRAAR) Business Rules

​​​​​​Message Mapping

User Data Dictionary

AIRAAR - Messaging Rules

1. The valid Message Function Codes for an AIRAAR are:

   1. Original (9)
      
   2. Change (4)
   3. Withdraw (50)

2. AIRAAR 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 AIRAAR 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 AIRAAR message will be reported in an AIRAAR Response message (AIRAARR).

6. Any advice messages resulting from the AIRAAR message will be reported in an AIRAAR Response message (AIRAARR).

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 AIRAARR has been reached.

8. A Change to an AIRAAR will be rejected if there is no difference between the Original and the Change AIRAAR.

9. Each Change AIRAAR 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 AIRAAR messages for which no original exist will be rejected by the ICS.

11. The Withdrawal of an AIRAAR is for the entire record.

12. Once an Actual Arrival Report has been created, amended or withdrawn online through the ICS, future processing via EDI will not be permitted.

AIRAAR - Processing Rules

1. An AIRAAR is sent by a carrier to the Department to report the Actual Arrival details of a flight to a single port. Service providers may also lodge AAR reports on behalf of a carrier.

2. AIRAAR messages must be reported to the Department within a specified time of the aircrafts arrival. If the AIRAAR is reported outside of this timeframe, an Advice is sent to the AIRAAR rep​orter in an AIRAARR message. See Import Cargo Reporting Timeframes for more detail.

   ​

3. An AIRAAR is linked to an AIRIAR by the:

   1. Airline Code;
      
   2. Flight Number;
      
   3. Port of Arrival; and
   4. Estimated Date of Arrival

4. If an AIRAAR cannot be linked to an AIRIAR an Advice is sent in an AIRAARR Response message.

5. The AIRAAR will also be linked to one or more Air Waybill Outturn Reports (AIROUT) where cargo has been discharged. The link will be established using the:

   1. Airline Code;
   2. Flight Number;
   3. Port of Arrival; and
   4. Estimated Date of Arrival.

6. An AIRAAR is uniquely identified by:

   1. Airline Code;
   2. Flight Number
   3. Date of Departure from Last Overseas Port;
   4. Last Overseas Port of Departure; and
   5. Port of Arrival.

7. The unique identifiers within an AIRAAR cannot be amended. The existing AIRAAR must be withdrawn and a new AIRAAR submitted with the new identifiers supplied.

8. At a minimum, the following attributes are required to withdraw an AIRAAR:

   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;
   9. Date of Departure from Last Overseas Port; and
   10. Port of Arrival.

9. For all amendments to an AIRAAR, the full report with all attributes is required.

10. If the withdrawal of an AIRAAR is successful, an Advice is sent to the AIRAAR reporter in an AIRAARR message confirming the successful withdrawal.

11. All port references are to be supplied in UNLOCODE format.

12. The Responsible Party Client ID is mandatory for an Original AIRAAR. 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).

13. The Responsible Party Client ID cannot be Changed. The AIRIAR must be withdrawn and a new AIRIAR submitted.

Data Dependency Tables

An Air Actual Arrival Report Message can be Created, Changed or Withdrawn. The mechanism for carrying out these transactions utilises Message Function Code. The Message Function Code is a document level transaction indicator that is applied to the document.

Data Dependency Table for Original and Change

The following table models the Data dependencies of the Air Actual Arrival Report Document where the document is considered an "Original" or a "Change".

Data Dependency Table for Withdrawal

The following table models the data elements of the Air Actual Arrival Report Document where the document 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