Accidentally Squawking a Code

C172capt

Filing Flight Plan
Joined
Jun 7, 2011
Messages
18
Location
Houston, TX
Display Name

Display name:
BonanzaPilot
Hey guys, I am a Private Pilot and today I was on a small VFR cross country flight. The plane had just come in and was squawking a code other than VFR. However, I did not realize this until I was about 10-15 miles from my destination. Is anything going to happen because of this stupid mistake like my license being revoked? Thanks.
 
Were you talking to anyone or flying through any airspace? Unless you were squawking 7700 or some other priority code, I highly doubt anything will happen. But, if you're concerned about it, you could always fill out and send in a NASA ASRS form. http://asrs.arc.nasa.gov/
 
Were you talking to anyone or flying through any airspace? Unless you were squawking 7700 or some other priority code, I highly doubt anything will happen. But, if you're concerned about it, you could always fill out and send in a NASA ASRS form. http://asrs.arc.nasa.gov/

I wasn't talking to anyone and was underneath the Class B for a small portion of the flight.
 
Short answer, no.

I have accidently squawked 7500, 7600, and 7700. The most that ever happened was Ground Control quiered if I was indeed being hijacked on the taxiway or that ATC asked if I wanted to declare an emergency after being cleared into Class B to land at a satellite airport. The latter occurred after a handoff and I was assigned a different beacon code.*

On purpose I have twice squawked 7700 and once 7600. In all cases everyone conducted themselves as expected. No aftermath, no letter to arrive in the mail.

*In reference to another, somewhat obscure thread, I have several times hear the term "beacon code" uttered by both ATC and pilots.

The above is based on my experience and anecdotal stories gotten from other pilots.
 
Short answer, no.

I have accidently squawked 7500, 7600, and 7700. The most that ever happened was Ground Control quiered if I was indeed being hijacked on the taxiway or that ATC asked if I wanted to declare an emergency after being cleared into Class B to land at a satellite airport. The latter occurred after a handoff and I was assigned a different beacon code.*

On purpose I have twice squawked 7700 and once 7600. In all cases everyone conducted themselves as expected. No aftermath, no letter to arrive in the mail.

*In reference to another, somewhat obscure thread, I have several times hear the term "beacon code" uttered by both ATC and pilots.

The above is based on my experience and anecdotal stories gotten from other pilots.

It's not uncommon at all for me to hear ATC use the term Beacon Code.
 
When selecting your assigned squawk, start with the from the right and work to the left when dialing in the code to avoid errant codes. This is for non digital units.
 
But, if you're concerned about it, you could always fill out and send in a NASA ASRS form. http://asrs.arc.nasa.gov/
I would suggest submitting an ASRS. One, it is collected in the files for statistical purposes. Two, it helps other pilots to identify probable errors. Three, it helps the submitter in understanding the system.
 
I was under the Class B for the first portion of the flight but I guess I won't worry about it. Thanks for the feedback guys.
 
I was under the Class B for the first portion of the flight but I guess I won't worry about it. Thanks for the feedback guys.
Yes, nothing to worry about but still I would suggest learning about the system is important. Committing to memory of the FAR/AIM is part, so is the NASA ASRS system, so is NTSB 830. Of course, understanding the NAS and being knowledgeable and proficient in flying IFR is important.

It is what it is, knowing these things makes a well rounded pilot.
I still suggest filing an ASRS form. Get on the e-mailing list of Callback.
 
...or 7500, although if they'd seen that, you'd know about it by now. Likewise, an inadvertent 1200 in the DC SFRA is also a big deal. Other than that...

Now wonder what kind of response 7500 in DC SFRA would result in... :eek:
 
Now wonder what kind of response 7500 in DC SFRA would result in... :eek:
Did you mispell? Or are you conjecturing what may happen in future tense?

I say it will be a shoot down or an intentional ramming. And I say it will be in error. Some stumblebum in a one fitty two will die. And hopefully the peasants and serfs will have had enough that at this point they will pick up arms to march upon the hill. (Cue Marie Antoinette)
 
Did you mispell? Or are you conjecturing what may happen in future tense?

I say it will be a shoot down or an intentional ramming. And I say it will be in error. Some stumblebum in a one fitty two from Smoketown will die.

