Leaderboard

Plenty of people, I am sure. Nav Skool students, ABM's, non rates. Great way to come in and comment on a post that is five years old and show your ass. Wanna try again for a first post on the board? Edit: Now with more harsh words

Not all of us are wearing radiator wings, dude. I've never sat in an RSU. Know your audience, clown.

Valid and on to the next "funniest thing you've heard over the radio" so as to not derail another thread.

Anything out of Wizard's mouth (sts) is the funniest thing on the radio.

If you think Charleston is so awesome see It is all about what you want. I personally thought Mountain Home is the best gig in the Air Force, but I just loved the fact that I could hunt on 70% of the land in the state even though I lived in an apartment in town...but that is just me. Not to mention the possibilities for weekend ski trips was awesome..Sun Valley, Jackson Hole, Northern and Central Idaho, and Salt Lake all within roadtrip distance for a weekend.

Wow...really? No....really? That's good...the 60% solution after as long as portal has been around is certainly a desirable outcome. If I was only 60% of the way to wings after at least 2.5 years (when I remember doing the last portal migration) then I'm sure people would be defensive of my progress as well...at least I'm better than I was last year. I might actually start to believe you on this one if they didn't replace shit with more shit that actually runs worse than the shit it replaced... It costs $$$ to have a preload from the factory...money we don't have, so we pay people to spend their time installing it on this end which most likely ends up costing more than it would have been to order a preload or get a open source ghosting software. Again these decisions are being made by the same folks that are buying the shit computers in the first place...and another group of folks that decide that a 7/1500 support ratio is sufficient. So why are we so bad at doing it? Why are we still running a NetOS based on M*soft instead of a Linux distro (Really...it's just not that hard to learn, especially with KDE/Gnome/etc). You know how much f*ing money we'd save running OpenSource (or a secure internal branch thereof)? Initial learning curve might be a hurdle, but it'd be easily doable. We still run computers (including every laptop I've seen) with unencrypted hard drives when there's even opensource software for Windows that will provide a solution that would brickwall 99.9% of folks...unsat Maybe, but it wouldn't take us this long to defeat the threat...especially with COTS options that are already preconfigured to do what we need and it would be defeated offensively not by only sitting around for a year or longer shoring up our walls. So far the Air Force is doing Cyber wrong. They grabbed it as a mission because of the $$$'s associated with it, but it's gonna be a hard sale to convince people we should be in charge of our electronic battleground when we're largely stuck 3-5 years (or more) behind the standard...let alone running along the cutting edge.

i just want everyone to know that its called a CYBERSPACE BADGE not wings. so you all can get ur panties out of a bunch now.

I can't imagine how tough it must be for you to have to type those extra two characters and completely spell "your".

not really but i just find it hilarious how u guys are going bonkers over a badge that looks nothing like aero wings. if anything the space cadets should be the ones pissed bc it looks like their badge more than anything.

First: Each of the AWOs (WDs) listens to four external nets; more often than not they are not the same net and every bit of information which is transmitted to Wizard isn't shared among the controllers or the rest of the crew (I'm sure you can imagine the amount of information which comes across 13 different UHF let alone 2 satcom, 3 vhf, 3 hf, etc...) So when BoneXX radio checks AC-1 he may be talking to someone, potentially not a controller, who doesn't share that non-mission essential bit of information with the rest of the crew and our training supports that. Do we make sure that things like TICs, CSAR/SAR, tanker information is shared amongst the crew? Absolutely and our crew TTPs/contracts are set up to support that information flow. Imagine for a second that you, your copilot and your loadmaster (or engineer or other crew position XX) each listened to 4x different nets. Do you think all information passed among those 8-12 nets would get shared even with two-three crewmembers? If you're a single seat guy imagine if all of your wingman were listening to 3x different nets with a single common? Second: We're system limited as to the # of SIF we can load to have the computer display your callsign when it senses your unique SIF. I'm positive that every aircraft which takes off in the AOR uses their ATO assigned mission # and has a valid M4 (sarcasm) While M4 doesn't mean much in certain theaters it means quite a bit in others. While that comm interaction is commical, thereby meeting the intent of the thread, I'm sure that there is no way someone could have loaded the incorrect mode 2/3 or stepped to spare and didn't reset the modes (sarcasm) thereby increasing the chances that the AWO (WD) would think Bone XX is airborne when in fact it was Bone XY. Third: Wouldn't you rather have that comm instead of not having it and potentially swapping paint? Not likely but then again I'm positive that everyone, everywhere (sarcasm) is always on their ACO/ACP/SPINS/COF assigned altitude and in their corridor. I'd prefer the controller has the SA to not make that call in the first place but I'd rather that piece of extraneous SAFETY related comm instead of not having it. Waldo

wow, your description of RSU pattern trends was extremely enlightening. I'm sure everyone reading this board appreciates your expertise and is happy to take in this new information! I look forward to more posts that heighten this board's aviation knowledge. Seriously, how many people reading your stupid post haven't sat in an RSU? know your audience, clown.