Hi guys, pretty new to this and trying to understand something. When I put in my flight plan and then load in the wrong leg of the flight is activated. What am I doing wrong?
Also, on the last image there’s a line I don’t understand. It’s not my flight plan or anything. What is it?
Seeing as I am not that much of an expert on this topic I was waiting for someone else to chime in with an explanation. But seeing as there has been no response yet I thought I would put up my 2c worth.
I think part of the problem is the short distance between your departure and destination airports. If you take a look at the Arrivals and Approaches for KSTS, this is what you see:
From this is is clear that O69 is closer to KSTS than the entry points for all the runway 32 Arrivals. In your case, what the MSFS flight planner did was to not use any Arrival and just use the the LUSEE approach. But it did indicate that you were supposed to use Vectors to Final - the “VTF- KSTS - ILS32” line in your flight plan. So your flight plan basically had a gap there that you had to fill with assumed vectors to final.
Now for an interesting quirk: I made up the basic flight plan in LittleNavMap with no Arrival and just the ILS32 Approach. Imported that into MSFS to see what the simulator did. As an alternative I also created your flight plan in the MSFS flight planner. In both cases the FP looked like this in the flight planner:
Now I cannot recall which was which, but in the one case it came up with a flight plan identical to yours in the aircraft and in the other case it came up with this:
So it decided to insert the SGD arrival!
Neither of the FP’s in the aircraft was ideal, so what I did is just to delete everything up to the LUSEE IAF and then inserted a “Direct to” leg from O69 to LUSEE. This is what that looked like:
Not sure what that little white “curved tail” is at LUSEE but it did not affect anything in the flight. On track after takeoff.
Just before LUSEE, still on GPS. Was quite the task to get to 3,000ft before LUSEE!
On the localiser & GS before I started slowing down.
Followed the ILS perfectly. On short final
Unfortunately I have no idea if what we see happening here is realistic for the real life system or not. But it does work if you do what it takes.
EDIT: Oops, I was mistaken. Still 1920 x 1080 And BTW: have they again reduced the image upload size? I used to be able to upload 1920 x 1080 images but these got downsized to 690 x 388, which is pretty silly.
Hi there, thank you so much for getting back to me. I apologize in my late response! I think your research on this was excellent and believe you might be spot on in that the proximity may trip up the load-in screen flight plan. I believe if I put it in the g1000 manually it would probably work perfectly, though I’m on xbox and that would be a terrible pain 
I am trying to understand one other aspect of this flight plan that I see in your screenshots too. Why does the plan not end at runway 32? it goes past it. Is that in case of an aborted landing?
Also, did you use ATC at all on your flight here? I kept waiting for their instructions but they never really directed me to the ILS.
Anyway, a lot for me to learn obviously. Thank you so much for enlightening me on your thoughts here. I really appreciate it.
You are very welcome: I was intrigued because it looked like an unusual and interesting situation.
It is normal for an approach to have a “missed approach” part. This is what you are seeing beyond the runway. This is what it looks like in LittleNavMap:
No, because I was just looking at the technicalities of the flight plan I did not bother with ATC. But it is generally accepted that ATC is quite deficient when it comes to vectors to final. I find it simpler to just enter a “Direct to” the point where I need to be and follow the flight plan.
