Just taking a short look at your last flight and my main suggestion is: You should make it easier for yourself until you are more familiar with PF3:
- Select a distinct callsign at first ... Sky Express 334, Sky Express 344, Sky Express 316, Sky Express 386, Sky Express 224, Sky Express 495, Sky Express 8403 ... at least I was confused
- Try using VCP mode 2 first, so you see what PF3 expects from you. And later run PF3_Displayer, so you see which hotkey sends what with the current ATC contact.
- You missed the first waypoint by 3.5 miles, but PF3 switched to the next waypoint as you got nearer to the second waypoint, so no problem here, but for your first tries you might want to disable SIDs (and not include them in your flight plan) so you get vectoring during departure.
- You did not get vectoring at the last waypoint because you were using a STAR, which basically says: I want to fly my approach, PF3 should not interfere with it:
Sky Express 334 at Delta Alpha Yankee November Echo Descend to 3 thousand 5 hundred Cleared to final for Sierra Tango Approach runway 6 Left at pilot's discretion Contact Tower on 118.62 when established. |
There is the possibility to mark waypoints as start and end of the STAR, then you will get vectors from the end of the STAR to the FAF, but I really suggest keeping that for later.
- When in contact with departure or approach, "request vectors" does not work (you received "unable at this time"). They will give you vectors (unless this is disabled by SID or STAR) on their own.
- You ignored multiple speed calls and e.g. stayed at 150 when approach instructed you to reduce to 120.
- After the runway change the STAR was disabled and PF3 gave you vectors, so you already see that it works, but since your last waypoint was too close to the airport (and you were too fast and you turned in the wrong direction at first), PF3 needed to vector you away from the airport to catch the FAF in a useful heading. At 11 miles from the airport it seems you had given up waiting on further vectors and turned on your own. PF3 did not complain here (this is a known bug Dave is looking into), but explains why you did not get further turning instructions. A real-world explanation could have been "he isn't following our instructions, so we vector anyone else away, let him do what he wants and call the authorities"
In this situation it might have been appropriate to declare an emergency due to pilot and ATC confusion
Regarding the handovers:
- The Denmark/Copenhagen control was not in the flight for which you uploaded logs, so I can't comment on that. But you can check the handover points after loading the flight plan in PF3. The directory PF3/Flight/FPP/ will then contain a file named "(yourflightplanname).json", which you can upload at
http://geojson.io/ to see center boundaries, waypoints and "X" markers for the handover waypoints.
- Handover to Approach will be better if do not include the STAR waypoints in your flight plan (and later: if you include them, declare to PF3 which waypoints are part of the STAR)