I encountered a very odd issue when attempting an ILS landing at KCLT 36L.  Basically I setup everything as expected, however, the runway was way off, and not even close.  It had me basically landing 1/2mile west in the trees.  Is this a P3D issue or an issue with PMDG777?  It also was not able to pick up the localizer (for good reason I suppose)

 

 

Thanks

 

Rob Polak

I encountered a very odd issue when attempting an ILS landing at KCLT 36L. Basically I setup everything as expected, however, the runway was way off, and not even close. It had me basically landing 1/2mile west in the trees. Is this a P3D issue or an issue with PMDG777? It also was not able to pick up the localizer (for good reason I suppose)

 

 

Thanks

 

Rob Polak

Runway 36L does not exist in default FSX or P3D at KCLT - it was only opened in 2010. If you were following the extended centerline in LNAV mode using current AIRAC data, it was sending you to where the runway now exists, but indeed, that location was only empty fields in the default sim, (which reflects the way things were before construction of the new runway started).

 

I know there is at least one payware KCLT add-on that may have the new runway, and there are free AFCAD updates here in the AVSIM file library that will add the new runway as well. The one by Ray Smith is likely to be excellent, as he does outstanding work.

Thanks!

 

Runway 36L does not exist in default FSX or P3D at KCLT - it was only opened in 2010. If you were following the extended centerline in LNAV mode using current AIRAC data, it was sending you to where the runway now exists, but indeed, that location was only empty fields in the default sim, (which reflects the way things were before construction of the new runway started).

I know there is at least one payware KCLT add-on that may have the new runway, and there are free AFCAD updates here in the AVSIM file library that will add the new runway as well. The one by Ray Smith is likely to be excellent, as he does outstanding work.