What Is UAE Advanced Passenger Information?
In 2012, the General Civil Aviation Authority (GCAA) of the UAE introduced a mandatory Advance Passenger Information (API) requirement applicable to all passengers and crew arriving to and departing from the UAE. This regulation established a structured, computer-based system to provide concerned UAE government authorities with Advance Passenger Processing (APP) and Passenger Name Record (PNR) data for all international flights operating inbound and outbound from UAE airports.
The UAE API system is designed to capture passenger and crew data in advance of travel, ensuring that authorities receive the required information prior to arrival or departure. The framework incorporates both Advance Passenger Processing (APP) and Passenger Name Record (PNR) data elements for all international inbound and outbound operations.
For major airlines, API transactions are typically carried out through their Departure Control Systems (DCS) during the standard check-in process. This integration enables automatic submission of passenger data at the point of check-in. However, there has been no way to capture all other sorts of travelers who are not going through the normal check-in procedure at major airports.
Coverage Scope and Gaps Addressed
The great majority of travelers enter and leave the UAE by scheduled flights. These operations are generally supported by established check-in processes and system connectivity, allowing API submissions to flow through DCS platforms.
• However, there was a group that had not been covered in the past:
• Crew (since crew do not go through a check-in at the airport)
• Passengers flying with carriers without connectivity to the SITA network
• Passengers on unscheduled flights with small carriers
• Passengers and crew on international bus services
• Passengers and crew on international shipping services
These gaps highlighted the need for a broader submission mechanism capable of supporting non-scheduled operations and transport modes beyond standard airline infrastructure.
In particular, smaller airlines, private jet operators, and other aviation companies carrying out non-scheduled flights required a compliant way to submit APP transactions to the API system. Without such a mechanism, certain categories of passengers and crew would not be captured within the same regulatory framework as scheduled airline travelers.
By addressing these operational gaps, the UAE API framework ensures that all applicable passenger and crew data for international inbound and outbound movements is captured in alignment with the regulation.
Carrier Portal Solution
To close this gap for smaller airlines, private jet operators, and other aviation companies carrying out non-scheduled flights, a Carrier Portal has been designed for the purpose of providing a way to submit APP transactions to the API system.
The Carrier Portal enables registered operators to submit required APP data directly to the UAE API system for flights not supported by traditional DCS-based transmission.
Access to this Carrier Portal is given to registered users that can be national and foreign air carriers, their appointed agents, and Fixed Base Operators (FBOs). The usage of the Carrier Portal is only available for registered carriers and agents.
This structure ensures that APP transactions can be submitted even when operators do not have connectivity to major airline networks or do not operate through standard departure control systems. The Carrier Portal therefore provides a dedicated channel for compliance across scheduled and non-scheduled aviation sectors.
Responsibility & Submission Workflow
The accountability of providing accurate APP data lies with the Aircraft Operator, irrespective of whether it is a private or a commercial operator. The operator is required to provide APP passenger and crew data for all inbound and outbound flights to the UAE.
This can be done by the operator directly, the operator’s appointed agent, or the FBO used for the flight. Regardless of the submission channel, responsibility for accuracy remains with the Aircraft Operator.
For airlines operating with Departure Control Systems, API transactions are transmitted during the check-in process. For non-DCS-enabled flights or carriers without connectivity, the Carrier Portal provides the required submission pathway.
By structuring the submission workflow in this manner, the UAE API system ensures that the same regulatory responsibility applies to all operators conducting international flights to and from the UAE.
Key Objectives and Benefits
The objective of the UAE Advanced Passenger Information requirement is to provide concerned UAE government authorities with APP and PNR data for all international inbound and outbound flights operating to UAE airports.
Through a computer-based system, authorities receive passenger and crew information prior to arrival or departure. This ensures that the regulatory requirement applies uniformly to all applicable travelers and crew, including those who are not processed through standard airport check-in procedures.
By incorporating both scheduled and non-scheduled operations into the API framework, the UAE has established a comprehensive structure for passenger and crew data submission.
The inclusion of crew members, carriers without SITA connectivity, unscheduled small carriers, international bus services, and international shipping services ensures that previously unaddressed operational segments are now integrated into the regulatory environment.
The Carrier Portal further strengthens this framework by enabling direct APP transaction submission for registered carriers and agents operating outside standard airline system connectivity.
Operational Support for UAE API Compliance
UAS is registered to access the Carrier Portal and can create carrier accounts on behalf of its clients. Our operations team is trained to use the portal to file inbound and outbound API in accordance with the regulation.
For operators conducting international flights to and from the UAE, ensuring accurate and timely submission of Advance Passenger Information remains a regulatory requirement. If you require assistance with UAE API submissions, carrier portal access, or coordination of inbound and outbound API filing, contact UAS to support your compliance and operational requirements.