On Feb 21, 7:17*am, " wrote:
On Feb 20, 10:43*am, "Steven P. McNicoll"
wrote:

That's not "IFR to VFR-on-top then cancel", t

Your terminology flat out wrong...... *Based on the question you
asked, my scenario answered your question. *You said VFR ON TOP.


"IFR to VFR-on-top then cancel" is not my terminology, it's the OP's,
Myname. Your response did not answer the question I directed to him.



You can't be VFR on top WITHOUT an *IFR clearance. *VFR on TOP is IFR..


Correct.



Once you cancel IFR, you no longer are VFR on top. * So what you say
above is absolutely an impossible scenario.


And that's why I asked the question.



There is specific terminology for VFR traffic that you are not picking
up on and that is VFR OVER the top.


We're not talking about that.



That is build in for VFR. *VFR rules require contact with the ground
OR maintain 1000 feet above the cloud deck and fly VFR OVER the top
with your departure and destination being VFR for the flight to be
legal.

And even then you don't report to ATC that you are VFR over the top,
it's just simple flight following.


Flight following is not a requirement of VFR over-the-top operations.



In my answer to you, , I file IFR, fly through the cloud, get VFR on
top and cancel IFR. *Once I cancel IFR, I have the option of electing
flight following and maintaining VFR OVER the top. *In this case, you
could drop me for workload consideration.


But why request VFR-on-top if all you want to do is punch a cloud deck
and cancel upon reaching VFR conditions? Why ask for something you
don't intend to use?



You can't drop me if I am VFR ON TOP as I am IFR until I cancel.


Correct.