"Please call the tower..."

If it gets to a hearing, just look at the American flag in the room. If it has yellow fringe, then that's a military flag, and the court has no jurisdiction over you. All you have to do it point it out to the court and they will let you go.

http://www.ecclesia.org/truth/flags.html
 
Years ago Mary and I saw the aftermath of a Mooney driver landing on a taxiway at a resort in Wisconsin: The sheriff was administering a breath-a-lyzer test to the pilot when we arrived. ;)

This taxiway was narrow, and had a dogleg in it. Getting the Mooney down and stopped on that taxiway took superior piloting skills, even if his judgement was obviously impaired.

I found out later the guy was an original Tuskeegee airman. Obviously his stick and rudder skills were not diminished by age.
 
If it gets to a hearing, just look at the American flag in the room. If it has yellow fringe, then that's a military flag, and the court has no jurisdiction over you. All you have to do it point it out to the court and they will let you go.
I saw that episode of Law & Order, too -- IIRC, he got the death penalty for felony murder. Don't think it works any better in real life than it did on TV.
 
These are all nice points; they illustrate the capability to have the matter escalated uncontrollably. Being immediately responsive to the request is essential - delay puts it further out of your reach. The initial phone call should be adequately contrite and respectful of ATC's responsibility and role in maintaining a safe, orderly system. Don't volunteer too much information, but don't forget that facts are stubborn things -so don't be cute. Also, consider having a conversation face-to-face (as in visiting the tower cab, where you can - not likely at OAK). Mistakes and errors happen; it is important that we learn from them. ATC knows this, and they are generally desiring respectful consideration of themselves and their product. While the request "to call the tower" may smell like a reprimand, YOU are setting the tone for whatever happens next. Generally, ATC dislikes paperwork outside of their usual activity, and they conscientiously discharge matters in polite discourse. P*ssing contests are entered at your own peril; truthful humility goes a long way.
Well stated.

Having been asked to call the tower on at least 3 occasions I can think of, I completely agree with the above. Once I screwed up and was politely reprimanded. One time the controller called but I did not hear him (so I did not reply nor comply with altitude assigned) and when I didn't descend as instructed in his unanswered call he chastised me for not complying. One time I had a stuck throttle on approach in relatively low IMC and refused climb vector away from the field after informing tower of failure. In all cases, it ended with a polite discussion.
 
I saw that episode of Law & Order, too -- IIRC, he got the death penalty for felony murder. Don't think it works any better in real life than it did on TV.

That's just the TV execs in on the conspiracy to keep it secret. Just another disinformation campaign. Don't you believe it.
 
Listening through various LiveATC recordings marked as interesting, just for fun (I know, it's an illness), and one was a Piper pilot who landed on a taxiway at Oakland -- oops!

As you might imagine he got a phone number and was asked to call the tower when able, but that made me wonder, how does that call usually go and what happens after that, usually? I realized I have no idea how the process usually goes from there, if there even is a "usually."

Just curious how this works. :)

Most likely that ends with a 44709 ride. The phone call will start with asking you what happened. Everything after that will determine what happens next, but I'm betting there's a 709 ride at the end of this road.

Calling the tower itself can be a mixed bag. Once I was asked to call to clarify a local procedure that wasn't published yet. Not an issue, just some information to keep the neighbors quiet when I depart.
 
Last edited:
And I bet not.

Under the circumstances, maybe not.

The OAK north field is a huge mess of construction right now, with half the runways closed. And they happen to be the half of the runways ALWAYS used by transient GA aircraft.

Student pilots like 15/33 for the crosswinds, but no one else uses them. And it's very unpleasant if there is a game going on, 'cause it points near the Coliseum and its beehive of activity, barely a mile off the DER.

