Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

The anal-retentiveness that is SMO

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
A Squared said:
True, but incomplete. You the controler, may still be responsible, in the sense that you may have to face the music within your own organization for not catching and correcting the readback. However, if the pilot reads back the clearence as he understood it (but incorrectly) and the controller dosen't catch and correct the mistake, and the pilot subsequently gets in trouble for following his mistaken understanding of the clearence, the pilot will still be held in violation of not complying with a clearence.

That's only if the facility management decided to persue both avenues together. (Controller error and pilot deviation) I can't recall where I've ever seen that happen. Not that it couldn't I suppose, if the error caused a really nasty incident. I'm not aware of any NTSB or Appeals Court finding where a pilot was held responsible for a readback that was received, but NOT corrected by the controller, are you? In any event, my reply was in direct response to the question;

I thought controllers were no longer responsible for erroneous pilot readbacks?

We are still responsible.
 
I'm sorry Sam, I never even heard of such an ATIS statement until just a few weeks ago. I don't know the answer. Where I work, if you want to do an abbreviated readback, that's fine, and I'll correct anything I hear that's questionable. If you want me to read the whole Route start to finish, and read the whole thing back, we do that to.
 
Why don't they just make a DP for SMO?

I used to fly there several times a week and can't say I miss the readback police, the noise nazis nor the parking at SuperMarine.;)
 
HMR said:
Why don't they just make a DP for SMO?

I used to fly there several times a week and can't say I miss the readback police, the noise nazis nor the parking at SuperMarine.;)
But at least they've got a pretty decent restraurant within walking distance.

Speaking of Noise Nazis, I just received a certified letter form the Orange County John Wayne noise nazis. It seems that I rang their bell the other night. If we rang it in an Astra, I wonder what the G-3 guys did that departed right after us?

'Sled
 
Vector4fun said:
That's only if the facility management decided to persue both avenues together. (Controller error and pilot deviation) I can't recall where I've ever seen that happen. Not that it couldn't I suppose, if the error caused a really nasty incident. I'm not aware of any NTSB or Appeals Court finding where a pilot was held responsible for a readback that was received, but NOT corrected by the controller, are you? In any event, my reply was in direct response to the question; We are still responsible.

My point was that neither English's comment :

I thought controllers were no longer responsible for erroneous pilot readbacks?
...nor your response:

If you read it back, and we hear it, then we're (ATC) still responsible.
.......is completely accurate. The truth, as usual lies somether inbetween.
In the other thread I posted a link with information on an FAA interpretaive ruling which is at the center of English's remark. The interpretive rule, which was published in the Federal Register makes it abundently clear that the pilot will still be held responsible even if he gives a full readback.

From the interperative Rule.

However, the simple act of giving a readback does not shift full responsibility to air traffic control and cannot insulate pilots from their primary responsibility under 14 CFR 91.123 and related regulations to listen attentively, to hear accurately, and to construe reasonably in the first
instance.

This interperative rule http://www.avweb.com/other/faa9914.pdf was issued as a result of the Merrell case and it was issued for the express purpose of reversing a trend in NTSB case law which tended to absolve the pilot if a readback was given.
Now I don't presume to know what will or will not happen to a controller in such an instance, I'll accept that they may be subject to some sort of sanction also. Your words seem to suggest that the controller bears *full* responsibility if a readback has been given, and that is patently untrue.
 
The reason for the "no delay", is they really do not want you to wait for the radial to center prior to turning to the assigned heading. This is for spacing with LAX departures. They also need you at about that radial for noise reasons prior to turning so they don't say intercept it. Basically if you can see outside, at aprox. the shore line, is where the radial comes into play and you turn.

I can not stand the noise nazi's of S. Cal though. It is rediculous. Get a life. Does 1db make a noticeable diff? Not to me. All these noise nazi's do is reduce a margin of safety to show on paper that they are responding to the local's complaints.
 

Latest resources

Back
Top