ATC Navigation protocol

[GridNorth]

I've submitted a flight plan and taken off following ATC instructions. I get to the point where ATC says "Resume own navigation" so I change to GPS but before I can get on track ATC issues another heading change. What is the right thing to do? Should this happen?

 

Alan

[mrzippy]

I would acknowledge ATC but then continue on with what you are doing and see how it goes from there.

[GridNorth]

I do, it just seems odd.

 

Al

[Rupert]

I've submitted a flight plan and taken off following ATC instructions. I get to the point where ATC says "Resume own navigation" so I change to GPS but before I can get on track ATC issues another heading change. What is the right thing to do? Should this happen?

 

Alan

 

I think "before I can get on track" is operative here. Apparently ATC assumes you're not following the GPS line close enough so it's trying to help you get lined up again. Similar to the occasional "please expedite your" request we all receive closer to arrival.

[noparts]

If you're using the GPS to get to your destination, why not just "Cancel IFR"? They won't bother you again; then when you get close enough, you can just contact the tower. If it's an airport you frequent, you will already know the best approach, etc... Personally, I have no patience for:

 

"..Contact Oakland Center on 121.675"

then in 10-15 seconds:

"..Contact Norcal Approach on 119.525"

about 20 seconds more:

"..Contact Oakland Center on 121.675"

 

Depending on the length of the flight, this just goes on and on! Finally, I have to cancel IFR, or throw my monitor out the window! A few times, I've not been familiar with the destination and had some slight problems; nothing major, though.

 

Rupert nailed it, though.

[kingnorris]

If you're using the GPS to get to your destination, why not just "Cancel IFR"? They won't bother you again; then when you get close enough, you can just contact the tower. If it's an airport you frequent, you will already know the best approach, etc... Personally, I have no patience for:

 

"..Contact Oakland Center on 121.675"

then in 10-15 seconds:

"..Contact Norcal Approach on 119.525"

about 20 seconds more:

"..Contact Oakland Center on 121.675"

 

Depending on the length of the flight, this just goes on and on! Finally, I have to cancel IFR, or throw my monitor out the window! A few times, I've not been familiar with the destination and had some slight problems; nothing major, though.

 

Rupert nailed it, though.

 

Or, you can acknowledge the request, but DON'T contact next controller. They still won't bother you. Then, about 90 miles out, contact the tower and follow descent instructions.

 

It's what I do if I want to speed up the sim,or just don't feel like being bothered, lol.

[theyorks]

I might be out on a limb here, but if you are using an FSX generated IFR

flightplan, ATC will always try to vector you along the Victor or Juliett airways, even if you selected Direct GPS. When you are told to Resume own navigation, leave the Nav Select switch in Nav mode.

Even so, the best advice is as above, acknowledge a controller handover, but do not change frequency until you are at TOD or closer.

 

 

Sent from my tablet thingy!

[eelb]

The native ATC in FSX has two issues. One, it was an overly simplistic system to begin with. Two, with the implementation of DP's and STARS with GPS based RNAV fixes in recent years, radar vectoring has been reduced to the point that the FSX method of controlling is increasingly becoming obsolete. With the F1 GTN-750, a little ATC knowledge, and the ability to read IFR charts and approach plates, one can do a better job being their own controller. Tower isn't much better. No sequencing, who ever reaches 5 miles out first, is cleared to land. Regardless of the relative speed of the traffic ahead or behind you. And my favorite, turning a 172 or Cherokee on downwind in front of you, when your inside the final approach fix in a jet. "Extend Downwind" isn't in FSX's book of phraseology.