I don't think there are any games going on (except maybe the Warriors, but that's indoors), but it's real easy to just never even see that runway. No PAPI, it's behind a row of hangars, it's in a strange direction that seldom aligns with the wind or with standard approaches into the airport (one direction points at a mountain range, and the other points into Class B) and it's offset from the "main" north field And OAK strongly discourages GA from using 12/30 (though I think they'd cut a break if the 28s are closed).

I think there is going to be a real interesting ASRS coming from this one.

Now, unless it's an emergency, there is no need to land right now, so going around the pattern a few times to figure it out isn't unreasonable. Neither is circling over the Bay just outside Class B.
 
Last edited:
Really? Huh, what kind of answer to "Why?" would not call question to competence?

What are the other circumstances? Was this his first offense? Does his previous record show that perhaps there is a question of incompetence? Was there negligence involved? Was a loss of separation involved?

What does the EDP (enforcement decision process) call for?

Lots of variables here. Probably rises to remedial training or perhaps a SNAAP (Streamlined No Action and Administrative Action Process) with a warning letter.
 
You guys crack me up! ATC does NOT enforce the FARs! All we do is gather the information. It then goes to quality assurance, and then eventually to FSDO. They are the ones that decided your fate. Rotor & Wing is pretty much correct in the whole process...

As a FAA supervisor in Phoenix TRACON, I take these calls all the time. Most of the time, it's just a chat. Why did you turn the wrong way on the DP? Why did you descend early on the STAR? Are you aware you operated in Class B?

I can bet that 98% of these phone calls go very well. I'm ATC, but that doesn't give me the right to chew anybody out. I'm just gathering information, or trying to found out what went wrong so we can prevent them in the future. We also have pilots that call who didn't like their ATC service. It is my job to investigate and then coach and mentor my controllers if they did something wrong. Yes, controllers screw up too!!

For the other 2%, if they have previous background on you, your probably going to do a ride with the FAA. And then there was the poor gentleman last week who came busting through the VIP security TFR. This guy had no clue there was a TFR in effect. He's lucky he didn't get escorted by some F-16's! From what I hear, a security TFR is an automatic suspension.

So please, don't be afraid to make that call! We are not police or lawyers...
 
Even if it comes to a 709 ride, it's not a big deal. Costs half an hour in a plane.
 
Even if it comes to a 709 ride, it's not a big deal. Costs half an hour in a plane.
For the ride itself, perhaps, but most folks like to get some training from an instructor on the areas being examined so that half hour doesn't end badly. When I've been that instructor, I know the Inspector giving the ride checked the examinee's logbook to see whether or not he'd gotten such training, and complimented the examinee on choosing to get that training.
 
For the ride itself, perhaps, but most folks like to get some training from an instructor on the areas being examined so that half hour doesn't end badly. When I've been that instructor, I know the Inspector giving the ride checked the examinee's logbook to see whether or not he'd gotten such training, and complimented the examinee on choosing to get that training.

That would likely be required without the 709 anyway.
 
Maybe, maybe not. I've seen 709 rides go south.

Well, that's why they happen, isn't it? Once is an oops, screw it up on the ride as well... that's two strikes, isn't the system set up to try to make sure there isnt a third strike? If so then the system has worked either way.
 
I know you're a lawyer and I'm not, but I'm pretty darn sure your 5th Amendment right to refuse to answer on the grounds that it might tend to incriminate you still applies to an FAA enforcement proceeding. As I understand it, you can certainly refuse to answer an Inspector's questions.
The 5th A applies to FAA proceedings in the same way it applies to any civil or adminstrative proceeding - you can refuse to answer because the answer may incriminate you in a criminal proceeding, whether existing, pending or possible. But unlike criminal proceedings, generally speaking, there are legal consequences, the primary one being the "adverse inference" - the refusal to answer allows the fact-finder to infer that your answer, if truthful, would be bad for you.

There has been discussion that the adverse inference rule shoul be gotten rid of in administrative proceedings which tend to be at least quasi ("sort of") criminal. That has not happened wholesale on the federal level. In the case of the FAA and NTSB, there has generally been a policy to not require an answer, to not take advantage of the adverse inference rule and for the FAA to not call a pilot to the stand if the pilot doesn't want to testify. And the Pilots Bill of Rights specifically says no adverse inference may be drawn from refusal to answer a Letter of Investigation. But those are not required by the 5th A.
 
Hmmmm

Bugsmasher 1234, you asked me to give you a call, Yes, hmmm didn't know that, my name? Ummm Tim Winters
 
I've mentioned this before, but it's worth repeating for this thread:

Working a Pilot Deviation (PD) is one of the least favorite jobs an ASI has. Never, ever have I heard an ASI say "I sure hope I get some new PD's this week to work!"

They are tedious and in addition to his already planned workload, they are "on demand work", i.e. extra jobs to perform. And he gets nothing additional for having a bunch of PD files dumped on his desk with due dates. He would like to see these end quick and painless as much as you would.

With that being said, be polite and be accommodating. Whatever you do, don't motivate the ASI into taking something benign and turn it into an enforcement. Like I said before, a large number of these end informally with a bit of counseling and a better understanding of what went wrong and how to prevent another occurrence.

Just FYI.
 
The 5th A applies to FAA proceedings in the same way it applies to any civil or adminstrative proceeding - you can refuse to answer because the answer may incriminate you in a criminal proceeding, whether existing, pending or possible. But unlike criminal proceedings, generally speaking, there are legal consequences, the primary one being the "adverse inference" - the refusal to answer allows the fact-finder to infer that your answer, if truthful, would be bad for you.
So you do have the right to remain silent, but it's probably not smart. Thanks.

There has been discussion that the adverse inference rule shoul be gotten rid of in administrative proceedings which tend to be at least quasi ("sort of") criminal. That has not happened wholesale on the federal level. In the case of the FAA and NTSB, there has generally been a policy to not require an answer, to not take advantage of the adverse inference rule and for the FAA to not call a pilot to the stand if the pilot doesn't want to testify. And the Pilots Bill of Rights specifically says no adverse inference may be drawn from refusal to answer a Letter of Investigation. But those are not required by the 5th A.
Understood. But even if the PBOR says no adverse inference may be drawn in terms of an enforcement action, they can still treat your refusal to talk with them about it as not showing a positive attitude towards compliance, and that can turn an administrative action (like remedial training) into an enforcement action (like a suspension) even if they can't make any adverse inference from that silence during the actual enforcement action.
 
If it gets to a hearing, just look at the American flag in the room. If it has yellow fringe, then that's a military flag, and the court has no jurisdiction over you. All you have to do it point it out to the court and they will let you go.

http://www.ecclesia.org/truth/flags.html

attachment.php
 

Attachments

  • Frivolous Lawsuits.jpg
    Frivolous Lawsuits.jpg
    24.8 KB · Views: 336
As a FAA supervisor in Phoenix TRACON, I take these calls all the time. Most of the time, it's just a chat. Why did you turn the wrong way on the DP? Why did you descend early on the STAR? Are you aware you operated in Class B?

Here's an opportunity to clarify. I've had to call the tower once in S TX, and the only thing I heard after hello, and me identifying myself were questions.

Many of them started with 'Why...'.

Suppose I would like to answer those questions, but I feel that answering may indeed confirm guilt. In such case as there may be mitigating factors, I'd prefer to not answer directly. How about if most of the time my answers are 'let me get back to you on that specifically', or 'I can check and let you know once I've reviewed'.

Is this going to escalate things? I'm not in the habit of helping the gatherer of facts to determine my fate later on. The ATC folks aren't the cops, but they can take statements, which are all recorded, along with the tapes, and give them to someone who certainly can make a good case for enforcement.

BTW, I've landed and taken off on taxiways several times. Pretty much all you have to do is ask, and they will say no, or 'at pilots discretion....'. It's a regional thing, and completely dependent on the location.
 
The Oakland North Field is a moderately busy GA airport with not very many taxiways. I doubt it will be safe to land on a taxiway there at any time. During the day due to ground traffic (and now, due to construction equipment) and at night due to darkness.

While taxiing on Twys C, and D. I've often been asked to give way to opposite direction traffic also on C or D. I haven't gotten that instruction anywhere else. The taxiway was built for piston airliners, so there is plenty of room to fit one Cessna single on one side of the taxiway.

And I think the issue here is landing on a taxiway without clearance. That's a no-no at any towered airport.
 
Last edited:
Suppose I would like to answer those questions, but I feel that answering may indeed confirm guilt. In such case as there may be mitigating factors, I'd prefer to not answer directly. How about if most of the time my answers are 'let me get back to you on that specifically', or 'I can check and let you know once I've reviewed'.

I think it's a combination of "confirm guilt" and how reasonable your answers are. If they asked why you landed on a taxiway, if they were sitting in the tower when you did it, there's not really any doubt of "guilt"; they're just wondering why. And I don't know what you could "review" to get a clearer picture of that.

Similarly if you clip a Bravo, etc. etc. Don't worry about confirming guilt if they have you on radar and tracked you to the airport, or etc etc. Now if they call and ask "why did you land in that golf course" then I think "my engine was making strange noises, but I can't say for sure until it's test run" that's fine. But the NSTB will (probably?) be doing that, not you. (Unless there's no damage? Not sure how that would work.)

My completely uneducated rule of thumb would be: if you think what you did might land you in jail, get a lawyer before (as) you cooperate. If you're dealing with administrative law, answering factual-ish questions in an upfront way is going to not **** off the investigator, which will make a bigger difference than coming up with a clever theory about how you misheard a helo's instruction to land on a taxiway.
 
Suppose you get a request to call ATC and they accuse you of 'clipping the Bravo'. When you know, by every reasonable navigation facility at hand that it wasn't you, and they have confused with another aircraft(yes, it's happened).

So, the second thing they ask after your name and cert is 'why did you clip that Bravo?'

'Why whut? Well Mr controller, are you assuming facts not in evidence?' I don't doubt that a plane did clip the Bravo, but I also don't doubt for an instant that it wasn't me. So, going back to my question, suppose I say to them that I'll review your question as to me clipping the Bravo, I'll look at the track, I'll check my alt, I'll do a VOT check, I'll test my GPS with WAAS, I'll have my TXP tested, and let you know.

On the other hand, I could just say 'gee sorry, it won't happen again', and admit guilt where I may not be at fault and let the system start grinding, knowing that I just ADMITTED to clipping the Bravo. You can't be unpregnant, but you can get an abortion. Getting an abortion is very expensive, and like a statement admitting guilt, going back and proving the opposite is fraught with peril.
 
It's really one of those situations that parallels talking to the police about something that may or may not have been a crime. Whatever you say when you make that phone call can and will be used against you. On the flip side, just as with police, sometimes they will just let you go on your way if you are polite and cooperative. Quite a gamble, though.

Personally I'd call AOPA Legal Services first as I'm a member and that's what I am paying for. It's probably not a bad idea to make the call but you have to be guarded about admitting any fault. If the person starts out the conversation by yelling at you then you might want to be extra careful about saying anything further. If they cannot speak with you then they have nothing extra to add to a potential enforcement action. Whether or not that makes them extra "angry" and willing to file paperwork that they otherwise wouldn't bother with is anybody's guess. Technically you don't have to speak to anyone, including the FSDO, unless they actually go to enforcement and you have to appear. Again - talk to the lawyers.
 
Now if they call and ask "why did you land in that golf course" then I think "my engine was making strange noises, but I can't say for sure until it's test run" that's fine. But the NSTB will (probably?) be doing that, not you. (Unless there's no damage? Not sure how that would work.)
If you land on a golf course, the FAA will have someone from the FSDO looking into it unless you manage to remove the plane before anyone else knows it's there. Once the call goes out to police/fire (pretty much inevitable in such a case), the press will be on it, and then the FAA cannot avoid at least asking some questions.

