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 ID - This option will default airport identifiers to appear as the airport ID, specified in the airport record, on the schedule board. Airport ID field ...
Airport Module Overview
Accessing the Airports Module To access under the Aircraft Module select the Operations Tab and then the Airports button: The FOS Airport Database is a rather large database and is updated quarterly with data provided from a third-party. Updating the ...
Interface Tab
The Interface tab is a quick way to connect to an external website to the third party sites listed below without leaving FOS. Select a radio button to navigate to the page. If prompted, credentials may need to be entered, or it may use stored ...