September 25, 201213 yr Author Hi all, I found the cause of my problem: I did not clear all weather with my tutorial flight. Doing that put me down right on 16L. I was following Mike Ray suggestion to use saved situation file, so I did not notice the weather at all. Any how, thank you all for all the helps. Now I need to go find out how to account for wind on approach. If there is a general guide somewhere out there, please let me know. Thanks again. Vu Pham i7-13700K 5.2 GHz OC, 64 GB RAM, RTX5090, SSD for Sim, SSD for system. MSFS2020, XP-12, DCS
September 25, 201213 yr Not to be too pedantic but 16L/34R has been there for years, the new runway is 16R/34L. What was 16R/34L in the original FSX is now 16C/34C. regards, Joe You are correct and I was wrong. My apologies for misreading the OP's post. I was going to suggest a scenery conflict, but the OP seems to have solved the problem. Todd
September 25, 201213 yr Now I need to go find out how to account for wind on approach. If there is a general guide somewhere out there, please let me know. Normally the AP will compensate for a crosswind, up to a limit. If the wind exceeds its capability then you will have to manually fly the plane. Jay
September 25, 201213 yr Broken heading at KSEA could be down to your AI traffic package as the br2_ksea.bgl image that vonmar posted is part of mytraffic and the heading is way out as the stock fsx ksea and the orbx ksea both share a heading of 161 on the runway 16's. If you use MTX then you need to find the KSEA bgl and disable it or check the support forums to see if there is a fix. The heading shown in my screenshot is not (to the best of my knowledge) is not way off .... it is the TRUE heading .. not runway approach Magnetic heading. Here is a stock afcad from fs9.1 Best Regards, Vaughan Martell PP-ASEL KDTW
Create an account or sign in to comment