stract

umm, no.

you and LumberJack go skinny dipping together?

but yet you still screwed it up!

but I'm not saying the words, I'm saying "you saw fuh" the acronym. I went to "you saw fuh". Not "I went to the you saw fuh" There is a difference!

I'm not going to get into this conversation except to point out the extraneous use of the word "The." It's not "the USAFA". The only place "the" belongs is in front of Ohio State.

umm, Rucker dudes don't get FW anything in the drop, so not sure what you're thinking of.

I'm sorry, this is a little flawed, as not all 461 dudes were necessarily eligible for the bonus. Your bro would need to go look and see how many of the 461 met the eligibility requirements. As mentioned, prior E, prior service, other factors are in play here. Once your bro knows the true number of the 461 who met eligibility requirements, only then will we know what the true % takers was.

the trend I notice is that forums that have the word "login" in the redirect get blocked, and forums that don't, don't.

that was some entertaining coversation to say the least!

I already know of two times in recent past where a crew has PL'd b/c a backender saw daylight through a 308 beam crack. They've stiffened the beef-up plates enough that the new weak point is the engine bay. Both Patrick and Nellis have seen cracks there in the last year.

Only the login redirect is blocked, I can browse the site just fine as long as I don't try to log in. But not logging in is annoying, I can't navigate to the most recent posts, etc.

so, I used to not have a problem logging into the boards from work, but then we migrated to AFNET, and the redirect page when you hit submit to login gets blocked. In the past if they happened, I was usually able to just refresh the page and the login would have taken, but not anymore. Any idea how to login at work, or are we just SOL?

so, the med group here has a chiro on staff, and I see him every three weeks. Never had to get a referral from flight med, it's free, the guy is great, and I always feel great after. He can tell when I've been flying a lot, and especially a lot of NVGs. No bad stigmas at this base; I think the flight docs understand he's the reason so many rotorheads AREN'T DNIF.

interesting article about Microsoft and their rating system... https://money.cnn.com/2013/11/13/technology/enterprise/microsoft-stack-ranking/index.html?source=cnn_bin

well my squadron's motto is "We Come in the Dark"...

I'm on safari/ios7, and see green and red arrow buttons for voting...

When comments for MOFE are submitted, they are actually posted below the final message for a given mishap in AFSAS. Anyone can read those comments. One can also look at the access log to see that folks at AFSEC are in fact reading these comments as well. I can't speak to how much weight they give to unsolicited comments as I haven't sat through an actual MOFE, but I would think if the comments are intelligent and thought-provoking, they would be considered. I'll ask some folks I know at AFSEC about this.

there are some mishaps where I definitely get more from reading the final message than reading the final outbrief. Having been a part of two SIB outbriefs to COMACC, the SIB has to decide what from their report is absolutely necessary for the convening authority to know or understand, and some details, which may actually be quite useful to someone else, are left out of the brief. The briefing is great when it's time to brief it to everyone in the SQ, but any FSO worth their salt better understand they need to read the final message and be able to speak to the details. I've even called the pilot member or IO to clarify things prior to briefing the SQ if it's a SIB I wasn't a part of. I agree that photos and videos speak a thousand words...and it's also important to periodically revisit a mishap, so that the lessons learned continue to stay learned. Arbitrary requirements to not save a briefing to a drive, and delete it after a set period of time are ridiculous. The AFI guidance is to "delete when no longer required for mishap prevention purposes" but of course people will hoard things they're giving such limited access to, b/c they will ALWAYS be needed for mishap prevention purposes! I don't download and save final messages because I can readily access that information in AFSAS. If I could readily access the outbrief (Part 1A/B/C) and any re-creation as well, we wouldn't have these problems. Bringing a solution to the table: when the final message is released and after the AFSEC QC process is complete, Part 1 of te Tabs (where the outbrief is) should be automatically unlocked. If AFSEC or the Convening Authority is concerned about folks downloading things and saving them locally (even with password protection), then make it readily available so that folks don't feel the need to download and save a local copy.

especially when you only get tab access for a specified period of time (like 2 weeks or a month). I've been lucky recently getting my tab access requests granted...there's been a resent change in AFSEC/JA personnel, and the new individual seems to be a little more willing to understand and grant access. As a Chief of Flight Safety, I too will gladly let folks read through a final message from AFSAS. I'm not a fan of playing "I have a secret" when there is so much to learn from others mistakes. Just briefed the Kadena H-60 Class A to a room full of A-10 pilots and C-130 aircrew, and there were takeaways for all in attendance.

Other than a dislike for the forum symbols (quote cloud with quotes in it), everything looks great. Safari with iOS 7.0.3.

https://www.veterantributes.org/TributeDetail.php?recordID=19

SIB's out on the Moffett class A. Let's just say I'm not surprised with what the SIB found about that unit's culture. https://mountainview.patch.com/groups/police-and-fire/p/marijuana-cleanup-volunteer-falls-from-129th-rescue-wing-helicopter

Somehow I survived Whiting without fucking up the course rules...

You won't get that answer here. Go read the SIB, as was suggested above.