Appendix_7_USAFA_UAS_OI_VOL_3_2_20140601.pdf

USAFA SUAS OI VOL 3.2 1 June 2014 1

USAFA SUAS OI V3.2

BY ORDER OF THE DIRECTOR OF STAFF, DEAN OF FACULTY

1 Jun 2014

OPERATIONS Chapters 6-10

SMALL UNMANNED AIRCRAFT SYSTEMS (SUAS)

OPERATING INSTRUCTION

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

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

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: 1 December 2013 This instruction provides basic principles and knowledge to enable USAFA RPA 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

A change to the procedures used for handoff missions is included together with minor formatting changes.

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

2 1 December 2013 USAFA SUAS OI VOL 3.2

Chapter 6

EMERGENCY PROCEDURES

6.1. General Emergency Procedures (EP) Considerations

6.1.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.

6.1.2. Refer to boldface when appropriate.

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

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

6.1.3.2. The AV is leaving the approved area.

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

6.1.3.4. Unusual AV malfunction and/or erratic behavior.

6.1.4. Reporting Requirements: See Figure 6.1, 6.2 and 6.3.

6.2. Emergency checklists

6.2.1. Manned Aircraft Collision.

6.2.2. Fly Away.

6.2.3. Lost AV.

6.2.4. Offsite Landing.

6.2.5. Failed Launch.

6.2.6. FPCON Increase / Terrorist Threat.

6.2.7. Wild Animal Close To Site.

6.2.8. Environmental Threat.

6.2.9. Communications Failure.

6.2.10. Weather Recall.

6.3. Manned Aircraft Collision

6.3.1. Under no circumstances give identity of persons involved over the telephone, radio or

“brick.”

USAFA SUAS OI VOL 3.2 1 June 2014 3

6.3.2. Ensure SOF is notified.

6.3.3. Notify program Director and OIC of the incident.

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

6.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.

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

6.3.6.1. TFEF.

6.3.6.2. Student training folder/ETA records as required.

6.3.6.3. IP training records.

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

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

6.3.6.6. Ops Sup log.

6.3.6.7. Ops notes.

6.3.7. Hold a unit meeting as appropriate.

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

6.4. Fly-away

6.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).

6.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.

6.4.3. Complete the lost AV checklist.

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

6.4.5. Complete the “SUAS Mishap Worksheet” (See Figure 6.1).

6.4.5.1. Be as complete and accurate as possible.

6.4.5.2. Provide any other information that might relevant.

6.4.6. Complete Off Site Landing checklist as appropriate.

6.4.7. Return to the AOC.

4 1 December 2013 USAFA SUAS OI VOL 3.2

6.5. Lost AV

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

6.5.2. If the AV could still be airborne but you have lost your link:

6.5.2.1. Send Autoland Command.

6.5.2.2. Execute the lost link procedure.

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

6.5.3. Keep GCS powered.

6.5.3.1. Note last known AV location.

6.5.3.2. Estimate AV location.

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

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

6.5.3.2.3. SO will note mag bearing to the AV last observed position (compass in field kit).

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

6.5.3.2.5. Remaining estimated flight time.

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

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

6.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 point, contact the Ops

Sup as soon as possible and provide the following information to the controlling agency:

6.5.4.1. SUAS RQ-11 Raven DDL / tail number.

6.5.4.2. Last known location and time of LOL.

6.5.4.3. Heading, altitude, and airspeed.

6.5.4.4. Estimated flight time remaining.

6.5.4.5. Is the AV likely within USAFA boundaries?

6.5.4.6. Estimated location.

6.5.4.7. Confirm the AV recovery team is mobilized.

6.5.4.8. Confirm all other SUASs have been recovered.

6.5.5. Contact the AV recovery team.

6.5.5.1. Ensure team has accurate FalconTracker frequency and coordinates.

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

USAFA SUAS OI VOL 3.2 1 June 2014 5

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

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

