Appendix_6_USAFA_UAS_OI_VOL_3_1_20131223.pdf

USAFA SUAS OI VOL 3.1 1 December 2013 1

USAFA SUAS OI V3.1

BY ORDER OF THE DIRECTOR OF STAFF, DEAN OF FACULTY

1 Dec 2013

OPERATIONS Chapters 1-5

SMALL UNMANNED AIRCRAFT SYSTEMS (SUAS)

OPERATING INSTRUCTION

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

PDF PASSWORD: USAFA Raven

ACCESSIBILITY: This publication is available on the USAFA/RPA Share Point Site:

https://eis.usafa.edu/centers/UAS/default.aspx

RELEASABILITY: Access to this publication is restricted. This publication is FOUO and requests for accessibility must be approved by the OPR.

Certifying Official: USAFA/DFV (Lt Col Jennifer Alexander) OPR: USAFA/RPA (Col John C. McCurdy) Supersedes: 8 Jun 2013 This instruction provides basic principles and knowledge to enable SUAS students to learn vehicle operator (VO), mission operator (MO), instructor and evaluator skills utilizing a small UAS (SUAS). This manual also provides instruction on all USAFA RPA operations and procedures. File a copy of all approved waivers with this instruction. The use of the name or mark of any specific manufacturer, commercial product, commodity, or service in this publication does not imply endorsement by the Air Force.

Refer recommended changes and questions about this publication to the Office of Primary Responsibility (OPR) using AF Form 847, Recommendation for Change of Publication. Send AF Forms 847s through USAFA RPA/DO, USAF Academy, CO.

SUMMARY OF CHANGES

This document has been substantially revised and must be completely reviewed.

https://eis.usafa.edu/centers/UAS/default.aspx

2 1 December 2013 USAFA SUAS OI VOL 3.1

Chapter 1

INTRODUCTION

1.1. The U.S. Air Force Academy provides the unique opportunity to develop airminded cadets with a fundamental understanding and appreciation for the advantages of air operations through a deep educational and first-hand immersion into Air Force operational functions. Through these experiences they learn the fundamentals of the air domain, the skills of aircraft operations, the expertise to properly employ sensors, and command and control. Cadets also significantly mature through the inspiration, discipline, teamwork, and leadership fundamentals of planning, managing, and executing all aspects of a complex air system.

1.2. The Remotely Piloted Aircraft (RPA) Program’s mission is to further develop within each cadet the profession of arms and build future combat Airpower leadership for the USAF leveraging RPA technology to present a realistic, integrated, air warfare training environment.

Provide cadets academic knowledge, experiential learning, and operational familiarization related to the Air Force’s air combat mission. Teach cadets “what’s going on above them in the battlespace” IAW CSAF intent.

1.3. In addition, USAFA uses a variety of remotely piloted systems as research platforms. SUAS provide unique opportunities for cadets to interact with leading-edge operational concepts and technologies from actual vehicle design to command and control technologies and even doctrine.

1.4. To accomplish these mission objectives, the USAFA Airpower Battlelab, located in Building 2413, includes an open-architecture Air Operations Center that provides command and control of all USAFA RPA activities, to include familiarization training, support of military training, and related research. Unmanned systems provide airborne platforms to perform missions through which cadets experience a wide variety of the challenges related to airpower.

NOTE: This OI generally uses the term “SUAS” or simply “UAS” to refer specifically to Group 1 and Group 2 systems, to include associated ground control systems and other related equipment operated at USAFA under current DoD/FAA guidance; “AV,” or “Aerial Vehicle” often refers to the remotely piloted airplane itself; “RPA” refers to the broader remotely piloted program to include the Airpower Battlelab and AOC.

USAFA SUAS OI VOL 3.1 1 December 2013 3

Chapter 2

ROLES & RESPONSIBILITIES

2.1. Director, USAFA RPA Operations. Oversees all flight operations. Reports directly to the USAFA chain of command providing the status of Current Operations, Standards and Evaluations, Safety and Training Operations, and Aircraft/Equipment Maintenance. Coordinates with outside organizations on issues directly affecting USAFA RPA research, operations and training. The Director will be small unmanned aircraft system operator (SUAS-O) qualified, and is normally a SUAS evaluator (SUAS-E).

2.2. Director, RPA Research Center of Excellence. Coordinates all research activities at USAFA that utilize RPA/UAS. Coordinates with the Director, USAFA RPA Programs to ensure access to de-conflicted airspace to support research flight operations.

