I think i noticed a little anomaly with 2601 rev2 (was fine in 2601 rev1).
On the chart the CRS is 244 (a lot to the right of the runway but that’s on purpose to avoid the terrain and it’s what makes this approach challenging), in the navdata the heading is now 251 so it brings the plane dangerously close to terrain on the left, i guess this was done to align the ILS with the runway but in this case it’s very wrong and dangerous.
as you can see on the pic below, i’m perfectly on the LOC and GS, but the chart clearly shows my position being wrong and terrain ahead is getting very close.
with rev1 (pic below) everything was fine and the chart data was matching ‘BGL data’ with CRS at 244 so the approach was correct.
I think (might be wrong) that the heading in the navdata BGL should always match with what’s on the chart. It also seems that the LittleNavMap Navigraph file is always correct (LNM sqlite file has 244 so you have the correct data somwhere) but it just ends up being wrong in the BGL (in this particular case \0601\NAX49150.bgl which has 251). It’s certainly easier said than done though and i obviously have no idea of how the data is parsed
No rush obviously, just a little report to try to improve the realism of our flights and the quality of the data. And to make it clear I’m really happy with the product