Just to stick in my Fourpenny's worth, I've just flown my 737-800NGX into JFK on a Parch1 STAR using the stock airfield provided by FSX. I'm on Airnav 1310. Yesterday I couldn't work out what was happening, as when I activated VOR/LOC the A/C swung onto a heading that didn't align with the runway. Weather was good, so flew it in manually, but also noticed no VASI/PAPPI lights.

 

I pulled up the stock airport on ADE, and found the ILS as supplied by Microsoft was misaligned and PAPPI lights were missing on 22R as informed by AIRNAV. Reflew the same route today, and found that were I to use the NAVIGRAPH data to fly the approach, I would again miss the runway. I plotted the coordinates given for MATTR and CORVT and they are displaced from the runway. I checked the runway position, both with AIRNAV and Google Maps, but all was well, so I'm confused. Nothing new there. Anyone got any ideas?

Although there are several misaligned localizers in stock FSX, JRK 22R is not one of them. The actual real-world localizer is indeed offset 3 degrees to the right of the runway centerline, and FSX does show this accurately.

 

If you compare current charts for the ILS 22R, you will see that the localizer course is 222 degrees, while the adjacent runway 22L has a localizer course of 225 degrees. I'm not sure why the 22R offset exists, but it may be required in order to provide adequate lateral spacing when the two runways are being used for simultaneous parallel ILS approaches.

 

For a similar reason, there is indeed no PAPI lighting system on the r/w JFK 22R - only 22L has a PAPI

 

Since 22L is a CATIII runway, its localizer course of 225 degrees is precisely the same as the physical runway's heading.

Thanks Jim, that's really interesting and of course indicates my lack of observation with regard to the CAT status. 

 

I've since done some more research, and it would appear that the localizer equipment can't be placed beyond the runway, since that is the Bay, and there are various wildlife issues as well.

Just as a note, unlike FSX, X-Plane does support "core"  navdata updates via Navigraph!

Thanks Jim, that's really interesting and of course indicates my lack of observation with regard to the CAT status. 

 

I've since done some more research, and it would appear that the localizer equipment can't be placed beyond the runway, since that is the Bay, and there are various wildlife issues as well.

Ah! That makes sense. I just took a look at an Google Maps aerial shot of the runway ends at JFK, (The runway 04 thresholds)  where the runway 22 localizer arrays would be located. 22R extends right onto an marshy island in Jamaica bay, and there is indeed no place to put the antenna. There is more "dry land" off the end of 22L, and you can see the localizer antenna right in the middle of the extended centerline.

Hi all,

 

Not sure if my comments are any good for the original question here.

 

Over the last few years I have bought the PMDG 737, then the 777, the Quality Wings, 146 and others, I use the Aivlasoft EFB and Simbrief too, but noticed that many of these addon's use the latest Airac cycle at the time they originally were released. So over the years you end up with addons using different cycles.

 

I don't fly online, so reading the above posts you would think there is no point installing any Navigraph updates. I do however think there is a thought here that it is worth mentioning, and so say once a year all my addon aircraft are updated so they all using the same set of Navigation Data from Navigraph. I currently use cycle 1408 as that was the last addon which came with a cycle installed, so I updated everything else to the same cycle.

 

Not sure if it's worth doing or not, I just like to update the sim so everything is running with the same settings. Hope this helps any.