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

PLEASE use your full call sign!!

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
Register   Log in
H

Hawkered

Well-known member
Joined
Sep 29, 2004
Posts
496
OPTIONS 913! You guys in that Legacy got everything screwed up the other day on New York departures out of Teterboro. We had an EXECJET 913 that took an altitude change for you that was corrected by another Netjets crew.

YOU ARE NOT "NINE THIRTEEN"! YOU are "OPTIONS 913".

For crying out loud guys, yuou have a company callsign-freakin' well use it!!
 
Any more details?

I'm curious how OPTIONS 913 caused EXECJET 913 to take their clearance? Granted, the FLOPS crew should use their full callsign, but how did that contribute to this incident? Am I missing something here?
 
Basil said:
I'm curious how OPTIONS 913 caused EXECJET 913 to take their clearance?
Click to expand...

That's easy. Because it's never EJA's fault. :D

hawkered said:
For crying out loud guys, yuou have a company callsign-freakin' well use it!!
Click to expand...

Options crews certainly don't have the market cornered on the use of non-standard phraseology. This is a good example of why we should all adhere to the AIM and pilot-controller glossary. But having a brain aneurysm while lashing out at the crew flying OPT913 that day probably isn't the most productive way to communicate your thoughts on the matter.
 
I could not agree more that you should use your full callsign, but I think I am missing something. How is its Options fault that NJA guy took the clearance?? Did the controller not use Options callsign? What am I missing?
 
Usually starts with the controller using the call sign, then crew reads back. If you answered someone elses clearence when the controller called, wouldn't that be your own fault. I wasn't there. Not passing blame. More details may be in order before an attack is made.
 
Hawkered said:
PLEASE USE YOUR FULL CALL SIGN!!
Click to expand...

Even simpler - if you fly a QS aircraft - don't let ATC sucker you into saying '6QS' or '7QS' - use all the digits. I can't tell you how many times there have been two QS planes on the same frequency that have the same 'final' digit!!
 
Hawkered said:
OPTIONS 913! You guys in that Legacy got everything screwed up the other day on New York departures out of Teterboro. . .
Click to expand...

When was this? OPT913 hasn't been to TEB at least since before the 25th according to Flight Aware.

And please enlighten us as to how Netjets A/C taking an Options clearance is the fault of the options pilots. . . there must be more to it ???
 
If a clearance was givin to Options 913 and the call back was just "913", then Exec Jet 913 actually flew to that altitude...it sounds like the Execjet screwed up and they were the ones who messed up the ATC communication. The other Execjet must have made a comment as to who that might have been for and that was how it was caught. To me, I think Options did nothing wrong based on the original post.
 
But really!!......... why Mr. HAWKERED can't give us a better explanation about this....???
Most people agreed here that this was NJ's fault.
Is there more to the story?? anyone??
 
Yep you guys are right! We are perfect!

Except for one thing...it was Options that took the read back for Netjets according to my F/O so I did screw that up!

Anyway nobody got into trouble and this has been another good company bashing thread brought to you by www.idontgivea********************.com
 
Yeah, my point exactly. Let's all spread the word...FULL company callsigns with all read backs!

Thanks to all!
 
dime line said:
I have never made any mistakes in my years of flying, I'm so darn perfect......


Get real.
Click to expand...

Wow I thought I was the only one!!..You're perfect to??..lol I guess someone pissed in someone else's cheerios this morning...I mean radio mistakes never happen!! whaaaa
 
Hawkered said:
Yep you guys are right! We are perfect!

Except for one thing...it was Options that took the read back for Netjets according to my F/O so I did screw that up!

Anyway nobody got into trouble and this has been another good company bashing thread brought to you by www.idontgivea********************.com
Click to expand...

Look at what you wrote in the OP, and maybe you will understand why everyone thought something different, than what apparently happened here. . . and while we are at it, although everyone should read back their full call sign, the real problem was that they answered the wrong call. Can you honestly say that you have never done that? I say, quit whining and get over yourself.
 
Last edited:
Hawkered said:
Yeah, my point exactly. Let's all spread the word...FULL company callsigns with all read backs!

Thanks to all!
Click to expand...

Hawkered, You need a vacation..

I had one of your guys do the same thing to us (options) out of MMU. I caught it and told departure of the error and everything was fine. I agree we should all use our full call signs, however getting on here and slamming another crew is not cool.
 
Agreed! Good job in Morristown by the way!
 
It's a big sky out there... but sometimes we share close quarters.

Use the full callsign guys... regardless of who did who.

Next time it could have been an airliner and a biz jet, or a airliner on airliner, or a bizjet bizjet again.

Colliding metal is loud. Cut back on noise pollution.
 
FLYLOW22 said:
It's a big sky out there... but sometimes we share close quarters.

Use the full callsign guys... regardless of who did who.

Next time it could have been an airliner and a biz jet, or a airliner on airliner, or a bizjet bizjet again.

Colliding metal is loud. Cut back on noise pollution.
Click to expand...

yeah, you guys have seen the signs.....Fly Quiet!
 
Tango

WE LOVE OURS HERE AT FLEX-JET ON 135 LEGS TANGO...NOVEMBER ..XXX FOX X-RAY......NOT EVEN THE CONTROLLERS CAN SAY IT RIGTH SOMETIMES.

The "Tango" requirement for 135 was dropped several years ago. I was trying to find it for someone awhile back. Try finding something that is not there any more in the FARs .. will make you crazy.
 
old*art said:
WE LOVE OURS HERE AT FLEX-JET ON 135 LEGS TANGO...NOVEMBER ..XXX FOX X-RAY......NOT EVEN THE CONTROLLERS CAN SAY IT RIGTH SOMETIMES.

The "Tango" requirement for 135 was dropped several years ago. I was trying to find it for someone awhile back. Try finding something that is not there any more in the FARs .. will make you crazy.
Click to expand...

Still listed in the Feb 2008 AIM under "Aircraft call signs". I don't believe it has ever been a FAR requirement.

​

"Air Taxi or other commercial operators not having FAA authorized call signs should prefix their normal identification with the phonetic word “Tango.

EXAMPLE Tango Aztec Two Four Six Four Alpha."​
 

Share this page

Latest posts

Latest resources

Latest media

Carbon Cub FX-3 Shenandoah Valley
Carbon Cub at Kittyhawk
FX-3 in the backcountry
IFR Panel in a Carbon Cub FX-3
Cub-Provo-UT-c.jpg
Back
Top Bottom