6.5.6. Complete “SUAS Mishap Worksheet” (See Figure 6.1).

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

6.6. Offsite landing

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

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

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

6.6.4. Record unscheduled landing in the Ops Sup log.

6.6.5. Notify program Director or OIC.

6.7. Failed launch

6.7.1. Notify Ops Sup.

6.7.2. Fully inspect AV, repair damage as required.

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

6.7.4. Conduct full preflight checklist prior to initiating subsequent launch.

6.8. FPCON Increase / Terrorist Threat

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

Director.

6.8.2. Comply with Command Post or DFE instructions.

6.9. Wild Animal Close To Site

6.9.1. Notify Ops Sup of the situation.

6.9.2. Proceed with caution.

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

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

6.9.5. Do not confront bears or other large animals.

6 1 December 2013 USAFA SUAS OI VOL 3.2

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

6.10.1. Notify program Director and OIC.

6.10.2. Secure building, closing doors and windows.

6.10.3. Disconnect or turn off all unnecessary electrical equipment.

6.10.4. Restrict telephone calls.

6.10.5. Remain indoors as much as possible.

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

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

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

6.10.9. No warning: shelter in place.

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

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

6.11.2. Attempt to contact the Ops Sup via cell phone.

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

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

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

6.11.5.1. Verify the ability to contact the SOF via cell.

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

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

6.12. Weather recall

6.12.1. If deteriorating weather conditions require a recall:

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

6.12.1.2. Transmit the recall status to all aircrews.

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

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

USAFA SUAS OI VOL 3.2 1 June 2014 7

FIGURE 6.1

SUAS MISHAP WORKSHEET

NOTE

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:

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

8.14. Other:_____________________________________________

8 1 December 2013 USAFA SUAS OI VOL 3.2

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. Mission Controller (Name, Rank, SSN): _____________________ AFI11-502V3

9.4. 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:

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.): _________________________________________________

USAFA SUAS OI VOL 3.2 1 June 2014 9

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: _______________________

10 1 December 2013 USAFA SUAS OI VOL 3.2

FIGURE 6.2

INCIDENT INVESTIGATING & REPORTING

1. A reportable incident may be any event resulting in irreparable damage to the AV; damage to government or personal property; personal injury; or any unusual occurrence such as uncommanded AV behavior warranting a permanent record for future reference.

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

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

4. Notify unit safety representative to determine if further investigation and/or reporting is required. In the case of any event potentially meeting the above criteria:

4.1.Complete a SUAS Mishap Worksheet.

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 based on unit safety representative’s counsel whether to notify the 306th FTG SOF and USAFA Safety Office; and whether to resume training.

FIGURE 6.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 10th 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 10th 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 OI VOL 3.2 1 June 2014 11

Chapter 7

RADIO PROCEDURES

7.1. For all radio communications use the site name as the callsign. In the following examples, the location is site “Warrior.”

7.2. Basic terminology:

7.2.1. “Roger” or “Copy” – I have received your transmission and understand.

7.2.2. “Affirmative” – Yes.

7.2.3. “Negative” – No.

7.2.4. “WILCO” – I understand and will comply with your instructions.

7.2.5. “Say Again” – Please repeat last transmission.

7.2.6. Basic format: “[Receiver Callsign], this is [Transmitter Callsign] [request/statement].”

7.3. LMR Channel 1 is the primary operations frequency. If you require a discreet channel in order to have an extended conversation, Channel 2 is available, e.g., “Roost, Warrior, push 2.”

“Warrior Channel 2.”

7.4. Checking in on site.

7.4.1. “Roost this is Warrior on site.”

7.4.2. “Warrior, Roost copies.”

7.5. Radio Check

7.5.1. “Roost this is Warrior, radio check.”

7.5.2. “Warrior, Roost, loud and clear.”

7.6. Launch Clearance

7.6.1. “Roost, Warrior is Ops Normal, winds XX0 at XX knots, requesting launch clearance.”

