Wing callsigns

Started by Senior, January 14, 2008, 04:24:09 AM

0 Members and 1 Guest are viewing this topic.

_

Quote from: ZigZag911 on January 14, 2008, 09:40:03 PM
Jersey was "Zigzag" for land, "Domino" for mobile.

Changed to "Red Dragon" in the 90s in honor of our long time wing CC
mid 50s to early 70s), Col. Nanette Sears, AKA "The Dragon Lady" (which was the name of a character in the aviation related comic strip 'Terry & the Pirates')
I never heard that story.  I had always thought it was because of the Jersey Dragon aka the Jersey Devil.

RiverAux

I'd hate to lose CAP Flight for our planes.  Assuming that we would still retain our own special moniker and not return to using plane N numbers, I wonder what it might be?  Aux Flight? 

ZigZag911

Quote from: Bayhawk21 on January 14, 2008, 09:49:38 PM
Quote from: ZigZag911 on January 14, 2008, 09:40:03 PM
Jersey was "Zigzag" for land, "Domino" for mobile.

Changed to "Red Dragon" in the 90s in honor of our long time wing CC
mid 50s to early 70s), Col. Nanette Sears, AKA "The Dragon Lady" (which was the name of a character in the aviation related comic strip 'Terry & the Pirates')
I never heard that story.  I had always thought it was because of the Jersey Dragon aka the Jersey Devil.

Nope, although a lot of people, even NJ members, think that's so, I think mostly because of the hockey team!

SDF_Specialist

I've been trying so hard to not get involved in this conversation because of OPSEC, but I can't resist a good Comm topic. When I was a cadet (2001-2003) Ohio was Red Thunder. When I came back as an Officer in 2005, it was Columbus. I've asked several people as to why the switch, but I can never get the same story, so I just don't worry about it. RedFire11, I believe I've heard you on the nets a couple times. I have to get back on HF.
SDF_Specialist

W3ZR

OPSEC is indeed serious business, but I can't
let a good picture go to waste.



Move along, there is nothing for you to see here.
Robert Montgomery, soon to be former Captain, CAP

SarDragon

#25
Quote from: Bayhawk21 on January 14, 2008, 09:49:38 PM
Quote from: ZigZag911 on January 14, 2008, 09:40:03 PM
Jersey was "Zigzag" for land, "Domino" for mobile.

Changed to "Red Dragon" in the 90s in honor of our long time wing CC
mid 50s to early 70s), Col. Nanette Sears, AKA "The Dragon Lady" (which was the name of a character in the aviation related comic strip 'Terry & the Pirates')
I never heard that story.  I had always thought it was because of the Jersey Dragon aka the Jersey Devil.

Totally true. Col. Spears was CC WIWAC, '64 - '69 timeframe. There's also a patch commemorationg her:



Could somebody sizeify this, please? (And then PM me the code so i can lose it again?)

EDIT: IMG size - TA
Dave Bowles
Maj, CAP
AT1, USN Retired
50 Year Member
Mitchell Award (unnumbered)
C/WO, CAP, Ret

♠SARKID♠

Okay, Recruiter brought it up and I've been in the same boat.  Isn't this some bad opsec here?  Maybe its not in the secured section of the NTC site, but it's still bad juju in my book.  This is also coming from someone who got home from a mission today, checked his email, and in his google blog alerts for CAP found a link to a forum thread where our day's mission was being listened to and periodically posted about (crews, locations, sitreps ((though false)), freqs, etc)

mikeylikey

Reading these posts, OPSEC has not been violated.  I don't think anyone released current call-signs did they?  Call signs from 10 years ago, before the move to OPSEC are all public knowledge. 

PLUS...... perhaps you should take up the mission release with the person in charge of the mission.  I would suspect that the poster was in fact someone taking part in that mission.  That would be a violation of Cap's OPSEC.

Anyway, I have a security clearance on file with CAP, so I can read whatever you fools put out on this forum.  And I Herby grant Secret Security Clearances to everyone reading this so that we can continue to violate some OPSEC rules that no one even has any idea how to relate too.

Seriously talk about OPSEC.......why don't we get better Security Awareness training.  Instead of watching a 5 minute video and taking a crappy on-line test, we should have to sit through the AF 2 hour class.  Then we all will be like "OMG, I don't want to violate OPSEC or I will have to sit through that class again"

And on, and on, and on, and on.............
What's up monkeys?

Ricochet13

Quote from: mikeylikey on January 16, 2008, 07:43:35 AM

Seriously talk about OPSEC.......why don't we get better Security Awareness training.  Instead of watching a 5 minute video and taking a crappy on-line test, we should have to sit through the AF 2 hour class.  Then we all will be like "OMG, I don't want to violate OPSEC or I will have to sit through that class again"