Fixed that for you. Seems like they are the ones always in trouble down there.
 
Did you mispell? Or are you conjecturing what may happen in future tense?

I say it will be a shoot down or an intentional ramming. And I say it will be in error. Some stumblebum in a one fitty two will die. And hopefully the peasants and serfs will have had enough that at this point they will pick up arms to march upon the hill. (Cue Marie Antoinette)


I would think you want to blow it to tiny bits so it rains down gently... except the engines:eek: (cue Donny Darko:rofl:)

I don't think it's going to happen out of error except potentially a suicidal pilot goading a shoot. Personally if I wanted to go SFRA style I'd get cleared, close as I could then point at the White House full throttle and try to fly down a Phalanx.:D It would do 2 things, show that regardless the rules and security theater, a determined person will still get through, and that the defenses that were already in place pre 9/11 were really quite sufficient to handle any threat that the SFRA was likely to address, they just needed better thinking resources.
 
Last edited:
I would think you want to blow it to tiny bits so it rains down gently... except the engines:eek: (cue Donny Darko:rofl:)

I don't think it's going to happen out of error except potentially a suicidal pilot goading a shoot. Personally if I wanted to go SFRA style I'd get cleared, close as I could then point at the White House full throttle and try to fly down a Phalanx.:D It would do 2 things, show that regardless the rules and security theater, a determined person will still get through, and that the defenses that were already in place pre 9/11 were really quite sufficient to handle any threat that the SFRA was likely to address, they just needed better thinking resources.
Absolutely and wholeheartedly do I agree. This BS about the SFRA can be easily penetrated. It is a farce. It's worse than BS. F them on the hill, who do they think they are? As if all of a sudden the USA will tumble into zombieland if some GA plane (OMG...run around!!!) should overfly inside the beltway.

I still say...a 1,000 plane overfly of Wash DC. Big ramp up in publicity....let Pistole, Napiolitano, and all others spin it as they will. We're dying by a thousand cuts. In all of human history has man yearned to fly. And barely after 100 yrs of the achievement is the fed govt of the 'home of the brave' trying to quell the joyous freedom of flight.
 
Even if Andrews had flights angels 8 you might be able to make it to the reflecting pool in a light twin. But the noise would be hear 'round the world. A whole hunka love. Rally them troops, boys. The Library would take the hit.
 
I have a funny story about a transponder. I was ferrying an RV-9 from Washington state to NE. I was not talking to anyone squawking 1200. Obviously, several fuel stops and an over night. When I got home there was a note for me to call MN center asap. :eek:

Seems the transponder was malfunctining reporting 32,000' MSL. :yikes:

They had been tracking me for 2 days hoping I was not at 32,000' MSL going 185 MPH.

They just said please shut that damn thing off and get it fixed! :mad: I appoligized and explained the situation, that the plane was just annualed and the certificates were current, but the new owner would repair the defect.

Roger that. :redface:


To the OP, trust me, you are fine. Lesson learned.
 
Last edited:
snip..... Is anything going to happen because of this stupid mistake like my license being revoked? Thanks.

YES! You are never going to forget to check the transponder as part of your pre-takeoff checklist.

Your certificate is completely safe and you are a better pilot today.
 
Did you mispell? Or are you conjecturing what may happen in future tense?

I say it will be a shoot down or an intentional ramming. And I say it will be in error. Some stumblebum in a one fitty two will die. And hopefully the peasants and serfs will have had enough that at this point they will pick up arms to march upon the hill. (Cue Marie Antoinette)
Richard is quite wrong. What it will elicit is, initiallly, a query from ATC and then probably an escort away from the target area, followed by being met when you land -- assuming you do what you're told.

If, on the other hand, you ignore all calls, turn towards center of the FRZ and dive towards the White House, yes, you probably will get shot down as you get close to it.
 
Last edited:
I would suggest submitting an ASRS. One, it is collected in the files for statistical purposes. Two, it helps other pilots to identify probable errors. Three, it helps the submitter in understanding the system.
That's a good idea.

ASRS is not just a "avoid sanctions" system - it's there to track issues that wouldn't result in a violation, as well.

I've been digging through it as part of my research into cockpit technology, and it's been useful, as ASRS is where the accidents/incidents that DIDN'T occur get reported, such as:

