Kadena (Fukuoka) TACAN not recognized until 6 DME
-
I built a training mission in TE builder approaching Kadena (Fukuoka). It starts me about 20 miles out from Kadena, at angels 12 coming in from the north over the water.
When I select Tacan channel 57X and select TCN on the HSI, I get no DME reading for Kadena, and no arrow pointing towards Kadena. It is clear weather, I can literally see Kadena in front of me, but the HSI does not give me any information. That lasts until I am 6 miles out, then suddenly the HSI springs to life and points towards Kadena and I get a distance reading in the HSI.
Surely that can’t be right - the Kadena TACAN has a range of 100nm (according to the AIP doc). I have UFC selected, just to rule that out
Edit: Makes no difference if I call into Kadena approach and get a “welcome back”, TACAN is still not up.
Any advice is most welcome,
JB
-
Hi Jayb,
I am unable to confirm your observations, I got DME from Fukuoka well beyond 40DME on TACAN 57X - can you post the TE files so I can fly the TE you flew, please.
Ironman.
-
Hi Ironman,
I have attached the TE files here, they are very basic but so are my TE skills. So it might be something I set or did, I would be glad if you could find something so that it actually works afterall
Cheers,
JB -
I have had feedback that the problem must be with my setup, others do not have the issues that I do. So I will reinstall and see what happens. This is the issue I had - notice how the TACAN comes alive at 0:58:
-
Hi jayb,
I flew the 57X tacan no problem in your TE. What I did notice is that if your TACAN is set to 126X for IWAKUNI it “comes alive” at about 6Nm from FUKUOKA.
Try a reinstall and if you still have this problem we can fly it together on line and try to sort it out.
-
I did an uninstall, restarted, did a stock reinstall. And now the problem is gone. So I have a way of fixing it, which is good.
Interesting thing is that I then replaced the stock User folder with my User folder from the old install. I know, not the recommended approach, but I could always go back to stock so I figured I would try. Then the problem reappeared. So something in the User\Config folder most likely caused this.
-
“I then replaced the stock User folder with my User folder from the old install. I know, not the recommended approach,”
And now you know why ;0)
-
Haha, yes, I am slowly rebuilding my settings now