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. For example if you had a trip to IAH and then went into the airport list and deleted IAH, it would have said Airport IAH not found, but in this case it looks like the error just has a blank space.
Solution:
Add a blank airport to the database.
If the error stops, then this confirms that they have either a leg, crew activity, aircraft home airport, or crew home airport set to blank airport. By adding a blank airport back in, the function can now find the airport it is looking for in the database and the error isn't displayed.
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: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1)
Error: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1) Solution: An Aircraft Record was deleted from FOS or changed incorrectly. The record will need to be added back to FOS with the same tail and AC ID.Btrieve Error: Requested key not found (error=4) schedrpt_refresch_ac_lbox: actype_get XX (Thread 0)
Error: Requested key not found (error=4) schedrpt_refresch_ac_lbox: actype_get XX (Thread 0) Solution: The corresponding aircraft type referenced in the error was deleted. Go to aircraft type module and add the corresponding aircraft type back into ...Btrieve Error: Requested key not found (error=4) tripdata_setup: tripinfo_get (Thread 0)
Error: Requested key not found (error=4) tripdata_setup: tripinfo_get (Thread 0) This error message may be received when a trip has been deleted, however, still appears on the FOS Schedule Board. Users may receive the above Btrieve error message ...Btrieve Error: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1)
Error: This error may be seen when opening Operations Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1) Solution: When this error occurs when opening the Operations Page/Schedule Board the user will need to log out of ...