Thread
:
Silly controller
View Single Post
#
29
August 27th 06, 09:34 AM posted to rec.aviation.piloting,rec.aviation.ifr
Jim Macklin
external usenet poster
Posts: 2,070
Silly controller
And if you are not IR rated and current, they just put you
in violation of the FAR.
"Christopher C. Stacy" wrote in
message ...
|
(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.
Jim Macklin
View Public Profile
View message headers
Find all posts by Jim Macklin
Find all threads started by Jim Macklin