Isn't that what I was saying?
Just dropping off a controller's frequency and onto another is not an IFR procedure. If a pilot is concerned that it is time for handoff then by all means call the current controller and just ask when can we expect handoff to [name of next agency] it might annoy the controller but should get a response.
"So you've reached the point where you think you are just about out of range from your initial controller. You call to say that you're going to change en route."
If the pilot feels that radio contact has been lost as it has all gone quiet and nobody replies then that is what 121.5 is actually for. As you are in mandatory IFR airspace and you may be in conflict with other aircraft it would also be an idea to squawk 7600.
"In the case of 2, possible actions are;
w. Try in vain to establish comms with the initial controller
x. Do nothing and await a call on 121.5
y. Do nothing and expect an interception
z. Free call your next planned frequency"
To get out-of-range of a control frequency is quite difficult at high level unless you have flown a considerable distance and not bothered to maintain situational awareness, which appears to be the case with the BA aircraft in this post. All frequencies have multiple transmitter stations and can be expected to provide cover tens of miles beyond the sector boundaries.
"What I have said is that having a box failure and not knowing about until you are called on 121.5 or intercepted; is a different case to allowing yourself to run out of radio range of your current ATCU
The first is out of your control, the second, is simply poor airmanship."
I especially like IanW's latest;
Earlier he said;
"The frequency you have popped up on unannounced will try to work out what you are and who you are and why you are calling them and may have no idea where you should really go."
However in his latest post he tells us;
"You should also remember that there is a standard handover/assume procedure between all sectors. The receiving sector can see an aircraft coming toward the sector airspace with a datablock that tells the controller all the pertinent details about the flight. A sector controller will not sit there quiet while a flight under the control of the 'upstream' sector bores into the sector airspace. The controllers will be talking between each other about the flight trying to work out why it is not responding and being handed over."
So which is it? :roll eyes:
Don't forget, it is others that have said such classics as;
"There is simply no way to predict when you'll be out of range of your current frequency, or what the next one might be."
