Introduction

Historically users enter crew and passenger information into FBO One crew/pax page for the purpose of generating passenger manifests and/or general declarations. This integration replaces the requirement to generate these documents by automatically sending the information directly into the the national immigration database.

The UAE carrier portal has set some rules on when and how the data is exported which are summerised below:

1. Initial request submission (30Day threshold)
Users populate FBO One with the required crew/pax details

• If the flight sector is scheduled to operate within the next 30 days FBO One will automatically submit the details to the portal without any additional action from the user.
  
  
• If the flight sector is not schedueld to operate within the next 30days no action will take place until the 30day threshold is met. Once the threshold is met FBO One will automatically submits the details to the portal without any additional action from the user.
•  

2. Change request submission

Users updates either flight schedule or crew/pax details

• All changes are submitted automatically without any additional action from the user.
• The process used for this action is a cancellation of the previous request followed by a new submission for the updated details.

3. Cancellations

Users remove either the flght schedule or cancels the flight

• The previously submitted data is cancelled automatically without any additional action from the user.

What does this mean?

Only flight operating to/from the UAE within the next 30days will be submitted. All modifications, including cancellations, to the flight schedule or crew/pax list are are automatically submitted without any additional action from the user.

How do we know the status of the submission ?

Upon successful submission each crew/pax entry will display an ‘BOARD IF DOCS OK’ text to indicate a successful upload.

In the event that the mandatory crew/pax details are incomplete the status field will indicate the source of the issue. Examples of this may include missing date of birth, passport expiry date etc.

These error messages will also be highlighted in the order ‘Crew Pax API error’  displayed in the order screen. This same indicator will also be used to highlight other related errors such as technical failures

There is also provision to set a planboard ‘must review’ indicator that will:

1. highlight all orders that have been updated by this integration.
2. filter the planboard on the orders requiring review

The order third party audit log provides insight into all changes made by this integration

Good to know

Unknown registrations

In event that the UAE Carrier portal does not known the aircraft registration, FBO One will, on behalf of the user, create the registration in the UAE Carrier Portal (based on the FBO One database).

Operators or registrations can be exempted from this integration.

Certain operators will be authorised to submit their own data directly to the portal. In such cases these operators or registrations must be assigned a ‘Direct UAE Carrier Checkin’ custom value in order to prevent a duplicate submission.

Individual orders can be exempted this integration.

As some crew/pax data may have already been manually submitted to the portal it's undesirable to submit a duplicate request. To avoid this orders can be disabled by setting the ‘Disable UAE Carier API’ custom value which will prevent the any updates from this particular order.