2.3. Officer in Charge (OIC). Represents the Director during flight operations. Must be physically present on site or within the AOC when the Ops Sup is not SUAS-E qualified & SUAS operations are taking place; otherwise, the OIC will be readily accessible by phone and/or land mobile radio (LMR). Responsible for safe and effective operations conducted in accordance with all applicable directives, to include all RPA-related agreements between USAFA, AFSOC, AETC. Appointed by the Director. Will normally have either USAF rated instructor experience or SUAS-E qualification (preferred). Must complete all academics and ground testing requirements for SUAS-O/I/E.

2.4. Cadet in Charge (CIC). Appointed by the Director. Competitively selected from among the SUAS cadet cadre. During summer training periods the CIC will be the Cadet Squadron Commander. Responsible for leading and safely executing the cadet RPA Airmanship program.

Appoints eligible cadets to all cadet leadership positions. Maintains accountability for all cadre and students. Reports directly to the Director.

2.5. Operations Supervisor (Ops Sup). Normally the Ops Sup position is filled by a cadet, but can be a qualified officer or contractor. This is a functional position appointed by the Director.

SUAS-E preferred; however, may be filled by any properly trained individual as long as the OIC is present during actual flight operations. The Ops Sup will normally operate from the RPA Air Operations Center (AOC); however, at the OIC’s discretion the Ops Sup role may be filled by the site lead (normally during single-site and/or research operations). Ops Sup responsibilities include preparing and presenting the daily mass brief, approving and tracking launch and recovery, monitoring weather conditions to include seeking PIREPs and providing crews with weather updates, coordinating incident responses, air vehicle (AV) recovery, quick reaction checklist (QRC) initiation and completion, etc. The Ops Sup is the single POC between RPA operations and the 306th Supervisor of Flying (SOF). Signs off completion of MQT events.

Directs UAS mission termination if conditions require.

2.5.1. Ops Sup will:

2.5.1.1. Prepare and present the mass brief.

2.5.1.2. Complete the operational risk management (ORM) worksheet.

4 1 December 2013 USAFA SUAS OI VOL 3.1

2.5.1.3. Ensure all crewmembers are current and qualified for the duties they are scheduled to perform. Reference the Letter of X’s and training folders.

2.5.2. Mass brief.

2.5.2.1. The mass brief will be conducted using PPT as approved by the Director. It will include, at a minimum:

2.5.2.2. Time hack.

2.5.2.3. Weather: current and forecast.

2.5.2.4. Mission overview.

2.5.2.5. Airspace.

2.5.2.6. Safety observer locations and procedures.

2.5.2.7. Site assignments.

2.5.2.8. Manned aircraft conflict resolution review.

2.6. Cadet Logistics Officer (Raven). Ensures equipment accountability. Maintains all equipment inventory books. Assembles, maintains and inventories all field kits. Maintains all spare parts and replacements in a secure location. Stores all damaged equipment pending depot maintenance. Manages all vehicles and fuels. Oversees battery maintenance, safe storage and disposal. Maintains the Area Safety Observer (ASO) and AV recovery kits.

2.7. Cadet Scheduler. Schedules all academic and field events as required by volumes 1 and 2 of this OI and related Airmanship training syllabi. Schedules according to the following priorities:

MQT, evaluations, CT, and then student training. Provides all schedule-related products to include inputs for the daily mass brief.

2.8. Training Manager. Maintains all unit SUAS-O/I/E training records. Tracks cadre currency and reports currency lapses to the Director. Conducts monthly and annual training folder and currency reviews. Ensures all SUAS (cadre and student) training is properly documented.

Maintains and utilizes SUAS lesson plans and develops additional lesson plans as needed.

Receives trend analysis inputs from the Stan/Eval office and develops training plans to correct for identified deficiencies. Organizes and conducts quarterly training review boards, identifying candidates for upgrade to additional aircraft platforms, instructor, site lead and evaluator.

2.9. Stan/Eval Officer.

2.9.1. The Senior Stan/Eval Officer will be a SUAS-E qualified officer or contractor. Appointed by the Director. With no SUAS-E qualified individual available, the Director will appoint a suitable individual, preferably someone with rated evaluator experience. Responsibilities include overseeing the Stan/Eval program to include checkride scheduling, administration and record keeping, and ensuring the integrity of the testing program. Conducts trend analysis.

