Go Back  Airline Pilot Central Forums > Pilot Lounge > Hangar Talk
FAA Suspends Second Controller In One Week >

FAA Suspends Second Controller In One Week

Search

Notices
Hangar Talk For non-aviation-related discussion and aviation threads that don't belong elsewhere

FAA Suspends Second Controller In One Week

Thread Tools
 
Search this Thread
 
Old 03-30-2011, 09:02 AM
  #21  
Gets Weekends Off
 
f16jetmech's Avatar
 
Joined APC: May 2010
Position: CFI
Posts: 413
Default

Originally Posted by Group W Bench
If they are VFR and the captain agrees to take a look, where is the violation of seperation? Doesnt seperation below RSVM in VFR the responsibility of the PIC even on an IFR flight plan? I dont get what the big deal is. And lets face it, there is no way that cirrus is going to move fast enough where SW wont be able to get out of the way.
First, I don't know what the SWA crew did or didn't agree to do, so it's too early to pass judgement on them

However, please don't tell me that you believe it's OK to perform a little unbriefed formation flight in dissimilar aircraft types when one of them has a cabin full of paying pasengers just because it's VFR, because that's just poor judgement and we've got plenty of ANG pilots who get paid to do it and have far more practice at it than you.

And if you don't like my opinion, you might take a peek at FAR 91.111 which specifically prohibits unbriefed form flight and further prohibits any type of formation flight with paying PAX onboard
Ok but what is formation flying? This could be debated
f16jetmech is offline  
Old 03-30-2011, 09:09 AM
  #22  
Gets Weekends Off
 
TonyWilliams's Avatar
 
Joined APC: Jan 2007
Position: Self employed
Posts: 3,048
Default

There's something missing in all this. I don't get the problem. This is NOT a formation with 1,000 feet ATC assigned separation.

First, this was NOT an air traffic controller, but a supervisor, just like in DCA last week. Yes, the agency actually has supervisors who were never controllers, or failed trainees, etc. They typically aren't checked out on all positions in a facility / radar facility area, and most definitely did NOT get to their lofty positions based on being a stellar air traffic controller.

Second, on the surface, I see no loss of separation, and actually I don't see a problem. There is something missing. Every day, aircraft pass each other at 1,000 feet ALL OVER THE WORLD, safely and legally. Having the crew ask to check on another aircraft, regardless of type, or how man pax on board, seems perfectly responsible and reasonable to me with 1,000 feet separation.

Third, it doesn't appear that the Cirrus was VFR. Also, wake turbulence shouldn't be an issue here.

Lastly, visual separation doesn't appear to have been used, or necessary. Also, visual separation is not applicable for enroute operations (not sure if this was terminal or enroute ops). ATC must have communication with both aircraft, or the ABILITY to communicate with both:

b. EN ROUTE. Visual separation may be used up
to but not including FL 180 when the following
conditions are met:
1. Direct communication is maintained with one
of the aircraft involved and there is an ability to
communicate with the other.


a. TERMINAL. Visual separation may be applied
between aircraft under the control of the same facility
within the terminal area up to but not including
FL180, provided:
1. Communication is maintained with at least
one of the aircraft involved or the capability to
communicate immediately as prescribed in
para3-9-3, Departure Control Instructions, subpara
a2 is available, and:
2. The aircraft are visually observed by the
tower and visual separation is maintained between
the aircraft by the tower. The tower shall not provide
visual separation between aircraft when wake
turbulence separation is required or when the lead
aircraft is a B757.
3. A pilot sees another aircraft and is instructed
to maintain visual separation from the aircraft as
follows:
(a) Tell the pilot about the other aircraft
including position, direction and, unless it is obvious,
the other aircraft's intention.
(b) Obtain acknowledgment from the pilot
that the other aircraft is in sight."
TonyWilliams is offline  
Old 03-30-2011, 09:20 AM
  #23  
Gets Weekends Off
 
TonyWilliams's Avatar
 
Joined APC: Jan 2007
Position: Self employed
Posts: 3,048
Default

Originally Posted by RU4692
Even if they were both under IFR flight plans, in VMC conditions the pilot can elect to maintain visual separation from traffic that waives the separation standards for IMC flight.

I think your wording needs a little clean up. The controller will ASSIGN visual separation when certain conditions are met.

The pilot may either comply, or like virtually any clearance, turn it down based on safety.
TonyWilliams is offline  
Old 03-30-2011, 09:36 AM
  #24  
Line Holder
 
mundo1's Avatar
 
Joined APC: Jul 2007
Posts: 64
Default

All technicalities aside, I think the biggest point is, as a pilot, why put yourself in a position you would have to explain later on? Sadly, we live in a litigious society where it pays to try to think like an attorney would – in what context are my actions going to be framed on?

