Add missing airports to Nav database?

[Maddin91]

Excellent! Thank you guys! ))
Could we also try to add the ILS for the IGS 13 approach?
The ILS guides you down to the checkerboard. And there are some NDBs that also come in handy when trying to fly it as published.
Regards

[OmniAtlas]

Excellent! Thank you guys! ))
Could we also try to add the ILS for the IGS 13 approach?
The ILS guides you down to the checkerboard. And there are some NDBs that also come in handy when trying to fly it as published.
Regards

Hi Maddin -- can you provide some more information about the IGS13 approach? We will need raw data.

[bindook]

Is this the data yr after?

http://www.flytampa.org/forum/viewtopic.php?t=3105

[OmniAtlas]

I'll look over it but probably won't have time to test it out until next year. Data reposted over here from the link for easy reference, thank you.

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

[bindook]

I'm having a look at the rest of the coding in the navrecord.dat on how to put the above in ....... going to take a while to get it right.



Michael

[Maddin91]

Alright,

I managed to get all VORs, ILS, DME and NDB into the database working as they should. That's good so far.
Here's the code for additional.txt:

PA|VHHX|VH|22.316667|114.203333|15|250|F100|9000|KAI TAK INTL|
PG|VHHX|VH|RW13|10930|1864|197|22.322177|114.196318|15|136|KL|1
PG|VHHX|VH|RW31|10930|716|197|22.305538|114.215179|15|316|IHK|1
PI|VHHX|VH|KL|1|111.900|RW13|22.33390756|114.201911688|088|22.33390756|114.201911688|3.1|15|
PI|VHHX|VH|IHK|1|109.900|RW31|22.326954603|114.190941006|316|22.304784469|114.214619994|3.0|15|
D |TH|VH|115.500|VDHW|22.239000|114.289001||||||TATHONG POINT
DB|TP|VH|280.0|H MW|22.239000|114.289001|TATHONG POINT
DB|RW|VH|377.0|H MW|22.3265|114.19116666666667|HONG KONG INTL
DB|SC|VH|236.0|H MW|22.32|114.13216666666667|STONECUTTERS

Now I'm trying to work on the procedure, starting with the IGS 13 approach.
Here you can see how it should look like: http://www.flytampa.org/dwl/flytampa_hongkong.pdf (page 3).
That's what I tried so far:

PC|GOLF|VH|I F|?Latitude|?Longitude|VHHX|CH270007
PF|VHHX|VH|I13|A|CH|010|CH|VH|D |V C||||IF||| |||||||8000|0|0||||
PF|VHHX|VH|I13|A|CH|020|GOLF|VH|PC|V C||||IF||| ||||||+|6000|0|0||||
PF|VHHX|VH|I13|A|CH|030|SL|VH|DB|V C||||IF||| |||||||0|0|0||||

"Golf" is the first turning point after leaving CH VOR. Next is SL (SHA LO WAN) but from there you have to do an intercept onto the LLZ and I have no idea how to code that...

JeeHell: Is the approach procedure okay so far relating the coding? Or am I missing something? Can you explain how to put intercepts in the code?

Regards

[masterp]

Thanks Guys, my KaiTak is now alive.......
I have just thought about the possibility to adding it to database, and luckily I found this topic created by Martin.
Adding Procedures will be a very difficult task However, if we have PBD, we can manually create SID/STARs and put Constraint to each points...

[Maddin91]

Glad it worked for you.

There's only one problem with the IGS Approach so far (same applies for the opposite ILS approach of RW31):
The ILS is correctly tuned and appears in the PFD. But - because you can't select an ILS approach in the MCDU - the APPR mode of the Flight Director will only capture the LLZ but not the GS. The mode showed in blue is "FINAL" instead of G/S (result of not selecting ILS appr. in MCDU).

So coding the approach is kinda important for the system to work properly.

[masterp]

Hi Maddin,
I suggest to Turn off A/P and fly the airplane manually

[bindook]

Hi Maddin,
just having a look a the new PI|VHHX entries you have done ,for the new VHHH they end in W2.0 which I'm presuming is the magnetic variation? should we b adding tis o VHHX?


Michael