Per request by 'heavy767', the following are the Lat /Lon coordinates for all the various waypoints, markers, runway and Localizer data for FMC's.
Find the version of FS you will be loading when released (FS9 or FSX) and use the appropriate lat /lon format (Decimal or DDM).
FS9 Version
Runway IGS 13
<Waypoint (initial approach fix)
lat="22.3213642007333"
lon="114.002262128025"
waypointIdent="IAF13" />
<Waypoint (final approach fix)
lat="22.3256540253313"
lon="114.070892096467"
waypointIdent="FAF13" />
<Waypoint (MAP fix)
lat="22.3327371011312"
lon="114.18427743182"
waypointIdent="LDA13" />
<Waypoint (initial approach fix)
lat="N22 19.28185"
lon="E114 0.13571"
waypointIdent="IAF13" />
<Waypoint (final approach fix)
lat="N22 19.53924"
lon="E114 4.25352"
waypointIdent="FAF13" />
<Waypoint (MAP fix)
lat="N22 19.96423"
lon="E114 11.05665"
waypointIdent="LDA13" />
Outer Marker
Decimal
22.326972
114.092744
DDM
N22 19.6183
E114 05.5646
Middle Marker
Decimal
22.331569
114.165676
DDM
N22 19.8941
E114 09.9406
Runway IGS 13 Displaced Threshold
Decimal
22.322191
114.196308
DDM
N22 19.3314
E114 11.7784
Runway IGS 13 Localizer Antenna
Decimal
22.333867
114.201878
DDM
N22 20.0302
E114 12.1127
Runway IGS 13 Localizer DME
Decimal
22.321334
114.195378
DDM
N22 19.2800
E114 11.7227
FS9 Version
Runway 31
<Waypoint (initial approach fix)
lat="22.1882046331349"
lon="114.345829096544"
waypointIdent="IAF31" />
<Waypoint (final approach fix)
lat="22.2390519372417"
lon="114.288864811599"
waypointIdent="ALANE" />
<Waypoint (initial approach fix)
lat="N22 11.29228"
lon="E114 20.74975"
waypointIdent="IAF31" />
<Waypoint (final approach fix)
lat="N22 14.34311"
lon="E114 17.33189"
waypointIdent="ALANE" />
Outer Marker
Decimal
22.237971
114.288788
DDM
N22 14.278259
E114 17.327279
Middle Marker
Decimal
22.316959
114.202618
DDM
N22 17.0741
E114 14.2966
Runway 31 Displaced Threshold
Decimal
22.305538206
114.215178674
DDM
N22 18.332221
E114 12.910952
Runway 31 Localizer Antenna
Decimal
22.333867
114.201878
DDM
N22 19.6207
E114 11.4521
Runway 31 Localizer DME
Decimal
22.321334
114.195378
DDM
N22 18.2871
E114 12.8772
FSX Version
Runway IGS 13
<Waypoint (initial approach fix)
lat="22.3201835504145"
lon="113.991101919016"
waypointIdent="IAF13">
<Waypoint (final approach fix)
lat="22.3255266607098"
lon="114.073851926099"
waypointIdent="FAF13">
<Waypoint (MAP fix)
lat="22.3326390320936"
lon="114.184007813583"
waypointIdent="LDA13" />
<Waypoint (initial approach fix)
lat="N22 19.21102"
lon="E113 59.46613"
waypointIdent="IAF13" />
<Waypoint (final approach fix)
lat="N22 19.53160"
lon="E114 4.43111"
waypointIdent="FAF13" />
<Waypoint (MAP fix)
lat="N22 19.95833"
lon="E114 11.04048"
waypointIdent="LDA13" />
Outer Marker
Decimal
22.326835245
114.092402458
DDM
N22 19.610115
E114 05.544147
Middle Marker
Decimal
22.331539504
114.165248126
DDM
N22 19.892370
E114 09.914888
Runway IGS 13 Displaced Threshold
Decimal
22.322177435
114.196317836
DDM
N22 19.330751
E114 11.779194
Runway IGS 13 Localizer Antenna
Decimal
22.33390756
114.201911688
DDM
N22 20.034454
E114 12.114701
Runway IGS 13 Localizer DME
Decimal
22.321608961
114.195679128
DDM
N22 19.296538
E114 11.740748
FSX Version
Runway 31
<Waypoint (initial approach fix)
lat="22.1882046014071"
lon="114.345829188824"
waypointIdent="IAF31">
<Waypoint (final approach fix)
lat="22.2390519082546"
lon="114.2888648808"
waypointIdent="ALANE">
<Waypoint (initial approach fix)
lat="N22 11.29228"
lon="E114 20.74975"
waypointIdent="IAF31"
<Waypoint (final approach fix)
lat="N22 14.34311"
lon="E114 17.33189"
waypointIdent="ALANE"
Outer Marker
Decimal
22.237970978
114.288787991
DDM
N22 14.278259
E114 17.327279
Middle Marker
Decimal
22.284567654
114.238276184
DDM
N22 17.074059
E114 14.296571
Runway 31 Displaced Threshold
Decimal
22.305538206
114.215178674
DDM
N22 18.332221
E114 12.910952
RWY 31 Localizer Antenna
Decimal
22.326954603
114.190941006
DDM
N22 19.617276
E114 11.456460
RWY 31 Localizer DME
Decimal
22.304784469
114.214619994
DDM
N22 18.287068
E114 12.877200
Kai Tak Lat /Lon Coordinates for FMC's
This is for FMC's in planes like the Level D or PMDG, you don't need them fior the IGS to work. You can just set the nav to 111.90, hit approach on the autopilot and it will pick up the localizer, of course once you get to the middle marker you are on your own.Ken S wrote:Is this required to get the IGS13 to work? If so, where are these exactly suppose to go?
Thanks,
Ken S
Sorry Mike,
I do not have a full working FMS type plane. For what ever reason the Designers of the FMS will not confique the FMS using the existing FS approach code the way it was intended. The approach data that I write follows the FS way of doing it so the GPS receiver draws the lines properly.
If someone would show me how the data is confiqured for the FMS I could then change the format.
I do not have a full working FMS type plane. For what ever reason the Designers of the FMS will not confique the FMS using the existing FS approach code the way it was intended. The approach data that I write follows the FS way of doing it so the GPS receiver draws the lines properly.
If someone would show me how the data is confiqured for the FMS I could then change the format.
The "latest" SIDSTAR for VHHX can be found here [direct link to file], in this case for the PMDG FMCs.
As you can see, there are some small but existing descrepancies between the given coordinates and yours, so I suppose a future update will be needed to make it work. For example, see the OM13 (line 23): vs. your
Disclaimer: With this post I did not volunteer to produce an updated SIDSTAR. 
As you can see, there are some small but existing descrepancies between the given coordinates and yours, so I suppose a future update will be needed to make it work. For example, see the OM13 (line 23):
Code: Select all
FIX OM13 LATLON N 22 19.404 E 114 06.009Code: Select all
FIX OM13 LATLON N 22 19.6183 E 114 05.5646Hey Jim,
Thanks as always for all of your work.
Here is an excerpt from the VHHH section of the PSSstars.dat file. Based on this, any way to compile an approach for the PSS birds?
Thanks in advance,
-Paul
[VHHH/ELAT1B/RW25B/RW25B]
2, RW25B,010, ELATO, 22.333333, 117.500000, ,IF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,09000
2, RW25B,020, MAGOG, 22.296111, 115.825000, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,00000
2, RW25B,030, ASTRA, 22.274444, 115.193056, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,00000
2, RW25B,040, MELON, 22.269444, 115.013056, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,250, ,FL130,00000,00000
2, RW25B,050, TD, 22.247894, 114.293139, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,00000
Thanks as always for all of your work.
Here is an excerpt from the VHHH section of the PSSstars.dat file. Based on this, any way to compile an approach for the PSS birds?
Thanks in advance,
-Paul
[VHHH/ELAT1B/RW25B/RW25B]
2, RW25B,010, ELATO, 22.333333, 117.500000, ,IF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,09000
2, RW25B,020, MAGOG, 22.296111, 115.825000, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,00000
2, RW25B,030, ASTRA, 22.274444, 115.193056, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,00000
2, RW25B,040, MELON, 22.269444, 115.013056, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,250, ,FL130,00000,00000
2, RW25B,050, TD, 22.247894, 114.293139, ,TF, ,000,000.000,000.0,000.0,0.000000,000.0,000, ,00000,00000,00000
I found this in another forum, for the 9Dragons version. I'm still going for the PMDG FMC here:
Now, this is the code that would have to be added to the wpNavAPT.txt. I'm currently trying to figure out what all those values mean, so it can be changed/adapted to the FT version. Here's what I came up with:
VHHX13 is RWY13 of course. 10930 is the length in ft, 136 is RWY heading. Then comes longitude and latitude of the threshold. Then, after the last dot: I don't know what the 90 means. 088 should be the ILS course, and 00015 the altitude in ft.
Now, in the airports.dat file VHHX would have to be added in the following format, although I don't know which exact coordinates would have to be used.
Code: Select all
HONG KONG KAI TAK VHHX13 10930136 22.321667 114.196667111.9008800015
HONG KONG KAI TAK VHHX31 10930316 22.305500 114.214500109.9031600015VHHX13 is RWY13 of course. 10930 is the length in ft, 136 is RWY heading. Then comes longitude and latitude of the threshold. Then, after the last dot: I don't know what the 90 means. 088 should be the ILS course, and 00015 the altitude in ft.
Now, in the airports.dat file VHHX would have to be added in the following format, although I don't know which exact coordinates would have to be used.
Code: Select all
VHHX 22.321364 114.002262Re: Kai Tak Lat /Lon Coordinates for FMC's
how do i add this to my pmdg fmc database?jvile wrote:Per request by 'heavy767', the following are the Lat /Lon coordinates for all the various waypoints, markers, runway and Localizer data for FMC's.
Find the version of FS you will be loading when released (FS9 or FSX) and use the appropriate lat /lon format (Decimal or DDM).
FS9 Version
Runway IGS 13
<Waypoint (initial approach fix)
lat="22.3213642007333"
lon="114.002262128025"
waypointIdent="IAF13" />
<Waypoint (final approach fix)
lat="22.3256540253313"
lon="114.070892096467"
waypointIdent="FAF13" />
<Waypoint (MAP fix)
lat="22.3327371011312"
lon="114.18427743182"
waypointIdent="LDA13" />
<Waypoint (initial approach fix)
lat="N22 19.28185"
lon="E114 0.13571"
waypointIdent="IAF13" />
<Waypoint (final approach fix)
lat="N22 19.53924"
lon="E114 4.25352"
waypointIdent="FAF13" />
<Waypoint (MAP fix)
lat="N22 19.96423"
lon="E114 11.05665"
waypointIdent="LDA13" />
Outer Marker
Decimal
22.326972
114.092744
DDM
N22 19.6183
E114 05.5646
Middle Marker
Decimal
22.331569
114.165676
DDM
N22 19.8941
E114 09.9406
Runway IGS 13 Displaced Threshold
Decimal
22.322191
114.196308
DDM
N22 19.3314
E114 11.7784
Runway IGS 13 Localizer Antenna
Decimal
22.333867
114.201878
DDM
N22 20.0302
E114 12.1127
Runway IGS 13 Localizer DME
Decimal
22.321334
114.195378
DDM
N22 19.2800
E114 11.7227
FS9 Version
Runway 31
<Waypoint (initial approach fix)
lat="22.1882046331349"
lon="114.345829096544"
waypointIdent="IAF31" />
<Waypoint (final approach fix)
lat="22.2390519372417"
lon="114.288864811599"
waypointIdent="ALANE" />
<Waypoint (initial approach fix)
lat="N22 11.29228"
lon="E114 20.74975"
waypointIdent="IAF31" />
<Waypoint (final approach fix)
lat="N22 14.34311"
lon="E114 17.33189"
waypointIdent="ALANE" />
Outer Marker
Decimal
22.237971
114.288788
DDM
N22 14.278259
E114 17.327279
Middle Marker
Decimal
22.316959
114.202618
DDM
N22 17.0741
E114 14.2966
Runway 31 Displaced Threshold
Decimal
22.305538206
114.215178674
DDM
N22 18.332221
E114 12.910952
Runway 31 Localizer Antenna
Decimal
22.333867
114.201878
DDM
N22 19.6207
E114 11.4521
Runway 31 Localizer DME
Decimal
22.321334
114.195378
DDM
N22 18.2871
E114 12.8772
FSX Version
Runway IGS 13
<Waypoint (initial approach fix)
lat="22.3201835504145"
lon="113.991101919016"
waypointIdent="IAF13">
<Waypoint (final approach fix)
lat="22.3255266607098"
lon="114.073851926099"
waypointIdent="FAF13">
<Waypoint (MAP fix)
lat="22.3326390320936"
lon="114.184007813583"
waypointIdent="LDA13" />
<Waypoint (initial approach fix)
lat="N22 19.21102"
lon="E113 59.46613"
waypointIdent="IAF13" />
<Waypoint (final approach fix)
lat="N22 19.53160"
lon="E114 4.43111"
waypointIdent="FAF13" />
<Waypoint (MAP fix)
lat="N22 19.95833"
lon="E114 11.04048"
waypointIdent="LDA13" />
Outer Marker
Decimal
22.326835245
114.092402458
DDM
N22 19.610115
E114 05.544147
Middle Marker
Decimal
22.331539504
114.165248126
DDM
N22 19.892370
E114 09.914888
Runway IGS 13 Displaced Threshold
Decimal
22.322177435
114.196317836
DDM
N22 19.330751
E114 11.779194
Runway IGS 13 Localizer Antenna
Decimal
22.33390756
114.201911688
DDM
N22 20.034454
E114 12.114701
Runway IGS 13 Localizer DME
Decimal
22.321608961
114.195679128
DDM
N22 19.296538
E114 11.740748
FSX Version
Runway 31
<Waypoint (initial approach fix)
lat="22.1882046014071"
lon="114.345829188824"
waypointIdent="IAF31">
<Waypoint (final approach fix)
lat="22.2390519082546"
lon="114.2888648808"
waypointIdent="ALANE">
<Waypoint (initial approach fix)
lat="N22 11.29228"
lon="E114 20.74975"
waypointIdent="IAF31"
<Waypoint (final approach fix)
lat="N22 14.34311"
lon="E114 17.33189"
waypointIdent="ALANE"
Outer Marker
Decimal
22.237970978
114.288787991
DDM
N22 14.278259
E114 17.327279
Middle Marker
Decimal
22.284567654
114.238276184
DDM
N22 17.074059
E114 14.296571
Runway 31 Displaced Threshold
Decimal
22.305538206
114.215178674
DDM
N22 18.332221
E114 12.910952
RWY 31 Localizer Antenna
Decimal
22.326954603
114.190941006
DDM
N22 19.617276
E114 11.456460
RWY 31 Localizer DME
Decimal
22.304784469
114.214619994
DDM
N22 18.287068
E114 12.877200
Re: Kai Tak Lat /Lon Coordinates for FMC's
Sorry to bring this up again, but I am still unsure as to how to do it for my PSS planes. I am fine for the PMDG ones, I simply use the files/info that came with 9 Dragons and that's good enough.
But which files do I have to edit in the PSS environment so that the airport and runway data appear in the FMS and on the ND?
There was a thread somewhere here but that solution somehow didn't work. Maybe I misread the instructions.
Thanks a lot
But which files do I have to edit in the PSS environment so that the airport and runway data appear in the FMS and on the ND?
There was a thread somewhere here but that solution somehow didn't work. Maybe I misread the instructions.
Thanks a lot