Can't use TACAN as waypoint

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I ran into an odd situation yesterday; I raised it on the Avidyne Facebook group but am reposting it here since I know lots of folks don't use FB.
I was flying KHSV-KSIK. For weather, I wanted to divert to the west; I asked ATC for direct DYS. DYS shows in Foreflight as a TACAN-only waypoint. (It happens to be colocated with KDYS, the Dyersburg airport, FWIW). I couldn't get the IFD to accept DYS as a waypoint.

Mike Salmon was kind enough to investigate, and here's his feedback:

"The nav database only contains a TACAN if it is referenced by a SID, STAR, or Approach. For instance, COF is a TACAN at Patrick. It's included in the database because it's referenced by the OCEAN4 departure. DYS isn't referenced in a procedure, so it's not included in the database."

This seems like a sensible approach for Jepp to take, but it doesn't seem to be documented anywhere that I can find, so I'm posting here in case anyone else runs into a similar situation.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
paulr Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 24 Jan 2014 Status: Offline Points: 545	Post Options Post Reply Quote paulr Report Post Thanks(1) Quote Reply Topic: Can't use TACAN as waypoint Posted: 06 Aug 2023 at 5:34pm
	I ran into an odd situation yesterday; I raised it on the Avidyne Facebook group but am reposting it here since I know lots of folks don't use FB. I was flying KHSV-KSIK. For weather, I wanted to divert to the west; I asked ATC for direct DYS. DYS shows in Foreflight as a TACAN-only waypoint. (It happens to be colocated with KDYS, the Dyersburg airport, FWIW). I couldn't get the IFD to accept DYS as a waypoint. Mike Salmon was kind enough to investigate, and here's his feedback: "The nav database only contains a TACAN if it is referenced by a SID, STAR, or Approach. For instance, COF is a TACAN at Patrick. It's included in the database because it's referenced by the OCEAN4 departure. DYS isn't referenced in a procedure, so it's not included in the database." This seems like a sensible approach for Jepp to take, but it doesn't seem to be documented anywhere that I can find, so I'm posting here in case anyone else runs into a similar situation.