TACAN Points on Aggressor Campaign

[Wayc00lio]

I've noticed that the TACAN points for the aggressor FAM flight waypoints on the map are not the same as the waypoints in the documentation. For example, if you look at the Nellis departure, FYTTR is 267 for 33 from LSV. However, if you look at the flight plan in the mission editor and draw ruler lines from LSV to the position of FYTTR, its at 281 for 33.

 

I take it the magnetic variation is in effect? How does one use Mag Var properly?

 

Mag to grid - get rid. Grid to Mag - Add. So, from the data on the map/docs, and translating this to 3d world, you add the variation - right?

 

Looking at the docs, I see that LSV has a Mag Var of 15, adding 15 to 267 = 282 which is closer to my measurements within the map editor, however, the map editor must be out as this should still read 267 for 33.

 

Am I missing something?

[Redglyph]

I also found some discrepancies between the headings (or the distances) in the flight plan and - at least - the instruments, so flying from FYTTR to JAYSN to FLUSH for example will not work with headings 306 then 318, but haven't investigated that yet.

[Wayc00lio]

Copy that mate - I'll have a look a the heading changes.

 

I've reworked the TACAN points for the waypoints too. I'll fly that again to check accuracy.

[Terzi]

I also found some issues regarding to the navigation points.

 

For example if you look to the page "Red Force Recovery Routes STRYK" STRYK is located on LSV 283 26NM but on "BFM Flight Plan" it is shown as 280 26NM.

 

Unfortunately I didn't write down other things I noticed.

 

During FAM mission the voice record can be deceptive since it does not take the navigation errors in the account. I remember that on the way back to Nellis it said "On the right is Mopo town" but in my flight for some reason Mopo was on my left.

[Wayc00lio]

Yeah - This is prob a magnetic variation thing. I also had probs in the northern part of the map getting LSV signal - I switched to Groom Lake and that helped.

 

I was trying to be as exact as possible but I'm guessing that using TACAN far away from a TACAN station is fairly inaccurate.

 

What is the best procedure to follow for TACAN nav then? I'm guessing, follow the departure to the letter and then from FYTTR its best to turn onto the bearing to JAYSN, dial in the new TACAN and fly to that point, then turn onto Flush bearing, dial in that TACAN and fly there - correct?

 

So not only do I need the TACAN locations of each waypoint, I also need to note the bearings to each new waypoint.

 

This is all very new to me as you have probably have guessed!

[Terzi]

I skip that switching to BTY TACAN and then back to the LSV TACAN. The reason why JAYSN is there in real life is probably to keep you away from the Creech AFB. So instead of switching, I avoid flying a direct route between FLUSH and FYTTR but follow a curve bended towards southwest.

[D-Day]

I've noticed that the TACAN points for the aggressor FAM flight waypoints on the map are not the same as the waypoints in the documentation. For example, if you look at the Nellis departure, FYTTR is 267 for 33 from LSV. However, if you look at the flight plan in the mission editor and draw ruler lines from LSV to the position of FYTTR, its at 281 for 33.

 

I take it the magnetic variation is in effect? How does one use Mag Var properly?

 

Mag to grid - get rid. Grid to Mag - Add. So, from the data on the map/docs, and translating this to 3d world, you add the variation - right?

 

Looking at the docs, I see that LSV has a Mag Var of 15, adding 15 to 267 = 282 which is closer to my measurements within the map editor, however, the map editor must be out as this should still read 267 for 33.

 

Am I missing something?

 

Nevada will be an Easterly declination so it will be the opposite from above.

 

Easterly Declination: Mag to Grid - ADD. Grid to Mag - SUBTRACT.

Westerly Declination: Mag to Grid - SUBTRACT. Grid to Mag - ADD.

 

I'm relatively new to DCS and have mainly flown in the Caucus map so far, anyone please correct me if I'm wrong. So far my understanding is that the map in the mission editor and the runways are True North but the aircraft report magnetic headings in their instruments like HSI, etc. I'm not sure if DCS World is modeled after real world declination or not but Nellis AFB is currently 11.8 degrees Easterly declination, so 281 (Grid) from the map in the mission editor minus 11.8 is 269.2 (Mag). Close but not exact to 267 still unless the ruler lines in the mission editor were roughly drawn to get 281 degrees causing the difference.

 

One last thought, magnetic declination is constantly changing, so does the declination in DCS stand still in the time when the map (Caucus or NTTR) was created or is it being updated to match the real world declination every year?

[Sydy]

I skip that switching to BTY TACAN and then back to the LSV TACAN. The reason why JAYSN is there in real life is probably to keep you away from the Creech AFB. So instead of switching, I avoid flying a direct route between FLUSH and FYTTR but follow a curve bended towards southwest.

 

Use LSV 279 by 53 for JAYSN. Works like a charm.