This is new…I have no idea whats going on…
Maybe when the map is set to North Up, the Plane Icon is thinking that the map is Track Up , so it is pointing UP. ?
Have not seen this before, – I assume it may be a WT GNS530 issue ? Never seen this with the original Asobo GNS530, or the pms50 one ether.
If it happens again, try switching the display back and forth between Track up and North Up, and see if it fixes itself 
I’ve encountered something similar, where all my avionics glitched and showed me flying 90 degrees off my known course (I was flying patterns at my home airport at the time, so it didn’t matter that much). It went away when I next started the game so I didn’t sweat it too much.
Have you tried pressing “D”?
I actually thought of that…but D is currently mapped to drone…So I searched for the appropriate key under “gyro drift” but nothing came up. I have no idea what the right term is for this, and there are way too many for me to browse them all one by one and hope I recognize the right one.
I’ve seen this in the Comanche, and it was due to gyro drift.
The one you’ll want is “Set Heading Indicator” which should be under Flight Instruments. Be sure to view “All” rather than “Assigned” or “New” controls to find it. Good luck!
I don’t think it is that simple. It happened to me after switching to the drone view, panning around and then switching back. I am pretty sure it is a bug, but I’m not sure how to reproduce it.
When panning around with the drone, what keys do you use? I think default is WASD+QE+RF? Here’s why I’m asking: Is it possible that some of the keys you have bound to operate the drone cam are also affecting the heading indicator? Specifically, check for “Increase Heading Bug” and “Decrease Heading Bug” to make sure you aren’t double-bound where two actions are using the same keys. Edit: Same if you’re using a controller for the drone cam. Check that device’s bindings as well if so.
I use the top hat on my Honeycomb Alpha. I have all key assignments and controls deleted in the profiles in the game because I use Spad.next. I avoid the games bindings because they load up the system (Spad’s event viewer shows that the games native bindings cause events at 100s of Hz, which when combined across lots of controls yeilds 1000s of events a second that the game has to process)