How about putting something together and recommending it?  Would be nice to see something generated by one who is in the "trenches".  Might end up with a Security Awareness process that would be an improvement. 

Nick

#29
Or, CAP could just go to "<Insert State Here> CAP" callsigns like half the country already is.

I would like to put in a reminder about OPSEC real quick.  OPSEC is "a process for identifying, controlling, and protecting generally unclassified information which, if it becomes known to a competitor or adversary, could be used to our disadvantage."

I can't imagine how the disclosure of a callsign would place CAP to a disadvantage, since there is (as we all know) no rhyme or reason from one wing to the next in how callsigns are assigned.  Frequencies?  Sure, I can understand that ... given the right transmit and tone settings, someone could maliciously interfere with our communications (why someone would want to, I'm not quite sure).  But I don't quite get the callsign deal.
Nicholas McLarty, Lt Col, CAP
Texas Wing Staff Guy
National Cadet Team Guy Emeritus

flyguy06

I was a cadet in the 80's and 90's GAWG's callsign was Redstar. From what I understand they changed because some of them(like Redstar) were real USAF callsigns and to avoid confusion Iguess they changed them all.

ZigZag911

Odds are a given CAP radio station (assuming the 'bad guys ' have the frequencies, or have a scanner) will be VHF.

This of course means line of sight range, enhanced somewhat by repeaters.

The likelihood then, is that it's range will be limited to the geographical confines of the home wing, possibly spilling over into adjacent wings.

The 'bad guys' probably already know what state (i.e., wing!) they are listening in, so it really does not seem like an OPSEC situation.

Gunner C

Back in the 60s when I was a cadet in AKWG:

Mukluk = Mobile Station
Sourdough = Ground Station
Aurora = Airborne Station

GC

SDF_Specialist

Quote from: ♠SARKID♠ on January 16, 2008, 06:48:23 AM
Okay, Recruiter brought it up and I've been in the same boat.  Isn't this some bad opsec here?  Maybe its not in the secured section of the NTC site, but it's still bad juju in my book.  This is also coming from someone who got home from a mission today, checked his email, and in his google blog alerts for CAP found a link to a forum thread where our day's mission was being listened to and periodically posted about (crews, locations, sitreps ((though false)), freqs, etc)

Gotta love those hams who have/can find the frequencies. This is a major reason as to why you shouldn't give your location. Turkal, have you ever been on a team that works from laptops to relay information, or are you in one of those ares of WIWG that has a mountain in front of you, a mountain behind you, and hills everywhere else?
SDF_Specialist

♠SARKID♠

^We don't relay from laptop to laptop.  No satellite connection if thats what you mean.

SDF_Specialist

Something like that. I mean from laptop to Mission Base. Doing this would dramatically cut down on radio transmissions, and keep a lot more sensitive material out of the eyes of those who don't need it
SDF_Specialist

♠SARKID♠

Negative.  We don't have the capability.

SDF_Specialist

That sucks. From your posts, you sound as though you go on your fair share of missions. I was have someone from your unit talk to WIWG Logistics, or the Communications guy, and see about getting a laptop for such purpose.
SDF_Specialist

Frenchie

Quote from: Hartley on January 14, 2008, 06:28:34 PM
The "CAPFlight" callsign is registered with the FAA, not DoD, though it is listed with DoD as well - and I doubt it will be changing anytime soon.

Actually it already has.  CAPFlight is actually no longer a valid callsign for CAP as far as the FAA is concerned.  Every FAA authorized callsign is assigned a 3 letter identifier.  CAP's used to be CPF.  This 3 letter identifier has now been assigned to a private company in the Ukraine.
http://en.wikipedia.org/wiki/Airline_codes-All

I'm not entirely sure how this happened.  My guess is there may have been a merging of ICAO and US callsigns at some point and CAP lost theirs.  I found an old listing from a couple of years ago which showed CPF still belonged to CAP.

The only valid FAA authorized CAP callsign is BXR "Box Kar" which is assigned to the South Carolina Wing.

Our local ATC still allows us to use CAPFlight, but technically this is not legal per the FAA.

FW

Old PAWG callsigns:  
Land: Keystone (Keystone State)
Mobile: Rollingstone (Local Beer)
Air:  Flightstone (just to keep it uniform)

Things changed about 10 years ago because CAP changed from FCC rules to NTIA rules for reasons I have no idea why.  Hence, the mass changing of call signs, the development of "tactical" call signs and the use of "CAP Flight".  

BTW, to my knowledge the prefix "CPF" is still allowed by all ATC's.  At least no one has bothered me about it.