25.02.2013 Views

AFI 11-2C-130v3 - BITS

AFI 11-2C-130v3 - BITS

AFI 11-2C-130v3 - BITS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

122 <strong>AFI</strong><strong>11</strong>-<strong>2C</strong>-130V3 23 APRIL 2012<br />

8.5.1.2. Investigation and analysis. Report circumstances which required/drove<br />

deviation(s).<br />

8.5.1.3. Findings and conclusions.<br />

8.5.1.4. Recommendations to prevent recurrence.<br />

8.5.1.5. Corrective actions taken.<br />

8.5.2. Include the following attachments with the report:<br />

8.5.2.1. Formal notification of incident.<br />

8.5.2.2. AMC Form 41 or approved crew orders.<br />

8.5.2.3. Crewmembers‘ official statements (if applicable).<br />

8.5.2.4. Other pertinent documents submitted in evidence (logs, charts, etc.).<br />

8.5.3. In addition to above (when aircraft is equipped), PIC shall download original flight<br />

plan to a floppy disk and turn it in to the C2 center or parent standardization and evaluation<br />

office.<br />

8.5.4. OG/CC shall send the original investigation report to the appropriate MAJCOM<br />

within 45 days of the event/notification. NOTE: (ANG Only) If inquiries come from the<br />

NGB, units will respond to NGB/A3O directly who will in turn notify AMC. If inquiries<br />

originate from AMC, units will respond to AMC and courtesy copy NGB/A3O.<br />

8.5.5. Use OPREP-3 reporting procedures contained in <strong>AFI</strong> 10-206, Operational Reporting,<br />

for navigation errors over 25 NMs.<br />

8.5.5.1. When notified of a navigation position error, the PIC (or agency that receives<br />

initial notification) shall document the circumstances surrounding the incident (using<br />

report format below) and ensure C2 agents submit an OPREP-3.<br />

8.5.5.2. Include the following information in the report:<br />

8.5.5.3. The name and location of agency/unit submitting report.<br />

8.5.5.4. Affected mission identification number.<br />

8.5.5.5. Reference OPREPs-3 to determine type of event (i.e., state "navigation position<br />

error.").<br />

8.5.5.6. The date, time (Zulu), and location (e.g., ARTCC area) of alleged infraction.<br />

8.5.5.7. Describe facts and circumstances. Include aircraft type and tail number, unit<br />

(aircrew‘s wing or squadron), home base, route of flight, point of alleged deviation, and<br />

miles off course.<br />

8.5.6. PICs shall expeditiously report unusual events/circumstances that impact their mission<br />

to appropriate MAJCOM agencies. Reportable events include, but are not limited to,<br />

spectrum interference, interception, fuel dumping, multiple engine failure, hostile fire, injury<br />

to passenger or aircrew member, etc. This list is not all exhaustive. Most events require C2<br />

agents to forward OPREP reports to higher headquarters. In all cases, pass the ―who, what,<br />

when, where, why, and how‖ of the incident to a C2 agency.

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

Saved successfully!

Ooh no, something went wrong!