TACAN Navaid located at Trenton (CYTR) airport doesn't work

ISSUE DESCRIPTION

In the sequence of the following topic (which is now closed without solution):

I found that TACAN Navaid located at Trenton (CYTR) airport located in Trenton, Ontario, Canada - with the frequency of 034X - named UTR doesn’t work!
This seems to be related to the TACAN itself and not with other issues/objects since I don’t have this problem with other TACANs such as the ones located Cold Lake, Alberta, Canada or Comox, BC, Canada - TACANs (frequency: 082X - name: UOD and frequency: 041X - name: UQQ, respectively).

I tested with the Super Hornet and the C-17 (I own Premium Deluxe MSFS2024 edition) where when flying around Cold Lake (CYOD), Alberta, Canada TACAN (082X - UOD) or Comox (CYQQ), BC, Canada, I had information about these Navaids but when doing the same around Trenton (CYTR) Ontario, Canada - TACAN (034X - UTR), no information - neither bearing and distance - appears.

The bug/issue persists even after the latest Sim Update 5.

FREQUENCY OF ISSUE

Always

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Just fly with any aircraft that has TACAN, namely and for example the already mentioned Super Hornet or C-17, around Trenton (CYTR) and configure the aircraft to pick up the TACAN station, this case 034X (UTR).

  2. Repeat the step above but now fly near another TACAN station like for example the one in Cold Lake (CYOD), this case 082X (UOD) since this one works and there might be other TACAN stations worldwide that might have the same problem as Trenton/034X/UTR.

1 Like

I don’t have military aircraft & TACAN knowledge, but spawning at CYTR with the A400M, Tacan 34X (UTR) is received:

Maybe I am missing something ?
If issue is still the same than the other report you mentioned (automatically closed after 365 days without any posts), I can reopen it and merge your report there.

I am flying with Vulcan and Jaguar mostly. I have similar issue with Tacan from EBFS (BFS), EGOV (VYL), EBFN (KOK).

Some others TACAN in europe are working only from very very short distance, like 15nm only.

1 Like

After anothers little nav from UK to Netherlands, most of tacan in Netherlands are working fine, but the one from Eindhoven EHEH (EHV) is not working at all.

1 Like

First of all, thanks for the reply!

But what you shown in your picture is not really a TACAN. You can even see VOR1 and VOR 2 written. This means that the aircraft is actually using VOR and not TACAN.
While one can consider TACAN as a sort of a “military VOR” but it is NOT a VOR. For instance, TACAN is usually tuned via channels, for instance 034X in case of Trenton TACAN and not as a frequency, although civilian aircraft can tune TACAN’s using frequencies but in this case they will only get the DME (distance) “portion” of TACAN and will NOT get the bearing/direction data.

After reading your post, I tried the A400M for the first time and from what I gather, the A400M modeled in FS2024 doesn’t have TACAN and that can be seen in your screenshot (only VOR’s are “tunable”). So and IMO what is happening in your case can be one of two situations:

  1. Either the A400M is improperly tuning the TACAN station as a VOR, something which again would be wrong and therefore somehow a problem/bug with the A400M aircraft and FS2024 or this was done by the A400M devs in order to implement a sort of a “makeshift” TACAN. For instance the A400M could be handling a TACAN like it was a VORTAC but this would be wrong/unrealistic since Trenton has a TACAN not a VORTAC (more on that below). Anyway, this is not how TACAN’s work and that’s why I used the F/A-18E Super Hornet and C-17 examples since they are realistic in this regard (TACAN tuning). And remember that both the Super Hornet and C-17 but specially the Super Hornet are also FS2024 stock planes.
  2. Or, the A-400M in your example/screenshot is in fact tuning the ILS for Runway 24 (ILS24) which uses the same 109.70 frequency as Trenton’s TACAN (UTR) but this would be strange as the it’s using the UTR code while Trenton’s ILS24 code would be ITR.

In line with what was mentioned above in point 1-, Trenton has a TACAN not VORTAC. TACAN can only be tuned (for bearing/direction) using a proper TACAN radio (military) equipment. VORTAC’s as the name implies, besides TACAN military radio equipment can also be tuned (for both bearing/direction and range) using civilian VOR radio equipment and this is something that I’m starting to suspect that the FS2024 A400M aircraft is doing (but I’m obviously not sure about it). Like I already said above, Trenton has a TACAN (and not VORTAC) beacon which can be seen here:

There are other locations worldwide that have VORTAC beacons like for example Moose Jaw, Saskatchewan, Canada:

Also like mentioned above, both Trenton’s ILS of Runway 24 (ITR) and TACAN (UTR) use/share the same 109.70 frequency. Could this be one of the reasons for this problem?

Anyway and to confirm what I’ve been saying and that this is a real issue/bug, below I’ll post a screenshot of the Super Hornet correctly tuning the Cold Lake TACAN (082X):

And now the same Super Hornet in Trenton and there you can see that it cannot tune Trenton’s TACAN (034X):

And next, the same experience above with the Super Hornet but now with the C17. Below I’ll post a screenshot of the C-17 correctly tuning the Cold Lake TACAN (082X):

And now the same C-17 in Trenton and there you can see that it cannot tune Trenton’s TACAN (034X):

Finally, below there’s a screenshot of the C-17 in Trenton tuning the 109.70 frequency using VOR1 (NAV1) and there you can see that it’s correctly tuning Trenton’s ILS for runway 24 (ITR) and not Trenton’s TACAN (UTR):

Sorry for the long post, but I think it was important to explain with better detail, what’s happening here. And I hope this help you solve this issue.

1 Like

@DementedCorn327
@RicHornet

There’s a NOTAM out for the TACAN at CYTR (U/S on a NOTAM generally means unservicable):
G1011/26 04/15/2026 1724 TRENTON TACAN UTR 109.7MHZ/CH34X U/S
Reference:
https://notams.aim.faa.gov/notamSearch/nsapp.html#/details

Regards

1 Like

Sure but there’s a two fold problem with what you said:

  1. This is not a new problem. If you look at the other thread that I mentioned in my first post of this thread, I already reported this issue during May of last year (2025) and thus, well before the NOTAM. Read here:
    Asobo F-18 TACAN course selection doesn't work on MSFS2024 - #2 by Kassadgla
  2. I figure/imagine that updates received from NOTAM should only carry on to the sim with Live settings, no? Anyway, even when playing with completely offline setting and/or pre-NOTAM dates, Trenton’s TACAN (034X) still does not work.

At the same time and as you can also read in the referred thread above that there are other TACAN’s with the same problem/issue.

There no online/offline mod related to navdata, there is monthly AIRAC cycle update for the whole sim.

1 Like

Thanks for the reply/heads up.
Nonetheless, the problem still stands with Trenton’s TACAN since this always happened, even prior to the “Unserviceable” Trenton TACAN notification.

Hi @RicHornet
Didn’t know this was an issue before the NOTAM. Do me a favor, after the newest AIRAC update drops following the end date of the current NOTAM (assuming it’s not extended or a new one added), drop a note in this thread, and I’ll retest to validate the issue! If it’s not working then, we should be able to get a formal bug report started.

Regards

1 Like

Roger, will do.

1 Like

This has been an issue with the Asobo F/A-18E since FS2020. UTR will only tune from approximately 30NM out or further.

No, this isn’t the same issue. And yes, I’m aware that in FS2020 the UTR TACAN will only be picked up at relatively short distances but and nevertheless, it still works (for example, I often do that with IndiaFoxtEcho’s F-35 Lightning II, again in FS2020).

But in FS2024 it’s a completely different case since UTR will never be picked up (it simply doesn’t work!), no matter how close you are to Trenton’s airport and UTR TACAN beacon. For example, even if you are on the taxiways or runways of Trenton’s airport, UTR TACAN will never be picked up.

That’s in agreement with my point, the error is that UTR does not work in the Asobo Hornet when close to the station, only at significant distance. I lack the developer depth to confirm, but imagine the assumption earlier in this thread is correct that it has to do with frequency conversion in the code and converted frequency matching the localizer, hence why you can only pick up UTR when outside localizer range.

1 Like

After reading your post, I did some more tests and yes you’re right! That’s indeed the issue!

I started with the C-17 (in FS2024) on Trenton airport’s Runway 24 and tuned the UTR TACAN (034X) and like you said, nothing was tuned. Then I took off and headed West and when I reached a distance of about 29.4 Nautical Miles (around the 30 nautical miles that you mentioned) then and suddenly the aircraft (C-17) started to pick up the UTR TACAN beacon and continued to do it so as far as I continued to fly away from the TACAN.
Then I turned back again and headed to Trenton’s airport (in the direction of the TACAN beacon) and as soon as I got closer than 29.4 Nautical Miles from Trenton airport/TACAN then the TACAN beacon wouldn’t be picked up.
But if I got again farther than the same 29.4 Nautical Miles then Trenton’s TACAN (UTR) would be picked up again and so on…

Nice finding there @Raynen! Thanks :+1:

I attach here two screenshots showing this:

1 Like