My completely uneducated rule of thumb would be: if you think what you did might land you in jail, get a lawyer before (as) you cooperate. If you're dealing with administrative law, answering factual-ish questions in an upfront way is going to not **** off the investigator, which will make a bigger difference than coming up with a clever theory about how you misheard a helo's instruction to land on a taxiway.
That sounds very reasonable.
 
So you do have the right to remain silent, but it's probably not smart. Thanks.
No, if you had the right to remain silent, they couldn't use that silence against you. But you do have the right not to incriminate yourself in another proceeding, so you can't be compelled to testify.
 
No, if you had the right to remain silent, they couldn't use that silence against you. But you do have the right not to incriminate yourself in another proceeding, so you can't be compelled to testify.

This only applies to criminal proceedings though, yes? Administrative actions, which includes all the sanctions up through pulling your ticket, are a completely different story as I understand it, right?
 
See, this is the splitting of the hair that no one can/will answer. Pretty much the advise is to prostrate yourself on the FAA, be polite and apologetic and it'll all turn out as it turns out.

Not wanting to be confrontational, and letting the questioner know that I'm trying to help them do their job while retaining my claim of innocence is what I'm after. Anyone can tell the ATC person who requested a phone call to get stuffed, but of course, knowing human nature, they will take that position that the rights of the accused should be well exercised and forward that to those who's job it is to investigate further, and violate where they think appropriate.

