AviationBanter - View Single Post

**Hamish Reid** · August 26th 06, 11:17 PM posted to rec.aviation.piloting,rec.aviation.ifr

In article ,
(Christopher C. Stacy) wrote:

Hamish Reid writes:
I had a similar experience Wednesday evening with the VOR/DME GPS A
practice approach into Tracy in good VMC. I explicitly asked for a
practice approach, negotiated with the controller for the missed, and
got switched to CTAF fairly early on. The approach went fairly normally,
then when I came back to him on the (new, improved) missed and asked for
flight following back to Hayward, he says "report cancelling IFR". I
thought maybe he'd confused us with someone else, so I repeated the
request, and got the same terse response. So I cancelled IFR, even
though it was a practice approach; there was no mode c code change or
any other change after cancelling IFR.

When he gave you the clearance for the approach, did he say
"Maintain VFR?" If not, you were really IFR.

Hmmm. That's not how I learned it...

And that makes
sense, since he subsequently asked you to report when you were
cancelling your IFR clearance.

But as explained in my first posting, I'd already cancelled my original
clearance some 30 minutes earlier; I was now doing a sequence of
practice approaches first at Stockton then into Tracy (something I've
done many times in the past year or two).

The above exchange sounds to me
like he gave you a new pop-up IFR clearance -- what you requested:
direct Hayward.

But I didn't request direct Hayward -- I requested (and got) the
practice VOR/DME GPS A approach into Tracy, and I was on the published
missed for that approach when I asked for VFR flight following back to
Hayward...

The part where you asked for "practice" and "flight
following" seems inconsistent with what he was saying back to you.
Are you sure it was the same guy who you started the approach with?

Not certain, but it sure sounded like him.

In any case, what both Robert and I noticed was that NorCal appears to
have either changed the SOP for practice approaches 'round here, or a
particular controller or sector was doing things differently, or maybe
it was just a bad day :-).

Hamish