POC Flights in Progress Map Airport Data Update

[Al O'Brien]

When using FSACARS, the POC does not display my NM flown or my NM to destination or ETA. I am not using VATSIM is this the reason.
Al SAX067

[Dave Blake]

When using FSACARS, the POC does not display my NM flown or my NM to destination or ETA. I am not using VATSIM is this the reason.
Al SAX067

I have seen this on occasion. I think this is caused when one or both the departure or destination airports are not in the FSACARS database.

[Al O'Brien]

That makes sense. Am using it now between frankfurt and rome and it is reporting both parameters.

[David Vega]

Credit goes to Dave Blake for finding the cause and the fix.

In the FSAcars folder, usually C:\Program Files\FSAcars, there's a file named apt.txt. This file has the airport information FSAcars uses to determine distances. If either your departure or destination airports aren't on this file, FSAcars can't determine distances. This also means that you can't use the FSAcars feature to pause the simulator so many miles before the flight plan's destination.

To fix the problem:

1. Wash your hands, this is surgery and you don't want to kill the patient.
2. Backup the file.
3. Carefully edit the file with any text editor, such as Notepad, and add the missing airport and the lat/long.

You can find the lat/long information from http://worldaerodata.com/.

You could edit it right away and replace the ICAO code for Hawaii's Honolulu International from PHIK to PHNL. Though PHIK is the code for Hickam AFB, which shares the runways with Honolulu Intl, our flights are scheduled for Honolulu Int, not the Air Force base.

Dave Vega
SAX702

[Dave Blake]

In the FSAcars folder, usually C:\Program Files\FSAcars, there's a file named apt.txt. This file has the airport information FSAcars uses to determine distances. If either your departure or destination airports aren't on this file, FSAcars can't determine distances. This also means that you can't use the FSAcars feature to pause the simulator so many miles before the flight plan's destination.

To fix the problem:

1. Wash your hands, this is surgery and you don't want to kill the patient.
2. Backup the file.
3. Carefully edit the file with any text editor, such as Notepad, and add the missing airport and the lat/long.

I have updated my "apt.txt" file to add some missing and incorrect airport information. With this updated file all current SAX airports should now be listed correctly on the POC FSACARS map.

Here is the list of airports I corrected:
Change: UGGG to UGTB, LESJ to LEPA, KIKR to KABQ, PHIK to PHNL.
Added: KDRO, KISO, KJKA, KMQI, KMQI, KMVY, KMWA, KPSC, KSEZ, KXNA

You may replace your apt.txt file with my updated one. I strongly recommend that you rename your old apt.txt file to something like apt_old.txt for a backup before adding the new one.

[JohnnyT]

Thanks Dave!
You made it a lot easier for us.
Johnny