Started by Holding Pattern, January 16, 2020, 05:39:26 pm
0 Members and 1 Guest are viewing this topic.
Quote from: CAP9907 on January 17, 2020, 07:12:02 pmThis is not the case, at least as far as the regulations are concerned. Your Wing may do it that way, but the Wing Commander need not be the first call, or any call at all to start an AFAM. I'd refer you to 60-3 and the C-1 tab of the CI process (on the NHQ IG page). I'm not a CC or deputy at any level, but I am a WAO and IC. When I get the call from AFRCC, I am able to commit the Wings resources and accept the mission on behalf of the CC without involving him. WMIRS 1.0 has every Wings alert roster, and that's what they use to alert. Go check your Wings roster, I'd bet your CC is not on that alert list, as most are not. Of course I'd give him a courtesy call to keep him advised about the event, but the missions do not stop because the CC is in the john , at work, or on a safari.
Quote from: Holding Pattern on January 16, 2020, 05:39:26 pmIn my CERT thread, one comment was made about CAP's long spin-up time for response.Anyone here have thoughts on how to decrease that spin-up time?
Quote from: xyzzy on January 17, 2020, 11:47:51 amFor example, an ambulance is driving down the street and sees a house on fire, so the crew chief is the incident commander until the fire department arrives.
Quote from: etodd on January 18, 2020, 03:23:28 amQuote from: xyzzy on January 17, 2020, 11:47:51 amFor example, an ambulance is driving down the street and sees a house on fire, so the crew chief is the incident commander until the fire department arrives.Yep. Its constantly drilled into us to never "self deploy". Sit back and wait.
Page created in 0.070 seconds with 22 queries.