2.9.2. Cadet Chief of Stan/Eval. Appointed by the CIC, approved by the Director. Should be a SUAS-E qualified cadet if possible. Responsible for writing and administering the Boldface/Ops Limits, Closed Book, and mission qualification training (MQT) Open Book written tests.

Maintains a checkride currency tracker and schedules checkrides. Establishes Training and Flight Evaluation Folder (TFEF) standards. Inspects TFEFs at least quarterly.

USAFA SUAS OI VOL 3.1 1 December 2013 5

2.9.3 Cadet Stan/Eval Liaison (SELO). Appointed by the CIC. Maintains the FCIF program.

Assists the Cadet Chief of Stan/Eval in the performance of all Stan/Eval duties. Normally a second class cadet SUAS-O.

2.10. Pilot in Command (PIC). A PIC must be designated at all times. IAW AFI 11-502 the PIC is responsible for all aspects of the mission (equipment preparation, planning, briefing, ground and air operations, recovery, mission debriefing, and equipment accountability); and is responsible for the safety of the Unmanned Aircraft (UA) and persons and property along the UAS’s flight path. The PIC must be a qualified and current SUAS-O/I/E in the type UAS in operation. The PIC will be positively identified during the site crew briefing.

2.10.1. The PIC will be the crewmember with the highest qualification. If two or more operators have the same qualification, the Ops Sup will designate a PIC.

2.10.2. A student may “act” as the PIC, but cannot be the actual PIC.

2.10.3. During handoff missions, PIC responsibility will rest with the PIC who has verbally accepted control of the AV. For example, once the receiving site verbally and positively accepts control of the AV, that site’s PIC has sole authority and responsibility as PIC. If there is a designated “Mission Commander,” he/she does not have authority over the PIC.

2.11. Site Lead. In the event familiarization training is conducted by SUAS-O-only qualified operators there will be a designated Site Lead who will be the mission PIC. The Site Lead must be at least SUAS-I qualified in the type SUAS being flown, and certified by appointment letter by the Director to perform Site Lead duties.

2.12. Cadet Safety Officer. Appointed by the CIC. Responsible for developing safety standards, and for verifying compliance. In charge of the safety observer program. Conducts regular safety inspections of all program facilities and sites. Provides safety inspection feedback to the Director and CIC. Conducts quarterly safety meetings.

2.13. The ASO will maintain visual and situational awareness over the entire operations area.

Primary responsibility is to maintain vigilance against non-participating aircraft entering the SUAS Ops Area. The ASO will maintain positive communications with Ops Sup and all sites at all times. Required equipment includes LMR, binoculars, a compass, and USAFA V877S area map.

2.14. The Site Safety Observer (SO) will maintain visual primarily with the aerial vehicle (AV), its immediate surrounding area, and with potential conflicting traffic. The SO will guard against the AV leaving designated airspace, flying into terrain, and overflying buildings or no-fly areas.

The SO will be directive if necessary to the VO to prevent loss of visual, loss of the AV, or the AV presenting a hazard to manned aircraft.

6 1 December 2013 USAFA SUAS OI VOL 3.1

Chapter 3

OPERATIONS PROCEDURES

3.1. Operational Risk Management (ORM):

3.1.1. Prior to operations, the Ops Sup will complete an ORM worksheet. Each site lead instructor will review the worksheet to ensure its validity for their scheduled crew(s) and conditions. Director/OIC approval is required to launch with any single “HIGH” category, or “HIGH” overall.

3.1.2. The ORM worksheet is only a tool. The Ops Sup will use judgment and consult with the Director/OIC anytime risk appears to be elevated regardless of the ORM worksheet score.

3.2. Rest and Duty Day Limitations

3.2.1. The Duty Day begins when a crewmember reports for duty and ends upon departure from the duty location. The flying duty period will not exceed 12 hours. Maximum continuous control time will not exceed 6 hours.

3.2.2. Crew Rest. Crews require 12 hours off duty, and the opportunity for 8 hours of uninterrupted rest. Personnel cannot act as a crewmember (even as a student) unless these minimums are met. As an example, if you had your last official duty at 2000 hours and your first official duty the next morning was before 0800, you did not have 12 hours off, and you can’t fly or perform flight duties that day. If you do not have crew rest, you will show for duty as scheduled and identify yourself as not having crew rest.

3.2.3. Alcohol and medications. Crewmembers will not consume alcohol within 12 hours of flight duties. Regardless of “bottle to throttle” time, crewmembers will not fly while impaired.

Crewmembers will not use medications without the express consent of a qualified flight surgeon.

