service terminated squawk 1200

Stubby wrote:

Suppose you have to do a missed approach or just go around. What does
the controller want to see you as? You "own" the runway until you
terminate the code,

Ah, what? The code has nothing to do regarding VFR/IFR. A controller
does not gain the ability to use VFR separation standards on an IFR
aircraft because he told him to squawk VFR, such as going into an
uncontrolled field.

Robert M. Gary wrote:
I'm curious how important it really is to punch in 1200 as soon as the
controller instructs squawk 1200 as you approach for landing at an
uncontrolled field.

Just one opinion: I was taught Aviate, Navigate, Communicate (in that
order). Transponder is just a communication, if I felt (as pilot in
command) that squawking VFR while entering the pattern to land would
reduce safety, then I wouldn't do it. I think it'd be important to
switch it before flying again, but I doubt a controller would be that
agitated if you kept it for a minute longer.

I'm also curious to hear what a controller has to say about this.

Ben Hallert
PP-ASEL

If you are close to the airport and busy during the approach don't
worry about changing the squawk code and turn it off once on the
ground...
If you are not busy during the approach, dial in 1200 as convenient..
The controller will not care as you are in the airport traffic area and
no longer his problem...
denny

the digital "push button" VFR code makes it so much easier
BT

"Denny" wrote in message
oups.com...

If you are close to the airport and busy during the approach don't
worry about changing the squawk code and turn it off once on the
ground...
If you are not busy during the approach, dial in 1200 as convenient..
The controller will not care as you are in the airport traffic area and
no longer his problem...
denny

"Robert M. Gary" wrote in message
oups.com...
I'm curious how important it really is to punch in 1200 as soon as the
controller instructs squawk 1200 as you approach for landing at an
uncontrolled field. I've always blown it off and just landed with my
original code. My thinking is 1) Of the things I need to do to
configure for landing, watch for traffic, get the plane slowed down,
etc this is way, way down on my important to-do list 2) What the heck
can ATC care anyway, are they going to reuse that code in the next 2
minutes 3) If something did happen to me, maybe they'd have a better
radar track if I'm still on the old code??

Im just curious from controllers how important is this change in code
before landing.

-Robert, CFI


Robert,

If you don't go 1200 for some time and they really want you to they will
tell you so! I understand about some times being to busy with other things
that are going on that prohibit the task of squawking 1200 for a few min.
The new digital transponders with the one touch VFR button is awesome.

NW_PILOT wrote:

If you don't go 1200 for some time and they really want you to they will
tell you so!

How will ATC tell you since presumably, ATC also turned you over to another
frequency along with the transponder code change?


--
Peter

"Robert M. Gary" wrote in message
oups.com...

I'm curious how important it really is to punch in 1200 as soon as the
controller instructs squawk 1200 as you approach for landing at an
uncontrolled field. I've always blown it off and just landed with my
original code. My thinking is 1) Of the things I need to do to
configure for landing, watch for traffic, get the plane slowed down,
etc this is way, way down on my important to-do list 2) What the heck
can ATC care anyway, are they going to reuse that code in the next 2
minutes 3) If something did happen to me, maybe they'd have a better
radar track if I'm still on the old code??

Im just curious from controllers how important is this change in code
before landing.


Remaining on the discrete code for a few minutes is unlikely to cause any
problems.

Robert M. Gary wrote:
I'm curious how important it really is to punch in 1200 as soon as the
controller instructs squawk 1200 as you approach for landing at an
uncontrolled field.

Aviate, navigate, communicate. Your squawk code comes under
communicate. It shouldn't be a big deal to reset the code to 1200,
but certainly, if you're busy with other tasks, that's pretty low on
the priority list.

Most of the time, when the controller turns you loose, you're about to
drop below radar coverage anyway, so it's a moot point.

Not important at all.



Robert M. Gary wrote:
I'm curious how important it really is to punch in 1200 as soon as the
controller instructs squawk 1200 as you approach for landing at an
uncontrolled field. I've always blown it off and just landed with my
original code. My thinking is 1) Of the things I need to do to
configure for landing, watch for traffic, get the plane slowed down,
etc this is way, way down on my important to-do list 2) What the heck
can ATC care anyway, are they going to reuse that code in the next 2
minutes 3) If something did happen to me, maybe they'd have a better
radar track if I'm still on the old code??

Im just curious from controllers how important is this change in code
before landing.

-Robert, CFI

"Robert M. Gary" wrote in message
oups.com...
I'm curious how important it really is to punch in 1200 as soon as the
controller instructs squawk 1200 as you approach for landing at an
uncontrolled field.

As others have said, if changing the transponder code is at all a problem
with respect to the safety of the flight, don't do it.

It may or may not cause problems for ATC. More likely not, but even if it
does, that's their problem. They should have given you the transponder code
change earlier, when you aren't so busy with your landing prep (I can only
imagine changing the code being a problem on short final...otherwise,
there's plenty of "downtime" during the traffic pattern and approach to do
it).

Pete