AC560 said:
My understanding has always been that if you are filed VFR on top you are still on a IFR plan just operating at VFR altitudes and rules, thus I never understood the point to it was.
Wouldn't it just be simpler to file, climb up, and then cancel when VFR as opposed to being filed VFR on top (why cancel in the first place considering you get direct almost anywhere with a GPS now anyways)?
As mar said, it's a matter of flexibility. Most of the time under Part 121, you are required to be IFR, so cancelling is not an option, usually. One example. you are descending to a non-radar destination on a VFR day. Another IFR plane has already departed, headed toward you. ATC will assign altitude restrictions to both plans until passage is assured, usually by DME reports. Now, if you are cleared "vfr on top", you may descend at your discretion, and you are not given altitude restrictions which conflict with your plan for descending into the airport.
Another advantage is that under Part 121 (but interestingly, not under part 91 or 135) you may descend below the MEA on a "VFR on Top" clearence. AN example of where this is useful is coming into Anchorage eastbound on V319, the MEA is 12,000 until 50 west of ANC, even though the mountains are *well* behind you. (WEstbound you may cross 50 west of ANC at 8100 headed *toward* the mountains, but easbound away from the mountains, they keep you at 12K, go figure) Anyway, it's very difficult to lose 12,000 ft in 50 nm in hte DC-6 and still observe all your limitations and proper engine management, especially with a tailwind. However, if you're VFR on Top, you can start your descent from 12K much earlier, and make it easier on the engines.