Sometimes good intentions can come back and bite us in the butt. Be careful out there.
mundo1 is offline  
Old 03-30-2011, 09:55 AM
  #25  
Gets Weekends Off
 
DelDah Capt's Avatar
 
Joined APC: Feb 2008
Posts: 515
Default

As to the "definition" of Formation flying....you won't find one. As far as the FAA is concerned, it's contained in 91.111 where it says that no airplane shall fly close enough to another to create a 'hazard'. To me, that's a loose enough phrase for any FAA lawyer to drive a 737 through so I don't want to test the boundaries.

If ATC asks me to be a comms relay for a lost jet...hey, glad to help. If he asks me during the normal course of my route from departure to destination airport to look out the window for somebody, I'll do my darndest. The problem comes when he starts actively vectoring me or asking me to climb/descend for the sole purpose of getting me closer to another jet when I'm full of paying pax who didn't sign up for that. All the articles I've seen (including the FAA's own press release) say that there was a loss of normal separation standards. That to me says that either the controller purposely vectored/descended the 737 into a closer position for no other reason than a 'look see' or the 737 crew voluntarily maneuvered their jet towards another aircraft...either way it just doesn't pass the sniff test to me

But hey, last week I had no problem with the crews landing at DCA once they declared it an uncontrolled field and set up the approach that way. I guess that's what these boards are for, to debate different viewpoints of what we would have done from our comfy armchairs.
DelDah Capt is offline  
Old 03-30-2011, 10:26 AM
  #26  
Line Holder
 
Joined APC: Apr 2008
Position: Desk: Designing Instrument Approaches/Departures
Posts: 54
Default

I just read the article on CNN among other sources. At first I heard the controller was suspended...

After reading that the crew was suspended as well is just outrageous! In fact, it's infuriating.

This type of thing de-incentivizes moral behavior that can help save lives!

Controller, airline crew suspended over incident in Florida skies - CNN.com
clipperstall is offline  
Old 03-30-2011, 10:37 AM
  #27  
Gets Weekends Off
 
Joined APC: Dec 2007
Position: Window seat
Posts: 5,482
Default

It's hard to make an informed judgement if we don't know how close the aircraft came.

Now, how close are aircraft flying into SNA? Are they closer than the SW jet was to the Cirrus? If yes, is the FAA, and D.S. Babbitt, going to go back and take thousands of pilots, and controllers, licenses that have operated into SNA? How about parallel visuals? Is that seperation unsafe?

Let's find out what the seperation actually was.

How about the old STOL operations in DCA with Dash 7's?
What was that seperation????
Sliceback is offline  
Old 03-30-2011, 11:52 AM
  #28  
Gets Weekends Off
 
Joined APC: May 2010
Posts: 350
Default

Originally Posted by RU4692
I remember being in Atlanta's airspace on an arrival and there was a twin Cessna that had broken bravo and wasn't talking to anybody. The controller asked us to visually identify the aircraft, maintain separation while maintaining the integrity of the STAR, and to get the tail # if we could. Do you think it was unsafe for the controller to ask us to identify the make, model and tail number if we could?
It was not only unsafe, it was, at best, foolhardy. How close do you think you'd have to get to read the registration number?

Originally Posted by Sliceback
How about the old STOL operations in DCA with Dash 7's?
What was that seperation????
Makes me pine for the good old days! Which actually were quite good.
EasternATC is offline  
Old 03-30-2011, 01:03 PM
  #29  
Gets Weekends Off
 
TonyWilliams's Avatar
 
Joined APC: Jan 2007
Position: Self employed
Posts: 3,048
Default

Originally Posted by EasternATC

Makes me pine for the good old days! Which actually were quite good.

The good old days always seem to look better in retrospect. The last 4 years have had a single air carrier fatality. I think in terms of safety, these are the good old days.
TonyWilliams is offline  
Old 03-30-2011, 01:26 PM
  #30  
Portuguese Troubleshooter
 
ImEbee's Avatar
 
Joined APC: Aug 2007
Position: Burrito Bomber
Posts: 370
Default

The Southwest pilots reported seeing two people in the cockpit
I may not have eagle eyes but in order to see inside of a Cirrus I am going to need to be a lot closer than 1000 ft and I'm guessing inside of 1/4 mile. Forget that. Do you think they wrote on the back of the release "contact APP on 123.45" and put it up to the window?
ImEbee is offline  
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
palgia841
Regional
17
01-21-2011 04:37 PM
AUS_ATC
Major
14
03-09-2010 06:26 AM
N7225G
Hangar Talk
14
04-30-2007 12:32 PM
AUS_ATC
Major
8
04-26-2007 07:07 AM
CRM1337
Major
1
10-02-2005 07:12 AM

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

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Your Privacy Choices