7.6.2. “Warrior, launch approved.”

7.6.3. “Roost, Warrior is launch approved.”

7.7. After Landing

7.7.1. “Roost, Warrior on the. Code X.”

7.7.1.1 Code 1: Aircraft status is green, no MX needed.

7.7.1.2 Code 2: Aircraft status is yellow, minor field repairs required that could delay launch.

7.7.1.3 Code 3: Aircraft status is red, damaged beyond what can be repaired in the field.

7.7.2. “Warrior, Roost copies.”

7.8. End of the day, after landing.

7.8.1. “Roost, Warrior is on the deck, terminating ops, Code X, returning to the AOC.”

7.9. AV Collision with Another Aircraft.

7.9.1. “Roost, Warrior, aircraft collision. Collision is at (location). Altitude (altitude). AV was traveling (direction). Type of manned aircraft (high wing, low wing, single engine) was flying (direction). Status of manned aircraft (status). Status of Warrior AV is (AV status).”

7.9.2. “Warrior, Roost acknowledges, contacting SOF.”

12 1 December 2013 USAFA SUAS OI VOL 3.2

7.10. AV Causes Damage to Personnel or Property.

7.10.1. "Roost, Warrior, pedestrian/property collision at (location). [Request paramedics etc.]"

7.10.2. "Warrior, Roost acknowledges, contacting SOF [fire department/safety/paramedics, etc.]"

7.11. Lost Sight and Link.

7.11.1. Last data capture and record

7.11.2. "Roost, Warrior, lost AV. Last known location was [give location], attempting auto land.”

7.11.3. Or: “Roost, Warrior, offsite landing. Auto land successful at location (location).”

7.12. Can't Contact Ops Sup.

7.12.1. Cell phone call—see contacts list.

7.12.2. Call DO or Sq CC (whoever is not Ops Sup).

7.13. Launch Failure or Delay.

7.13.1. “Roost, Warrior is unable to launch due to (problem).”

7.13.2. “Roost copies.”

USAFA SUAS OI VOL 3.2 1 June 2014 13

Chapter 8

RAVEN SPECIFIC PROCEDURES

8.1. Required equipment:

8.1.1. AV Case

8.1.1.1. Two GCSs and at least 2 AVs

8.1.2. Field Kit (Case)

8.1.2.1. Toughbook with transformer and cord

8.1.2.2. Compass

8.1.2.3. Wind Meter

8.1.2.4. SUAS Handbook

8.1.2.5. This OI, Volumes 1-3.

8.1.2.6. Training sortie instructor guides

8.1.2.7. Site surveys

8.1.2.8. Incident Reporting Sheet

8.1.2.9. Training day log

8.1.2.10. USAFA Map V877S

8.1.2.11. NVGs

8.1.2.12. GPS

8.1.2.13. Flashlight

8.1.2.14. 5 Headlights

8.1.2.15. Gaffer’s tape

8.1.2.16. 3 fully charged GCS batteries

8.1.2.17. Field repair kit

8.1.2.18. Inverter

8.1.2.19. Vehicle antenna kit

8.1.2.20. 2 FalconTracker transmitters with batteries.

8.1.2.21. Stakes: 4 AV, 4 Tent

8.1.2.22. Mallet

8.1.2.23. Helmet

8.1.2.24. Safety Glasses

8.1.2.25. External Monitor

8.1.3. Other Require Site Equipment

8.1.3.1. 5 fully charged AV batteries

8.1.3.2. Generator

8.1.3.3. Reel with extension cord

8.1.3.4. Other required site equipment:

8.1.3.5. EZ Up

8.1.3.6. 5 Chairs

8.1.3.7. 2 Tables

8.1.3.8. Mobile launch harness, if planned

8.1.4. ASO Kit:

8.1.4.1. Ruck

14 1 December 2013 USAFA SUAS OI VOL 3.2

