IGS 13 KL
DME not showing.
Thank you.
Hi,
thanks I will check it possible that the dme component is missing in the tailored records. Let me check this … Thanks for the hint!
Cheers,
Richard
Thank you. That would be perfect.
1 Like
G’day all, the tailored data does include KL and IGS beacon data so hopefully this would provide DME information for the IGS approach.
Regards, Martin YBLT
Hi Martin,
this is correct but what I have seen is indeed, that the DME part is missing. I will contact you directly when I’m finishing with my tests and I’m really know where the issue is.
Thanks,
Richard
2 Likes
For those flying the IGS 13 with an FMS equipped airplane no problem even though CH is now DME only. Others can do the 11-3B IGS using CC and SL instead of CH and GOLF.
I hope the KL DME can be put in although it was never part of the procedure. ATC usually asked for reporting once established inbound around SL and then the OM.
Thank You.
Thats right and I’m pretty sure that this is the case. I’m currently testing the added DME component now …
Just for info Martin (@stewamar) is the designer of the tailored records in our database, and he has made a couple of special approaches in NZ and Australia for us.
… but anyway, I pretty sure we will find a solution and can fix this together.
Cheers
Richard
1 Like
Thank you, you guys are the best.
Some time ago I requested that CH be reinstated as a VOR but was told that’s not possible but you kindly reinstated CC (which in the real world no longer exists). Maybe with the passage of time CH as a VOR? For an old Hong Konger, the thought of Kai Tak without Charlie Hotel would have been unthinkable. 
1 Like
Will check this too again …
Normally, we don’t add outdated data only for really special places, like Kai Tak, Berlin Tegel, …
Our mission is primarly to offer real world data and we must avoid (also due our contracts) a mix of real- and outdated data. Therefore we must very careful with such additionals.
But, let me check it - also with Martin, if we can add it the Charly Hotel VOR.
Cheers
Richard
PS: before I forget: thanks for your kind words - it’s the team which works very close together plus you, our user which are also necessary to get the ideas …
1 Like
Hi again,
I have added the DME component and it´s working now … You can expect the change with the next AIRAC cycle 2307 (or in the next revision, if we create one of 2306). Hope that helps!
Cheers
Richard
1 Like
Thank you. (Must be more than 20 characters!
1 Like
Nice job Richard!! Thank you for all you do it is really appreciated.
Martin
1 Like
You´re welcome Martin … I will send you the specific records to complete your dataset too 
Cheers,
Richard
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
My last post on this is now closed. You said the DME would be added in the 2307 AIRAC. It has not been added.
Thank You.
Chris Stanley
Hi Chris,
I will check it, when I’m back … I know, that I have added it … but I will check it again.
So, please be patient, thank you.
Cheers
Richard
1 Like
Will this be fixed in 2308?
Thank You.
Hi,
normally yea, but I have just recognized that the screenshot is from PSX. Not sure, if this addon can handle tailored records because we must use their own parser and we have no clue about the data structure. So, we will see if this is working now or not. I hope so. Sorry.
Cheers
Richard
Thank you.
In every other situation with PSX the DME, frequency and identifyer show and the GS and LOC behave normally. With KL, the GS and LOC work fine but the DME does not. I doubt this is a PSX issue.