Xscaliber
Pre-takeoff checklist
I'm making a similar trip under the Tampa class bravo shelf at 1200' for the first time next Monday KBOW - KSPG
I think I'll be double checking my altimeter !
I think I'll be double checking my altimeter !
I don't like counting on a controller, or anyone for that matter, ignoring a policy .
Never said you should count on a controller to ignore a policy. You can expect them to comply with policy but plenty of times it's handled with a phone call. Like I said, who cares if you call? If there is fault and an ASRS is filed, you've already admitted it. If it's a radar issue, the tapes don't lie. If it's a runway environment issue, the tower has multiple witnesses and they have the comm tapes to prove their side. Call the tower, explain your case, file the ASRS and wait for the FSDO to give you a scolding. Maybe a letter of caution.
I'll give a perfect example of controllers being more than reasonable when it comes to reporting pilot errors. Earlier this year a friend of mine was working a helo doing closed pattern work. He noticed a pedestrian standing near the runway. He informed the helicopter and the student replied "that's my instructor." Apparently the instructor got out in the runway and walked over to the grass. The instructor then walked back on the runway and got into the helo and taxied into parking. My friend told the instructor to call tower. Even though it was a flat out PD, he just wanted to talk to the CFI and let him know you can't be walking around on the runway. The CFI was irate on the phone and asked "what is this? The rookie crew working today." He said he was going to call the airport manager. My friend, called the manager first and explained the situation. Airport manager said "write his a$$ up." My friend was going to handle it with a civil conversation but because the CFI chose not to, it ended up being a PD sent to the FSDO.
In the OP's case, they probably didn't even file a PD (8020.17). Most likely it started as a mandatory occurrance report. Barely even meets the need for that since no ATC or alternate air crew course of action was needed for the OP's transponder.
The ASRS is stripped of all identifying information, so it's irrelevant whether you admit fault or not, it can't be used in any enforcement proceeding. As has been pointed out, read any article written by an attorney on this subject (or talk to one). Most, if not all, recommend NOT making the call to the ATC facility.
Attorneys who don't understand the ATC system. Nothing in the phone call is meant to be incriminating. It's just to notify the pilot of the suspected error and to inform them how it's going to go from there. You can tell the controller that you do not wish to make a statement. There's a block on the form for that. you can even ask to talk on a non recorded line. We had both lines at my facility.
You don't make the call and I assure you, things will end up being worse for the pilot. FSDO gets word you are resisting or trying to hide when all the evidence is in ATC favor, look out.
Here's the problem: while it may not be "meant" to be incriminating, most people can't keep their mouths shut in those situations. They're almost always going to say something that incriminates them, just like when talking to the cops.
Further, and perhaps a bigger point, in some cases ATC may not actually know the identity of the pilot who was flying the plane. If you're not on an flight plan, all ATC has is a tail number. By making the call, you'll be providing evidence of your identity to ATC, either via caller ID, or by giving the controller your info. All that does is make it easier for the FSDO to move forward with an investigation or violation.
Your suggestion that refusing to call is "resisting" or trying to "hide" ignores the fact that there is -zero- obligation on the part of the pilot to call the facility. That's a very law-enforcement type attitude (where exercising your rights is seen as a bad thing, e.g., "why won't you let me search your car if you have nothing to hide?").
Here's the problem: while it may not be "meant" to be incriminating, most people can't keep their mouths shut in those situations. They're almost always going to say something that incriminates them, just like when talking to the cops.
Further, and perhaps a bigger point, in some cases ATC may not actually know the identity of the pilot who was flying the plane. If you're not on an flight plan, all ATC has is a tail number. By making the call, you'll be providing evidence of your identity to ATC, either via caller ID, or by giving the controller your info. All that does is make it easier for the FSDO to move forward with an investigation or violation.
Your suggestion that refusing to call is "resisting" or trying to "hide" ignores the fact that there is -zero- obligation on the part of the pilot to call the facility. That's a very law-enforcement type attitude (where exercising your rights is seen as a bad thing, e.g., "why won't you let me search your car if you have nothing to hide?").
There's a Stephen Pope how was the editor of Flying magazine, which is who I assume wrote that article, because I can't find an attorney in NJ with the same name. So again, we've got an aviation expert opinion on a legal issue. But you'll note that he says AOPA and ALPA give the same advice: call a lawyer, not the tower.
Is that what you do when you get pulled over for speeding? "Officer, please tell me the maximum fine and where to send it, and I'll have a check in the mail tomorrow." Certainly nothing wrong with that strategy if you're prepared to take the full force of possible punishment, irrespective of how unjust you think it might be under the circumstances. OTOH, if you've adopted that strategy because you think its likely to win you leniency or justice, that would be very foolish. Heck, for all you know, you might be thinking you got the number for something minor that you know you did, but the controller saw something else entirely, maybe something major. Or maybe he's just having a bad day and he going to make an example of you and **** you all the way to Washington.I guess there are two distinct plans of action here. Try and hide your identity or facts, or just own up to the mistake and take a scolding. I'm going with the later.
The irony is that you're the one who brought into this thread an example of a pilot making the call because he thought he'd done nothing wrong and getting ****ed by it. Sure, the same thing might have happened if he hadn't made the call, but maybe it wouldn't have. And it definitely wouldn't have been worse.The OP's situation is minor. Even if the MOR goes to the FSDO, he'll get nothing more than a talking to by the safety inspector to make sure the equipment problem is resolved. The MOR process that implemented years ago is just a data collecting system. It's a yawn for the FSDO. Far more worse things controllers and inspectors deal with than just a transponder issue. I probably had a dozen PDs as a controller and only wrote up one. Only reason why I wrote him up was it was military vs civilian.
Just own up to it and you'll either get completely off the hook or get a lesser punishment.
Edit: oh yeah, I have had a speeding ticket reduced drastically by pleading no contest in court also.
So again, we've got an aviation expert opinion on a legal issue. But you'll note that he says AOPA and ALPA give the same advice: call a lawyer, not the tower.
These two things are inconsistent. So you think other people should "own up to" their mistakes, but it's cool for you to plead "no contest" to a ticket? While "no contest" is effectively a guilty plea, why didn't you just plead guilty and pay the fine like a good, honest, moral citizen?
And don't assume that just because someone at an FBO says that approach wants you to call that you are the actual person they are asking for.I'm making a similar trip under the Tampa class bravo shelf at 1200' for the first time next Monday KBOW - KSPG
I think I'll be double checking my altimeter !