CYSB VOR Verification

Good morning forum,

I have noticed that I can never pickup the VOR at CYSB. It is a VOR/DME and I can get it to rigister in my aircraft DME, but it never picks up on the OBI.

I have had other VOR’s do this, but have got them working with a restart. This one seems consistant. I checked the NOTAM’s and don’t see any messages regarding it.

I was flying at FL080 maybe to low for that VOR? I am not using any custom / mod for that airport it is Asobo stock.

Any insight would be apprecaited.

Thanks.

This is YSB SUDBURY 112.30 185° 0.2?

Correct, that’s the one!

According to my Navigraph reference charts, YSB 112.30 is no longer a VOR/DME, but a DME only with a range of 130 nm. That would explain why the OBI stays inactive.

1 Like

That deffinetly explains it!

Would it be to much trouble to ask for a screenshot of your chart? (I have navigraph as well) not sure where I missed it being changed.

Thanks!

@skypilotYTS I just looked at all CYSB charts in Navigraph and to my surprise, even though the enroute charts seem correct, the approach charts on which YSB is depicted have not been amended to indicate DME only.

On the Low and High Enroute charts, we can see that YSB is a DME only by having the correct navaid symbol and the mention of “DD” in the Navaid info box (DD 112.30 YSB). DD indicates DME only. But on the ILS RWY 22 approach chart, YSB is depicted as “D”, as in (D 112.30 YSB), which would indicate VOR/DME.

My initial reply to you was based on the DME symbol and the “DD” mention on the Enroute charts, and since this is what we observe in MSFS, I conclude that the approach charts are not up to date regarding YSB information.

I have not checked if things are different if removing the Navigraph data from MSFS.

Best regards,

I apprecaite the follow-up I’ll take a look!

Regarding the comment quoted above, am I miss understanding or are you saying if I remove the Navigraph data from MSFS, that the VOR may then respond?

Thanks.

I don’t know if the VOR might respond or not, it will depend on what the base navaid info in MSFS has regarding YSB (VOR/DME or DME only). My guess is DME only since the Asobo AIRAC is recent.

Just to clarfic the Sudbury (Ident: YSB) navaid is a DME only navaid. The NavBlue-stock data and the Jeppesen Navigraph data reflects this change. At least YSB is defined as DME-only in BGLs.

Here a screenshot from the AIP Canada (reference link):

Cheers
Richard

1 Like

I have found Navigraph Charts (I use their Desktop Charts application) are more than often several cycles or more out of date. For example, the KHOU ILS04 chart is dated 28 JUN 19 and their Class B airspace chart is dated earlier and still indicates the HUB Hobby VORTAC, which has been decommissioned and no longer exists. Interestingly, even the free web site Skyvector uses current charts. Too bad a service we pay for cannot do the same.

@Downscc I can´t find any difference here - would be great when you can help us to find it. We will report this to Jeppesen than - thank you. Airspace update (due the wrong HUB VOR) is noted.

Left the FAA charts, right the Jeppesen charts:

Cheers,
Richard

Awesome!

Thank you very much for this, that document helps and will bookmark it for future reference. I guess I was confused because in Navigraph I saw the following.

Showing “VOR”

Is this expected or should it be something else if only DME?

Thanks.

No, according the Jeppesen specs for the airport diagrams, this is only a symbol for an airport navaid, it can also be a VORDME, VOR, DME, NDB, LCTR (excl. ILS), …

It shows you only the reference that there is a navaid, nothing more. Not the ident, the type, the frequency, the power, the range, …

Cheers
Richard

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.