<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>The PAO/PIO problem is that CAP’s PIO certification is nearly devoid of PA skills, yet there are lots of CAP PIOs who passed the few tasks required by the SQTR and can potentially end up being the PIO on a mission. But, if you look at the FEMA training required of PIOs, CAP does not prescribe any of that training for our PIOs, some of whom may be PIOs but are not PAO rated.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>The reverse problem is that of PAOs who have no PIO training, and working as a PIO is not the same as being a PAO. The merry dance starts when the emergency chooses a PAO, with no PIO able to help either onsite or via communications because the hurricane, tornado or earthquake has broken down all links, and the IC who supervises that PA person has insufficient PA training too. So here is a a blind-leading-the-blind situation, a recipe for disaster.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>I have advocated for some time the idea that a PAO should not rise above technician unless that PAO also becomes a FEMA-compliant PIO, and a master-rated PAO should be at least a senior-rated FEMA-compliant PIO. How else would a wing PAO who is not PIO rated be an effective resource person for the wing’s PAOs and PIOs? <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Separating PAOs from PIOs is a mistake. But an even bigger mistake is having PIOs who are not PAOs too.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Arthur ~<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>__________________________________<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>ARTHUR E. WOODGATE, Lt. Col., CAP<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Director of Public Affairs & Director of Organizational Excellence<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Southwest Region<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Civil Air Patrol - "Citizens Serving Communities"<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>512.432.0231 <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>512.547.6997 <<< VoIP (secondary)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>512.567.1935 (cell - not always on)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>awoodgate@austin.rr.com <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>LtColWoodgate@gmail.com<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> cap-pao-bounces@lists.sempervigilans.org [mailto:cap-pao-bounces@lists.sempervigilans.org] <b>On Behalf Of </b>Karen Copenhaver<br><b>Sent:</b> Saturday, September 07, 2013 8:04 AM<br><b>To:</b> CAP Public Affairs Officers<br><b>Subject:</b> Re: [PAO] September Disaster Preparedness Month<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><b><i><span style='font-size:13.5pt;color:#333399'><br>With respect, I do not agree..... mainly because being a PIO is more specialized and focused on emergency services. The responsibility of a PAO is different in that he/she is responsible for the image of CAP in general. When first joining CAP, usually the PAO is focused on learning more about the organization, how it works or functions within the community, impacts the future of our leaders (cadets) and just what CAP is and does as part of our congressionaly mandated missions. The PIO must be experienced and have gained the confidence to work emergency / training missions. There is a significant difference as my personal professional training taught me, and all those professional practioners will agree. Let's not forget, that all PAOs do not want to serve as PIOs. I can't imagine a new PAO automatically being considered a PIO, it's akin to telling a new CAP member is automatically certified to fly as an observer, or field operative. NO WAY. There must be a specified dedicated training program to instruct a PAO in how a mission is initiated, who initiates, learning the responsibilities of fellow mission members, what should and should not be released, how to interact with fellow mission members, the public and any members of a family involved. The list goes on... however, once the PAO gains the knowledge and training in emergency services, then.... then he/she should be evaluated before being certified to served as a PIO, but must serve as a PAO first, at least for a year...... hope this helps.<br><br><br>Karen L. Copenhaver, Lt Col, CAP<br>Deputy Director, Public Affairs<br>MER<br></span></i></b><br><br><br>On 9/6/2013 4:10 PM, Cianciolo, Lt Col, Paul wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>That makes me even more convinced that CAP should not be separating PAO and PIO responsibilities as is now. We are one organization and can't compartmentalize it so much. SAR, HLS, and DR missions are part of the whole mission. Without them, would CAP be here? At times its like being in two different organizations depending on what the activity is.<o:p></o:p></p></div><p class=MsoNormal>Paul <o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>v/r<br>--<br><b>PAUL S. CIANCIOLO, Lt Col, CAP<br>Public Affairs Officer<br>National Capital Wing</b><o:p></o:p></p><div><p class=MsoNormal>Cell: 301-751-2011<o:p></o:p></p></div><div><p class=MsoNormal>Work: 202-385-9599 (@FAA)<o:p></o:p></p></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p></div></blockquote><p class=MsoNormal><o:p> </o:p></p></div></body></html>