8.1.4.2. Compass

8.1.4.3. Sunscreen

8.1.4.4. Binoculars

8.1.4.5. LMR

8.1.4.6. USAFA Map V877S

8.1.5. AV Recovery Team Kit

8.1.5.1. All contents of the ASO kit.

8.1.5.2. FalconTracker receiver

8.2. Training Day Log

8.2.1. Each crew will maintain a training log for their site issued by the Training Officer.

8.2.2. Logs will be returned to the AOC upon completion of the training day.

8.3. Training Sortie Guides

8.3.1. These sortie outlines provide standard Tactics, Techniques and Procedures (TTPs) that should be used during all instructional sorties.

8.3.2. Instructors are authorized to work through the AOC to provide support to ESET, CST, Polaris Warrior, etc., as long as support can be integrated into the training syllabus in such a way as to enhance rather than detract from training.

8.3.3. Integration with other training programs should normally be limited to strong students.

8.3.4. Ensure all students meet all maneuver requirements.

8.4. Demo

8.4.1. For the demo flight, two SUAS-Is will set up a site to the point where the waypoints are verified.

8.4.2. The students will then observe execution of the remaining checklist items, a launch, several maneuvers from the Intro flight (e.g., tear drops, box patterns, loiter), followed by an autonomous recovery.

8.4.3. If conditions do not permit an autonomous recovery, a manual recovery will be flown.

8.4.4. SUAS-Is will then demonstrate proper aircraft recovery techniques, concluding the demo flight.

8.5. Throw Practice

8.5.1. Throw practice will normally be conducted at Stillman, with as many throw birds as available.

8.5.2. If a baseball bat is available, SUAS-I’s will demonstrate proper throw technique with the bat followed by student practice and critique.

8.5.3. Students will then take turns throwing the throw birds until they have mastered the throw technique.

8.5.4. This is usually a good time to demonstrate a few field maintenance items such as screw replacement.

8.6. Intro Flight (30 minutes each student, each crew position)

8.6.1. Launch / MAN / 200 – 300 / HOME.

8.6.2. Heads Up (App 15 min).

USAFA SUAS OI VOL 3.2 1 June 2014 15

8.6.2.1. ALT Mode to assign ALT.

8.6.2.2. Tear Drop.

8.6.2.3. Box Pattern.

8.6.2.4. 360* turn.

8.6.2.5. Dash / Hold.

8.6.2.6. LOITER.

8.6.2.7. NAV – ABCD 1 Lap.

8.6.2.8. HOME (Both Methods).

8.6.3. Heads Down (App 15 min).

8.6.3.1. ALT Mode ensure assign ALT.

8.6.3.2. Box Pattern.

8.6.3.3. 360* turn.

8.6.3.4. Dash / Hold.

8.6.3.5. LOITER.

8.6.3.6. NAV – ABCD 1 Lap.

8.6.3.7. Tear Drop.

8.6.3.8. Target Deliberate Offset.

8.6.3.9. “Go Around” Landing.

8.6.4. Nav E-L Autonomous landing.

8.7. Falcon View Flight (60 minutes)

8.7.1. Launch / MAN / 200 – 300 / HOME.

8.7.2. MO - RSTA (App 20 min).

8.7.2.1. NAV Mode @ Assigned Alt.

8.7.2.2. Image capture during flight.

8.7.2.3. Range and Bearing tool.

8.7.2.4. Orbit Target – ALT Mode.

8.7.2.5. Drag /Drop Waypoints/Orbit points.

8.7.2.5.1 Orbits moved via Mission Planning.

8.7.2.5.2 Via MGRS / Range and Bearing.

8.7.2.6. Adjust Altitude via Mission Altitude Control.

8.7.2.7. Linear Target via ABCD Leap Frog.

8.7.2.8. Linear Target via ABCD Box.

8.7.2.9. MGRS/Latitude-Longitude switch.

8.7.2.10. Save Imagery as JPEG as needed.

8.7.3. High Level Landing (Go Around or Land at 30 min total flight time).

8.7.3.1. 800 ft AGL Minimum.

8.7.3.2. With wind/Into wind/Stair Step.

8.7.3.3. Go Around – Hot Key/throttle NLT 200 ft AGL.

8.7.4. Crew swap, repeat.

16 1 December 2013 USAFA SUAS OI VOL 3.2

8.7.5. Last approach = Land.

8.8. Hand Off’s (15 minutes desired each student at each crew position)

8.8.1. This sortie will consist of a handoff to forward location(s) in order to accomplish mission requirements, followed by a return to launch site.

8.8.2. The AV handoff to subsequent sites and/or launch site will be accomplished for mission and operational considerations.

8.8.3. The AV will be landed by the launch and recovery crew IAW operational limitations.

Within the available flight time students will endeavor to execute the mission from each crew position to the extent possible.

8.8.4. Handoff Out.

8.8.4.1. Launch / MAN / 200 – 300 / Assigned Alt.

8.8.4.2. Alt Mode to Rev. Azimuth To overhead.

8.8.4.3. Handoffs.

8.8.4.3.1 Ensure Comms with other site.

8.8.4.3.2 AV# / Flight Alt / Channel / Location / FT freq.

8.8.4.3.3 Hand off.

8.8.5. Tactical.

8.8.5.1. Alt Mode to Rev. Azimuth To overhead.

8.8.5.2. Options.

8.8.5.2.1 Scan for a target (Raster/grid/perimeter, etc.).

8.8.5.2.2 Find a target based on MGRS coordinates.

8.8.5.2.3 Covert approach/departure.

8.8.5.2.3.1. Downwind in / Downwind out.

8.8.5.2.3.1.1. ALT Mode Option.

8.8.5.2.3.1.2. Man Mode Option.

8.8.5.2.3.2. Upwind in / Optional Direction out.

8.8.5.2.3.3. Orbit Point technique.

8.8.5.2.4 Road clearing.

8.8.5.2.5 Vehicle following.

8.8.6. Handoff back.

8.9. Night

8.9.1. Launch / MAN / 200 – 300 / Assigned Alt.

8.9.2. Alt Mode to Rev. Azimuth To overhead / Home.

8.9.3. Target Acquisition (app 31-50 min, opportune with ESET if able).

8.9.3.1. NAV Mode @ Assigned Alt.

8.9.3.2. Image capture during flight.

8.9.3.3. Range and Bearing tool.

USAFA SUAS OI VOL 3.2 1 June 2014 17

8.9.3.4. Orbit Target – ALT Mode.

8.9.3.5. Drag /Drop Waypoints.

8.9.3.6. Orbits moved via Mission Planning.

8.9.3.7. Via MGRS / Range and Bearing.

8.9.3.8. Adjust Altitude via Mission Altitude Control.

8.9.3.9. Linear Target via ABCD Leap Frog.

8.9.3.10. Linear Target via ABCD Box.

8.9.3.11. Save Imagery as JPEG as needed.

8.9.4. Nav E-L Autonomous landing (Illuminator Off).

8.10. Mobile

8.10.1. Launch / MAN / 200 – 300 / Assigned Alt.

8.10.2. Alt Mode to Rev. Azimuth To overhead / Home.

8.10.3. Mobiles.

8.10.3.1. Find/Fix/Track Vehicle in Front /Side.

8.10.3.2. HOME changed X 2 minimum.

8.10.4. Landing – Heads Up / MAN or ALT.

8.11. Field Site Normal Procedures

8.11.1. The first crew to arrive at a training site will assemble the site using the “Site Survey and Setup” checklist of the Raven DDL Operator’s Manual, with the last crew tearing it down and conducting final inspections using the “Post-Flight Procedures” checklist.

8.11.2. Insure all equipment is ready for flight.

8.11.3. Set up FalconView using procedures at Para 8.12 below.

8.11.4. Each crew will run the “Pre-Flight Checks”.

8.11.5. Following each training sortie:

8.11.5.1. The off-going crew will remove both the GCS and AV batteries.

8.11.5.2. Site lead will complete the site activity log for the completed sortie to include takeoff and land times, IP and crew names, training accomplished, maintenance status, debrief notes.

8.11.5.3. The oncoming crew will insert fresh batteries in the AV and GCS.

8.12. Site Arrival Checklist (Once Per Day)

8.12.1. VO: notify OPS SUP on Ch 1.

8.12.2. Conduct initial site survey (all).

8.12.2.1. VO / MO: Assess impact of winds and terrain.

8.12.2.2. Select “+” location (ensure clear path upwind “E” to “L”).

8.12.2.3. Select GCS location.

8.12.3. Equipment – assemble.

8.12.3.1. Begin charging batteries.

8.12.3.2. Orient site to mag north.

8.12.3.3. AV – assemble (VO/MO).

8.12.3.4. GCS – assemble (VO/MO).

18 1 December 2013 USAFA SUAS OI VOL 3.2

8.12.4. AV logbook and site training day log – initiate (Site Lead).

8.12.4.1. FalconTracker – check (MO).

8.12.4.2. Preflight briefing (lead instructor).

8.12.4.3. Preflight briefing guide (once per crew).

8.12.5. Airspace (IP).

8.12.5.1. Boundaries.

8.12.5.2. Assigned altitude.

8.12.6. Review site survey sheet (IP).

8.12.6.1. Visually identify all hazards.

8.12.7. Weather – update (IP).

8.12.7.1. Winds – trends, mountain wave.

8.12.7.2. Hazards – TRW, precipitation, etc.

8.12.8. Site Mission Brief (IP).

8.12.8.1. Mission plan modifications.

8.12.8.2. Takeoff and departure sequence.

8.12.8.2.1 Flight modes.

8.12.8.2.2 Target altitude.

8.12.8.3. Approach and landing.

8.12.8.3.1 Type.

8.12.8.3.2 Techniques.

8.12.8.3.3 Go around.

8.12.8.4. Get safe action below go around altitude.

8.12.9. CRM: identify crew positions and responsibilities.

8.12.9.1. Site lead is the mission commander / pilot in command.

8.12.9.2. SO.

8.12.9.2.1 Maintain visual contact with AV at all times.

8.12.9.2.2 Call out hazards: anticipate, be proactive.

8.12.9.2.3 Be directive if necessary e.g. “Padlocked, Hook Left/Right.”

8.12.9.3. VO/MO (or SUAS-I/E).

8.12.9.3.1 Maintain altitude SA.

8.12.9.3.2 Verbalize all inputs.

8.12.9.3.3 Monitor link status.

8.12.9.4. MO supports the VO.

8.12.9.4.1 Back up VO/SO on airspace, AV position.

8.12.9.4.2 VO confirmation before making nav inputs.

USAFA SUAS OI VOL 3.2 1 June 2014 19

8.12.10. Execute preflight checklist (VO).

8.12.11. FalconView setup checklist – initiate after GPS 4 “+” (MO).

8.13. Mission Operator Toughbook Setup Checklist (Comm/Origin/DTED)

8.13.1. Ethernet Cable – ATTACHED

8.13.2. Select FalconView Icon on the desktop.

8.13.3. Select RPUAV icon on the toolbar.

8.13.4. Open Network Port and minimize electronic logbook once it appears (COMMS).

8.13.5. Open Mission Management .

8.13.5.1. In mission management select “UAV origin” tab along the top (ORIGIN).

8.13.5.2. Click “Use” tab (bottom right).

8.13.6. Drag waypoints as required for executing the mission

CAUTION

In order to fully utilize DTED and the Mission Altitude Control tool, waypoints must be placed so that the entire mission area is covered. For most missions, Operators should build a “ROZ” out to 0.8 Km from H within airspace constraints to ensure visual contact with the AV.

