(ENEMY ACTION) SAFIRE RPT (AAA) A, -%%% CAV ( /%%%, 2X OH ) : %%% INJ/DAM

:%%%\012\012REPORT TYPE: Initial\012\012WHO: A, -%%% CAV, /%%%, 2X OH-%%%\012\012WHEN: 031510NOV08\012\012WHERE: Kirkuk Province, SW of Kirkuk - %%%\012\012WHAT: SAFIRE ( %%%)\012\012HOW: While traveling north on RTE %%% conducting reconnaissance, SWT lead aircraft received a %%%. The round exploded underneath the lead aircraft. Trail aircraft saw the %%% and reported it to lead. SWT began to develop the situation. At , /%%% was alerted. /%%% requested QRF and the IPs are going to check out the grid. \012\012INITIAL BDA: None\012\012UPDATE AND FINAL: 032242OCT08\012At %%% while conducting reconnaissance along RTE %%% at %%% kts, heading of %%% degrees, lead aircraft at %%% AGL, and trail aircraft at %%% AGL, %%% received SAFIRE in the form of a %%% vic ME %%%. Trail aircraft ( %%%) immediately identified the POO site, and instructed lead aircraft to take evasive maneuvers and break left (East) away from the site. %%% engaged with %%% x .%%% Rockets in a low CDE area. No personnel movement or secondary explosions were observed in vic of rocket impacts. SWT assessed they had no damage to the aircraft and remained in the area to develop the situation and guide ground forces to the location. At , %%% TAC notified %%% and dispatched /-%%% AR QRF to the reported POO site. At %%%, Iraqi IPs arrived IVO the POO Site and congregated until Coalition Forces arrived. At %%%, conducted a %%% with SWT %%% and %%% FOB Warrior. SWT %%% provided area security for QRF while they attempted to PID the POO site. Due to limited visibility, QRF ended their search and planned to continue their search the following morning. At %%%, SWT %%% broke station and continued with previous mission set. \012\012FINAL BDA: NONE \012\012Assessment: This attack and possible location have been anticipated over the last week and thus %%% techniques have been briefed to crews numerous times. This attack also occurred within %%% of two previous %%% attacks along this portion of %%%. As it had been %%% days since the last %%% attack in the AO, it would be difficult to determine when this aerial ambush was %%%. The terrain in the area of these attacks is highly conducive to an early %%% with a long surveillance phase. The %%% could conceivably %%% this ambush site a month in advance and then just wait for the best time. As %%% are on a schedule, having the same time periods to work in on a weekly basis, and are also restricted in their air avenues of departure and approach to FOB Warrior, it would not be difficult for an observer/%%% to determine when to expect A/%%% outside Warrior. We do not normally see more than two %%% attacks in the same location nor do we see back-to-back %%% attacks closer than a month together at the same location so we can reasonably expect the next attempted ambush to occur within the first week of %%%. \012\012CLOSED: 032243OCT08\012\012