This includes all crewmembers, to include contractors and students.

3.3. Flight Medicine.

3.3.1. Flight medicine is the only office authorized to determine flight crew official health status. All illness and medication requirements will be administered by Flight Medicine. Do not self-medicate (with the exception ibuprofen or aspirin taken only as prescribed on the container).

3.3.2. If sick, determine the walk-in sick call hours at Flight Medicine. (If at all possible attend sick call well prior to the scheduled flying period.) Flight Medicine will determine whether or not you are grounded. If so, you will be assigned to Duties Not Including Flying (DNIF) status and receive an AF Form 1042, Medical Recommendations for Flying or Special Operational Duty, or the interim USAFA Form 18. DNIF documentation must be hand carried to the Ops Sup.

3.3.3. If Flight Medicine determines bed rest is appropriate, the 1042/Form 18 must still be delivered to the Ops Sup via any means.

3.3.4. Return to Flying Status (RTFS) is also only authorized by Flight Medicine. Return to Flight Medicine as soon as you are well, and another 1042/Form 18 will be issued for RTFS.

USAFA SUAS OI VOL 3.1 1 December 2013 7

Notify the Ops Sup immediately upon RTFS, and deliver your new 1042/Form 18 to the AOC.

You will not be allowed to fly until your RTFS paperwork is posted in your TFEF.

3.4. Flight Weather Requirements. All crews will adhere to SUAS weather requirements for DOD Class G operations: 3 SM visibility; plus 500 feet below, 1,000 feet above and 2,000 feet horizontal cloud clearance.

3.4.1. Additional limits for Raven operations

3.4.1.1. Minimum weather is 500-3. Greater than 1000-1 is considered low risk. Less than 1000- 1 is medium risk (Ops Sup approval), with less than 700-1 high risk (OIC or Director approval).

3.4.1.2. Max wind is 20 kts, surface or aloft. Operations at greater than 15 kts surface or aloft require Ops Sup approval and the ability to continuously operate upwind of waypoint “E” until setting up for landing. Crews must be aware that this requirement could prevent operations from some sites.

3.4.1.3. Student hand launches require Director approval and are prohibited with less than 5 kts surface wind.

3.4.2. Research SUAS

3.4.2.1. TBD

3.5. Procedural control

3.5.1. All UAS operations will be conducted within approved airspace.

3.5.2. All launch and recovery clearances will be coordinated through the Ops Sup.

3.5.3. Minimum planned vertical separation is 50’. Crews will remain at their assigned altitudes to the maximum extent possible. If vertical maneuvering is required for training, crews will coordinate with the Ops Sup to ensure lateral separation of at least 0.5 Km, and positive verified situational awareness among adjacent sites.

3.5.4. (Raven) Vertical maneuvering must be accomplished within .5 Km of “H”.

3.6. Lost Link Planning

3.6.1. Raven

3.6.1.1. Loss of link (LOL) logic for the Raven will normally be set to “En Route Rally.”

However, when required e.g. conducting hand-offs, LOL may be set to “Finish Flight” in order to avoid unintended flight over no-fly areas. The “Land Immediately” setting is not authorized.

3.6.1.2. Flight loop time will be set no longer than planned mission time plus 10 minutes not to exceed 60 minutes in order to mitigate potential for loss of battery power.

3.6.2. Research SUAS

3.6.2.1. TBD

8 1 December 2013 USAFA SUAS OI VOL 3.1

Chapter 4

RPA ADMINISTRATION

4.1. DoD-FAA MOA: Refer to the RPA SharePoint

4.2. USAFA RPA Contact List

4.2.1. USAFA RPA

Director, Col McCurdy ..................................210-854-9859 (C) /333-8225 OIC, Kip “Bonemass” Warton .......................719-209-0409 (C) /333-8578 Ops Sup (AOC) ..............................................333-1475

4.2.2. USAFA

Dean of Faculty ..............................................333-4270 Gen McCarthy ................................................333-2746 / 719-649-4995 (C)

306 FTG/CC...................................................333-3330

Supervisor of Flying (SOF) ...........................333-1162/2012 Tower .............................................................333-3913 Base Ops ........................................................333-2367/2526 Weather ..........................................................333-2058 Fire Department .............................................333-4433 Command Post ...............................................333-2633 Cadet Wing Command Post ...........................333-2910

USAFA/PA ....................................................333-4040

USAFA SUAS OI VOL 3.1 1 December 2013 9

Chapter 5

