13.07.2015 Views

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

WWW.SURVIVALEBOOKS.COM34 AFI10-207 4 APRIL 20085.3.2.2.3. Weather Conditions. Cover current and forecasted weather to include weatherwatches, weather warnings, and other weather conditions that may impact unit mission accomplishment.5.3.2.2.4. Off-Station and Transient <strong>Air</strong>craft if applicable. Cover the location and status ofunit aircraft that are off station and any transient aircraft currently on station or projected toarrive.5.3.2.2.5. Key Personnel. Address the location of designated key personnel and distinguishedvisitors.5.3.2.2.6. Open QRCs. All incomplete QRCs requiring further action.5.3.2.2.7. Upcoming events (e.g., expected visitors, CP or unit exercises, planned commanderoff-station, etc.)5.3.2.2.8. Duress codes to include primary, alternate, and exercise.5.3.2.2.9. Status of required reports.5.3.2.2.10. Safe and entry combination. Verify correct combination with off-going controllerand verify combination change dates.5.3.2.2.11. Equipment Status. Review current operational condition of equipment, call signsand frequencies, and any in-progress or scheduled maintenance.5.3.2.2.12. Two Person Control/Two Person Integrity (TPC/TPI) material, if applicable.Address the next safe inventory date and required combination change date, if applicable.5.3.2.3. Controller Shift Checklists. Shift Checklists are developed and maintained to ensure controllerscomplete all required actions throughout their shift. Shift Checklists, as a minimum, willinclude:5.3.2.3.1. Secure Voice Equipment Tests. Accomplish communication checks with anotherunit after each change of keying material or at least weekly for each secure voice telephonesystem (e.g., NATO Secure Voice, Secure Telephone Unit-III (STU-III) and Secure TelephoneEquipment (STE)) installed in the CP console area. Log test completion and deficiencies in theCP daily events log.5.3.2.3.2. Installation Warning/Base Notification Systems Tests. Log test completion and anydeficiencies in the CP daily events log. Report any deficiencies to the appropriate agency.5.3.2.3.3. Periodic Security Checks. Controllers will log results of periodic security checks inthe CP daily events log. Report any discrepancies to the appropriate agency.5.3.2.3.4. Emergency Lighting Test. Conduct weekly functional checks of emergency lightingsystems. Log test completion and any deficiencies in the CP daily events log. Report any deficienciesto appropriate agency.5.3.2.3.5. Time Standardization. CP clocks will be hacked at least once daily with the U.S.Naval Observatory Master Clock (DSN 762-1401/312-762-1401) to within one second. Logtime hack accomplishment in the CP daily events log.5.3.2.3.6. Required Reports. List all recurring/routine reports.5.3.2.3.7. Housekeeping Tasks. List tasks to be accomplished by duty controllers.

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

Saved successfully!

Ooh no, something went wrong!