>>208238

>>208306

There was a marked increase in helo activity in my region after trump won the election, (one even had an ARV Drive core strapped under it, which they can't transport by truck.) Lots of heloes over last week, and there have been a few peaks in traffic like this over the last few months, but no one else on the chans seems interested in reports that are made, of getting out of their basements to look into the skys to make their own reports. I wonder if other regions of the USA get the helo traffic that corresponds to 'chan happenings' or not, prolly never know because they don't show up on those sites.

They are heading between portland and the peninsula, NOT towards ft lewis. This is NOT NORMAL. Their are ZERO helos' stationed in portland, and when I was stationed their we never had helo's stop by casually. We only got to call them in a few times a year for training purposes. It costs to much money to keep a whirly bird in the air, this is what the cargo planes and trucks (and contractors) are for.

Also, their are lots of Apaches' & Kiowas in addition to the transports. I've seen black / stealth faceted / and massive electronic warfare pods on the guys buzzing neighborhoods.

Transponders are always off.

Never on the sites.

No one cares.

2T1x1 (Air Force Transportation) Anon

>>209224

I was cross trained into security (for norad) when they deployed all our reall security forces people overseas. It was litterly my job to shot anyone who crossed a red line without proper authorization.

>>209398

Military uses different date formats than civilians do.

27JAN18 27JAN

27/01/18 27/01

27-1-18 27-1

>>209451

Only in code, we never used those on forms or in practice. What I meant is that in the military we ALWAYS write dates using the day/month(/optional year) method. Always. This is so their is no confusion, the same way you always use 24 hour clock (besides some holdouts in guard units for local-only things). Can't believe I didn't notice those where dates before. So much of this looks obvious in hindsight but is hard to figure out real time.

>>209492

Gotta love those ancient IT systems designed to 'make things easier and more efficient' That you still have to do everything in paper in parallel in case the computers go out. Especially lovely is when the contractor who wrote the program didn't get the memo about what date format we use in the military, and we have to transpose the numbers all day long :p That kind of explains why the loaner guy we got from supply into trans never wanted to go back to his own shop, our hokey computer systems must have been more 'user friendly' in comparison to yours if you had to convert to julian for every entry!!

>>209551

That assumes the ancient dos program that you use which only runs on an old un networked XP box is hosted on a machine capable of running office (it often isn't), that you are authorized a license for office on that workstation (you are often not) and that the ancient dos based system is capable of importing or exporting the excel files (nope, out of luck here), or that there is source code or a contractor available to allow your IT guys to update the software to support that, (good luck on that) Their is a lot of filling out forms, typing them into computers, printing out reports, and then typing that into other programs and then printing out more logs from that to file away in cabinets. It's mostly all done manually, and its all done in digital & paper forms. So so tedious. Form Force. Glad I'm out.