26.03.2013 Views

by order of the commander cannon air force - Air Force E-Publishing

by order of the commander cannon air force - Air Force E-Publishing

by order of the commander cannon air force - Air Force E-Publishing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

18 CANNONAFBI34-242 30 OCTOBER 2012<br />

2.3.2.2. Authorize <strong>the</strong> S&R action as <strong>the</strong> incident <strong>commander</strong> at an accident site.<br />

However, if <strong>the</strong> incident is suspected as criminal or terrorist in nature, <strong>the</strong> area will be<br />

secured <strong>by</strong> <strong>the</strong> 27th Special Operations Security <strong>Force</strong>s Squadron, (27 SOSFS), and<br />

immediate notification will be made to Curry County Sheriff’s Office (CCSO). If CCSO<br />

relinquishes jurisdiction, AFOSI will assume overall control <strong>of</strong> <strong>the</strong> scene until released<br />

back to incident <strong>commander</strong>.<br />

2.3.2.3. Ensure Public Aff<strong>air</strong>s (PA) provide photographic support to all S&R incidents.<br />

2.3.2.4. Provide, through 27th Special Operations Comptroller Squadron (27 SOCPTS),<br />

special/temporary duty (TDY) <strong>order</strong>s support and processing.<br />

2.3.2.5. Provide, through agencies under <strong>the</strong> 27 SOMSG, o<strong>the</strong>r resources required to<br />

support <strong>the</strong> S&R Team, and temporary storage activities when <strong>the</strong> Memorandum <strong>of</strong><br />

Agreement between <strong>the</strong> New Mexico Medical Examiner cannot be used due to situational<br />

local medical examiner resources.<br />

2.3.2.6. Ensure <strong>the</strong> 27th Special Operations Logistic Readiness Squadron (27 SOLRS)<br />

provides a vehicle for <strong>the</strong> S&R team and equipment.<br />

2.3.3. The Commander, 27th Special Operations Civil Engineer Squadron (27<br />

SOCES). Will:<br />

2.3.3.1. SOCES will provide global positional system (GPS) and/or optical survey<br />

equipment and trained personnel to plot remains, personal effects and <strong>air</strong>craft wreckage.<br />

2.3.3.2. SOCES will define <strong>the</strong> hazards <strong>of</strong> <strong>the</strong> incident.<br />

2.3.3.3. SOCES will provide chemical, biological, radiological and nuclear (CBRNE)<br />

monitoring through <strong>the</strong> S&R operation to ensure team safety via appropriate limited<br />

exposure time/level.<br />

2.3.4. The Commander, 27th Special Operations Medical Group (27 SOMDG). Will:<br />

2.3.4.1. Provide all reports and documents for completion <strong>of</strong> <strong>the</strong> mortuary case files as<br />

requested <strong>by</strong> <strong>the</strong> MA <strong>of</strong>fice.<br />

2.3.4.2. Alert <strong>the</strong> traumatic stress response team (TSR) for activation as needed.<br />

2.3.4.3. Provide supplemental training to <strong>the</strong> base S&R team as required <strong>by</strong> MA for<br />

items such as blood-borne pathogens, TSR, and human anatomy.<br />

2.3.4.4. Provide manpower and equipment necessary for proper fitting <strong>of</strong> respirators,<br />

Tyvek suits, and o<strong>the</strong>r mishaps specific equipment as needed. Ensure <strong>the</strong> S&R team<br />

members receive respiratory protection program and training.<br />

2.3.4.5. Ensure potential S&R team members are physically and mentally fit for S&R<br />

duties and are provided Hepatitis B vaccinations and annual testing for <strong>the</strong> human<br />

immune-deficiency virus (HIV).<br />

2.3.5. The 27th Special Operations <strong>Force</strong> Support Squadron (27 SOFSS) Mortuary<br />

Officer. Will:<br />

2.3.5.1. Assist <strong>the</strong> installation <strong>commander</strong> and implement <strong>the</strong> installation's MA program.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!