August 22, 20241 yr Hi Nico, I know that this subject has been raised before, but I can't recall the issue, so I don't know if there might now be a solution... Almost all landing aircraft at KDEN (I have tried with both the Flightbeam as well as the X-Codr versions) land way short of even the approach lights. They simply fly on the ground until they reach the threshold and runway. I seem to recall you had mentioned something about elevation around the airport, but I'm not sure what the effect was/is. Can you please advise whether there might be anything that we can do? Thank you,
August 22, 20241 yr I see this issue as well and also at Flytampa KLAS landing runway 26L. There are no large QNH discrepancies I see either which is what I thought was causing it David
August 22, 20241 yr 14 hours ago, mmcmah said: Can you please advise whether there might be anything that we can do? You cannot do much other then checking the airport altitude in the airport file, but for both publishers you mentioned it is ok. Other possible causes: a very high QNH value, or the addon airport designer has not placed the beginning of the landing runway as in real live. PSXT aircraft have no notion of runways, they just follow the lat/lon in the RT traffic data. What program were you using? In PSXT I do the altitude correction for the local QNH, while in PSXTraffic Balthasar from RT does that job. Nico Edited August 22, 20241 yr by kiek
August 22, 20241 yr Author 1 minute ago, kiek said: You cannot do much other then checking the airport altitude in the airport file, but for both publishers you mentioned it is ok. Other possible causes: a very high QNH value, or the addon airport designer has not placed the beginning of the landing runway as in real live. PSXT aircraft have no notion of runways, they just follow the lat/lon in the RT traffic data. What program were you using? In PSXT I do the altitude correction for the local QNH, while in PSXTraffic Balthasar from RT does that job. Nico I use PSXT. This has been an issue for as far as I can remember. Original PSXT (running RT as well), forked PSXTraffic and now the current PSXT. I don't know if the runways aren't as real life, but I would suspect that they are, as the both 3rd party sceneries have the same issue. In the past, you have mentioned some strangeness with the elevation around KDEN, but it's pretty flat around the airport in real life and I don't think the QNH values are high. I can't remember what they were, but I will check next time.
August 23, 20241 yr 18 hours ago, mmcmah said: In the past, you have mentioned some strangeness with the elevation around KDEN, but it's pretty flat around the airport in real life and I don't think the QNH values are high. Well in FlightBeam one runway is at a plateau, higher then the terrain in front of it. That can lead to difficulties at very high QNH's. However, at other airports with landing runways higher then the surroundings it goes well. Take for instance 05 at Madeira or landing over the sea at KSFO or LFMN. It is strange. The algorithms in PSXT are generic, the airport does not matter. It is not, "hey we are going to land at KDEN, now we are doing something different" 😉 Edited August 23, 20241 yr by kiek
August 25, 20241 yr I saw this a few hours ago at EGKK. While waiting for my turn to take off I saw 3 a/c landing well short of the runway. Local QNH was 1020, but RT reported 1013. Later when I approached EIDW RT reported correctly 1009. Cheers, Søren Dissing Intel i9-13900K @5.6-5.8 Ghz | ASUS ROG RYUJIN III | ASUS ROG Astral RTX 5090 OC | ASUS ROG Maximus Z790 Hero | 64Gb DDR5 @5600 | 1Tb Samsung M.2 980 PRO (Win11), 1Tb Samsung M.2 980 PRO (MSFS), | ASUS ROG Helios 601 | 32” ASUS PG32UCDM 240hz 4K | Chaseplane | TM TCA Captain's Edition, Winwing FCU + EFIS L/R, Tobii 5 | Win 11 Pro 64 | MSFS 2024 | BA Virtual | PSXT, RealTraffic w/ AIG models
Create an account or sign in to comment