# Incorrect approach headings for 27K VOR 3

**URL:** <https://forum.navigraph.com/t/incorrect-approach-headings-for-27k-vor-3/14023>\
**Category:** General non MSFS data\
**Created:** [November 27, 2023, 6:38pm UTC](https://forum.navigraph.com/t/incorrect-approach-headings-for-27k-vor-3/14023 "2023-11-27T18:38:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamostew](https://avatars.discourse-cdn.com/v4/letter/j/77aa72/32.png) [@jamostew](https://forum.navigraph.com/u/jamostew)\
**Post date:** [November 27, 2023, 6:38pm UTC](https://forum.navigraph.com/t/incorrect-approach-headings-for-27k-vor-3/14023/1 "2023-11-27T18:38:47Z")

</div>

The Jeppesen chart for airport 27K (Georgetown, KY) VOR Rwy 3 shows a heading of 006 while the heading in the G1000 flight plan is 012. It seems I’ve run across this before, but never this far off.

Windows 10 Pro  
X-Plane 12  
Navigraph FMS Data Manager v1.8.4.0804  
Current data revision 2311.1102.1.0

Screenshots of each below.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/3/2/32557a14cffff892dfc2d4da746d1b7f5f441410.jpeg)  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/b/4/b4459a637dfc01450f3a8e05c672dfbe8916bcea.jpeg)

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [November 27, 2023, 6:52pm UTC](https://forum.navigraph.com/t/incorrect-approach-headings-for-27k-vor-3/14023/2 "2023-11-27T18:52:21Z")

</div>

Hi,  
we don’t offer any track or course values. This will calculate by the sim, depending on the waypoints and the leg type. Please report this to Laminar, it looks like there is a calculation error because before and after the course is correct. That seems strange …

Thank you  
Richard

---

<div class="post-metadata">

**Author:** ![jamostew](https://avatars.discourse-cdn.com/v4/letter/j/77aa72/32.png) [@jamostew](https://forum.navigraph.com/u/jamostew)\
**Post date:** [November 27, 2023, 7:54pm UTC](https://forum.navigraph.com/t/incorrect-approach-headings-for-27k-vor-3/14023/3 "2023-11-27T19:54:34Z")

</div>

Strange indeed! Thank you for the quick reply. I submitted a report to the folks at X-Plane.

Cheers!

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [November 28, 2023, 7:39am UTC](https://forum.navigraph.com/t/incorrect-approach-headings-for-27k-vor-3/14023/4 "2023-11-28T07:39:10Z")

</div>

Hi again,  
I was curious and had looked deeper into it but it really seems a Garmin issue than a navdata issue.

Here the coding for the VOR03, what we offer:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/7/2/725f9c38f7dbe9676571471b1dcd03751d88e842.png)

The yellow marker are from our source and you see the 0060 which is equal to 006° … you also see the ie. CAMRY has also 0060, so 006° … LATMY has nothing because this is an initial fix, which doesn´t have any course or distance values.

So my assumption is, that there will be something calculated wrong due the holding before but again, this is only a personal assumption. What I know is now, that this is not a navdata issue.

Sorry and thank you,  
Richard

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\
**Post date:** [November 30, 2023, 7:39am UTC](https://forum.navigraph.com/t/incorrect-approach-headings-for-27k-vor-3/14023/5 "2023-11-30T07:39:32Z")

</div>

Closed on November 30, 2023, 7:39am UTC

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