Error: Arrival or departure airport not found (when launching Fatigue Interface)

Error:

Arrival airport not found

OR

Departure airport not found

This will be seen when attempting to launch the fatigue integration:

Solution:

Error is received from vendor. For Pulsar, the airport must be added into the User Preferences on the Pulsar site. Please reach out to the vendor with the message and airport codes referenced.

• Related Articles

• Airport Tab

  The airport data in FOS is composed of information from a third party vendor. The information is updated on a quarterly basis. Fields in blue throughout the Airport Database note the fields that are imported from the third party database. If the ...

• Error: schlegal_get_airport: Airport not found.

  Error: schlegal_get_airport: Airport not found. It appears that some trips are trying to run legality on have a blank airport ID. If it wasn't blank, but an airport that was not in the airport database, it would have put the ID in the error message. ...

• Airport Tab

  The “Airport” Tab contains options specific to using airports in the Operations module. Airport ID Section Airport ID - This option will default airport identifiers to appear as the airport ID, specified in the airport record, on the schedule board. ...

• Error: Fos.exe - Entry Point Not Found

  Error: Fos.exe - Entry Point Not Found The procedure entry point _NULL_IATA could not be located in the dynamic link library AND/OR Fos.exe - Entry Point Not Found The procedure entry point @InterfaceHelper@LoadTripDetails5qo could not be located in ...

• Error: The IATA code Could not be found for: XXX FOS will attempt to substitute the AP ID for the IATA code. Otherwise XXX will be listed for the IATA code per Customs requirements

  Error: The IATA code Could not be found for: XXX FOS will attempt to substitute the AP ID for the IATA code. Otherwise XXX will be listed for the IATA code per Customs requirements. This will be seen when attempting to file APIS from FOS. Solution: ...