Of course, it'll all be couched in the legalese and the defendants attitude will never be formally mentioned, but if you decide to stand on prinicpals and not admit anything, you are dickering with the very real probability that the FAA is going to make an example of you.

In the case I used, if one is accused of clipping the Bravo when no such action occurred, I want to know what magic words to say to the guy on the phone with all his 'why ........?' questions absent a direct admission of what I'm accused of. So, I guess since no has an answer, or they have it and aren't willing to share, I'm going to go with my original thesis and tell them I'll review what transpired, ask for the best info they have on the situation and get back to them with a definitive statement at a later time. While not actually mentioning the PBOR, I will certainly be thinking of the protections offered, limited though they may be.
 
:rolleyes2:

The number of holes in this little tale you could drive a truck through...:nonod:

Eh..the one time I was given a number and told to call ATC the guy absolutely lit me up and was quite rude. Told me the FSDO would be calling me in the morning. Of course, the morning was new years day, so that didn't happen.

However his supervisor did call me on new years day and was a very nice guy. I told him my side of the story. He told me the controller made a mistake, and that he was trashing the report. Never heard a word from the FSDO.
 
See, this is the splitting of the hair that no one can/will answer. Pretty much the advise is to prostrate yourself on the FAA, be polite and apologetic and it'll all turn out as it turns out.

