Radar contact before squawk

"David Brooks" wrote in message
...

It's probably a good thing Bud Turner is no longer (a) at KNUW (b)
apparently online. He might have felt it his duty to go stop a practice
that
seems to work fine :-)


It'll work fine until the day an aircraft calls that isn't being painted and
there's one that is being painted but hasn't called. There's a reason it
isn't proper radar identification.

In article et, "Steven P.
McNicoll" writes:

It'll work fine until the day an aircraft calls that isn't being painted and
there's one that is being painted but hasn't called. There's a reason it
isn't proper radar identification.


It is my memory that about 30 years ago a number (like 25) people were drowned
in Lake Erie by this type mistake. The photo plane was in the right position
over land and the jump plane was over the lake (above cloud cover). Radar
advisory confused the two and told the jump plane he was in position. Don't
know, didn't they have transponders then?

Chuck

In article ,
(PaulaJay1) wrote:

In article et, "Steven P.
McNicoll" writes:

It'll work fine until the day an aircraft calls that isn't being painted and
there's one that is being painted but hasn't called. There's a reason it
isn't proper radar identification.


It is my memory that about 30 years ago a number (like 25) people were drowned
in Lake Erie by this type mistake. The photo plane was in the right position
over land and the jump plane was over the lake (above cloud cover). Radar
advisory confused the two and told the jump plane he was in position. Don't
know, didn't they have transponders then?

Chuck

Are you trying to tell me that a jump plane released jumpers out of
sight of land and with no navigation other than a radar controller
telling them where they were???

Also, 105.17*says, "No person may conduct a parachute operation [...]
(a) Into or through a cloud". Was that regulation (or something
similar) not in effect at that time?

"PaulaJay1" wrote in message
...

It is my memory that about 30 years ago a number (like 25) people
were drowned in Lake Erie by this type mistake. The photo plane
was in the right position over land and the jump plane was over the
lake (above cloud cover). Radar advisory confused the two and
told the jump plane he was in position. Don't know, didn't they
have transponders then?


They existed then, but they were less common.

Once when I was working graveyards, and off work but awake at night, I
made a night XC at about 4 am across the local Class B airspace. When I
landed, I shut down, refueled and when departing popped up with approach
for flight following. No sooner than I released the mic, he relied
Radar Contact, and gave me a squawk code.

Chances are, I was the only guy within 30 miles he was working.

Dave

David Brooks wrote:
I learned something Friday night while getting in some night solo time. I
called Whidbey Approach for a few minutes of flight following and possibly
clipping their Class C, and the controller annonced radar contact, and then
issued a squawk. I hadn't given my position (I wasn't too sure where I was
anyway :-) ). He apparently didn't find it necessary to talk to me after I
popped up with the discrete code.

I was probably the only VFR target in his entire airspace, so there was no
ambiguity. Still, question for the controllers, is it standard procedure to
announce radar contact to an untagged target?

-- David Brooks

I'm not a controller, so I can't speak intelligently on standard
procedure involving radar contact. I do however fly frequently at
night in and around Class B PIT airspace. I always use flight
following at night and can not recall any instance when I was "radar
contact" without first being assigned a code.

Rick

On Sun, 21 Mar 2004 20:56:36 -0800, "David Brooks"
wrote:

I learned something Friday night while getting in some night solo time. I
called Whidbey Approach for a few minutes of flight following and possibly
clipping their Class C, and the controller annonced radar contact, and then
issued a squawk. I hadn't given my position (I wasn't too sure where I was
anyway :-) ). He apparently didn't find it necessary to talk to me after I
popped up with the discrete code.

I was probably the only VFR target in his entire airspace, so there was no
ambiguity. Still, question for the controllers, is it standard procedure to
announce radar contact to an untagged target?

-- David Brooks




-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Next time you call up give your position relative to a published VFR
reporting point, one of them little purple flags on the sectional.
Those points are also on the radar scope.



Rick McPherson wrote:
I'm not a controller, so I can't speak intelligently on standard
procedure involving radar contact. I do however fly frequently at
night in and around Class B PIT airspace. I always use flight
following at night and can not recall any instance when I was "radar
contact" without first being assigned a code.

Thanks Newps, I usually report in relation to the nearest airport,
most often the one I just departed from. I'll keep the "flags" in mind
for future use.
On Wed, 24 Mar 2004 04:19:58 GMT, Newps wrote:

Next time you call up give your position relative to a published VFR
reporting point, one of them little purple flags on the sectional.
Those points are also on the radar scope.



Rick McPherson wrote:
I'm not a controller, so I can't speak intelligently on standard
procedure involving radar contact. I do however fly frequently at
night in and around Class B PIT airspace. I always use flight
following at night and can not recall any instance when I was "radar
contact" without first being assigned a code.



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----