OPERATIONS SUPERVISOR STANDARD PROCEDURES

5.1. Day Prior to Scheduled Fly Day.

NOTE: Some procedures refer to Raven or Research-only requirements. These will be designated, e.g., [RAVEN].

5.1.1. Scheduling officer will email Ops Sup finalized schedule for the day.

5.1.1.1. [Raven] includes assigned drivers, IPs, Site Lead, ASO, and AV recovery lead.

5.1.1.2. [Raven] logistics officer email Ops Sup AV frequency and falcon tracker frequencies.

5.1.4. Ops Sup builds the mass brief for the next day with posted aerial events and without weather.

5.2. Opening Checklist.

5.2.1. Arrive 2 hours prior to first takeoff.

5.2.2. Unlock the storage room and AOC.

5.2.3.Ops Sup check current KAFF weather, NOTAMs and TFRs.

http://www.aviationweather.gov/adds/tafs/ http://www.USAFA.edu/tu/306ftg/oss/weather/ http://www.FAA.gov/pilots/flt_plan/NOTAMs/

5.2.3.1. 306th weather PHONE # 333-2058 – call WX only if online information is inadequate.

5.2.3.2. Insert weather and NOTAM information into mass brief slides.

5.2.4. Ops Sup gives the mass brief 1+ 30 minutes before the first launch.

5.2.4.1. Refer to RPA SharePoint for latest airspace site slides.

5.2.5. Flight crews depart with gear after mass brief.

5.2.6. Ops Sup will monitor the WX via HWAS located on the 306th FTG weather website and through the ADDS TAF website for the current observation. See para 5.2.3 for web address information.

5.3. Contact SOF after mass brief and before stepping crews.

5.3.1. Phone # 333-1162.

5.3.2. Inform SOF of:

5.3.2.1. Flying Schedule for the day (Ops, DFAN, DFEC).

5.3.2.2. Scheduled airspace and times.

5.3.2.3. Altitudes should be “standard IAW FCIF altitude CAPs” as there is no reason to exceed the published altitudes.

5.3.2.4. Confirm published flight restrictions (aerial events, TFR’s, etc.).

5.4. [Raven] Logistics Officer check inventory for the day.

5.4.1. Assemble field kits and UAS cases for transport.

5.4.2. Check and log out radios and batteries for the day.

5.4.3. Assign supplies to trucks for transport.

http://www.aviationweather.gov/adds/tafs/ http://www.usafa.edu/tu/306ftg/oss/weather/ http://www.faa.gov/pilots/flt_plan/NOTAMs/

10 1 December 2013 USAFA SUAS OI VOL 3.1

5.5. Aircrew Step Checklist.

5.5.1. Check [Raven].

5.5.1.1. DNIF status.

5.5.1.2. Initial flight authorization form for any changes to scheduled sorties.

5.5.1.3. Verify athletic fields are not in use (if required).

5.5.1.4. Ensure airspace is deconflicted.

5.5.1.5. Check that crew verifies site binder in the field kit.

5.5.1.6. Confirm crew qualifications and Ops Limits/BF are complete via letter of X’s.

5.6. Brief.

5.6.1. Flying status/restrictions/trends.

5.6.2. Hot ops notes.

5.6.3. NOTAM/airfield advisories/BASH status/fly-bys/etc.

5.6.4. Current and forecast winds/weather (observer 333-2058).

5.6.5. Route of flight awareness – PFP/NIFA NAV route and area deconfliction.

5.6.6. ORM mitigation.

5.7. Step [Raven].

5.7.1. Crew sign out equipment and truck keys – Ops Sup Desk.

5.7.2. PIC sign the flight authorization log – Ops Sup Desk.

5.7.3. Crews should load vehicles with the appropriate equipment.

5.8. Continuing Duties.

5.8.1. Update the WX METAR every hour on the hour unless rapidly changing conditions are observed.

5.8.1.1. Review HWAS regularly again depending on the severity of the wind conditions and the stability of the weather conditions.

5.8.1.2. As wind states exceed 10 kts notify the crews over the LMR of changing weather conditions.

5.8.1.3. At 15 kts notify the crews of the potential dangers over the LMR. Recommend crews to consider recovery if warranted or continue operations within a safe recovery distance.

5.8.1.4. When the forecast and HWAS indicate winds will likely exceed 20 kts, direct recovery of all UAS.

