SATA List Compliance Updates

Owned by Nicolas Maillet (Unlicensed)
Last updated: Jun 10, 2019
2 min read

In the past, SATA list checks could be bypassed by using the incorrect (or no) gender. The potential and definite matching and the UI around this has been improved.

ameliaRES Desktop:

Check-in:

Figure: Passenger Protect Check

If all the provided information of the passenger-in-check matches against the information in the No-Fly list, a Definite No-Fly Match popup appears to warn the agent. Only agents who have No Fly Override - Modify permission can override this warning and check the passenger in.

Figure: Definite No-Fly Match warning

If a full match does not occur, first name and last name of the passenger-in-check will be used to check against the information in the No-Fly list to suggest a potential match. A Possible No-Fly Match popup will appear to warn the agent if there is a potential match.

Figure: Possible No-Fly Match warning

ameliaRES Web:

Online Check-in:

The passenger won’t be allowed to check-in if there is a definite match or potential match. They are advised to contact the airline or go to the airport to complete check-in.

Mobile:

Mobile Check-in:

The passenger won’t be allowed to check-in if there is a definite match or potential match. They are advised to contact the airline or go to the airport to complete check-in.