ILS Approach to low ?

[Sydney1962]

Hello,

we have tried yesterday also some approaches in full cockpit with prosim installed, but also
noted same issue I have at home with my pmdg b737, aircraft landing is slightly off centerline
on runway 27 and runway 18c we tested , will do more testing on other runways, but landing
was approx 1m left or right from centerline runway.

hope you can check again, have installed latest updated afcad files as mentioned in above topic item
but issue is not 100% solved, didn't have this issue when used default airport in P3D V3.4

maybe localiser beacon is misplaced and have to be moved a fraction of degree. It is not big difference
but should be nice if it in the next updated installer works perfect.

thanks,

[AviationPro]

I also applied the fix last week, and made a flight today landing at runway 27 with the PMDG 777-200LR. Also here, ILS approach is too low, I'll try to apply the fix again next week to try again but this is definitely something that still needs a bit of a review. It does not feel safe to land in low visibility, making it impossible to do a CATIII.

Other than that, I am really really enjoying this scenery!

Evert

[Sydney1962]

Hello Saldo

have looked again your video , and it also looked that your landing is right of centerline on 06
because when you are sitting in captainsseat and your view is exact on centerline in video
this should main your nose-wheel is right of centerline.

so maybe point to be check before next installer release.

rgds sydney

[atco]

You're right, a have noticed a couple of localisers are marginally offset to the scenery. I am fixing all the ADE's now and I have also sent to Emilios an update with the glidepath aerials set to the exact position of the aerial on the scenery.
I'll be sending the fixed localisers to Emilios to be included in the next update

[noisy]

Hi,

I have the same problem here, glideslopes on all approaches I have flown are far too low (PAPI all red). I have the AFCAD update installed, but it didn't help. However, today I noticed something interesting. I installed the navaid update from aero.sors.fr, and the installer has a 'Conflicts' button, which shows a list of navaids overriding the default navaids. Of course the ILSs of the FlyTampa Amsterdam scenery are shown here, but they are shown twice, in the ADEX_ files and in the ZHAM_Flytampa.bgl file:

Code: Select all

ABA  (ILSDME)  Freq: 111,95 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]
ABA  (ILSDME)  Freq: 111,95 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ZHAM_Flyatmpa.bgl]
BVB  (ILSDME)  Freq: 111,55 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]
BVB  (ILSDME)  Freq: 111,55 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ZHAM_Flyatmpa.bgl]
KAG  (ILSDME)  Freq: 110,55 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]
KAG  (ILSDME)  Freq: 110,55 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ZHAM_Flyatmpa.bgl]
MSA  (ILSDME)  Freq: 108,75 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]
SA   (ILSDME)  Freq: 108,75 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ZHAM_Flyatmpa.bgl]
SCH  (ILSDME)  Freq: 109,15 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]
SCH  (ILSDME)  Freq: 109,15 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ZHAM_Flyatmpa.bgl]
SP   (LOC)     Freq: 108,00 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]
SP   (ILS)     Freq: 109,50 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ZHAM_Flyatmpa.bgl]
VPB  (ILSDME)  Freq: 110,10 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]
VPB  (ILSDME)  Freq: 110,10 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ZHAM_Flyatmpa.bgl]
ZWA  (ILSDME)  Freq: 109,50 [Path: D:\Prepar3D v3\FlyTampa\Amsterdam\scenery\ADEX_FLYTAMPA_EHAM_2016_EAST.bgl]

I have no idea what the ZHAM_Flytampa.bgl file is used for, but I tried to disable it by renaming it to .off, and then the glideslopes were correct. However, I don't know what side effects disabling that file could have. But this file seems to be causing the problem. I hope that information will help you to fix it.

[emilios[flytampa]]

When you say "by renaming it to .off, and then the glideslopes were correct" did you mean that you had no more conflicts or are you referring to landing performance?

[noisy]

When you say "by renaming it to .off, and then the glideslopes were correct" did you mean that you had no more conflicts or are you referring to landing performance?

I'm referring to landing performance. I just flew approaches to runways 36R and 06 (with ZHAM_Flytampa renamed to .off), and the glideslopes were correct. If I rename it back to .bgl, the glideslopes are too low again.
I could also see it in the P3D map window, with ZHAM file active I see two ILSs (per runway) shown there which are slightly displaced, with ZHAM disabled I see only one.

[emilios[flytampa]]

Just updated AFCADs on sticky thread, please try re-downloading issue no.7 (after following brief instructions)

[noisy]

Hi,

thanks for the quick update. The new ZHAM_... file seems to be OK now, but it seems the new ADEX_... files are wrong again. With all the new files in the zip I get low glideslope again (only checked Rwy 06 so far). If I combine the new ZHAM file with the previous ADEX files (from end of December), it is OK.

[emilios[flytampa]]

here's what i get on rwy06 with current AFCAD setup. shots for DME 2.3, 0.7
stays accurate up until 0.5-0.4 DME i think

dme_2.3.JPG (1.04 MiB) Viewed 6545 times

dme_07.JPG (1.02 MiB) Viewed 6545 times

[noisy]

This is what I see:

With ADEX_FLYTAMPA_EHAM_2016_EAST.bgl from 23.01.2017 19:37:

ils06_1.jpg (813.28 KiB) Viewed 6537 times

With ADEX_FLYTAMPA_EHAM_2016_EAST.bgl from 29.12.2016 02:45:

ils06_2.jpg (802.9 KiB) Viewed 6537 times

I did the screenshots in slew mode, both from the same position (above beginning of runway), just different height. Also note the different DME display.