damastas

If they are looking for entry level, try having them contact the veteran center on a college campus. There seems to be a much larger amount of veterans in engineering than any other major. They would be able to post job ads in the veteran center or pass information to relevant parties.

Just the other day when wx was bad we get the Intel slide listing the other assets that'll be up.. Or in this case wx canx. Without going into specifics, there were 4 planes up in the entire AOR. I'll let you guess which 4. One of the hearts of the problem is the ATO no matter what mentality. I thought we were past that.

I said the only a sensor part to express any lack of formal flying knowledge. Everything picked up was from observation and interphone. And maybe more suited for the safety thread but it's rather disturbing to me how active the MC-12 community tries not to talk about it. I'm already flying with pilots in a deployed location who have not even seen the SIB or AIB. Completely unsat.

Correct me if I'm wrong as I'm just a mere sensor, but isn't the max part of that mantra a big part of what caused issues for Indy08? From the AIB it sounded like max throttles increased left yaw after the autopilot was disengaged and that's what pushed it into a stall. That and the part where radar pinged them at 283 knots vertical. I ask this as a backender without any formal piloty knowledge, and it's almost a taboo subject to bring up at the squadron. Hopefully someone here can answer this.

There's some pretty big differences in the SIB vs AIB findings.

https://www.airforcetimes.com/article/20131025/NEWS/310250017/Stall-unrecoverable-spin-brought-down-MC-12-in-April

Beale Sensor here.. like KState_Poke22 said most of the sensors are burnt out from getting the shit deployed out of them. For a squadron that deploys at such a high tempo (sensor wise anyway.. I'm about to go on my fourth barely 1:1 dwell deployment in 3 years) there is a lot of queep at home station. Lot of it is self induced queep, a lot of it is lack of manning queep. Regardless for how much time we spend down range we spend way too much time doing stupid shit at home station. No word of the sensor becoming a CSO position (of course with all the AFSOC rumors, who knows. main rumor is AFSOC gets the planes and uses CSOs instead of enlisted sensors). Overall it's not a terrible gig. I don't regret volunteering for it and I don't regret volunteering to PCS. Hell of an experience, but personally I'm burnt out. I'll be punching when my contract is up along with a large portion of the other sensors hanging around.

"The uproar prompted Gen. John Allen, commander of NATO's International Security Assistance Force, to issue a directive "that all coalition forces in Afghanistan will complete training in the proper handling of religious materials no later than March 3," the NATO-led force said.." What a ######ing joke. This CBT better consist of "do you shit on the koran before or after lighting it on fire?" Get the ###### over it. You shoot rockets and take pot shots at us daily. Pretty sure you guys can go ###### yourselves as far as me giving two shits what you think. *This is probably not the politically correct response. ###### these people, and ###### this country.

Yeah, that's exactly how it went.

Pakistan stealing all our Rip-Its.

https://whois.arin.ne...234-216-0-1/pft Quick whois from ARIN shows that the physical address is in Atlanta and that the POC for whoever owns the network is in Arizona. Unfortunately you can't get much more information than that. If you had the date/time that whatever fraud was committed, the ISP could easily pull up their logs and see what physical location that IP address belongs to. But chances are, the ISP won't just hand you that info without a search warrant, and no law enforcement office is gonna bother getting a warrant for something that minor. Which really, even if they did, there are so many other variables - just because they find the physical location of that IP address and who it belongs to, doesn't mean that was the one who committed the crime. Could have had an open WiFi access point that anybody could have done it from, somebody could have proxied it through his computer.. just too many variables. EDIT: 1-480-212-1710 is the ISP's POC number, could always call them and see what they say. :P

Along the lines of these two reasons. Here is a serious question not meant in jest at any admin/support folks: Why do we have a career field for things like finance, admin jobs, services? Whatever happened to people in the military actually fighting in the war? I've been in a few squadrons where we "deployed" as a squadron - ie, we flew our aircraft there. We had our aircrew. We had ground maintenance. We had ground intel support. And there was no one else. We didn't take finance guys with us, we didn't take admin guys with us, we didn't take services guys with us. These are the "smoothest running" deployments I've been on. We bring our own stuff and support, and that's it, no extra bullshit. What says that it has to be a uniformed AF member doing my paperwork or finances at home station when they will NEVER EVER pick up a weapon and shoot it at bad guys(without it being a ILO or JET tasking). The biggest thing that gets me is that 90% of the people I meet are so far removed from the fight they couldn't even point to Bagram or Kandahar on a map. And then it's these same people that some how end up in charge and running the base, making everything as much of a pain in the ass as possible for people who actually do remotely do something useful.

One step forward, two steps back. Apparently every call I make from my phone in uniform is now going to be an "official" call. EDIT: Also, got a kick out of this one: