Was asked on the Discord server to post this here on the forums as a bug. The track from FLO doesn’t appear to match when comparing the IFR low chart and approach plate for ILS23.FLO at KSMS.
The navdata has an FC leg on that approach between FLO and GAUGH (course from a fix, here FLO, to an along track distance, here, the track is 261 and the distance is 23.6):
APPCH:010,A,I23,FLO,FLO,K7,D, ,V A, , ,FC, ,FLO,K7,D, , ,0000,0000,2610,0236,+,02000, ,18000, , , , , , , , , ,0,D,S;
If I read the above correctly, it looks like the data does reference FLO as the “recommended navaid” for this leg but, my guess is, the Charts software is ignoring this and using the current local magnetic declination (about 7 degrees west) to draw the path, as opposed to that of the VOR (about 3 degrees west, calibrated in 1965) resulting in a path that’s about 4 degrees off over 24 miles, as depicted above.
Regards,
Tim
1 Like
Hi,
We’re investigating!
Regards,
Stephen
1 Like