ILS and PAPI do not match

Ask here for software oriented support
Post Reply
dkreiskott
Posts: 211
Joined: Thu Dec 15, 2022 11:11 am
Location: Germany \ near EDDL
Contact:

ILS and PAPI do not match

Post by dkreiskott »

Hello Jean Luc,

In the last few months I've noticed that the ILS and PAPI are never correct when landing. I've tried a few things with the airports because I was looking for the error there. But thanks to Herve's tools I was able to rule that out.

Could it be a software error? The screenshot shows the problem.

Image
Regards
Dieter

A320 cockpit Prepar3d v5.4 with full voice control for ATC and ground crew
Developer of EWD Overlay and Home Cockpit Builder
balu69
Posts: 113
Joined: Thu Nov 03, 2022 4:15 pm

Re: ILS and PAPI do not match

Post by balu69 »

Hello Dieter
How does the landing work?
Could it be that the camera position has changed?
Greetings
Stephan

P3D V5.4, Skalarki FCU, MCDU, RMP, ECAM, TCAS, own OVH-Panel and MIP with Leo Bodnar and Arduino, Thrustmaster TCA Captain Pack Airbus Edition, Thrustmaster TPR Pendular Rudder
P.S. translate by google
dkreiskott
Posts: 211
Joined: Thu Dec 15, 2022 11:11 am
Location: Germany \ near EDDL
Contact:

Re: ILS and PAPI do not match

Post by dkreiskott »

Hi Stephan,
I don't use camera tools. And I haven't changed the views either. I've already revised the airports in line with the current AIRAC's regarding ILS. But that didn't solve the problem either.
An approach using ILS also works, but sometimes it means that you touch down too late.
That depends on the airport.

The screenshot isn't from my home cockpit either. I use a separate computer for software development and have a separate Prepar3d license there.
So the problem exists on both computers.
Regards
Dieter

A320 cockpit Prepar3d v5.4 with full voice control for ATC and ground crew
Developer of EWD Overlay and Home Cockpit Builder
bbruechmann
Posts: 133
Joined: Thu Nov 03, 2022 9:24 pm

Re: ILS and PAPI do not match

Post by bbruechmann »

Dieter, Captain Ingo would say "the PAPI lights doesn´t matter at an precison instrument approach via ILS" The ILS glideslope rules it out, only." The PAPI lights are made for non-precision visual approaches.
That´s said, i don´t mean that the PAPI and ILS GS never match, but they don´t have to, nessecarely.
Regards
Bernd

P3D 6, I9-9900K overcl+ RTX3090 24GB, Skalarki Homecockpit + JH FMGS on a dedicated Server, AS/ASCA, EnVShade +Tex, PF3 + MCE, CorteManager + ExtPWR from CaptPERO, AIGAIM and many of add-on sceneries
jeehell
Site Admin
Posts: 413
Joined: Thu Nov 03, 2022 10:14 am

Re: ILS and PAPI do not match

Post by jeehell »

Depending on the airport the glide path antenna and the PAPI location may not match in p3d. Also if you use add-ons that can be a problem.
Also I am not convinced p3d PAPI & ILS are correct, for instance the ILS over an ellipsoidal earth is actually not a simple trig computation which I believe p3d does...
Regards,
Jean Luc
dkreiskott
Posts: 211
Joined: Thu Dec 15, 2022 11:11 am
Location: Germany \ near EDDL
Contact:

Re: ILS and PAPI do not match

Post by dkreiskott »

@Bernd
I agree with you that the ILS and the PAPI don't have to match exactly. But the deviation that I've documented here is very large.

As JL already describes, who knows whether the PAPIs are in the right place. As far as I know, you can't adjust that.

Nevertheless, I've seen the problem with the ILS so far and have therefore updated the airport. In this extreme case, however, it didn't leave me alone. What I only noticed later is that the developer of the scenery (ENAL) lowered the airport from 70 feet to 36 feet. I don't know why you do something like that.

If you correct the airport height, the PAPI and ILS almost match.
Regards
Dieter

A320 cockpit Prepar3d v5.4 with full voice control for ATC and ground crew
Developer of EWD Overlay and Home Cockpit Builder
Sameerachathu
Posts: 3
Joined: Tue Mar 21, 2023 5:03 am

Re: ILS and PAPI do not match

Post by Sameerachathu »

Hi Guys I Had the same issue, and it was caused by the Nav database mismatch. Try to uninstall all the nav data and run with the newest Nav Cycle with all the computers involved. This fixed the issue for me.
Post Reply