![]() ![]() I have made the changes suggested by Gray_Lensman in ADE9 but i see no change.ĭ:\Microsoft Flight Simulator X\MyTraffic\Scenery\BR2_UHPP.BGL ![]() If it was offset an equivalent amount to the other side of the approach path, I would be inclined to think that it had such a purpose but as it is to the wrong side, I am inclined to believe it's another FSX airport design goof of which there are many. If it was meant to guide around obstructions to the airport, then being offset in the direction that it is in stock FSX would actually guide your flight path closer to some higher hills/mountains on the approach path on that side of the approach to runway 34R, a direct contradiction to the purpose of an offset Localizer as described above. However, in this case the chart does not call it an LDA and. It is then called a Localizer Type Directional Aid (LDA). In some cases, a course projected by localizer is at an angle to the runway (usually due to obstructions around the airport. In aviation, a localizer (LOC) is one of the components of an Instrument Landing System (ILS), and it provides runway centerline guidance to aircraft. Has anyone checked if this localiser is not offset in reality? ![]() In this case, I aligned to the displayed Garmin localizer arc near the apex then snapped the pics. I used the Cessna 172 with the Garmin because it best visually shows the Localizer Arc Zoomed in or out. Here's a pic of the ADEX corrected UHPP airport alignment on my system AFTER ADEX correction: Here's a pic of the stock UHPP airport alignment on my system BEFORE ADEX correction: Correcting the Localizer to also be 338.77 corrects the issue. The further away from the airport you get the worse it aligns especially at distances usually around the FAF. The problem is that the stock airport had the Localizer aligned to 337.00 but the corresponding runway was aligned to 158.77/338.77. I used to see this before in where the localiser actually matches the runway opposite instead of the one its meant to, think i fixed that by moving Mytraffic scenery around in scenery.cfg.īut this time the localiser matches non of the 4 runways at UHPP.Īny idea how to fix this globally in fsx, if not whats the best way to fix for each airport i find the issue. I moved the localizer slightly to one side at runway 16 at YMML so now the aircraft lands right on the centerline and not to one side.The BGL airport files that I change and are the ones from MyTraffic X.Sitting on the runway Tuned 110.30 for 34R at UHPP, but the localiser is pointing way off to the left. Checked the Navdata arrival plate for the runway and indeed it was wrong. Now the aircraft tracks exactly the runway heading and lands smack on the center of the runway.I changed an ILS frequency at EIDW after the nav radio informed me, via a FMC message, while trying to tune to it during an approach that it was an invalid frequency. I moved the localizer to align with the runway centerline. An example of what I am talking about is Runway 16L at YSSY, the approach was always to the right of the runway and I always touched down on the grass on the righthand side. ![]() I do hope that you are checking the charts to make certain that there IS an error before making changes.What I usually do is check the chart but also I look where the localizer is by zooming in with google maps to check is actual position in the real world. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |