Appendix_8_USAFA_SUAS_Operations_Supervisor_Operating_Instruction_20140101.pdf

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 1

USAFA SUAS OPERATIONS SUPERVISOR OI

BY ORDER OF THE DIRECTOR, USAFA UAS/RPA PROGRAMS

1 January 2014

Operations

SMALL UNMANNED AIRCRAFT SYSTEMS (SUAS)

OPERATIONS SUPERVISOR OPERATING INSTRUCTION (OI)

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: This publication is available on the USAFA/UAS Share Point Server:

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

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

OPR: USAFA/SUAS (Col John C. McCurdy)

Supersedes: NA

This instruction establishes USAFA UAS Operations Supervisor requirements. Submit suggested changes directly to the OPR using USAF Form 847.

SUMMARY OF REVISIONS

This is an original document and should be reviewed in its intirety.

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

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 2

1. Small Unmanned Aircraft Systems (SUAS) Operations Supervisor (Ops Sup) Duties

1.1. The Ops Sup is responsible to the USAFA UAS/RPA Director and then to the 306 FTG

Supervisor of Flying (SOF) for all RPA flying operations at USAFA. The Ops Sup oversees RPA flying operations and insures compliance with regulatory guidance, safety protocols, and syllabus directed/continuation training.

1.2. Ops Sup Administration

1.2.1. The Ops Sup position will be filled by the Squadron Commander (Sq CC)/ Cadet in Charge (CIC), Director of Operations (DO)/Deputy CIC, and the Standardization

& Evaluation Officer (Stan/Eval) with Director certification following the successful completion of a Stan/Eval open book test pertaining to Ops Sup procedures.

1.2.2. The Ops Sup will be familiar with all applicable operating procedures and regulatory guidance with particular focus on USAFA SUAS OI V3.

1.2.3. The Ops Sup is responsible for conducting the mass brief prior to the start of the flying period. As such the Ops Sup must prepare slides reflecting the mission, flying locations, schedule, weather, and administrative details. The briefing will be conducted in a professional manner beginning on time covering all applicable information in a timely manner and formatted in accordance with briefing academics.

1.2.4. The Ops Sup is responsible for maintaining situational awareness (SA) of all RPA operations, weather systems, potential air traffic conflicts, 306 FTG aerial events, and schedule requirements. As such the Ops Sup must maintain broad situational awareness over the entire RPA operations.

1.3. Daily Operations

1.3.1. The Ops Sup with the DO is responsible for execution of the daily and weekly

Ops flying schedule, modifying the schedule as required maximizing training based on real time operational constraints.

1.3.1.1. Confirm qualifications of individuals on the schedule via the letter of X’s.

1.3.1.2. Confirm availability of personnel cross-referencing the availability log book which is maintained by Training.

1.3.1.3. The availability log book also includes annotation for those cadets who are

DNIF. Confirm the effective date of the log book to insure the latest information is available that will impact the immediate flying schedule.

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 3

1.3.2. The Ops Sup will prepare the Ops mass brief slides with the exception of the weather no later than the day prior to the scheduled flying period. Follow the master briefing information given below (Section 2). The weather slide must include the current METAR, TAF, NOTAM, and TFR information which will be prepared NLT one half hour prior to the briefing.

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

1.3.2.1.1. http://www.aviationweather.gov/adds/tafs/ select the window for

METAR and TAF, and search KAFF for the USAFA Airfield and KCOS for the Colorado Springs Municipal Airport weather conditions.

1.3.2.1.2. http://www.USAFA.edu/tu/306ftg/oss/weather/

1.3.2.1.3. http://www.FAA.gov/pilots/flt_plan/NOTAMs/

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

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

1.3.2.4. The Ops Sup will be prepared to verbally brief the PIC for research sorties in lieu of preparing and delivering a formal briefing.

1.3.3. The Ops Sup arrives approximately 45 minutes before Mass Brief or scheduled research launch in order to ascertain the weather conditions, update the weather slide, and determine the status of the aircraft for the day’s flying. Additionally, the Ops

Sup must contact the 306 th

OG/SOF (333-1162) before flying begins and at flight termination. Confirm with the SOF any restrictions to flying during the scheduled period of flying and record the time and initials of the SOF on the Ops Sup radio communications log.

1.3.3.1. Review Aerial Events and weather information forwarded via email through the USAFA UAS/RPA Ops distribution list prior to calling the SOF.

1.3.4. The Ops Sup is responsible during flight operations for maintaining SA of operations, ensuring safety standards, observing weather trends and current weather, responding to emergencies.

1.3.5. For rapidly changing weather conditions call 306

th

FTG (333-2058) while maintaining awareness of current METAR/TAF and USAFA wind conditions by accessing HAWS at: http://hwas.usfa.edu/ http://www.aviationweather.gov/adds/tafs/ http://www.usafa.edu/tu/306ftg/oss/weather/ http://www.faa.gov/pilots/flt_plan/NOTAMs/

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 4

1.3.6. After mass brief, Ops Sup should review the Ops Sup Book to include all routine and contingency checklists.

1.3.7. Ops Sup prepares the notes for the end of day debrief conducted by the Sq CC

(CIC) or Ops Officer (Deputy CIC).

1.3.8. Ops Sup is responsible for properly securing the building, either by personally locking all doors or delegating this task to a RPA official.

1.4. Out-processing instructions

1.4.1. Ops Sup is responsible for Battlelab and AOC shut down at the end of the training period. Comply with all written instructions in the Ops Sup Book.

2. Mass Brief Procedures

2.1. Time Hack Slide

2.1.1. Accomplish time hack using http://time.gov/widget.html to provide accurate time

(use cell phone’s web-browser if no internet is available).

2.2. Mass Brief intro slide

2.2.1. Ensure proper date is displayed.

2.3. Admin slide

2.3.1. This slide is used to di splay the various positions not associated with specific sites or flying crews. These include: AOC OIC, Ops Sup, Safety officer, Area Safety officer, Recovery team members, and drivers.

2.4. Weather and NOTAMS

2.4.1. Use weather and NOTAM resources (given above) to fill out weather information.

Raw METAR and TAF data is required, but it is useful to provide bullet points outlining weather that applies specifically to RPA flight ops (wind direction, changing weather conditions, dew point spread).

2.5. Schedule Slides

2.5.1. These slides are to be filled out the night before the brief and are provided by

Scheduling. First, a general schedule slide is displayed showing show-times for instructors and students, along with other pertinent events such as academics or demonstrations.

2.5.2. The following scheduling slides are intended to be detailed and specific about the following information: date, site locations, assigned altitude blocks, site OIC, SUAS-http://time.gov/widget.html

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 5

Os, assigned driver, aircraft information (a/c number, operating frequency, and tracker frequency), student crews, and flight times.

2.6. Motherhood overview

2.6.1. Displays an overview of what is to come during the rest of the brief

2.7. Airspace and site slides

2.7.1. Shows all flight ops personnel the general location on USAFA grounds of the specific sites. Useful for maintaining SA and maintaining airspace deconfliction.

2.7.2. Specific site slides are used to show exactly where take off and recovery are to be accomplished. Also, important information about the sites is provided such as elevation, terrain features, and hazards.

2.8. Airspace deconfliction and intrusion of airspace.

2.8.1. These slides require only a restatement of safety and deconfliction procedures.

2.9. Mission overview slides

2.9.1. SAUS-O is designated to stand and brief students to a moderate level of detail as to how the mission is going to be accomplished. This includes training objectives and procedures.

2.10. ORM slide

2.10.1. Necessary to explain what ORM is and how it is accomplished to students.

Necessary to inform all flight operators of baseline ORM score.

2.11. Safety Plan

2.11.1. Assign specific locations to Site observers (SO) and Area Site Observer (ASO).

Should be a minimum of two SOs. More are required for specific missions (such as mobile, handoff, and night).

2.12. Questions

2.12.1. Answer questions and receive observations and critiques.

3. 306 th

OG Supervisor of Flying (SOF):

3.1. Contact SOF after mass brief and before stepping crews, # 333-1162.

3.2. Inform SOF of:

3.2.1. Flying Schedule for the day (Ops and Research).

3.2.2. Scheduled airspace and times.

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 6

3.2.3. Altitudes should be “standard IAW FCIF altitude CAPs” or IAW with temporary restrictions.

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

4. Aircrew Step Checklist.

4.1. Check:

4.1.1. DNIF status.

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

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

4.1.4. Ensure airspace is deconflicted.

4.1.5. Confirm with letter of X’s crew qualifications and Ops Limits/BF compliance.

4.2. Brief. (Appendix 1)

4.2.1. Current Operations Notes

4.2.2. NOTAMS / Airfield Advisories / AE Status / TFR’s

4.2.3. 306th Ops Considerations / Research-Ops Deconfliction / Frequencies / Airspace

4.2.4. METAR / TAF Changes / Trends

4.2.5. ORM Status

4.2.6. Site Binder

4.2.7. Situational EP Status

4.2.8. Crew, Equipment, & Vehicle accountability

4.2.9. PIC Sign Out on Flight Authorization Log – Responsibility for all site crew, equipment, & vehicle events

4.2.10. Ops Sup signs for PIC in event of verbal brief with verbal caveat of responsibility falling to PIC.

5. Continuing Duties.

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

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

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

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 7

5.1.3. At 15 kts notify the crews of the potential dangers over the LMR. Recommend crews recover if warranted.

NOTE: Continued Raven operations above 15 kts require the AV to remain upwind of waypoint E to prevent fly-away. Certain combinations of recovery location, wind, airspace and terrain could make this impossible. In such cases the Ops Sup will direct immediate recovery in the event the PIC fails to take appropriate action.

5.1.4. When HWAS indicate winds in excess of 20 kts, direct recovery of all RPA.

5.2. Ops Sup Activity Log. The Ops Sup will maintain a comprehensive activity log each duty day. At a minimum, this log will include all significant 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.3. Pass all status changes to the SOF.

5.4. Same day scheduling changes:

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

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

6. Ops Sup Changeover. NOTE: DO NOT changeover during an emergency.

6.1. Off Going Ops Sup.

6.1.1. Police the Ops Sup position and AOC.

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

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

6.2. On Coming Ops Sup.

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

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

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

6.2.4. Review the flying schedule.

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

6.2.6. Review continuing duties checklist for applicable duties.

6.3. Ops Sup Closing Checklist.

6.3.1. Account for all vehicles, equipment, and aircrews following flight.

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 8

6.3.2. Ensure all maintenance debriefs are completed as required.

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

6.3.4. Verify building cleanliness.

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

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

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

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

6.3.9. Verify all AV and GCS batteries are unplugged and stored in fire proof container.

6.3.10. Ensure the logistics room, AOC, and outdoor storage containers are locked.

6.3.11. Complete the Ops Sup Activity Log.

7. General Emergency Procedures (EP) Considerations

7.1. As with any aircraft incident, the PIC is expected to exercise judgment, apply appropriate procedures and when warranted, deviate from regulatory guidance if personnel are in immediate danger and deviation from guidance is the best solution to mitigate the risk. NOTE: This guidance is intended to augment, not replace flight manual procedures.

7.1.1. Refer to boldface when appropriate.

7.1.2. Consider sending an immediate Autoland command in the event of:

7.1.2.1. Any potential mid-air collision with a manned aircraft

7.1.2.2. The AV is leaving the approved area

7.1.2.3. The AV presents an immediate hazard to personnel or equipment

7.1.2.4. Unusual AV malfunction and/or erratic behavior

7.1.3. Reporting Requirements: See Figure 9.1, 9.2 and 9.3

7.2. Emergency checklists

7.2.1. Manned Aircraft Collision

7.2.2. Fly Away

7.2.3. Lost AV

7.2.4. Offsite Landing

7.2.5. Failed Launch

7.2.6. FPCON Increase / Terrorist Threat

7.2.7. Wild Animal Close To Site

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 9

7.2.8. Environmental Threat

7.2.9. Communications Failure

7.2.10. Weather Recall

7.3. Manned Aircraft Collision

7.3.1. Under no circumstances give identity of persons involved over the telephone, radio or “brick.”

7.3.2. Ensure SOF is notified.

7.3.3. Notify program Director and OIC of the incident.

7.3.4. Ground all other RPA as soon as conditions permit.

7.3.5. Post door guards to prevent RPA personnel from leaving the building. Personnel on official business may enter. Appoint an individual to confiscate all cell phones as personnel enter room. Appoint a troop commander (preferably officer). Disposition of personnel to be decided by Director.

7.3.6. Impound: (with a witness, place the following items in a sealed envelope for safety).

7.3.6.1. TFEF.

7.3.6.2. Student training folder/ETA records as required.

7.3.6.3. IP training records.

7.3.6.4. Insure appropriate logistics/maintenance personnel impound maintenance records.

7.3.6.5. Call cadet clinic and ensure they impound medical records.

7.3.6.6. Ops Sup log.

7.3.6.7. Ops notes.

7.3.7. Hold a unit meeting as appropriate.

7.3.8. Refer all inquiries to HQ USAFA/PA (333-4040).

7.4. Fly-away

7.4.1. Send Autoland command “in the blind” (Consider using directional patch antenna, but do not delay sending Autoland command in order to reconfigure the omni).

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 10

7.4.2. Notify the Ops Sup. Tell the Ops Sup the last known position, altitude, direction of flight, and remaining battery flight time. Ensure the Ops Sup notifies the SOF immediately.

7.4.3. Complete the lost AV checklist.

7.4.4. Ops Sup will direct the recovery of any other airborne SUAS.

7.4.5. Complete the “SUAS Mishap Worksheet” (See Figure 9.1).

7.4.5.1. Be as complete and accurate as possible.

7.4.5.2. Provide any other information that might relevant.

7.4.6. Complete Off Site Landing checklist as appropriate.

7.4.7. Return to the AOC.

7.5. Lost AV

7.5.1. This checklist is intended for use when the AV lands anywhere other than “L” with its whereabouts unknown.

7.5.2. If the AV is still airborne but you have lost your link:

7.5.2.1. Send Autoland Command.

7.5.2.2. Execute the lost link procedure.

7.5.2.3. Reacquire the AV; if unable, execute the fly away checklist

7.5.3. Keep GCS powered

7.5.3.1. Note last known AV location

7.5.3.2. Estimate AV location

7.5.3.2.1. If you have a link you have the current AV location

7.5.3.2.2. Do you have imagery? Can you tell if the AV is in a tree?

7.5.3.2.3. SO will note mag bearing to the AV last observed position

(compass in field kit)

7.5.3.2.4. Determine whether ASO was in visual contact at the time of loss

7.5.3.2.5. Remaining estimated flight time

7.5.3.3. Plot estimated location of the AV on the USAFA V877S map

7.5.3.4. Support the AV Recovery team and “standby for further instructions”

7.5.4. Contact Ops Sup: If operations spill out of the assigned airspace or a Loss-of-Link

(LOL) condition occurs and the UA does not return to the designated return home

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 11 point, contact the Ops Sup as soon as possible and provide the following information to the controlling agency:

7.5.4.1. SUAS RQ-11 Raven DDL / tail number

7.5.4.2. Last known location and time of LOL

7.5.4.3. Heading, altitude, and airspeed

7.5.4.4. Estimated flight time remaining

7.5.4.5. Is the AV likely within USAFA boundaries?

7.5.4.6. Estimated location

7.5.4.7. Confirm the AV recovery team is mobilized

7.5.4.8. Confirm all other SUASs have been recovered

7.5.5. Contact the AV recovery team

7.5.5.1. Ensure team has accurate FalconTracker frequency and coordinates

7.5.5.2. Ops check backup FalconTracker, as required, before recovery team departs

7.5.5.3. Conduct visual search of the suspected loss location if no FalconTracker signal is available

7.5.5.4. Corroborate all eye witness accounts to further refine AV location.

7.5.6. Complete “SUAS Mishap Worksheet” (See Figure 3.1)

7.5.7. Launch backup AV as required (coordinate with Ops Sup)

7.6. Offsite landing

7.6.1. Aircrews contact Ops Sup in the event of an offsite landing

7.6.2. If AV is outside USAFA property notify the Director immediately

7.6.3. Coordinate to have aircraft retrieved by the AV recovery lead

7.6.4. Record unscheduled landing in the Ops Sup log

7.6.5. Notify program Director or OIC

7.7. Failed launch

7.7.1. Notify Ops Sup

7.7.2. Fully inspect AV, repair damage as required

7.7.3. Log failed launch in the AV log, providing details in the comments block

7.7.4. Conduct full preflight checklist prior to initiating subsequent launch

7.8. FPCON Increase / Terrorist Threat

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 12

7.8.1. When an FPCON condition is declared via Giant Voice or email, notify program

Director

7.8.2. Comply with Command Post or DFE instructions

7.9. Wild Animal Close To Site

7.9.1. Notify Ops Sup of the situation

7.9.2. Proceed with caution

7.9.3. If necessary, move personnel to the vehicle and allow dangerous animal to leave the area

7.9.4. If the animal becomes a threat, do not provoke the animal

7.9.5. Do not confront bears or other large animals

7.10. Environmental Threat (e.g. fire, tornado, etc.)

7.10.1. Notify program Director and OIC

7.10.2. Secure building, closing doors and windows

7.10.3. Disconnect or turn off all unnecessary electrical equipment

7.10.4. Restrict telephone calls

7.10.5. Remain indoors as much as possible

7.10.6. If at a site, pack equipment as soon as possible and leave for the nearest shelter as soon as conditions permit

7.10.7. If time is not available, preservation of life takes first priority at all times

7.10.8. If directed, initiate personnel recovery to primary shelter (cadet gym)

7.10.9. No warning: shelter in place

7.11. Communications failure: If unable to communicate with the Ops Sup

7.11.1. Attempt contact through other site, ASO, etc.

7.11.2. Attempt to contact the Ops Sup via cell phone

7.11.3. Attempt to contact the OIC or other key personnel via cell phone (see key personnel phone roster in appendix)

7.11.4. Consider dispatching a runner to the AOC if communication is vital

7.11.5. The site lead may authorize launch without Ops Sup approval, conditions permitting

7.11.5.1. Must have the ability to contact the SOF via cell phone

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 13

7.11.5.2. Consider ORM factors such as scheduled hazards, number of AVs operating, nature of mission (vertical maneuvering?), weather trends, etc.

7.11.5.3. If in doubt, recover the AV or delay launch

7.12. Weather recall: If deteriorating weather conditions require a recall:

7.12.1. Notify the OIC/Director of the decision to recall if not already aware

7.12.2. Transmit the recall status to all aircrews

7.12.3. Coordinate to have AV recovered as soon as conditions permit

7.12.4. Instruct air crews to return to AOC as required, unless flying is expected to resume and no threat exists

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 14

FIGURE 7.1

SUAS MISHAP WORKSHEET

NOTE

1. This worksheet should be completed in the field, whenever there is an incident that involves the loss of a SUAS, damage that renders the SUAS non-repairable/non-recoverable, or an injury incurred as a result of SUAS operation. Use standard security markings and classified handling procedures for classified reports.

1. Owning Unit: _________________________________________________________

2. Date of loss _____________________ (DD/MO/YR) Time_________ (Local/Zulu)

3. Type of system: _________________________________________________________

4. Recovered: ________________________ Not recovered: ________________________

5. Site/location of incident: _______________MSL altitude of GCU ______________

6. Map sheet reference number: _____________________________________________

7. UA (or lost/destroyed item) fuselage number: ___________________________

8. Flight Log information:

8.1. Unit_________________________

8.2. Channel: _______

8.3. GPS Keyed: ______Y_______N____

8.4. Launch Time: _______

8.5. Land/Crash Time: _________

8.6. Duration of Flight: ________

8.7. Weather Conditions: __________ Temperature: ____Wind Speed: ____

8.7.1. Illumination:_____________________________

8.7.2. Precipitation:_____________________________

8.7.3. Clouds:_________________________________

8.8. Wind Direction: ___________

8.9. Lighting: Night _____ Dawn ____ Day _____ Dusk_____

8.10. GCU#________

8.11. RVT#_________

8.12. UA Battery type:

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 15

8.13. Camera Type: _____Day _____F/L _____Night _____S/L Night

8.14. Other:_____________________________________________

9. Crew information

9.1. PIC / SUAS-O (Name, Rank, SSN):____________________________

9.2. Date/location of PIC / SUAS-O completion of certified training:

9.3. __________________________________________

9.4. Mission Controller (Name, Rank, SSN): _____________________ AFI11-502V3

9.5. Date and location of MC completion of certified training:

10. Circumstances:

10.1. Origin/launch site: _______________________________

10.2. Mission: _______________________________________

10.3. Launch problem: ________

10.4. Landing problem: ________

10.5. Problem during flight: ____________________________

10.6. [Raven] Fight mode at time of loss: M___ A ___ H___ L___ N___

10.7. NOTE: M=Manual, A=Autopilot, H=Hover, L=Loiter, N=Night

10.8. Commanded altitude or throttle setting: _______________

10.9. Air vehicle altitude above ground (AGL): _______________Feet

10.10. Air vehicle heading: _______________ Degrees magnetic

10.11. Last known UA location: __________________________

10.12. Rally point location and altitude: ____________________

10.13. Loss-of-Link indications: __________________________

10.14. GPS startup problems: ____________________________

10.15. Previous problems/maintenance issue that may have contributed:

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 16

11. Flight recorded/taped? Y/ N Location of data ______________

12. Summary of mishap and damage:

13. Actions taken upon/after loss (search pattern used, number of searchers, duration of search, use of aircraft to assist, etc.): _________________________________________________

14. Damage

14.1. Aircraft: _____________________________________________

14.2. DoD property damage: _____________________________________

14.3. Private property damage____________________________________

15. Injuries

15.1. Names of injured person: ___________________________________

15.2. Status/extent of injuries: ____________________________________

15.3. Actions at time of injury: ___________________________________

16. Witnesses: (Name, Rank, SSN and role (i.e., RVT Data Capture, SUAS Team Leader, etc.)____________________________________________________________________

17. Worksheet completed by:

17.1. Name/Rank: _______________________

17.2. Unit/Office Symbol: _________________

17.3. Duty Phone: _______________________

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 17

FIGURE 7.2

INCIDENT INVESTIGATING & REPORTING

1. An incident is an event resulting in damage to equipment exceeding $20,000; recordable injury; or unusual occurrence warranting a permanent record for future reference.

2. Refer to AFI 91-204, AFMAN 91-223, and USAFA UAS/RPA Safety Continuity Binder.

3. Notify the Ops Sup, request medical support if required

4. If the incident involves injury to personnel, or likely resulted in greater than $20,000 but less than $50,000 damage to equipment (Class D):

4.1. Complete a SUAS Mishap Worksheet prior to resumption of training

4.2.Ensure OIC / Director is notified

4.3.Site lead will initiate initial investigation

4.4.Preserve data prior to disconnecting GCS power

4.5.Save AV screener data

5. Ops Sup will determine:

6. Whether to notify the 306th FTG SOF and USAFA Safety Office

7. If/when to resume training

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 18

FIGURE 7.3

OPREP-3B REPORTING

1. OPREPs provide senior commanders up to CSAF immediate notification of serious events.

Any serious incident could require an OPREP. The Director will work with 10 th

ABW/CP to determine whether an OPREP is required

2. AFI 10-206 Operational Reporting, para. 3.2.12. BEELINE (OPREP-3B).

3. Gather the relevant information for the incident/event (i.e. who, what, where, why, how)

4. Using the example below, complete a rough draft OPREP-3B

5. Send individual reportable events in separate OPREPs

6. Forward the rough draft write-up to the OIC / Director

7. When approved by the Director, forward a courtesy copy to DFE, Gen McCarthy, the Dean and the 306 FTG/CC

8. Upon review / approval from the Director, forward the OPREP-3B to 10 th

ABW Command

Post organizational email address

9. Example: BEELINE OPREP-3B: unusual aircraft incident, USAF Academy. On 02 Dec, at

2102z, an RQ-11 Raven DDL experienced a flyaway. The Raven was subsequently located and retrieved on private property approximately 5 miles northeast of the academy. The aircrew consisted of two cadet small unmanned aerial systems operators. All RPA activities are currently grounded pending further investigation. Media and FAA attention is anticipated. This is a command post final report.

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 19

8. Airspace Description: The RPA airspace at USAFA is defined by the FAA-DoD MOA that allows for SUAS to fly within class G airspace up to 1200’ AGL depending on class E airspace restrictions. This airspace has been further refined through agreements with the th

Operations Group that operates out of the USAFA airfield that restricts RPA operations to the area depicted in Figure 8.1 when the USAFA tower is in operation. When the tower is not in operation, all airspace defined by the lateral confines of the USAFA military installation reverts to class G airspace and is available for SUAS operations other than populated areas.

FIGURE 8.1

USAFA RPA AIRSPACE

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 20

8.1. Site: Stillman restrictions and procedures (See Figure 10.2)

8.1.1. Standard diamond, 0.2KM range

8.1.2. GCS should be as far east as practical.

8.1.3. No flight west of the stadium.

8.1.4. No flight over parking lot or structures.

8.1.5. Bearing to E must avoid all structures, approximately 225 degrees through 345 degrees depending on L placement. NOTE: May require crosswind approach and landing if LOL.

8.1.6. Tues and Thurs: No afternoon ops.

8.1.7. Contact Ops Sup if any maintenance or other users.

FIGURE 8.2

USAFA SITE STILLMAN

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 21

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 22

8.2. Site: Flicker restrictions and procedures (See Figure 8.3).

8.2.1. GCS should be set up as far east as possible.

8.2.2. Use caution when setting bearing to E to avoid the cadet area and the mountains.

NOTE: May require crosswind approach and landing if LOL.

8.2.3. Ridgeline at ~400 meters west.

8.2.4. Rising terrain at northwest corner.

8.2.5. ~300 ft Ridgeline at north.

8.2.6. ~30 ft tree at south edge.

8.2.7. Use extreme caution when athletic fields are in use—Flicker should only be used if western athletics fields are inactive.

FIGURE 8.3

USAFA SITE FLICKER

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 23

8.3. Site: Warrior restrictions and procedures (See Figure 8.4).

8.3.1. Check terrain clearance when establishing bearing to E. Bearings near 360 could place AV outside USAFA, depending on winds and location of L.

8.3.2. Avoid rocky drainage ditch southwest to northeast at center.

8.3.3. ~35 ft trees at northwest quadrant.

8.3.4. 50 ft trees at north and east edge.

8.3.5. Ditch running southwest to northeast at the southeast quadrant.

8.3.6. Possibility of gas mask training—gas masks available for use from NCOIC.

8.3.7. Contact Ops Sup if training activity in the vicinity.

FIGURE 8.4

USAFA SITE WARRIOR

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 24

8.4. Site: Smack restrictions and procedures (See Figure 8.5).

8.4.1. Not available during BCT Jack’s Valley training.

8.4.2. 30 ft square building at west edge of road, track with raised signs at south half of area.

8.4.3. Rising terrain with trees at northwest.

8.4.4. North to south power line at east edge; dirt road parallel to power line.

8.4.5. ~45 ft trees at south edge.

FIGURE 8.5

USAFA SITE SMACK

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 25

8.5. Site: Aardvark restrictions and procedures (See Figure 8.6).

8.5.1. Do not fly east of the north-south axis of the eastern edge of the Aardvark runway.

8.5.2. In order to keep E to L west of runway there may be a requirement to execute a crosswind approach and landing if winds are unfavorable for a normal headwind approach.

8.5.3. ~20 ft trees to the east and west approximately 125 ft from runway.

8.5.4. Maintain vigilance for diverting sailplanes and research SUAS operations.

FIGURE 8.6

USAFA SITE AARDVARK

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 26

8.6. Site: Buff restrictions and procedures (See Figure 8.7).

8.6.1. Avoid B-52 and public area to the north and west of launch area.

8.6.2. Park in helo pad and set up “DO NOT ENTER” sign.

8.6.3. Politely ask any tourists to remain clear of the GCS at all times.

8.6.4. Deliberately clear for civilians prior to launch and recovery.

8.6.5. Very open and level field. ~40 ft trees at north and south edge of the site.

FIGURE 8.7

USAFA SITE BUFF

USAFA SUAS Operations Supervisor Operating Instruction 1 January 2014 27

APPENDIX I

USAFA RPA TELEPHONIC STEP BRIEFING

1. Current Operations Notes

2. NOTAMS / Airfield Advisories / AE Status / TFR’s

3. 306 th

Ops Considerations / Research-Ops Deconfliction / Frequencies / Airspace

4. METAR / TAF Changes / Trends

5. ORM Status

6. Site Binder

7. Situational EP Status

8. Crew, Equipment, & Vehicle accountability

9. PIC Sign Out on Flight Authorization Log – Responsibility for all site crew, equipment, & vehicle events

10. Ops Sup signs for PIC in event of verbal brief with verbal caveat of responsibility falling to PIC.