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

Who's busted?



 
 
Thread Tools Display Modes
  #1  
Old March 20th 04, 06:04 PM
Steven P. McNicoll
external usenet poster
 
Posts: n/a
Default


"G.R. Patterson III" wrote in message
...

Can you tell me a little more about what that means? Does "or visual"
mean that adequate clearance exists when both planes have visual
contact and miss each other?


Only one aircraft has to sight the other one to use visual separation, the
other one just has to be informed that visual separation is being used.
There is no minimum distance in visual separation, it's whatever the pilot
is comfortable with.


  #2  
Old March 20th 04, 02:23 AM
Steven P. McNicoll
external usenet poster
 
Posts: n/a
Default


"Dan Luke" wrote in message
...

An aircraft departing a class D airport next to class C airspace
requests VFR flight following and is assigned a squawk code. The
aircraft is cleared for takeoff and instructed to fly runway heading at
or below 1,700. A few moments after takeoff, the pilot is instructed to
contact Approach but is unsuccessful after several attempts. The
aircraft nears clouds that extend well above and below its altitude and
will break VFR if it continues on its present heading. Still unable to
contact Approach, the pilot turns to maintain VFR and passes close to
an airliner inbound to the Class C airport, causing a loss of separation
incident. Who will suffer a violation, the pilot, the TRACON
controller, or both?


How do you know there was a loss of separation? If the VFR departure was
restricted to 1700 or lower, I'd expect the IFR arrival was restricted to
2200 or higher. Did the VFR departure bust his altitude restriction?

Controllers are aware that pilots are required to abide by applicable
regulations regardless of the application of any ATC procedure. The pilot
must do what's required to maintain VFR conditions even if it means acting
contrary to an ATC instruction. So if there's a loss of separation the
controller is going to get most of the blame.


  #3  
Old March 20th 04, 03:34 AM
Dan Luke
external usenet poster
 
Posts: n/a
Default


"Steven P. McNicoll" wrote:
How do you know there was a loss of separation? If the VFR
departure was restricted to 1700 or lower, I'd expect the IFR
arrival was restricted to 2200 or higher.


In this hypothetical incident, I'm assuming that the jet was cleared for
the ILS approach which prescribes an altitude of 1,800 until the FAF.
The VFR aircraft turned toward the ILS final approach course and passed
near enough to the IFR jet to cause the separation deal.

Did the VFR departure bust his altitude restriction?


No.

Controllers are aware that pilots are required to abide by
applicable regulations regardless of the application of any
ATC procedure. The pilot must do what's required to
maintain VFR conditions even if it means acting contrary
to an ATC instruction. So if there's a loss of separation the
controller is going to get most of the blame.


That's the answer I was looking for, thanks.
--
Dan
C172RG at BFM
(remove pants to reply by email)


  #4  
Old March 20th 04, 03:42 AM
Steven P. McNicoll
external usenet poster
 
Posts: n/a
Default


"Dan Luke" wrote in message
...

In this hypothetical incident, I'm assuming that the jet was cleared for
the ILS approach which prescribes an altitude of 1,800 until the FAF.
The VFR aircraft turned toward the ILS final approach course and
passed near enough to the IFR jet to cause the separation deal.


So what was the purpose of the 1700' altitude restriction then?


  #5  
Old March 20th 04, 03:58 AM
Dan Luke
external usenet poster
 
Posts: n/a
Default


"Steven P. McNicoll" wrote:
So what was the purpose of the 1700' altitude restriction then?


Damfino. It's what you get every time you depart BFM with flight
following.

This question came up because a friend of mine encountered this
situation with the exception of the separation incident. The TRACON
controller (very busy at the time) finally called him up and asked why
he was off his assigned heading. My friend explained, the controller
didn't seem too concerned and told my friend to maintain VFR and proceed
on course. We wondered what would have happened if my friend's
deviation had brought him too near an aircraft flying the ILS 14 into
MOB.
--
Dan
C172RG at BFM
(remove pants to reply by email)


  #6  
Old March 20th 04, 12:59 PM
Dan Luke
external usenet poster
 
Posts: n/a
Default


"Dan Luke" wrote:
too near an aircraft flying the ILS 14 into
MOB.


Oops. Should have said the ILS 32.


  #7  
Old March 20th 04, 01:15 PM
Steven P. McNicoll
external usenet poster
 
Posts: n/a
Default


"Dan Luke" wrote in message
...

Damfino. It's what you get every time you depart BFM with flight
following.


I'd wager the local MVA is 2200'.


  #8  
Old March 20th 04, 04:42 AM
Roy Smith
external usenet poster
 
Posts: n/a
Default

In article ,
"Dan Luke" wrote:

An aircraft departing a class D airport next to class C airspace
requests VFR flight following and is assigned a squawk code. The
aircraft is cleared for takeoff and instructed to fly runway heading at
or below 1,700. A few moments after takeoff, the pilot is instructed to
contact Approach but is unsuccessful after several attempts. The
aircraft nears clouds that extend well above and below its altitude and
will break VFR if it continues on its present heading. Still unable to
contact Approach, the pilot turns to maintain VFR and passes close to an
airliner inbound to the Class C airport, causing a loss of separation
incident. Who will suffer a violation, the pilot, the TRACON
controller, or both?


I certainly don't see anything that the pilot did contrary to FARs.
  #9  
Old March 20th 04, 12:24 PM
Dennis O'Connor
external usenet poster
 
Posts: n/a
Default

Yup, he did nothing wrong... I always return to tower frequency if I did not
get a reply within a reasonable time on any new frequency I am given...
Maybe the tower gave me the wrong frequency... Maybe ATC just had a
lightning strike... Who knows - but you do know who you just talked to and
he has telephone links, etc..

And, I suggest having all of the listed departure and approach frequencies
for that facility, scribbled on your knee board prior to take off, just in
case...

BTW, if the request was for VFR flight following, why was the pilot in the
soup at 1700 agl? rhetorical question
denny

"Roy Smith" wrote in message I certainly don't see
anything that the pilot did contrary to FARs.


  #10  
Old March 20th 04, 12:52 PM
Dan Luke
external usenet poster
 
Posts: n/a
Default


"Dennis O'Connor" wrote:
BTW, if the request was for VFR flight following, why was
the pilot in the soup at 1700 agl? rhetorical question


Well, I'll answer it anyway: It's pretty common down here on the bay for
aircraft departing the area to have to duck and dodge to maintain VFR.
--
Dan
C172RG at BFM
(remove pants to reply by email)



 




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
cleared, then busted virga Piloting 88 January 22nd 05 07:43 PM
Want KLN 88-90 Parts Unit -- Sell that busted unit Bill Hale Aviation Marketplace 0 June 16th 04 07:16 PM
Busted IFR Checkride Jon Kraus Instrument Flight Rules 77 May 4th 04 02:31 PM
rec.aviation.questions is busted Dan Jacobson General Aviation 2 November 18th 03 05:39 PM
Help - I busted into the Class B SEATAC airspace last night, does anyone have any advice ? steve mew Piloting 38 October 28th 03 06:08 PM


All times are GMT +1. The time now is 05:18 AM.


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