Consider placing one or more orbit point within the mission flight plan to ensure complete coverage. Refer to the Raven Operator’s Manual for detailed information related to the Mission Altitude Control tool.

8.13.7. Open RPUAV Options Icon .

8.13.7.1. Click “Hub” tab.

8.13.7.2. Select “Start DTED Transfer to Hub.”

8.13.7.3. Make sure 50km x 50km box covers mission area.

8.13.7.4. Click “start DTED data Transfer” (this will appear in a smaller window).

8.13.7.5. Click close once file transfer is complete.

8.13.7.6. Select “Show Hub DTED Coverage” (DTED).

8.13.8. Select appropriate chart (not satellite imagery as there are no readily interpreted terrain contour / elevation lines) for mission.

8.13.9. Drag waypoints as required to cover the planned mission area and verify terrain clearance on the chart in addition to the mission altitude control tool.

8.13.10. Select “mission management tab” to edit waypoints .

8.13.10.1. Load altitudes for all waypoints and orbit points.

8.13.10.2. Edit ranges and bearings for all waypoints as required.

8.13.10.3. LOL settings (go to rally, loop time out setting, rally altitude).

8.13.10.4. Set proper “E” bearing and altitude as well as “L” bearing and altitude.

8.13.10.5. Close mission management tab (“USE”).

8.13.11. Select “Mission Altitude Control” .

8.13.11.1. Waypoint altitudes – CHECK / SET.

8.13.11.2. Rally Altitude – SET to highest available altitude (top of Class G).

CAUTION

Mission and orbit waypoints should be set to minimum assigned altitudes in order to ensure terrain clearance. Therefore, if operating with a block altitude select the bottom of the block.

20 1 December 2013 USAFA SUAS OI VOL 3.2

8.13.11.3. VO will read waypoint data shown on the Hand Controller to the MO for positive verification.

8.13.12. Select “AV Screener DDL” .

8.13.12.1. Let the AV Screener DDL data page update (DO NOT CLOSE THIS SCREEN).

8.13.12.2. After the data page disappears, move AV Screener to desired location.

8.13.12.3. Do not block upper left portion of Falcon View (this is where “EN ROUTE RALLY” will appear if you lose link with AV).

8.14. Site Departure Checklist

8.14.1. Inspect all equipment.

8.14.2. Delete all .ntf, .jpg and .mpg files from c:\rpuav_logs.

8.14.3. NOTE: if a mishap has occurred preserve all mission data.

8.14.4. Ensure Falcon Tracker is deactivated.

8.14.5. Ensure AV and training day logs are complete (site lead).

8.14.5.1. Return AV log to the appropriate bag.

8.14.5.2. Remove training day log from binder and return to AOC.

8.14.6. Ensure all gear is returned to its proper place.

8.14.6.1. Notify Ops Sup prior to site departure if anything is missing.

8.14.6.2. Pull any damaged gear out of the cases, return to the AOC.

8.14.7. Conduct final area sweep.

8.14.8. Notify Ops Sup that you are departing the site.

USAFA SUAS OI VOL 3.2 1 June 2014 21

CHAPTER 9

RESEARCH

9.1. Overview

9.1.1. The use of SUAS at USAFA is governed by various AFIs, DoD policies, FAA rules and regulations, etc. Except for designated training and proficiency flight activities, the use of unmanned aerial systems at USAFA for the purpose of research and development will be considered “flight test” and adhere to all USAF instructions governing RPA flight test (e.g., AFI 11-5FT series).

9.2. Operations Supervision

9.2.1. The Operations Supervisor provides flight advisory services and exercises launch/recovery authority over all RPA activities at USAFA.

9.2.2. All research flight ops require a designated and certified Operations Supervisor (Ops Sup).

