I have not been able to fly as much as I'd like this winter. A couple of nights ago, I looked online and saw VATSIM had center, approach, and tower for the Grand Forks, ND area. So I thought maybe I'd fly to Grand Forks.
I looked at the winds aloft, checked METARs, did some rough calculations, "filed a flight plan" (with VATSIM), and got my clearance.
Switched to CTAF, announced, got airborne, over to center, cleared to proceed on course (from initial heading of 360).
Requested VOR RWY 17R approach, cleared to cross the grand forks VOR at or above 2,400, and also cleared for the approach. I was ten miles out from the VOR.
http://www.aeronav.faa.gov/d-tpp/1301/05187V17R.PDF
Here is one of the cool parts of simming where you have "ATC": it makes you think about situations that you wouldn't normally think about just studying. Like that moment; when to descend. The VOR to 17R there says you can descend to 2,400 once past BLITS. I'm already cleared to cross the VOR (5 miles away from BLITS) at or above 2,400.
Do I start my descent before the VOR? How much more? What should my rate of descent be? If I'm leaving an assigned altitude when not on a published portion of the approach, I'll need to tell ATC.
"Fortunately", I was only cruising at 5,000 in a Cessna 182 RG. I could easily wait for BLITS, and lose the altitude down to 2,400 following the published approach. If I'm a minute out, then turn one minute, then back one minute, let's just say 2500/3 minutes = easy 850 fpm.
It's fun to hand fly the thing, and it's fun to figure these things out. There is no pause when online, you must keep "flying the plane" while figuring these things out.
Also, just doing things like timing at the FAF, dropping the gear, etc. Visibility was 3 miles in snow, it was hard to make out the runway at first. It's always fun when an approach goes well, even if it's "fake".
So anyway, blah blah blah... online flight simming has been really fun and thought-provoking for me. I'd rather be doing the real thing, but in its absence, this is fun.