5.8.1.5. Ops Sup Activity Log. The Ops Sup will maintain a comprehensive activity log each duty day. At a minimum, this log will include all communications (telephone, LMR, VHF, etc.), airspace assignments, sorties, launch times, recovery times, and any unusual events. All logs will be retained for one year.

5.8.2. Pass all status changes to the SOF.

5.9. Same day scheduling changes:

5.9.1. Notify stepping crews of the changes in schedule/WX.

5.9.2. Cancels: notify crews of cancelations before step time.

5.10. Safety related events.

USAFA SUAS OI VOL 3.1 1 December 2013 11

5.10.1. Reference the safety continuity binder and comply with any immediate action.

5.10.2. Any safety related event (emergencies, near-midair collisions (NMAC), bird strikes, etc.)

contact Director or the OIC and safety officer ASAP.

5.11. The Ops Sup will continue to monitor the flying operation throughout the scheduled flight period for Ops, DFAN, and DFEC.

5.11.1. The Ops Sup will brief the oncoming or temporary Ops Sup of current activity prior to turning over responsibilities IAW the Changeover Checklist at para 5.13. The Temporary Ops Sup or the oncoming Ops Sup must be fully qualified and on the letter of X’s.

5.11.2. If the status is standby, it is not necessary to remain in the immediate area – continue to carry/monitor the brick and return to the immediate area NLT 30 minutes prior to the next scheduled launch.

5.11.3. If flying for the day is cancelled, accomplish the Closing Checklist below.

5.11.4. Log any unusual events for the next Ops Sup in the EOD report.

5.12. Post Flight.

5.12.1. Sign In.

5.12.1.1 [Raven] Logistician receives site kits, LMR’s, and conducts joint inventory.

5.12.1.2. PIC sign in at Ops Sup desk and log flight time per crew member.

5.12.1.3. PIC debriefs with the Ops Sup IAW debrief checklist.

5.12.2. [Raven] mandatory maintenance debriefs (listed below): contact the logistics officer.

5.12.2.1. Ground or air aborts.

5.12.2.2. Failed launches.

5.12.2.3. Offsite landings.

5.12.2.4. Discrepancies that affect safety of flight.

5.12.2.5. Discrepancies that will drive an aircraft impound.

5.12.2.6. At the request of the aircrew or Ops Sup.

5.12.2.7. After the last sortie of the day.

5.12.3. Remind crews to fill out SUASMAN, post flight, site specific log in the site binder.

5.13. Ops Sup Changeover.

NOTE: DO NOT changeover during an emergency.

5.13.1. Off Going Ops Sup.

5.13.1.1. Police the Ops Sup position and AOC.

5.13.1.2. Initial any changes you made to the flight authorization log.

5.13.1.3. Fully brief the oncoming Ops Sup of flying events, any singular occurrences, current WX and NOTAMS, and pending aerial events.

5.13.2. On Coming Ops Sup.

5.13.2.1. Receive the Off Going Ops Sup changeover brief to include weather, flying status, and unusual events entered in logbook.

5.13.2.2. Review all log entries on EOD report since your last shift.

5.13.2.3. Ops check Ops Sup LMR and replace with fresh radio if required.

5.13.2.4. Review the flying schedule.

12 1 December 2013 USAFA SUAS OI VOL 3.1

5.13.2.5. Update status board (digital) and mass brief slides.

5.13.2.6. Review continuing duties checklist for applicable duties.

5.14. Ops Sup Closing Checklist.

5.14.1. Account for all vehicles and aircrews following flight.

5.14.2. [Raven] ensure all maintenance debriefs are completed as required.

5.14.3. Retrieve all daily training logs and place in log binder.

5.14.4. Verify building cleanliness.

5.14.5. Inventory LMR’s, insure they are turned off and charging.

5.14.6. Save changes to mass brief before shutting down AOC computer.

5.14.7. Notify the Director / OIC of any significant events if not already notified.

5.14.8. Turn off and unplug any heaters or coffee makers.

5.14.9. Ensure the store room, AOC, and outdoor storage container are locked.

5.14.10. Complete the Ops Sup Activity Log.

5.15. Logistics Closing Checklist.

5.15.1. Verify the following:

5.15.2. Batteries are in the fire proof container.

5.15.3. All fuel cans and fuel containing generators are in the exterior fire proof container.

5.15.4. No batteries are left charging.

5.15.5. [Raven] check the equipment sign out log to make sure the equipment is signed back in.

5.14.1. Cross check sign out log with the supplies in the storage room. .

OPERATIONS Chapters 1-5