If you knowingly release a flight that doesn't comply with CAP regs, or has other safety issues you ignore, maybe.
Quote from: RiverAux on December 29, 2017, 06:46:24 PMQuoteHaving experienced the growth of administrative requirements placed on the people who actually are trying to execute the missions of CAP, I wonder what sort of data or analysis is driving this growth.Jeez, just recently learned that now even the production of annual histories is a requirement. I'm all about history, but making this a requirement in an organization that just barely has enough active people to conduct an operation in the first place is just nuts. Can you cite that?
QuoteHaving experienced the growth of administrative requirements placed on the people who actually are trying to execute the missions of CAP, I wonder what sort of data or analysis is driving this growth.Jeez, just recently learned that now even the production of annual histories is a requirement. I'm all about history, but making this a requirement in an organization that just barely has enough active people to conduct an operation in the first place is just nuts.
Having experienced the growth of administrative requirements placed on the people who actually are trying to execute the missions of CAP, I wonder what sort of data or analysis is driving this growth.
Email from Region Commander. Haven't bothered to look it up.
Quote from: RiverAux on December 30, 2017, 07:04:23 PMEmail from Region Commander. Haven't bothered to look it up. Sounds like a holiday wish - I couldn't find anything in the regs on it.
I've been involved in enough SAREXs and other situations to know that FROs typically operate differently when releasing pilots they do not know. Pilots in their Squadron that they fly with often, they know how they operate. At a SAREX, you may be releasing a pilot you've never heard of that just joined last year.Some of the things in the Checklist mentioned above seem redundant. Projected TO times and other info has already been entered into WMIRS. No need to have discussions with the pilot getting him to verbally repeat the WMIRS info.Occupants in the plane is all in WMIRS. Why rehash it?How long does the pilot intend to fly? Already in WMIRS.Mission and Sortie numbers ... WMIRS already enters that in the email sent to the FRO.A two minute phone call or text (yes, text) usually suffices for every flight I've ever flown as a MP.
Quote from: etodd on December 29, 2017, 10:49:31 PMI've been involved in enough SAREXs and other situations to know that FROs typically operate differently when releasing pilots they do not know. Pilots in their Squadron that they fly with often, they know how they operate. At a SAREX, you may be releasing a pilot you've never heard of that just joined last year.Some of the things in the Checklist mentioned above seem redundant. Projected TO times and other info has already been entered into WMIRS. No need to have discussions with the pilot getting him to verbally repeat the WMIRS info.Occupants in the plane is all in WMIRS. Why rehash it?How long does the pilot intend to fly? Already in WMIRS.Mission and Sortie numbers ... WMIRS already enters that in the email sent to the FRO.A two minute phone call or text (yes, text) usually suffices for every flight I've ever flown as a MP.It's been a very long time since I've seen so many red flags in one post.
I've been involved in enough SAREXs and other situations to know that FROs typically operate differently when releasing pilots they do not know. Pilots in their Squadron that they fly with often, they know how they operate. At a SAREX, you may be releasing a pilot you've never heard of that just joined last year.Some of the things in the Checklist mentioned above seem redundant. Projected TO times and other info has already been entered into WMIRS. No need to have discussions with the pilot getting him to verbally repeat the WMIRS info...
It was a "GOB" who likely released the pilot who was congested when he happily logged "over an hour of IMC" enroute to a sarex a few years ago, and another "GOB" who released another pilot so sick he couldn't go to work the next day a year or two after. IOW, FROs should certainly trust, but they should verify --- each time. It's the prudent thing to do. And it's, IMHO, what's expected of FROs.
In addition to the duties listed in CAPR 20-1, region and wing historians shall:a. Prepare region and wing histories on a calendar year basis.
Quote from: Eclipse on December 30, 2017, 07:21:21 PMQuote from: RiverAux on December 30, 2017, 07:04:23 PMEmail from Region Commander. Haven't bothered to look it up. Sounds like a holiday wish - I couldn't find anything in the regs on it.CAPR 210-1(6) QuoteIn addition to the duties listed in CAPR 20-1, region and wing historians shall:a. Prepare region and wing histories on a calendar year basis.
Yep. If a MP fills out the ORM saying he is good to go, and then tells the FRO he is healthy, because he wants to fly, even though he has the flu ... all the FRO can do is trust the pilot at his word. No way to 'verify'.
Quote from: etodd on December 31, 2017, 12:11:39 AMYep. If a MP fills out the ORM saying he is good to go, and then tells the FRO he is healthy, because he wants to fly, even though he has the flu ... all the FRO can do is trust the pilot at his word. No way to 'verify'.For the unaware FRO taking a MP's (or any other pilot) at face value is sometimes what can be done. However the regs require a telephone contact and I understand that to mean voice, not text or social media. A lot of information is conveyed by voice when an FRO listens to more than just words... like fatigue, congestion, stress, etc. offers an opportunity for responsible FRO feedback & mentoring. Also, that long known principle of management & leadership should apply: "Once fooled, shame on you! Twice fooled, shame on ME!" A sick, fatigued, stressed, etc pilot who is later discovered to have exercised either bad judgement through a flawed self assessment of IMSAFE compliance and/or a lapse in integrity by untruthful responses to the FRO should be a candidate for accountability.
Texts do have their good side. You can save them by doing a screen shot. I'd rather have a screen shot of the text then to rely on memory.Stops the "He said - she said" arguments too!
Quote from: RiverAux on December 31, 2017, 08:21:29 AMQuote from: Eclipse on December 30, 2017, 07:21:21 PMQuote from: RiverAux on December 30, 2017, 07:04:23 PMEmail from Region Commander. Haven't bothered to look it up. Sounds like a holiday wish - I couldn't find anything in the regs on it.CAPR 210-1(6) QuoteIn addition to the duties listed in CAPR 20-1, region and wing historians shall:a. Prepare region and wing histories on a calendar year basis.Like I said - technically a requirement for somebody, not a concern at the unit level and not really "new", per se.Frankly, if history is your bag, and you accept that role at the Wing or Region, what else do you have to do?
Wing Commanders are required to appoint a historian who is required to write a history. Sure, if someone is into it, this isn't a problem, but evidence indicates that there are very few willing to do it voluntarily and because of that it is now a requirement that someone spend CAP time working on it. Again, this is just another example of over-bureaucritization of CAP. Same thing happened in public affairs a while back.
I agree 100%. Unfunded mandates are useless.There are what, five mandated positions at the unit level, but only three seniors are required for a squadron?Math.