9.2.2.1. The Op Sup is the single point of contact between research flight ops, the chain of command, flight safety, emergency response personnel and the 306th (Supervisor of Flying).

Crews should not directly contact 306th personnel unless conditions dictate (i.e., the Ops Sup does not respond and communications with the SOF is critical for flight safety).

9.2.2.2. Properly trained and certified Operations Supervisors may be designated on site on an exceptional basis; however, it is preferred that the Op Sup be located within the RPA Operations Center (building 2413).

9.2.2.3. Research operators will not launch without Ops Sup approval. This is to ensure Ops Sup visibility over operations.

9.2.2.4. In the event the Ops Sup is aware of any reason why flight ops must be suspended the Ops Sup will deny the request to launch.

9.2.3. Upon AV recovery, research operators will notify the Ops Sup.

9.3. Scheduling

9.3.1. Research flights will be scheduled with the RPA Operations Center NLT the duty week prior to operations, preferably by COB Wednesday the week prior.

9.3.2. Operations Center personnel will ensure research and airmanship program operations de-confliction.

9.4. Flight Operations Support

9.4.1. The Ops Sup will support research operations just as airmanship operations are supported, e.g., weather and NOTAMs, inflight monitoring, reporting, incident support, etc.

9.4.2. The Ops Sup will provide a pre-flight briefing to all research crews.

9.4.2.1. This briefing may be formal, at the Operations Center if desired; or via telephone/LMR.

9.4.2.2. The pre-flight briefing is mandatory and will include, at a minimum, the items listed in the Ops Sup section of this OI.

22 1 December 2013 USAFA SUAS OI VOL 3.2

Chapter 10 Airspace

10.1. 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 306th Operations Group that operates out of the USAFA airfield that restricts RPA operations to the area depicted in Figure 10.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 10.1

USAFA RPA AIRSPACE

USAFA SUAS OI VOL 3.2 1 June 2014 23

10.2. Site: Stillman restrictions and procedures (See Figure 10.2)Standard diamond, 0.2KM range

10.2.2. GCS should be as far east as practical.

10.2.3. No flight west of the stadium.

10.2.4. No flight over parking lot or structures.

10.2.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.

10.2.6. Tues and Thurs: No afternoon ops.

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

FIGURE 10.2

USAFA SITE STILLMAN

24 1 December 2013 USAFA SUAS OI VOL 3.2

10.3. Site: Flicker restrictions and procedures (See Figure 10.3).

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

10.3.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.

10.3.3. Ridgeline at ~400 meters west.

10.3.4. Rising terrain at northwest corner.

10.3.5. ~300 ft Ridgeline at north.

10.3.6. ~30 ft tree at south edge.

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

FIGURE 10.3

USAFA SITE FLICKER

USAFA SUAS OI VOL 3.2 1 June 2014 25

10.4. Site: Warrior restrictions and procedures (See Figure 10.4).

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

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

10.4.3. ~35 ft trees at northwest quadrant.

10.4.4. 50 ft trees at north and east edge.

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

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

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

FIGURE 10.4

USAFA SITE WARRIOR

26 1 December 2013 USAFA SUAS OI VOL 3.2

10.5. Site: Smack restrictions and procedures (See Figure 10.5).

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

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

10.5.3. Rising terrain with trees at northwest.

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

10.5.5. ~45 ft trees at south edge.

FIGURE 10.5

USAFA SITE SMACK

USAFA SUAS OI VOL 3.2 1 June 2014 27

10.6. Site: Aardvark restrictions and procedures (See Figure 10.6).

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

10.6.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.

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

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

FIGURE 10.6

USAFA SITE AARDVARK

28 1 December 2013 USAFA SUAS OI VOL 3.2

10.7. Site: Buff restrictions and procedures (See Figure 10.7).

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

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

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

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

10.7.5. Very open and level field.

10.7.6. ~40 ft trees at north and south edge of the site.

FIGURE 10.7

USAFA SITE BUFF