dion73 Posted November 13, 2010 Share Posted November 13, 2010 Is there any way to add the SidStars for Kai Tak, especially the IGS13 approach with the outer and middle marker fixes (CC CH SL OM MM (SC) RWY13). Can this maybe be done by transferring the data there is for PMDG aircraft to the datafiles of Aivlasoft EFB? I read the other post about having to do this every other navdata update, but that's also the case for the PMDg airac update, so I don't mind... In the meantime i will try myself hoping i do not break anything Thanks, dion Link to comment Share on other sites More sharing options...
GG_Flyer Posted November 13, 2010 Share Posted November 13, 2010 This post has been edited to include a ZIPped TXT file containing SIDSTAR data for the freeware VHHX scenery. Dion, Yes, if the SID and STAR information is publically available then a VHHH.TXT file with them and the fix/waypoint/navaid information... approaches and gates, etc. could be added to the SIDSTAR folder. I believe the SIDSTAR change would only have to happen once. (But keep a separate backup, just in case.) I had thought to cast about on the wide Internets for already present data... failing that, someone would need r/w charts and the patience to transcribe lots of fix coordinates and procedure leg information. I had hoped to make a start with that over the weekend, but a customer problem (the missing RJBB procedures thread) takes slight precedence. The steps that would need to be updated each AIRAC would be this: - use "notepad.exe" to open the file "\Flight Simulator FSX\AivlaSoft\NavData\airports.dat" - append the following line to the end of the file (don't remove any whitespaces nor change the line) VHHX 22.326667 114.168331 - use "notepad.exe" to open the file "\Flight Simulator FSX\AivlaSoft\NavData\wpNavAPT.txt" - append the following two lines to the end of the file (don't remove any whitespaces nor change the lines) HONG KONG-OLD VHHX13 10930136 22.326667 114.191887111.9008800015 HONG KONG-OLD VHHX31 10930316 22.309570 114.209178109.9031600015 If you are editing an AIRAC dataset that has already been read by EFB you will have to perform these steps in addition: - use "notepad.exe" to open the file "Flight Simulator FSX\AivlaSoft\NavData\cycle_info.txt" - change the second line by incrementing the current numeric value: old: Revision : 1 new: Revision : 2 Due warning - These are unofficial edits. You should backup your entire dataset before altering anything. Any mistakes could send your aircraft into the Bermuda Triangle, never to be heard from again. There may be dragons about. Unlimited rice pudding. Etc. Etc. Link to comment Share on other sites More sharing options...
GG_Flyer Posted November 13, 2010 Share Posted November 13, 2010 Wow, the Internet can be a cool place (thanks, Al Gore!). I found such a file using data circa 1997, but I see that some editing to it will need to be made. I'll aim to make the edits / test on my system / and post the VHHX.TXT file here in 15 hours - that's when Oakland Center will shut down for the local evening. If not then, I should have it ready in 24 hours time. I'll start by trying to match it to FSX stock scenery, and then go with another freeware I've seen on Avsim. And again, I'll stress that this thread and what goes on here is totally unofficial - not supported by AivlaSoft and likely subject to my fat-fingering of data. On the other hand, if this data would be too old to meet anyone's needs, then let me know and I'll abort the process. But by now I'm curious as to if/how well it will work. Regards, Link to comment Share on other sites More sharing options...
Andydigital Posted November 13, 2010 Share Posted November 13, 2010 Did someone mention rice pudding YUM!!! Link to comment Share on other sites More sharing options...
dion73 Posted November 13, 2010 Author Share Posted November 13, 2010 Hi Travis, thanks for the quick reply, I have been testing myself and it works. I am going to try your numbers as i am heving problems with the correct diplay of the IGS approach arrow in the chart, whicch is slightly above and to the right of the RW NDB. Also the aproach course should be 088, which it is in the aircraft, but on the map it is shown as 090. Maybe you know why? I thought because of magnetic variation correction at first, but those are Westerly according to the chart and not to the East? I a have already updated to the 1.2 version. Whatever comes form this i want to thank you for this great piece of software Thanks, dion So the following lines have to be added in these files in the ..\MS FS\aivlasoft\navdata folder (all info comes from free downloads): navaid file IGS LLZ/DME RWY 13 KL ILSD 22.003299 114.104167111.90TLLZ/DME RWY 31 IIHK ILSD 22.324500 114.193667109.90TCH36X GP NDB 22.326667 114.191333333.00NHONG KONG INTL RW NDB 22.326667 114.191333337.00NIGS RWY 13 GP NDB 22.326833 114.092500331.00N navapt file PMDG:HONG KONG KAI TAK VHHX13 10930136 22.321667 114.196667111.9008800015HONG KONG KAI TAK VHHX31 10930316 22.305500 114.214500109.9031600015 AIVLASOFT:HONG KONG-OLD VHHX13 10930136 22.326667 114.191887111.9008800015HONG KONG-OLD VHHX31 10930316 22.309570 114.209178109.9031600015 The txt underneath can be downloaded at the Navdata site for free. You could also paste this into notepad, and save as VHHX in the ..\MS FS\Aivlasoft\SIDSTARS folder //LOOK at the Approaches section, I added 1770 after OM and 660 after MM. // This will get us the VNAV profile in the chart : ) [list=]SIDSTARS free download at Navdata // VHHX - HONG KONG KAITAK INTL// Copyrighted 17/7/2006 by Gary Law, Jacky Wan// Edited 12/7/2007 by Thomas Lau: Gates Added// Data from 10/9/1997.// If your FMC displayed "NOT IN DATABASE" this sentence or any other error, please visit this website:// http://www.hkadb.com/forum/viewtopic.php?t=11099 FIXESFIX A LATLON N 22 16.200 E 115 08.600FIX C LATLON N 21 17.480 E 113 36.300FIX D LATLON N 21 20.060 E 114 31.480FIX G LATLON N 22 12.550 E 113 54.180FIX J LATLON N 22 19.490 E 114 28.540FIX K LATLON N 21 52.300 E 114 41.300FIX L LATLON N 22 08.071 E 114 24.230 FIX M LATLON N 21 17.800 E 113 15.600FIX N LATLON N 22 17.400 E 115 11.400FIX O LATLON N 21 51.018 E 114 14.252FIX Q LATLON N 21 19.800 E 114 43.700FIX T LATLON N 21 12.200 E 113 43.600FIX W LATLON N 22 01.599 E 114 30.360FIX D15 LATLON N 22 19.008 E 113 55.516FIX OM13 LATLON N 22 19.404 E 114 06.009FIX MM13 LATLON N 22 19.574 E 114 10.209 FIX CH LATLON N 22 13.200 E 114 01.800FIX CC LATLON N 22 12.100 E 114 01.600FIX TH LATLON N 22 14.300 E 114 17.300FIX SC LATLON N 22 19.200 E 114 07.900FIX RW LATLON N 22 19.600 E 114 11.500FIX SL LATLON N 22 17.500 E 113 54.400 FIX BEKOL LATLON N 22 32.360 E 114 07.590FIX DAGON LATLON N 19 00.000 E 111 48.180FIX DOTMI LATLON N 22 43.060 E 116 10.050FIX DUMOL LATLON N 19 00.000 E 114 23.180FIX ELATO LATLON N 22 19.600 E 117 30.000FIX ENVAR LATLON N 21 59.500 E 117 30.000FIX EPDOS LATLON N 19 00.0 E 113 33.3FIX IDOSI LATLON N 19 00.000 E 112 30.000FIX KAPLI LATLON N 21 10.000 E 117 30.000FIX KILOG LATLON N 21 52.270 E 114 41.370FIX MAGOG LATLON N 22 17.460 E 115 49.300FIX NOMAN LATLON N 20 00.000 E 116 40.300FIX SABNO LATLON N 18 59.100 E 115 50.700FIX SIKOU LATLON N 20 50.360 E 111 30.000FIX TAMOT LATLON N 22 21.500 E 113 52.000 FIX CH055 LATLON N 22 17.046 E 114 05.208FIX CH010 LATLON N 22 06.046 E 113 54.113FIX CH001 LATLON N 21 43.140 E 115 44.290FIX CH013 LATLON N 21 40.497 E 114 42.544FIX CH021 LATLON N 21 30.344 E 113 33.222FIX CH015 LATLON N 21 28.499 E 114 26.571FIX CH020 LATLON N 21 26.574 E 113 40.505FIX CH019 LATLON N 21 23.286 E 113 54.197FIX CH017 LATLON N 21 23.218 E 114 08.187FIX CH002 LATLON N 21 08.170 E 115 23.420FIX CH004 LATLON N 20 47.560 E 113 05.120FIX CH003 LATLON N 20 44.250 E 114 51.500 FIX CC7 COLOCATED CC 270 7 FIX CH100 COLOCATED CH 104 100FIX CH117 COLOCATED CH 117 100FIX CH132 COLOCATED CH 132 100FIX CH175 COLOCATED CH 175 100FIX CH190 COLOCATED CH 190 100FIX CH199 COLOCATED CH 199 100FIX CH214 COLOCATED CH 214 100ENDFIXES RNWSRNW 13RNW 31ENDRNWS SIDSSID BEKOL1A FIX BEKOL RNW 13 FIX TH FIX OVERFLY L AT OR BELOW 7000 DIRECT FIX J 7000 FIX BEKOL AT OR ABOVE 11800SID BEKOL2C FIX BEKOL RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 TRK 154 UNTIL 9000 TURN LEFT FIX TH 11000 FIX BEKOL AT OR ABOVE 11800 SID DAGON1A FIX DAGON RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 235 INTERCEPT RADIAL 199 FROM NAVAID CH FIX CH199 FIX DAGONSID DAGON1B FIX DAGON RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 235 INTERCEPT RADIAL 214 FROM NAVAID CH FIX DAGONSID DAGON2C FIX DAGON RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX CH199 FIX DAGONSID DAGON2D FIX DAGON RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX DAGON SID DOTMI1A FIX DOTMI RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 090 INTERCEPT RADIAL 104 FROM NAVAID CH FIX CH100 FIX DOTMISID DOTMI2C FIX DOTMI RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX O AT OR BELOW 9000 TRK 090 INTERCEPT RADIAL 104 FROM NAVAID CH FIX CH100 FIX DOTMI SID ELATO1A FIX ELATO RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 090 INTERCEPT RADIAL 104 FROM NAVAID CH FIX CH100 FIX ELATOSID ELATO2C FIX ELATO RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX O AT OR BELOW 9000 TRK 090 INTERCEPT RADIAL 104 FROM NAVAID CH FIX CH100 FIX ELATO SID ENVAR1A FIX ENVAR RNW 13 FIX TH FIX W AT OR BELOW 7000 FIX KILOG AT OR BELOW 14000 FIX ENVARSID ENVAR2C FIX ENVAR RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX O 9000 FIX KILOG AT OR BELOW 14000 FIX ENVAR SID EPDOS1A FIX EPDOS RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 235 INTERCEPT RADIAL 190 FROM NAVAID CH FIX EPDOSSID EPDOS2C FIX EPDOS RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX EPDOS SID IDOSI1A FIX IDOSI RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 235 INTERCEPT RADIAL 190 FROM NAVAID CH FIX CH190 FIX IDOSISID IDOSI1B FIX IDOSI RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 235 INTERCEPT RADIAL 205 FROM NAVAID CH FIX IDOSISID IDOSI2C FIX IDOSI RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX CH190 FIX IDOSISID IDOSI2D FIX IDOSI RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX IDOSI SID NOMAN1A FIX NOMAN RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 136 INTERCEPT RADIAL 117 FROM NAVAID CH FIX CH117 FIX NOMANSID NOMAN1B FIX NOMAN RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 180 INTERCEPT RADIAL 132 FROM NAVAID CH FIX NOMANSID NOMAN2C FIX NOMAN RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX O AT OR BELOW 9000 TRK 090 INTERCEPT RADIAL 117 FROM NAVAID CH FIX CH117 FIX NOMANSID NOMAN2D FIX NOMAN RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX O AT OR BELOW 9000 TRK 090 INTERCEPT RADIAL 132 FROM NAVAID CH FIX NOMAN SID SABNO1A FIX SABNO RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 180 INTERCEPT RADIAL 132 FROM NAVAID CH FIX CH132 FIX SABNOSID SABNO1B FIX SABNO RNW 13 FIX TH FIX W AT OR BELOW 7000 TRK 180 INTERCEPT RADIAL 154 FROM NAVAID CH FIX SABNOSID SABNO2C FIX SABNO RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX CH175 FIX SABNOSID SABNO2D FIX SABNO RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX O AT OR BELOW 9000 FIX SABNO SID SIKOU1A FIX SIKOU RNW 13 FIX TH FIX W TRK 235 INTERCEPT RADIAL 190 FROM NAVAID CH FIX OVERFLY CH190 DIRECT FIX SIKOUSID SIKOU2C FIX SIKOU RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX OVERFLY CH190 DIRECT FIX SIKOUSID SIKOU2E FIX SIKOU RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH FIX CH AT OR ABOVE 3000 FIX OVERFLY CH214 DIRECT FIX SIKOUENDSIDS STARSSTAR MAGOG FIX MAGOG FIX A AT OR BELOW 15000 SPEED 250 FIX CH RNW 13STAR MAGOG31 FIX MAGOG FIX A AT OR BELOW 15000 SPEED 250 FIX L RNW 31 STAR NOMAN FIX NOMAN FIX CH RNW 13 RNW 31STAR NOMAN31 FIX NOMAN FIX D AT OR BELOW 15000 SPEED 250 FIX L RNW 31STAR SABNO FIX SABNO FIX D AT OR BELOW 15000 SPEED 250 FIX CH RNW 13 RNW 31STAR SABNO31 FIX SABNO FIX D AT OR BELOW 15000 SPEED 250 FIX L RNW 31STAR DUMOL FIX DUMOL FIX CH RNW 13 RNW 31STAR DUMOL31 FIX DUMOL FIX D AT OR BELOW 15000 SPEED 250 FIX L RNW 31STAR IDOSI FIX IDOSI FIX C AT OR BELOW 15000 SPEED 250 FIX CH RNW 13 RNW 31STAR IDOSI31 FIX IDOSI FIX C AT OR BELOW 15000 SPEED 250 FIX L RNW 31STAR DAGON FIX DAGON FIX CH RNW 13 RNW 31STAR DAGON31 FIX DAGON FIX C AT OR BELOW 15000 SPEED 250 FIX L RNW 31STAR SIKOU FIX SIKOU FIX CH RNW 13 RNW 31STAR SIKOU31 FIX SIKOU FIX C AT OR BELOW 15000 SPEED 250 FIX L RNW 31STAR TAMOT FIX TAMOT FIX OVERFLY M DIRECT FIX C 15000 SPEED 250 FIX CH RNW 13STAR TAMOT31 FIX TAMOT FIX OVERFLY M DIRECT FIX C 15000 SPEED 250 FIX L RNW 31ENDSTARS APPROACHESAPPROACH IGS13 FIX CH 8000 FIX OVERFLY G 6000 SPEED 180 DIRECT FIX SL FIX D15 4500 FIX OM13 AT or ABOVE 1770 FIX MM13 AT OR ABOVE 660 FIX RW RNW 13 HOLD AT FIX TH RIGHT TURN INBOUNDCOURSE 316 ALT 4500 SPEED 230 LEGTIME 1APPROACH IGS13CC FIX CC 8000 FIX OVERFLY CC7 6000 SPEED 180 DIRECT FIX SL FIX D15 4500 FIX OM13 1770 FIX MM13 660 FIX RW RNW 13 HOLD AT FIX TH RIGHT TURN INBOUNDCOURSE 316 ALT 4500 SPEED 230 LEGTIME 1APPROACH VISUAL13 FIX CH 4500 FIX OVERFLY SC DIRECT FIX RW RNW 13 HOLD AT FIX TH RIGHT TURN INBOUNDCOURSE 316 ALT 4500 SPEED 230 LEGTIME 1APPROACH ILS31 FIX L 4500 FIX TH 2000 RNW 31 FIX RW FIX SC TRK 251 INTERCEPT RADIAL 031 FROM NAVAID CH HOLD AT FIX CH LEFT TURN INBOUNDCOURSE 270 ALT 4500 SPEED 230 LEGTIME 1ENDAPPROACHES GATES// PASSENGER APRONGATE 1 N 22 19.6 E 114 11.6GATE 2 N 22 19.6 E 114 11.7GATE 3 N 22 19.7 E 114 11.7GATE 4 N 22 19.7 E 114 11.7GATE 5 N 22 19.7 E 114 11.7GATE 6 N 22 19.8 E 114 11.8GATE 7 N 22 19.8 E 114 11.8GATE 8 N 22 19.8 E 114 11.8GATE 15 N 22 19.6 E 114 11.7GATE 16 N 22 19.6 E 114 11.8GATE 17 N 22 19.6 E 114 11.8GATE 18 N 22 19.7 E 114 11.8GATE 19 N 22 19.7 E 114 11.8GATE 20 N 22 19.7 E 114 11.9GATE 21 N 22 19.5 E 114 11.8GATE 22 N 22 19.5 E 114 11.8GATE 23 N 22 19.6 E 114 11.8GATE 24 N 22 19.6 E 114 11.9GATE 25 N 22 19.6 E 114 11.9GATE 26 N 22 19.6 E 114 11.9GATE 27 N 22 19.5 E 114 11.8GATE 28 N 22 19.5 E 114 11.8GATE 29 N 22 19.5 E 114 11.9GATE 30 N 22 19.6 E 114 11.9GATE 31 N 22 19.6 E 114 11.9GATE 32 N 22 19.6 E 114 12.0GATE 33 N 22 19.3 E 114 11.9GATE 34 N 22 19.3 E 114 12.0GATE 35 N 22 19.4 E 114 12.0GATE 36 N 22 19.4 E 114 12.0GATE 37 N 22 19.5 E 114 12.0GATE 38 N 22 19.5 E 114 12.0GATE 71 N 22 19.0 E 114 12.2GATE 72 N 22 19.3 E 114 12.2GATE 73 N 22 19.3 E 114 12.2GATE 74 N 22 19.3 E 114 12.2GATE 75 N 22 19.3 E 114 12.3GATE 76 N 22 19.2 E 114 12.3GATE 77 N 22 19.2 E 114 12.4GATE 78 N 22 19.2 E 114 12.4GATE 79 N 22 19.1 E 114 12.4GATE 80 N 22 19.1 E 114 12.4GATE 81 N 22 19.1 E 114 12.5// MAINTENANCE APRONGATE M1 N 22 19.9 E 114 12.0GATE M2 N 22 19.9 E 114 12.1GATE M3 N 22 20.0 E 114 12.2GATE M4 N 22 19.7 E 114 12.0GATE M5 N 22 19.8 E 114 12.1GATE M6 N 22 19.8 E 114 12.1// CARGO APRONGATE Z41 N 22 19.6 E 114 12.1GATE Z43 N 22 19.6 E 114 12.1GATE Z44 N 22 19.6 E 114 12.2GATE Z45 N 22 19.7 E 114 12.2GATE Z46 N 22 19.7 E 114 12.2// Parking APRONGATE 47 N 22 20.0 E 114 12.2GATE 48 N 22 20.1 E 114 12.2GATE 49 N 22 20.1 E 114 12.2GATE 50 N 22 19.4 E 114 11.5GATE 51 N 22 19.5 E 114 11.5GATE 52 N 22 19.5 E 114 11.5GATE 53 N 22 19.4 E 114 11.5GATE 54 N 22 19.4 E 114 11.5GATE 55 N 22 19.4 E 114 11.5GATE 56 N 22 19.4 E 114 11.5GATE 57 N 22 19.4 E 114 11.5GATE 58 N 22 19.4 E 114 11.5GATE 59 N 22 19.4 E 114 11.5GATE 60 N 22 19.4 E 114 11.5ENDGATE Link to comment Share on other sites More sharing options...
GG_Flyer Posted November 13, 2010 Share Posted November 13, 2010 Dion, You found the file that I had found! And now you are seeing the tiny little problems that editing these procedures entails. [grin] It's literally trial-and-error... and if one of us is using BGL scenery that moves a runway or an ARP... then all of the "procedure waypoints" will need to be adjusted. For example if your runway is 300ft to the east of my runway, then the final fix on an approach that aligns straight for me might appear to you to be like a "sidestep." That is, you might be flying from waypoint to waypoint heading 136 degrees, 136 degrees, 136 degrees, and your final heading to the runway will shoot to the left at 96 degrees. (When I say "final fix" in that regard, I don't necesarily mean the FAF, but the "final fix" on an approach regardless.) So which VHHX scenery are you using? Default / freeware / FlyTampa? Link to comment Share on other sites More sharing options...
dion73 Posted November 13, 2010 Author Share Posted November 13, 2010 Hi Travis, I just flew the IGS13CC approach with the PMDG MD-11. The PMDG data i used contained your numbers, as did the data from Aivlasoft. In the approach the approach course in the ND showed 088, which is correct, while the Aivlasoft route on the chart shows 090. Does this mean that by placing the OM more Southernly (maybe also Easterly) and the MM more Northerly in the Navdata the course displayed will be more North to East? I'll have another look at it, but hope you're there already dion Link to comment Share on other sites More sharing options...
GG_Flyer Posted November 14, 2010 Share Posted November 14, 2010 I discovered that both the default FSX and the MyTrafficX scenery files for VHHX don't include ILSes in their BGLs, so the "found" data for a VHHX.TXT file had no ILS/LOC xmitter with which to support those approaches, rendering them only good for SIDs and STARs. So I took the VHHX freeware package (and its update) from the Avsim libraries and was able to get both approaches to work. I noticed that the FIXes in the TXT file didn't align with the freeware ILS, so I updated their LATLONG coordinates using data from the EFB approach chart and uploaded my finished product - attached to my first post in this thread in a ZIPped format. (I thought it best to keep the pertinent info in one place.) I assume that the FlyTampa scenery also has ILSes, but I don't know if its runway is placed exactly as the freeware package's. So this file may or may not work with the FT package. Caveat emptor. [attachment=2]vhhx landingaids.jpg[/attachment] The initial approach bearing for IGS13 read as 88 degrees - that was even before moving the FIXes - the ILS itself has a bearing of 86 degrees and adding in the 2 degree magvar gives me 88. That matches the scanned r/w approach plates, so I assume it's ok. I added an initial hold for IGS13 (CH), and a Transition for ILS31 that's just a hold itself. The SIDs and STARs are unchanged from what I found, so good on them I guess.... (I also decided to keep my AIRAC number the same, but I incremented the Revision number instead. I've edited my previous post to reflect that. It works, so I'm happy.) Other than that I make no claims to this highly unofficial and equally unorthodox set of data. All I know is that the lines look either straight or curved when I think they should be, and they go where I think they should go. [attachment=1]vhhx igs13ch.jpg[/attachment] [attachment=0]vhhx ils31.jpg[/attachment] Link to comment Share on other sites More sharing options...
dion73 Posted November 14, 2010 Author Share Posted November 14, 2010 Hi Travis, This is great, many thanks! I'm going to try to get this to work immediately. More thanks dion Link to comment Share on other sites More sharing options...
dion73 Posted November 14, 2010 Author Share Posted November 14, 2010 Hi Travis, I tested and updated your file so now it works correct with FLY TAMPA KAI TAK scenery as well. All data is freeware from the Fly Tampa forum and comes from Jim Vile as far as I know the same person who made the freeware VHHX BGLs (the AVSIM download). For PMDG these data should probably be used. Maybe the approaches section in the SIDSTARS should be left alone though... Next test will be to get the Aivlasoft generated RT2 routefiles for KAI TAK to work in the PMDG MD-11. thusfar i get the message unable to load flightplan... I added my file to be downloaded. Maybe you can merge it with your file and delete my other post with all the numbers which might be confusing thanks for all your help, dion Link to comment Share on other sites More sharing options...
ontheair Posted November 16, 2010 Share Posted November 16, 2010 Yes, very attractive but also very confusing, at least for me !! Could you please provide the proper "how to proceed" checklist to add SIDSTARs to VHHX. Many thanks Link to comment Share on other sites More sharing options...
GG_Flyer Posted November 16, 2010 Share Posted November 16, 2010 Jean-Louis, If you have the payware scenery, follow the instructions in Dion's TXT file. If you have the freeware scenery, follow the instructions in my message/TXT file. In either event, you'll have to update the data in the \NavData\ folder every time you update your AIRAC dataset. If you're planning on using a PMDG aircraft (MD11, 747) I believe you will have to sync your PMDG data to keep aligned with the EFB RT2 data - so they both would have the same waypoints, coordinates, etc. (I don't have those aircraft so I can't say for certain.) If that's not clear, let me know and I'll try again.... Regards, Link to comment Share on other sites More sharing options...
dion73 Posted November 16, 2010 Author Share Posted November 16, 2010 Hi Travis and Jean Louis, All the navdata changes are the same for Aivlasoft and PMDG. The difference with Jim Viles freeware scenery is the positioning of the airport and various fixes. Also the SIDSTARS file for the PMDG has a slightly different format than the Aivlasoft SIDSTARS file. (See fixes and approaches sections in notepad and compare, you will see and hopefully understand) I added a file with the correct "howw to" Navdata for both PMDG and Aivlasoft for the FLyTampa scenery. Also I added both SIDSTARS files. These should both be renamed to VHHX after pasting them in the respective SIDSTARS subfolders of the PMDG and Aivlasoft folders in the main FSX folder (..\prog files(x86)\ms games\ms FSX\PMDG or Aivlasoft). Hope this will get you an nice approach into Kai Tak. Have fun : ) dion Link to comment Share on other sites More sharing options...
dts Posted December 3, 2010 Share Posted December 3, 2010 found that in the airport.dat VHHX 22.316959 114.202621 is minus a - so correct one is VHHX-22.316959 114.202621 otherwise it crashes my EFB when reading the navdata Link to comment Share on other sites More sharing options...
aivlasoft Posted December 4, 2010 Share Posted December 4, 2010 Dave, as far as I know Hongkong is not on the southern part of the hemisphere . A minus sign is wrong for the latitude of VHHX. The correct Lat/Long for VHHX is as follows: "VHHX 22.316959 114.202621". North latitudes and eastern longitudes are positive values South latitudes and western longitudes are negative values Link to comment Share on other sites More sharing options...
ontheair Posted January 18, 2012 Share Posted January 18, 2012 Hi Dion, I'm reactivating this thread posted some time ago. From your "kai tak update airac" file attached to your previous post I can read : ..\prgram files\MS FS\Aivlasoft\Navdata OR SidStars wpNavaid file: IGS LLZ/DME RWY 13 KL ILSD 22.003299 114.104167111.90T LLZ/DME RWY 31 IIHK ILSD 22.324500 114.193667109.90T CH36X GP NDB 22.326667 114.191333333.00N HONG KONG INTL RW NDB 22.326667 114.191333337.00N IGS RWY 13 GP NDB 22.326833 114.092500331.00N I just can't find those lines in the wpNavaid file ? where are they ? thanks Link to comment Share on other sites More sharing options...
Recommended Posts