Not wanting to be confrontational, and letting the questioner know that I'm trying to help them do their job while retaining my claim of innocence is what I'm after. Anyone can tell the ATC person who requested a phone call to get stuffed, but of course, knowing human nature, they will take that position that the rights of the accused should be well exercised and forward that to those who's job it is to investigate further, and violate where they think appropriate.

Of course, it'll all be couched in the legalese and the defendants attitude will never be formally mentioned, but if you decide to stand on prinicpals and not admit anything, you are dickering with the very real probability that the FAA is going to make an example of you.

In the case I used, if one is accused of clipping the Bravo when no such action occurred, I want to know what magic words to say to the guy on the phone with all his 'why ........?' questions absent a direct admission of what I'm accused of. So, I guess since no has an answer, or they have it and aren't willing to share, I'm going to go with my original thesis and tell them I'll review what transpired, ask for the best info they have on the situation and get back to them with a definitive statement at a later time. While not actually mentioning the PBOR, I will certainly be thinking of the protections offered, limited though they may be.

TBH, I think you're right. Most people here (me included) are answering this question on the presumption that both you and the controller know you did something wrong. Maybe not majorly wrong, etc. etc., but wrong.

I think the answer I'm (reading between the lines) presuming you'd give in the hypothetical bravo situation is reasonable:

"Why did you clip the bravo?"
"I'm pretty sure I didn't, but I'll check my GPS and get back to you."