"Scrolling out on the map, I saw that my destination was outside the ring indicating my reserve fuel. I stopped for fuel enroute."
 
How fun would it be to have an unarmed suicidal 'dog fight' with an f-16 over the White House? Could you imagine the conflagration you'd cause flying a good vertical routine over the Capital as they try to figure out just what the hell to do with you?:rofl::rofl::rofl:
 
Short answer, no.

On purpose I have twice squawked 7700 and once 7600. In all cases everyone conducted themselves as expected. No aftermath, no letter to arrive in the mail.

Why squawk 7700 and 7600 on purpose? Did you have a real emergency? Or were you "testing" the system? Do you also dial 911 occasionally to test it?
 
I have a funny story about a transponder. I was ferrying an RV-9 from Washington state to NE. I was not talking to anyone squawking 1200. Obviously, several fuel stops and an over night. When I got home there was a note for me to call MN center asap. :eek:

Seems the transponder was malfunctining reporting 32,000' MSL. :yikes:

They had been tracking me for 2 days hoping I was not at 32,000' MSL going 185 MPH.

They just said please shut that damn thing off and get it fixed! :mad: I appoligized and explained the situation, that the plane was just annualed and the certificates were current, but the new owner would repair the defect.

Roger that. :redface:


To the OP, trust me, you are fine. Lesson learned.
If you were squawking 1200, how were they able to track you down? I mean how did they know it was you? No tail number was attached to your radar image.
 
Mode S transponders report a N number regardless of code selected.

Technically, don't Mode S transponders report a hex code which is correlated to an N number, as the hex code is part of the registration of the aircraft? I know the callsign/Flight ID can be altered in Mode S, but didn't think that the actual N Number was reported, just a random permanent hex code.
 
Technically, don't Mode S transponders report a hex code which is correlated to an N number, as the hex code is part of the registration of the aircraft? I know the callsign/Flight ID can be altered in Mode S, but didn't think that the actual N Number was reported, just a random permanent hex code.

When I set up the Garmin 330 transponder in my last airplane I had to enter the N number into the settings page.

If the FAA has the hex code I'm sure they have the registration number also.
 
Technically, don't Mode S transponders report a hex code which is correlated to an N number, as the hex code is part of the registration of the aircraft? I know the callsign/Flight ID can be altered in Mode S, but didn't think that the actual N Number was reported, just a random permanent hex code.

Actually, they have both. First off, a mode S is also a mode A/C transponder so those replies (essentially either squawk or altitude) still get answered. In mode S mode, there's the 24 bit code (which is your "address" in the sky) which is allocated to your aircraft registration. It's transmitted on each message. It is used for selective calls.

In addition one of the long mode S messages have a eight character identifier which can be set in the case of airline operations tot he flight number and in the case of your operations to your n numbers.

In either case, I've never seen ATC make use of EITHER piece of information.

I forget to reset to 1200 all the time, it's rarely a problem unless you happen to catch the one place where there is a code has been allocated to another aircraft that has not yet come into radar contact (or otherwise just happens to be close enough to you to cause problems).
 
If you were squawking 1200, how were they able to track you down? I mean how did they know it was you? No tail number was attached to your radar image.
They don't need Mode S to track a 1200 code to destination and then correlate with arrivals, or back to point of departure to correlate with departures. And around the DC area, NORAD can do the same with raw radar (I.e., without any transponder at all).
 
Richard is quite wrong. What it will elicit is, initiallly, a query from ATC and then probably an escort away from the target area, followed by being met when you land...
Perhaps more precisely is that you disagree with my comments. Time will tell if they are wrong or not.
-- assuming you do what you're told.
Then you say this. And if the errant pilot does not comply, then what?

If...you probably will get shot down as you get close to it.
I suppose you mean I was wrong in that certain scenario but here.
 
Perhaps more precisely is that you disagree with my comments. Time will tell if they are wrong or not. Then you say this. And if the errant pilot does not comply, then what?

I suppose you mean I was wrong in that certain scenario but here.
Despite the doomsayers and alarmists, given the experience of the Smoketown Bandits, it's pretty clear what happens even if you fly directly into the middle of the FRZ without acting like a threat -- you get escorted out, directed to a place to land, and handcuffed, and then you get to kiss the concrete.
 
Back
Top