Q1. How do you plan (a Nav Log) for this type of flight in light of ATC vectoring?
I’ve been flying a few short (0-30nm) IFR flights on FSX Demo. (FSX is way better than FS2004.) Compiling an accurate Nav Log is virtually impossible unless you know how ATC is going to vector you. Im assuming here that FSX approach is the same as real world approach. It seemed to me that they over do it even when I filed /G.
(Ex. flightaware.com/live/flight/N719 … /KPAE/KPWT
flightaware.com/live/flight/N719 … /KPWT/KPAE) But when I look at other tracks, it seems FSX does it just about right.
(Ex. flightaware.com/live/flight/N716 … /KBFI/KPAE
flightaware.com/live/flight/N716 … /KPAE/KBFI)
Does this have to do with the orientation of the runways? (i.e. If two runways are inline with each other (such as KPAE and KSEA), your approach will be more direct.)
Q2. Lieberma, I notice that your flights are pretty much direct. How come? Doesnt KJAN traffic interfere? Also, your track log usually ends at 2000 MSL. Is this because FlightAware cant track you or because you cancel IFR at DUHAB, AKALY, JAN, or some other place?