That seems fine to me. A lawyer might say that it's somewhat incriminating, as if you did in fact clip the bravo, it reveals you weren't situationally aware enough to know it. But in my mind that goes in the category of "things I would be thinking about in the criminal world but not in the admin world". But there's nothing wrong with thinking about it in the admin world if that's your game. You're right; it's a balance of factors that might be different every time.

So yes, read my responses earlier as mostly assuming that both you and the controller know you've done wrong -- I don't think it generally helps to try to play the "well, can you prove it?" game. But if you really don't think you did something, I think "answering the question honestly" can be "I don't believe I did" and briefly mentioning why not.
 
If the call to the tower goes with the proper format, there should be no questions pertaining to your actions anyway. In the military we used a separate form than an 8020 but neither one states "ask the pilot why they did the PD." The only questions that are required to be asked are pilot's personal info. They should be informing you of the deviation and that they're submiting to the FSDO. ATC's job is to gather the facts (controller observations, radar tapes etc). The FSDO will be the one asking questions.

Keep in mind the violation resulted in a loss of runway sep, there's a good chance the controller is going to submit the PD. If it's a PD that triggers an automatic response (snitch patch) then it's out of their hands. "Sweet talking" them won't do you any good in that case.

From the first few seconds of the conversation you'll know if the controller is going to write you up or not. If not, be thankful and learn from the experience. If it's getting written up, doesn't matter what you say, they'll have multiple forms of evidence or witnesses supporting their position. In that case, fill out the ASRS. You can bet when controllers screw up they're filling out a form (ATSAP) to protect their butts as well.
 
Last edited:
TBH, I think you're right. Most people here (me included) are answering this question on the presumption that both you and the controller know you did something wrong. Maybe not majorly wrong, etc. etc., but wrong.

I think the answer I'm (reading between the lines) presuming you'd give in the hypothetical bravo situation is reasonable:

"Why did you clip the bravo?"
"I'm pretty sure I didn't, but I'll check my GPS and get back to you."

That seems fine to me. A lawyer might say that it's somewhat incriminating, as if you did in fact clip the bravo, it reveals you weren't situationally aware enough to know it. But in my mind that goes in the category of "things I would be thinking about in the criminal world but not in the admin world". But there's nothing wrong with thinking about it in the admin world if that's your game. You're right; it's a balance of factors that might be different every time.

So yes, read my responses earlier as mostly assuming that both you and the controller know you've done wrong -- I don't think it generally helps to try to play the "well, can you prove it?" game. But if you really don't think you did something, I think "answering the question honestly" can be "I don't believe I did" and briefly mentioning why not.

:sigh: Here's the thing, unless you have committed some egregious act, the maximum penalty is next to nothing, and you only end up with that if you are an *******. Basically you end up plea bargaining with someone who wants to close the file with the minimum hassle. If you cooperate and own up to your errors, they go away with a couple of hours training and you're done. Worst is you'll get a 709 ride which is yours to screw up. I can tell you from my experience, they are not trying to screw you on it, at least not if you're not an *******.
 
:sigh: Here's the thing, unless you have committed some egregious act, the maximum penalty is next to nothing, and you only end up with that if you are an *******. Basically you end up plea bargaining with someone who wants to close the file with the minimum hassle. If you cooperate and own up to your errors, they go away with a couple of hours training and you're done. Worst is you'll get a 709 ride which is yours to screw up. I can tell you from my experience, they are not trying to screw you on it, at least not if you're not an *******.

Unfortunately that hasn't exactly been my experience. EDP looks good on paper; never seen it implemented.

For example, a 50 year pilot who's flown himself for business and pleasure, holds an ATP, with a spotless flying record before and since, has a minor and at most technical infraction; cooperates completely with the FSDO investigation, and completes a flawless 709 ride.

Yeah, throw it in the hopper, let it sit for three years (post complaint to avoid the stale complaint rule), then dig up the festering case and proceed to enforcement. I'm hoping as least someone got his set of steak knives.
 
Back
Top