Jump to content

Portland KPDX 2010 Fix


tstewart1963

Recommended Posts

Hi. know exactly what you are talking about. I opened the airport in ADE and created new airport file with 28L closed. This way I can only be vectored to 28R ILS. Bit of a cheating but works for me. I guess the alternative would be to create another 28L ILS in ADE overriding the faulty one but I am happy with only one 28 operating. Also in my airport bgl I made RW 28 parallel with 21 and RW 10 parallel with 3, so this way I have a choice to land on either one. Also AI is more separated for landing.

Peter Bendl

ex. British Airways

Link to comment
Share on other sites

Hi,

 

If you don't mind me asking, but what's the problem with ILS 28L?

I have this scenery, but haven't really done anything with it yet.

 

I (quickly) looked at it in ADE, but didn't really see a problem...

Or is it to do with the approach itself?

 

Regards,

DDP.

Link to comment
Share on other sites

Hi,

 

So I looked a bit closer and I see the problem. The 28L LOC is misaligned.

RWY 28L heading - 299.06

ILS 28L heading - 297.30

 

That's an easy fix.

Load up KPDX_ADE9_PH.bgl in ADE, and edit the 28L LOC to 299.06 heading.

Then select compile and you're done.

 

Be sure to make a backup first.

 

Regards,

DDP.

Link to comment
Share on other sites

Hi,

I do not think misalignment would do it. It is there for a reason to keep 28L and 28R aircraft further apart. (Just like JFK 22L and 22R).

I also have a different KPDX add-on scenery, and also have problem with 28L. The aircraft is vectored in by ATC but the 28L ILS (direction and glide slope) does not work, so cannot land using approach hold, just manually. Personally I think the problem is with FS having the same frequencies for 28L/10R and for 28R/10L I know these are actual but sometimes FS does not like it. Have seen ILS acting up with some other airports where the frequencies were same on oposit runways.

Peter Bendl

ex. British Airways

Link to comment
Share on other sites

Hi,

 

If we're talking about keeping AI aircraft apart, ILS freq are of no importance, only the "human" aircraft uses that.

AI only uses the approach code in the header as seen in ADE in approach mode (which is a FAF, a heading from that FAF to the runway centerline, a FAF altitude and a missed altitude).

 

If a KPDX scenery does not contain it's own corrected approach code it will use the stock code, and will have that error.

Portland KPDX 2010 may have imported the stock code.

 

And the misalignment would bring aircraft closer together. See below from stock KPDX.

 

KPDX-28L.PNG

 

Also note that the segment from ADDUM to 28L (for GPS) is properly aligned, as is the approach course (true, not mag) for the AI (bottom right).

 

Both I and the AI landed safely at KSEA here... :)

https://www.deltava.org/thread.do?id=0x1e1ca

 

 

If I have some time this weekend, I'll actually test a corrected ILS, to see if something funny happens, with my aircraft or with AI...

 

Regards,

DDP.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...