A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Piloting
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Silly controller



 
 
Thread Tools Display Modes
  #1  
Old August 27th 06, 10:09 PM posted to rec.aviation.piloting,rec.aviation.ifr
Christopher C. Stacy
external usenet poster
 
Posts: 43
Default Silly controller

Hamish Reid writes:
Since it was me you originally responded to, let's review the sequence
of events: I was on a pre-filed IFR clearance to Stockton (KSCK), went
missed on the ILS, went back to NorCal and cancelled IFR, requesting
multiple practice approaches. I got the standard "Maintain VFR..." at
that point, then did three practice approaches with NorCal


Oh, well I completely misunderstood your scenario! I thought you were
VFR, not an any IFR flight plan, asked for a "Practice Approach", were
never told "Maintain VFR", and then when you were done with those you
wanted to go home to a previously unannounced airport, were instructed
"report cancelling IFR".


  #2  
Old August 27th 06, 10:38 PM posted to rec.aviation.piloting,rec.aviation.ifr
Jose[_1_]
external usenet poster
 
Posts: 1,632
Default Silly controller

went back to NorCal and cancelled IFR, [...]
When I reported back on the [practice] missed at Tracy
and requested flight following back to Hayward (KHWD)
I was asked to cancel IFR.


Maybe they didn't receive your original cancellation. Either NorCal
didn't really cancel, or they didn't transmit the cancellation properly
(would Tracy have advance strips on you?)

Jose
--
The monkey turns the crank and thinks he's making the music.
for Email, make the obvious change in the address.
  #3  
Old August 27th 06, 11:58 AM posted to rec.aviation.piloting,rec.aviation.ifr
Steven P. McNicoll[_1_]
external usenet poster
 
Posts: 660
Default Silly controller


"Jim Macklin" wrote in message
news:POcIg.6099$SZ3.2344@dukeread04...

And if you are not IR rated and current, they just put you
in violation of the FAR.


Nope.


  #4  
Old August 27th 06, 04:57 PM posted to rec.aviation.piloting,rec.aviation.ifr
Newps
external usenet poster
 
Posts: 1,886
Default Silly controller



Jim Macklin wrote:

And if you are not IR rated and current, they just put you
in violation of the FAR.


He misunderstood, that's not what happens.

  #5  
Old August 27th 06, 09:36 AM posted to rec.aviation.piloting,rec.aviation.ifr
Christopher C. Stacy
external usenet poster
 
Posts: 43
Default Silly controller

(Christopher C. Stacy) writes:

(Christopher C. Stacy) writes:

"Robert M. Gary" writes:

Christopher C. Stacy wrote:
"Steven P. McNicoll" writes:

"Christopher C. Stacy" wrote in message
...

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


No. You're really IFR when you hear "Cleared to..."

Like in, "Cleared for the ILS runway 23 at Foobar maintain 2000 until established" ?
Or "Cleared to Land"

Word games aside, Steven is right. The difference between being IFR and
VFR in controlled airspace is being told "cleared to foobar".


The instruction "Cleared for the ILS runway 23 at Foobar maintain 2000 until established"
contains "cleared", a route (which is even a charted IFR procedure), an altitude,
and a clearance limit (landing Foobar airport, or executing the published missed
approach procedure). How is that not an IFR clearance?

I think it is, unless the controller adds the words "maintain VFR".
When I want a practice approach and the controller fails to say "VFR",
I add it back in to try and make sure, like:
"Cherokee 97R cleared for the ILS 29 maintain VFR".


I phoned Boston TRACON for their opinion, and the supervisor said that when
(for example) receiving multiple practice approaches in VFR conditions,
with the phraeology given above: unless the magic words "maintain VFR"
are in the instruction, you are in the system, receiving IFR separation,
and in the event of lost comm would be expected (in VFR conditions) to land.


I forgot to add to the scenario (and forgot to mention to the controller)
that the pilot was also given a transponder code (which I believe was the
case with the OP, and which is always my experience also). That's another
element that points to it being an IFR clearance. Probably everyone assumed
it anyway, even though of course you could also be assigned a squawk under VFR.
  #6  
Old August 27th 06, 12:01 PM posted to rec.aviation.piloting,rec.aviation.ifr
Steven P. McNicoll[_1_]
external usenet poster
 
Posts: 660
Default Silly controller


"Christopher C. Stacy" wrote in message
...

I forgot to add to the scenario (and forgot to mention to the controller)
that the pilot was also given a transponder code (which I believe was the
case with the OP, and which is always my experience also). That's another
element that points to it being an IFR clearance. Probably everyone
assumed
it anyway, even though of course you could also be assigned a squawk under
VFR.


You're contradicting yourself. If IFR and VFR aircraft are assigned beacon
codes, then being assigned a beacon code does not suggest it's an IFR
clearance.


  #7  
Old August 27th 06, 04:58 PM posted to rec.aviation.piloting,rec.aviation.ifr
Newps
external usenet poster
 
Posts: 1,886
Default Silly controller



Christopher C. Stacy wrote:



I forgot to add to the scenario (and forgot to mention to the controller)
that the pilot was also given a transponder code (which I believe was the
case with the OP, and which is always my experience also). That's another
element that points to it being an IFR clearance. Probably everyone assumed
it anyway, even though of course you could also be assigned a squawk under VFR.


Everybody gets a code to get service from the approach control. It
means nothing.
  #8  
Old August 27th 06, 11:58 AM posted to rec.aviation.piloting,rec.aviation.ifr
Steven P. McNicoll[_1_]
external usenet poster
 
Posts: 660
Default Silly controller


"Christopher C. Stacy" wrote in message
...

I phoned Boston TRACON for their opinion, and the supervisor said that
when
(for example) receiving multiple practice approaches in VFR conditions,
with the phraeology given above: unless the magic words "maintain VFR"
are in the instruction, you are in the system, receiving IFR separation,
and in the event of lost comm would be expected (in VFR conditions) to
land.


The phraseology given above would not make a VFR aircraft an IFR aircraft.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Air Force One Had to Intercept Some Inadvertent Flyers / How? Rick Umali Piloting 29 February 15th 06 04:40 AM
What was controller implying?? Bill J Instrument Flight Rules 65 September 28th 04 12:32 AM
Columns by a Canadian centre controller David Megginson Instrument Flight Rules 1 August 9th 04 10:05 PM
Skyguide traffic controller killed HECTOP Piloting 39 March 3rd 04 01:46 AM
AmeriFlight Crash C J Campbell Piloting 5 December 1st 03 02:13 PM


All times are GMT +1. The time now is 06:54 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.