**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5
**Copyright © 201 5**  **# CompanyName**  

# Cloud Nine **T**

**echnologies , LLC** 

**OPERATIONS MANUAL**

**DJI Phantom 3 Professional**

**& DJI**  **Phantom 2**

**This document is a combined Safety and Operations Manual that covers all the**

**appropriate aspects of C**  **loud Nine Technologies, LLC ("CNT") required to satisfy the requirements of**  **the Federal A viation A**  **dministration permissions**  **and exemptions for A erial Work.** 

**Document Reference: CNT**  **/OM Issue 1.0** 

**– 1**  **st January**  **2015**

**Copyright** 

### © 2015 **Cloud Nine Technologies, LLC**

**Al l rights reserved.**  **Copies of this publication may not be reproduced for personal, company or organization use without the expressed permission of**  **CNT**

**.**

### Cloud Nine **Technologies, LLC** Operations Manual



### INTENTIONA **LLY LEFT BLA NK** **Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 i 

### Am **endment Record**

Amendment Number Amendment Date

(dd

- mm

- yyyy) Incorporated by Amendments Incorporated

1.0 01

- 0 1

- 2015 **CNT** First issue of Operations Manual First issue**Cloud Nine Technologies, LLC** Operations Manual



### Commitment of A **ccountable Manager**

This Operations Manual describes the organization

, aircraft sy stems, personnel, flight operations and procedures by which CNT carries out its Small Unmanned Aircraft operations

It is accepted that the contents of this document do not override the necessity of reviewing and

com plying appropriately with any n ew or am ended regulation published from tim e to tim e by t he relevant National Aviation Authorities addressed by this document.

Signed...............................................................................................

Accountable Manager: Debbie J. Branch Director CNT

,LLC

For and on behalf of CNT , LLC a n Oklahoma limited liability company

I nquiries regarding the content of this document should be addressed to:

C loud Nine Technologies, LLC P. O. Bo x 727 Cleveland, OK 74020**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 4 

## Contents

Amendments Control Page..............................................................................i Commitment of Accountable Manager........................................................................ii Contents....................................................................................................iii

PART A

................................ ................................ ................................ ....................... 6 1. Purpose

................................ ................................ ................................ .............. 6 2. Scope

................................ ................................ ................................ ................. 6 3. Definitions and Abbreviations

................................ ................................ ............. 7 4. Document Control and Amendment Process

................................ ..................... 7 5. Company Positions..............................

......... ......................................................8 6. Responsibilities.................................................

...... ............................................. 8 7. Aircraft Systems and Technical Descriptio ns.......

..... .......................................... 9 8. Operating Limitations and Conditions.......................

...... ..................................10 9. Software and Firmware Update Policy.............................

..... ............................10 10. Maintenance Principles......................

. ............................................................... 1 0 11. Supervision of UAS Opera tion s..................................................

... ...... ...............12 12. Investigation and MOR Handling.......................................................................12 13. Incident Handling

................................ ................................ ............................. 10 14. Flight Team Composition

................................ ................................ ................. 12 15. Operation of Multiple Types of UAS

................................ ................................ . 12 16. Qualification Requirements

................................ ................................ .............. 13 17. Crew Health

................................ ................................ ................................ ..... 13 18. Logs and Records

................................ ................................ ............................ 14

PART B

................................ ................................ ................................ ..................... 16 1. FLIGHT PLANNING / PREPARATION

................................ ............................ 16 1.1 Determination of intended task and feasibility

................................ .................. 16 1.2 Operating Site Location and assessment

................................ ......................... 16 1.3 Risk Management

................................ ................................ ............................ 16 1.4 Communications

................................ ................................ .............................. 17 1.5 Pre

- notification

................................ ................................ ................................ . 18 1.6 Site Permissions

................................ ................................ .............................. 18 1.7 We ather

................................ ................................ ................................ ........... 18 1.8 Preparation and serviceability of equipment and UAS

................................ ..... 18 2. ON SITE PROCEDURES

................................ ................................ ................. 18 2.1 Arrival

................................ ................................ ................................ ............... 18 2.2 Site Survey

................................ ................................ ................................ ....... 18 2.3 Selection of operating areas and alternate

................................ ....................... 18 2.4 Crew Briefing

................................ ................................ ................................ .... 19**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 5 

### 2.5 Cordon Procedure

................................ ................................ ............................ 19 2.6 Communications

................................ ................................ .............................. 19 2.7 We ather Checks

................................ ................................ ............................... 20 2.8 Charging and fitting Batteries

................................ ................................ ........... 20 2.9 Loading of equipment

................................ ................................ ....................... 20 2.9 Pre

- flight Checks

................................ ................................ .............................. 20 3. FLIGHT PROCEDURES

................................ ................................ .................. 21 3.1 Start

................................ ................................ ................................ ................. 21 3.2 Take

- off

................................ ................................ ................................ ............ 21 3.3 In flight

................................ ................................ ................................ ............. 21 3.4 Landing

................................ ................................ ................................ ............ 22 3.5 Shutdown

................................ ................................ ................................ ......... 22 4. EMERGENCY PROCEDURES

................................ ................................ ........ 23 4.1 General emergency procedures

................................ ................................ ....... 23 4.1.1 Loss of primary control frequency

................................ ............................ 23 4.1.2 Aircraft battery failures

................................ ................................ ............. 23 4.1.3 Transmitter or transmitter battery failure

................................ .................. 24 4.1.4 Malicious or accidental interference with control frequency

..................... 24 4.1.5 Pilot incapacitation

................................ ................................ ................... 25 4.1.6 Aircraft incursion

................................ ................................ ...................... 25 4.1.7 View incursion

................................ ................................ .......................... 26 4.1.8 Fl y away actions

................................ ................................ ...................... 26 4.1.9 Loss of UAS

................................ ................................ ............................. 27 4.1.10 Loss of flight controller

................................ ................................ ......... 27 4.1.11 Public encroachment

................................ ................................ ........... 27 4.1.12 Fire

................................ ................................ ................................ ...... 28

APPENDIX A

– SITE SURVEY, OPERATION AND FLIGHT CHECKLISTS

APPENDIX B

- FLIGHT AND MAINTENANCE RECORDS

APPENDIX C

- DJI PH ANTOM 2 OPERATING MANUAL

APPENDIX D

– DJI PHANTOM 3 PROFESSIONAL OPERATING MANUAL

APPENDIX E

- FAA EXEMPTION LETTER

- Conditions and Limitations (pending)**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 6



# PART A

**SA FETY**  **1. Purpose**  The purpose of this document is to detail the item s to be covered for the safe operation of the DJI Phantom 2 and D JI Phantom 3 Professional

, Sm all Unmanned Aircraft Systems ( UAS ) by Cloud Nine Technologies personnel.



### 2. **Scope** This operations manual applies to all CNT ’s aircraft and personnel involved in the safe operation of the UAS detailed in PART A Paragraph. 4

**2.1 Safety Policy and National Perspective** CNT adopts best industry practice to ensure that all its flight operati ons using its UAS are carried out as safely as possible. CNT operations are carried out and limited to the United States

**2.2 Safety Goals** CNT is committed to having a safe and healthy workplace, including:

 The ongoing pursuit of an accident free workpla ce, including no harm to people, no damage to equipment, the environment and property.

 A culture of open reporting of all safety hazards.

 Support for safety training and awareness programs.
**2.3 Safety A ssurance**  Safety is assured by applying consistent safety management approaches, comprehensive safety information sharing, monitoring and analy sis. The aircraft airworthiness will be assured by the initial grant of the FAA Exemption and subsequent maintenance of th e aircraft by the manufacturer/vendor of the UAS at the applicable intervals. Maintenance of the aircraft shall be documented in the

ma intenance log (Appendix B 3). Safety of the operation will be assured by adhering to all procedures and requirements state d in this operations manual. Risks that could endanger the safety of the operation are assessed by using the operational risk assessment as described in part B, section 1.3

. **2.4 Safety Training** CNT will provide support for safety training and awareness programs. All employees shall maintain proficiency in their operator/observer abilities. In

- house training is provided for observer/payload operators to ensure safety of the operation during emergencies (refer to Part B

, 4 ). CNT will support a climate in which all employees are able to contribute to the safety of the operation. CNT believes that safety is not something management does to or for employe es. Management commitment to safety is necessary, but true safety excellence requires engagement from personnel throughout the organization. Factors discovered in investigations shall be fed back to the crew in the form of training in a process of Continu al Professional Development. The pre

- and post

- flight routines of CNT shall ensure that all crewmembers are able to contribute to the safety of the operation and voice any

con cerns as well as share any observations

.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 7 

### 3. **Definitions and A bbreviations**  The UAS ty pe and mo del is specifically refered to when unique procedures apply

. Otherwise, t he term “the UAS” shall also be used when referring to procedures that are generally applicable for all of CNT ’s UAS . The following definitions and abbreviations are used throughout this document.

**4. Document Control and A**  **mendment Process** The operations manual is a controlled document and a record of all major amendments to it shall be

ma intained by updating the Amendment Record on page “i”. All members of the organization shall be notified of the chan ges that have been made to the document and will be required to operate using the

mo st up to date information.

An y m ajor changes to the organizations ownership, structure, personnel or aircraft sy stems which im pacts the pilot qualification or any Permissi on for Aerial Wo rk shall be noted through amendment to the operations manual.

The Accountable Manager is responsible for the amendments to CNT ’s operations manual. All

am endm ents shall be signed off by the Accountable Manager (Refer to Part A, 8.1).



### Referenced Documents
**Phantom 2 User Manual**  **Ap pendix**  **C**

Phantom 3 U ser Manual Appendix D FAA Exemption Letter Appendix E To be added **Reference Title**  AGL Above Ground Level ESC Electronic Stability Control FAA Federal Aviation Administration GPS Global Positioning System IMU Inertial Measurement Unit includes a 3

- axis accelerometer, a 3

- axis angular velocity and a barometric altimeter. MTOM Maximum Take

- Off Mass NAS National Airspace PIC Pilot In Command RPAS Remotely Piloted Aircraft System CNT Cloud Nine Technologies, LLC UAS Unmanned Aircraft System VLOS Visual Line Of Sight**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 8 

### O **RGA NIZA**  **TION**

**Cloud Nine Technologies, LLC Oklahoma Limited Liability**  **Company**

**5. Company**

**Positions**

Accountable Manager :

Chief Operations Officer

Pilot

- in

- Command (PIC):

Observer:

Pa yload operator:



### 6. **Responsibilities** The responsibilities of personnel by CNT are divided as follows:

**6 .1**  **Ac countable Manager**  The accountable manager has the overall executive responsibility for the operation of CNT . The accountable manager has corporate authority for ensuring that all operations activities can be financed and carried out to the standard required by the regulator . The accountable manager is responsible for the amendments to CNT ’s operations manual. The accountable Manager shall sign off the

am endm ents the document.

**6 .2 Chief Operations Officer**  The chief operations officer is responsible for ma naging all hands

- on operational aspects of the

com pany. These responsibilities include: a) Maintaining CNT ’s documents (including the operations ma nual) and ma king changes to these documents. Documents that are controlled by CNT shall be held compliant with the mo st current avia tion regulation that applies to the UAS; and b) Updating the software and firmware of the flight systems (refer to Part A, 9 ) and logging this in the Software Update Log (Appendix B 5); and c) Ensuring that all persons involved in the operation will be provided with the appropriate training and the necessary information before commencing an operation; and d) Maintaining the airworthiness approval given by the FAA by a rranging ma intenance to the aircraft at the appropriate intervals (refer to Part A, 10 ). e) Controlling the pre

- and post

- flight check sy stem, by checking if logs have been completed and

ma king changes to the system when needed.

**6 .3 Pilot** 

**- in** 

**- Command (PIC)**  The PIC is responsible for the safety o f: the aircraft, its surroundings and all the me mb ers of the op eration including himself. Therefore, the PIC must, before taking off for any flight, take all reasonable steps so as to be satisfied of the matters specified below: a) The flight can safely be ma de, taking into account the latest information available such a s w eather reports and forecasts and any alternative course of action which can be adopted in case the flight cannot be completed as planned; b) The equipment that is carried is in sufficient conditions for use;**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 9 c) The aircraft is in ever y wa y fit for the intende d flight; d) The load carried by t he aircraft is of such weight, and is so distributed and secured, that it may safely be carried on the intended flight; e) An y pre

- flight check sy stem established by t he operator and set out in the operations ma nual or elsewhere has been complied with by e ach me mb er participating in the operation. (Part B & Appendices A & B ) f) Be satisfied that it is capable of safely taking off, reaching and maintaining a safe height and

ma king a safe landing at the place of intended destination h aving regard to: 1) the performance of the flying machine in the conditions to be expected on the intended flight; and 2) any obstructions at the places of departure and intended destination and on the intended route.

By u sing the pre

- flight check sy stem as specified in Appendix A

, the PIC should be able to ensure safety consistently. During flight, the PIC is responsible for: g) Keeping the aircraft within operating limitations (refer to Part A, 8 ); and h) Maintaining clear communications with the flight team a bout the intended flight path. i) Notif yi ng the flight team when any thing unusual happens or mi ght occur, so the flight team can respond accordingly.

**6 .4 Observer**  For all operations with the UAS, the flight team will have an observer to assist the PIC. Wh ile the PIC

mu st keep his ey es on the UAS all the tim e, the observer can have a better overview of the surroundings during the operation. The observer is responsible for: a) Notif yi ng the flight team when any thing unusual happens or mi ght occur, so the flig ht team can respond accordingly; and b) Keeping an overview of possible other aircrafts or obstacles in the vicinity of the UAS; and c) Maintaining a clear take off/landing site by i nforming and instructing passers

- by or spectators to stay at a safe distance; an d d) Making sure that the PIC does not get distracted from its main task of safely controlling the UAS.

**6 .5 Payload operator**  The payload operator shall assist the flight team for operations in which a camera is attached to the UAS. The payload operator is re sponsible for: a) Notif yi ng the flight team when any thing unusual happens or mi ght occur, so the flight team can respond accordingly; and b) Maintaining clear communication with the flight team about the desired flight path for the aerial footage.



### 7. **Ai rcraft**  **Systems and Technical Description** The DJB Phantom 2 and DJI Phantom 3 aircraft sy stems are covered by their respective Operations Manua ls

. Both UAS are mu lti

- rotor platform designed for professional aerial photography. General specifications of the aircraft follow below. Extended details are provided in the Operations Manual of each aircraft: Phantom 2 ( Appendix C ) and Phantom 3 ( Appendix D ) respec tively.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 10 **Specifications DJI Phantom 2**  **DJI Phantom 3 Professional General:**  UAS Name: DJI Phantom 2 Manufacturer: DJI Innovations Model: DJI Phantom 2 Ty pe: Multi

- rotor system (4 rotors) Registration / Serial Number: We ight: 1280g Max Ascent Speed: 6 m/s Command and Control Frequenc y: 2.4 GHz ISM **General:** UAS Name: DJI Phantom 3 Professional Manufacturer: DJI Innovations Model: DJI Phantom 3 Ty pe: Multi

- rotor system (4 rotors) Registration / Serial Number: We ight: 1000g Max Ascent Speed: 5 m/s Command and Control Frequenc y: 2.4~2.483 GHz **Engines** Number of engines: 4 Engine type: Brushless Electric Motor Power capacity (W ): 500 (max) Battery: LiPo 35 **Engines** Number of engines: 4 Engine type: Brushless Electric Motor Energy (W h): 99.9 for TB47

129.96 for TB48 (optional) Battery: LIPo 45



### 8. **Operating limitations and conditions** The conditions under which operations are allowed by the aviation authorities are as follows:

In the Exemption Letter issued by t he FAA dated _________, (pending) see Lim itations and Conditions; and.

with the operating limitations and conditions as defined by the manufacturer of the UAS which are uniquely defined for each of the UAS of CNT . They can be found in Ap pendix C and Appendix D

.


### 9. **Softw are and Firmware Update Policy**  The Chief Operations Officer is responsible for the status of the software and firmware that is used by CNT ’s UAS and flight controller. The upgrading of software and firmware is an integral part of the

ma intenance procedures of CNT and shall be performed at regular intervals. Maintenance to the UAS is performed by

a n approved technician as selected by CNT (Refer to Part A, 10 ). All software and firmware changes shall be documented using a Software Update Log (Appendix B 5), which is controlled by the Chief Operations Officer of CNT

.

The specific software and firmware update procedures that apply f or each of CNT its U AS and flight controllers, can be found in Appendix C and Appendix D

. As software and firmware is updated during

ma intenance of the aircraft, the same testing procedures that are part of CNT ' s ma intenance procedure apply (Refer to Part A, 10 ).



### 10. **Maintenance Principles and Regime** The Chief Operations Officer of CNT is responsible for maintaining the airworthiness approval given by the FAA by

a rranging ma intenance to the aircraft at the appropriate intervals. Maintenance of the aircraft is logged in the maintenance log (Appendix B 3 ). The following maintenance intervals apply for each of CNT its UAS :**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 11 **An nual Preventative Maintenance (<300 hours of flight time per year):**  A preventative ma intenance inspection shall be carried out annually when the UAS has logged less than 300 hours of flight time. This inspection shall be com pleted by a n approved technician. During this inspection, the following tasks shall be completed:

 The UAS shall be disassembled; all components shall be inspected for wear and t ear; and

com ponents shall be replaced as required.

 All batteries are tested for capacity

 Software and firmware version is checked to see if they a re of the latest version or need to be updated by the approved technician.

**300 Hours within one year:** An in spection shall be carried out when the UAS has logged 300 hours of flight tim e within one year tim e. This inspection shall be completed by a n approved technician. During this inspection, the following tasks shall be completed:

 The UAS shall be disassembled ; all components shall be inspected for wear and tear; and

com ponents shall be replaced as required.

 All batteries are tested for capacity

 Software and firmware version is checked to see if they a re of the latest version or need to be updated by the appro ved technician.

**500 Total hours of flight time (Major inspection):** The following inspection shall be carried out when the UAS has logged 500 total hours of flight time since its last ma

jor inspection. This inspection shall be completed by a n approved tec hnician. During this inspection, the following tasks shall be completed:

 An approved technician should disassemble the AV and inspect all components for wear and replace any components as required.

 Replace all engines.

 Test all batteries for capacity.

 Software and firmware version is checked to see if they a re of the latest version or need to be updated by the approved technician.

After ma intenance to the UAS has been performed and software and firmware versions have been checked and updated, a test f light is conducted by CNT to check the operational capabilities of the aircraft. During a test flight, basic flight ma neuvers shall be performed by t he PIC and the correct functioning of the emergency functionalities is checked.

The approved technician th at CNT shall use for its ma intenance is the distributor of the UAS. This

com pany has also built the UAS that CNT shall use for its operation. The contact details are:

Company: # DistributorName Address: #

Address # PostalCode, City, Country: # CountryName**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 12 

### OPERA **TIONA L CONTROL** 

**11. Supervision of UA**  **S operations** The PIC on the day

i s responsible for supervising the operation of the UAS. All responsibilities for the roles within the company a re described in Part A, 6

. The Chief Operations Officer is responsib le for all

ma n a gerial activities and tasks that need to be executed within CNT

. The Chief Operations Officer shall ma ke sure before each operation that all personnel who participate in an operation me et mi nim um r equirements (Refer to Part A, 16 ), have valid qualifications and have received the appropriate instructions

. It is also his or her responsibility t o control and store records and logs for a mi nim um of seven ye ars (Refer to Part A, 18 ).

The Chief Operations Officer is also responsible for ma in taining all CNT ’s documents and ma king changes to the documents (Refer to Part A

, 6.2 ). The operations ma nual shall be compliant with the

mo st current aviation regulation that applies to the UAS

. New information which may b e of an operational nature shall be added from tim e to tim e to the operations ma nual or other documents that

are controlled by CNT

. When the Chief Operations Officer introduces new documented information into the company, which affects the operations manual, a new amendment to the operati ons manual is

ma de (Refer to Part A, 18 ). An am endm ent is signed off by t he Accountable Manager and then submitted to the regulator y authorities for approval.

The FAA has the power to evaluate, correct and approve of CNT its practices and documentation. The organization is responsible for this independent assessment of the operator on behalf of the FAA. In case of an Operator Flight Test, the Chief Operations Officer shall be responsible for communicating with the repre sentatives of the FAA about facilitating the inspection and shall ma ke sure that their requests regarding the assessment of CNT its operations are met.



### 12. **Incident, Investigation and MOR Handling** An im portant part of CNT ’s safe operation is having the right culture within CNT ’s organization. CNT strives to create a culture whereby learning from incidents is key a nd the honest acknowledgement of mi stakes is seen as a chance to learn and as an opportunity to increase the sa fety or CNT its aviation activities. Therefore, CNT has specified procedures for the handling, investigation and logging of incidents. Wh en researching incidents it is the identification of the cause of the incident, which is the focal point and not the in dividual. This allows CNT to do something about that cause and prevent the

sam e incident from happening again. The issue of guilt is therefore not relevant, unless there has been negligent and reckless behavior.



### 13. **Incident handling:** If an incident/acci dent may occur, the pilot

- in

- command shall be notified as quickly a s possible. The flight team shall use their skills and knowledge acquired during ground course and practical training and flight experience to ensure that no further incidents occur and tha t the UAS and their surroundings remain as safe as possible whilst pausing or ending the operation. The incident shall be investigated and reported after the operation has ended.



### 13.1 **Incident Investigation** If an incident/accident ma y occur, CNT shall categorize the incident in degree of severity. The following table can be applied:

Severity Definition Accident An occurrence associated with the operation of the UAS in which: a) A person is fatally or seriously injured, and/or; b) The aircraft has sustained major damage or structural failure, and/or;**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 13 c) The UAS is mi ssing or is completely inaccessible/uncontrollable. This includes hijacking of the UAS.

Note: Due to the nature UAS controls, there is a small but not insignificant chance that a situation mi ght occur in which the UAS (temporarily) loses its communication with the controller. In this case, the UAS may

use its Failsafe feature (Appendix C and Appendix D ) to

ensure that the UAS will hover automatically w hen it loses signal. Wh en items a a nd b do not apply, this will be classified as either a serious incident, or a major incident, depending on the circumstances and judgment of the PIC. Serious incident An incident involving circumstances indicating that an accident nearly occurred. Major incident An incident associated with the operation of the UAS, in which safety of the aircraft may

h ave been compromi sed, having led to a near collision between aircraft, with ground or obstacles (e.g. VLOS safety margins not respected). Significant incid ent An incident involving circumstances indicating that an accident, a serious or
ma jor incident could have occurred, if the risk had not been ma naged within safety margins, or if another aircraft had been in the vicinity. No safety effect An incident which has no safety significance Not determined Insufficient information was available to determine the risk involved or inconclusive or conflicting evidence precluded such determination.

**13.2 Incident logging:**  If an incident /accident may occur during the operation of the UAS, it shall be logged using the Aircraft, Pilot and Crew log (Appendix B

- B1 and the Incident Log (Appendix B

- B2) as part of the post

- flight procedure. The PIC of the operation in which the incident/accident has occurred is responsible for

com pleting incident logging as part of the post

- flight check sy stem.

**Ma ndatory occurrence reporting:**  The aircraft, pilot and crew log as well as the incident log shall be made readily available upon reque st by the FAA

.

**14.** 

### Flight Team Composition

The flight team for operation with either of the UAS shall alway s consist of minimally:

• 1 PIC

• 1 Observer For operations that require photography or videography, such as im agery and ma pping or me dia operations

, a payload operator shall also be part of the flight team. For these operations, the flight team consists of minimally:

• 1 Pilot

- in

- command

• 1 Observer

• 1 Pa yl oad operator



### 15. **Operation of Multiple ty pes of**  **UA S**  CNT operates both the DJI Ph antom 2 and the DJI Phantom 3. Before each operation commences, the Chief Operations Officer is responsible for deciding which aircraft CNT shall use for the operation (Appendix A 1). Separate maintenance logs shall be used for the s ys tems (Appendix B 1, B 2, B3, B 4 and B 5). This operations ma nual ma kes a distinction between the two sy stems where necessary to support the safe operation for both ai rcraft.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 14 

### 16. **Qualification Requirements** All personnel operating as pilot

- in

- command of the UAS mu st be at least 18 ye ars old and me et the following requirements:

A. M ust possess at an airline transport, commercial, private, recreational or sport pilot certificate.

B. M ust possess a current FAA airman me dical certificate or a valid U. S. drivers license issued by

a s tate, the District of Colum bia, Puerto Rico, a territor y, a possession, or the Federal Government.

C. M ust me et the flight rev iew requirements in all aircraft for which the PIC is rated on his or her pilot certificate.

D. A PIC that did not fly f or 90 day s should have another check under supervision of a PIC still current.

All personnel operating as observer or pay load operator for the UAS mu st have followed an in

- house training by CNT

. This training ensures that the observer/payload know their responsibilities and tasks during the operation. It also ensures that the observer/operator are able to safely return the UAS when the PIC is unable to in an emergency situation (Refer to Part B, 4.1.5 ).



### 17. **Cre w Health**  To ensure safe operation of the UAS, CNT requires that all personnel shall comply w ith the following requirements on crew health: a) The flig ht team shall only deploy the UAS when rested and em otionally prepared for the tasks at hand. b) Ph ys ical illness, exhaustion, emotional problems, etc., can seriously impair judgment, memory and alertness. The safest rule is not to act as part of the flight t eam when suffering from any o f the above. Mem bers are expected to “stand down” when these problems could reasonably be expected to affect their ability to perform flight duties. c) A self

- assessment of p hy sical condition shall be ma de by a ll me mb ers during pre

- flight activities. d) Performance can be seriously h am pered by both prescription and over the counter drugs. The PIC shall be advised anytime such drugs are being taken. If it is determined that the

me dication being taken could hamper a pilot

- in command, observer or payload operator, that

me mb er shall be prohibited from the deploy me nt of exercise. e) No me mb er shall act as part of the flight team within eight hours after consumption of any alcoholic beverage, while under the influence or while having an alcoh ol concentration of more than 88 micrograms of alcohol per liter of exhaled air.

The mn em onic I.M.S.A.F.E can be used by p ersonnel to check whether they are able to operate safely:

**I** llness Do I have an illness or any sy mp toms of illness? **M** edication Have I been taking prescription or over

- the

- counter drugs? **S** tress Am I u nder psy chological pressure from the job? Wo rried about financial

ma tters, health problems or family discord? **A** lcohol Have I been drinking within eight hours? W ithin 24 hours? **F** atigue Am I tired and not adequately rested? **E** ating Am I adequately nourished?**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 15 

### 18. **Logs and Records** All logs and records that are used and controlled by CNT are featured in the appendices. It is the responsibility of the Chief Operations Officer to control th ese documents. The logs shall be kept for at least seven years, the same duration as the administrative documents of CNT

.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 16



# PART B

**OPERA TING PROCEDURES** 

**1. FLIGHT PLA**  **NNING / PREPA RA**  **TION**

**1.1 Determination of intended task and feasibility**  CNT will operate either upon customer request or for dem onstration/training purposes. A customer form shall be filled out by the appropriate contact within CNT , which gives CNT mo re information about the needs of the customer. The intended task shall eventual ly b e determined in consultation with the customer. The feasibility of the operation can be evaluated when the intended task is clear for both CNT and the customer. When evaluating the feasibility of the intended task, the following questions should be con sidered before the commitment to operate is made:

a) Is the proposed use of the UAS within the capabilities of the UAS equipment and personnel to perform? b) Does the proposed use of the UAS fall within the operational limitations of the UAS? c) Are sufficient tr ained and qualified personnel available to safely operate the UAS?



### 1.2 **Operating Site Location and assessment** Before operating, the flight can be prepared by investigating the operating site location. The information that is obtained shall be documented using the pre site survey form (Appendix B1). In order to make a supported assessment, the following conditions should be considered:

The type of airspace that will be used and the specific provisions that apply. Extraordinar y restrictions such as segregated airspace around prisons, nuclear establishments etc. (suitable permission may be needed) Other aircraft operations (local aerodromes or operating sites). Hazards associated with industrial sites or such activities as live firing, gas venting, high

- intensity radio transmissions etc. Local bylaws. Proximity of obstacles (e.g. buildings, bridges, masts, terrain). Proximity to sources of radio interference such as power lines. Habitation and recreational activities. Public access. Permission from l andowner (see Part B, 1.6) Likely operating site and alternative sites Prevailing local weather conditions and weather conditions for the planned event



### 1.3 **Risk Management** In order to operate safely, risk management is part of CNT ’s flight planning and preparation process. A risk assessment is performed in the form of a hazard analysis, which is used to identify, classify and assess the risks of hazards and to determine the steps necessary to reduce the risk for each hazard to

an a cceptable level.

Hazards are identified before commencing the operation by a pply ing the pre

- flight checks and operating procedures. Hazards that are identified shall be documented in the pre

- flight survey**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 17 checklist (Appendix A 1 ). Hazards identified duri ng operation are handled by a pplying em ergency procedures (Part B, 17 ) when necessary.

A risk ma trix is used (figure 1) in combination with the risk assessment form (Appendix E) to assess the risk of a haz ard. In this matrix, numbers have been assigned f rom 1 to 5 that represent the degree of severit y and the probability of a hazard. W hen mu ltiplying these numbers, the greater the outcome, the greater the perceived risk. The following steps are taken to assess the perceived risk of a hazard:

1. Identificati on of hazards 2. Assess probability of hazard leading to an undesirable outcome (as judged by PIC). 3. Assess severity of that outcome (as judged by PIC). 4. State risk as a product of probability and severity. 5. Show risk in an assessment matrix which identifies acceptability of risk.

**Figure 1: Risk assessment matrix**

An example is given using the ma trix in figure 1. For a particular ty pe of aircraft, if there is a high probability (say

4 ) of an engine failure (hazard) in any o ne flight and this would result in a rapid uncontrolled descent (undesirable outcome), then the potential for injuring someone underneath the flight path might be assessed as 3 (injury) or even 4 (major injury ). This would result in either 12 (4x3) or even 16 (4x4) in the risk matrix and CNT should question whether the flight should be undertaken at all.

However by

n ot fly ing over people and leaving an adequate ma rgin for wind effects, the potential for injury may be reduced to 1 or in high winds possibly 2. This gives CNT a result in the range 4 (4x1) to at worst 8 (4x2) in high winds when the flight path is less predictable. A much safer situation.



### 1.4 **Communications** If possible, contact numbers for other local aircraft operations shall be obtained beforehand to ma ke

sure al l operators, including CNT

, can be notified when needed, i.e. in case of em ergency. Wh en preparing to fly

w ith other operators in the area, control frequencies can be discussed and agreed upon beforehand (also see Part B 2.5). The information that is obtai ned shall be documented in the pre

- flight survey checklist (Appendix A 1).**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 18 

### 1.5 **Pre**

**- notification**  It may b e necessary that CNT contact the local police to inform them o f the intended operation to avoid interruption or concerns from the public. Wh en the operation is likely to disturb any r esidents

near the operating site, CNT shall consider informing them in advance. A me thod that can be applied for this purpose is to drop leaflets at these addresses



### 1.6 **Site Permissions** Once it is clear for CNT that airspace is available for the operation, permission shall be obtained for the take

- off and landing areas when needed. This “landowner’s permission” is usually needed when the take

- off and landing areas are situated on private property. If possible, t his “landowner’s permission” should be obtained in wr iting. Local authorities may a lso stipulate mi nim um i nsurance criteria. The information that is obtained shall be documented in the pre

- flight survey checklist (Appendix B1).



### 1.7 **Weather** We ather forecasts s hall be obtained as part of CNT pre

- flight procedure. We ather forecasts can be obtained by

checking the latest METARs and TAFs from stations on or near the area that will be used for the operation.

We ather conditions mu st be within operating lim itations and conditions of the UAS (see Appendix C and D ) when operating the UAS. Caution shall be taken by CNT when weather forecasts indicate conditions that fall outside of the UAS operating limitations. This could lead to rescheduling or cancellation of the ope ration when weather conditions do not improve. The information that is obtained shall be documented in the pre

- fli ght survey checklist (Appendix A 1).



### 1.8 **Preparation and serviceability of equipment and UA**  **S** Before em barking on an operation, the PIC is responsible (See Part A, 6.3 ) for ensuring that all equipment is ready for use, loaded and ready t o be taken out. The ma intenance log (Appendix B 3) shall be used to check whether the UAS is serviceable. An em bar kation checklist (Appendix A 2) shall be used to ensure that all tools and equipment are taken to the flight operation site.



### 2. **ON SITE PROCEDURES**

**2.1 Ar**  **rival** Wh en arriving at the area of operation, CNT shall perform its arrival procedure. By having a clear arri val procedure, CNT is able to ensure the safety of the operation from the moment it arrives on site. The arrival procedure shall be completed using the arrival checklist (Appendix A 3).



### 2.2 **Site Survey** The specific terrain, structures and activity on and in the immediate vicinity o f the flight operation site and surrounding area may b e different to what CNT was expecting on basis of its flight planning/preparation procedures (Part B, 1). CNT shall therefore ensure t hat all the assumptions that have been ma de as to the viability of the site for operation of unm anned aircraft are validated. This is done by completing the on

- site checklist. W hen completing this checklist, CNT shall take the operating lim itations of the UAS into acco unt (refer to Appendix C or Appendix D ). The PIC is responsible for performing the site survey and completing the on

- site checklist (refer to Part A, 6.3 )



### 2.3 **Selection of operating areas and alternate** The selection of operating areas depends up on the customer request. Wh en evaluating a proposed operating area, CNT will ensure safe operations by p erforming an operating area assessment as part of its pre

- flight procedures as described in Part B, 1.2. This pre

- flight procedure documents all relevan t**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 19 criteria for selecting the operating site. W hen arriving on site, an on

- site survey is conducted. This on

site survey

i s ver y similar to the pre

- flight survey that was conducted as part of the pre

- flight procedure. The on

- site survey e nsures that the cre w is aware of the latest situation and any unexpected changes to conditions and/or the environment that mi ght have occurred since the pre

flight survey.

In the on

- site survey checklist, space is available to describe the location of the em ergency a rea (a lternate). The exact location of this area shall be determined by t he PIC, taking into account the operating limitations of the UAS (refer to Appendix C or Appendix D ). The information that is obtained shall be documented in the on

- site survey checklist (Appendix A 4).



### 2.4 **Crew Briefing** CNT shall ensure that all crew me mb ers are briefed before any flight operation. The crew briefing is organized and conducted by the PIC fo r the operation. The CNT standard crew briefing consists of the following subjects:

a) Location/operating area b) Em barkation/arrival time c) Operation objective(s) d) Operating system (UAS) e) Operating conditions f) Roles and responsibilities g) Communication procedures h) Disc ussion on hazards/perceived risk i) Em ergency procedures j) Crew health k) Other remarks



### 2.5 **Cordon Procedure** Wh en operating the UAS, it is likely to attract attention from other people, especially w hen fly ing in public areas. CNT shall use a cordon procedure when ope rating to ensure the safety o f me mb ers of the public. Extra staff may b e utilized to ma intain the cordon when fly ing in an area that is likely to attract spectators. The take

- off and landing area shall be ma rk ed by a c ircle of orange py lons that is 150 me t ers in diameter to ensure appropriate spacing between the UAS and the public (refer to Appendix C or Appendix D ). Additionally, the observer shall keep control of the take

- off and landing

area by o bserving the area of operation and informing/instructing passers

- by w hen needed (refer to Part A, 6.4 ).

. 

### 2.6 **Communications** CNT shall establish the control frequency for the UAS and check whether this is not used by any other source in the vicinity

a s this could block CNT transm issions from being received by the UAS. Although it is very u nlikely that a signal conflict or interruption occurs as the frequency of controllers that are used by CNT shift hundreds of tim es per second, so there are no signal conflicts or interrupt ions and therefore no need for a frequency pin.

As part of the pre

- flight procedure (refer to Part B, 1.2), the surroundings are checked to see if there

are any o bstacles, such as power lines, that could interfere with the transmissions. Telemetry o n airc raft position and height are checked for proper fu nctioning during take

- off (refer to Part B, 3.2). Telemetry is continuously checked by t he PIC during the operation. Em ergency procedures for situations in which communications with the UAS are lost have be en described in Part B, 4.1.

Crew communications shall be established by u sing two way

r adios for each me mb er of the flight crew. This ensures that the flight crew can communicate easily and clearly when separated from each**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 20 other or operating in crowded or otherwise nois y areas. Wh ere possible, me mb ers of the operation that do not have a radio shall communicate with the PIC through the observer to avoid unnecessary distractions for the PIC. A fully charged mo bile phone shall be present in order to contact em ergency services if required (Appendix B2).



### 2.7 **Weather Checks** We ather can greatly affect the operation and effectiveness of the UAS. Therefore, CNT shall obtain and document weather information as part of the pre

- flight procedure (refer to Part B, 1.7) an d when arriving on site (Appendix A 3). We ather conditions must be within operating limitations and conditions of the UAS (see Appendix C or Appendix D ) when operating the UAS. Caution shall be taken by CNT when weather forecasts indicate conditions that f all outside of the UAS operating limitations. This could lead to rescheduling or cancellation of the operation when weather conditions do not improve.

Wi nd speed is measured by u sing a wind measurement device and the temperature is recorded using a thermo me ter . The PIC is responsible for judging whether he is able to fly in the situation he is presented with. Even when the PIC is capable of flying in high crosswinds, the images that are received from the camera might be too unstable which may lead to a de lay

or cancellation of the operation.



### 2.8 **Charging and fitting Batteries** Batteries are charged from CNT hom e base. Batteries are all uniquely numbered, starting from one. Batteries are stored at room temperature in separate storage boxes; containing only the batteries for a single type and model of UAS, so batteries for different sy stems cannot be confused with one another. Battery management is performed by using the batter y charge log (Appendix B4) , in which the status of all batteries is kept and updated. Separate charge logs are kept for both s ys tems . The charging and fitting of the batteries is one of the responsibilities of the PIC (refer to Part A, 6 ). A battery checker is used to check the status of each batter y before being fitted onto the UAS before each flight. Batteries shall not be used for flight if their charge status is lower than 90%. It is important to observe the safety handling and precautions needed with lithium batteries are used for both the Phantom 2 and 3. Battery charging should not be left unattended.



### 2.9 **Loading of equipment** CNT ' s UAS are capable of being fitted with a camera system to shoot aerial footage. W hen aerial footage is required for an operation with the UAS, CNT shall use a GoPro camera on the DJI Phantom 2. The DJI Phantom 3 Professional comes equipped with its own camera

. The camera is loaded onto a three

- axis electronic stabilization gimbal that stabilizes the camera during flight. This electronic gimbal is attached to the airframe of the UAS . The total weight of the UAS, including the

cam era and gimbal shall not exceed the MTOM as specified by DJI Innovations in the User Manuals (see Appendix C and D)

. The PIC is responsible for the correct and safe loading of the camera to the UAS (Part A ,6 ). The PIC shall ensure himself of the correct and safe loading of the camera to the UAS by completing the arrival checklist (Appendix A 3 ) and the pre

- flight checklist (Appendix A 4 ).



### 2.9 **Pre**

**- flight Checks**  The final checklist that has to be completed is the pre

- flight checklist (Appendix A 5), which is done by the PIC. Completing the pre

- flight checklist is the responsibility of the PIC (refer to Part A, 6.3) . This checklist is used to confirm the airworthine ss of the UAS and to safely power on the UAS to start the operation. If any fault is found during the pre

- flight checks, the PIC shall be responsible for calling the course of action to fix the fault. After a fault is fixed, another attempt can be made to complete the full pre

- flight checklist.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 21 

### 3. **FLIGHT PROCEDURES**

**3.1 Start**  The UAS is started as part of completing the pre

- flight checklist (Appendix A 5). By completing the pre

flight checklist, CNT ensures that the UAS is ready for take

- off, the crew is ready an d that public is a safe distance away. The PIC calls “TAKING OFF” when the motors are started.

Procedure:

SW IT CH ON, CHECK BATTERY POW ER IS W IT HIN SAFE PARAMETERS, ENSURE TRIMS ARE NUETRAL AND ALL SW ITCHES ARE IN THERE CORRECT POSITIONS

SW IT CH ON AND CONFIRM CORRECT OPERATION OF THE CAMERA

ENSURE AIRCRAFT IS LEVEL ON THE CALIBRATION PLATFORM

CALL " CLEAR PROPS " AND CONNECT FLIGHT BATTERY

WA IT FOR DIAGNOSTIC TO FINISH & GPS LOCK TO BE ESTABLISHED

CHECK FUNCTION & QUALIT Y OF A/V LINK FROM CAMERA

TEST FOR CONTROL AND OPERATION

ENSURE TRANSMITTER DISPLAYS ARE CONNECTED

START RECORDING

REPOSITION AIRCRAFT IN TAKE OFF AREA ON LEVEL GROUND FACING INTO WI ND

ENSURE ALL CREW , PUBLIC & CLIENT ARE IN CORRECT SAFE POSITIONS

DO WE HAVE CLEARENCE FROM AIR TRAFFIC CONTROL IF REQUIRED?

CALL " TAKING OFF

" AND START MOTORS ( # Left Transmitter Stick to Bottom Right Corner & Right Transmitter Stick to Bottom Left Corner)



### 3.2 **Take**

**- off**  Wh en the UAS has been powered on, the PIC takes one quick final look around, checks with the observer that they agree it is safe to fly, powers up and takes off as described in the pre

- flight checklist (Appendix A 5).



### 3.3 **In flight** After taking off, telemetry data is checked to see if it responds correctly to the change in the UAS position. Throughout the entire flight, the crew shall work together by maintaining clear communications with each other, listening for battery warnings, remaining cautious of airspa ce infringements, other aircraft operations, obstacles, public encroachments or any other hazards that could lead to aerial collision or otherwise endanger the safe operation of the UAS.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 22 

### 3.4 **Landing** Before landing, the PIC shall check with the observer that the landing area is readily available for use and no operating limitations shall be exceeded during the landing. All crew members shall be informed that the UAS will proceed to land in the landing area. W hen the UAS is hovering over the landing area, the PIC will take a quick look below the aircraft to confirm all is clear. The PIC calls “LANDING” and lands the UAS (Appendix A 5).



### 3.5 **Shutdown** Upon touchdown, the motors of the UAS shall immediately be s topped by the PIC. The PIC then walks toward the UAS, disconnects the flight battery and calls “SAFE”. The aircraft can then be removed from the landing area. CNT ends the operation by completing the post

- flight checklist (Appendix A 6).

Procedure:

UPON TOUCHDOW N EMMIDIATELY STOP MOTORS ( # Left Transmitter Stick to Bottom Right Corner & Right Transmitter Stick to Bottom Left Corner)

WA LK TO AIRCRAFT, DISCONECT FLIGHT BATTERY AND CALL " SAFE "

REMOVE AIRCRAFT FROM LANDING AREA

RECORD FLIGHT TIME DETAILS IN PILOTS LOGBOOK & BATTERY LOGBOOK

SW IT CH OFF TRANSMITTER

STOP RECORDING AND S WI TCH OFF

CHECK FOR DAMAGE, W EAR, TIGHTNESS OF FITTINGS, CONDITION AND SECURE FITMENT OF PROPELLERS AND SECURE ATTATCHMENT OF CAMERA

REMOVE FLIGHT BATTERY FROM AIRCRAFT, CHECK RESIDUAL BATTERY %, RECORD DETAILS IN BATTERY LOGBOOK & PLACE ON CHARGE IN LIPO SAFE BAG PROVIDED THAT THE BATTERY IS NOT WA RM (If So Allow to Cool)

REMOVE MEMORY CARD FROM CAMERA AND BACK UP TO COMPUTER

REVIEW IMAGES AND DISCUSS W IT H C RE W AND OR CLIENT IF REQUIRED**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 23 

### 4. **EMERGENCY PROCEDURES**

Wh en an emergency procedure has to be performed because of the occurrence of an incident or accident, the procedures as described in Part A, 13 shall be performed. Emergency procedures have been defined for several scenarios that could occur with the type of UAS that are used by CNT . W hen possible, the PIC shall perform the standard landing procedure (refer to Part B, 3.4) as the final part of the emergency procedure. After the emergency procedure, the operation shall be reviewed (refer to Part B, 3.5) so t he flight crew can immediately analyze what went wrong and learn from the situation.



### 4.1 **General emergency procedures**  The following em ergency procedures are generally applicable for all of CNT ’s UAS

. Em ergency procedures that feature UAS specific details or scenarios are described in Appendix C (DJI Phantom 2 and Appendix D ( DJI Phantom 3 ).

**4.1.1 Loss of primary control frequency**  A situation may occur in which the primary control frequency of the UAS is lost whilst the controller is powered on. The UAS shall hover automatically when communication with the controller is lost. The Failsafe feature (refer to Appendix C and Appendix D ) is activated once communication with the controller has been lost for more than 3 seconds. The UAS shall use its Failsafe feature to ensure that the UAS will hover automatically and eventually return to the landing point when the signal does not restore. Wh en such a situation occurs, the following steps shall be taken by the flight crew: PIC: Informs crew members of the situation by calling “CONTROL SIGNAL LOST” PIC: W ait for a possible reconnection to the UAS within a short length of time. PIC: W hile wai ting, check controls to see if no buttons or switches have accidentally been pressed or switched.

IF THE CONNECTION WI TH THE UAS IS RESTORED: PIC: Regain control of the UAS by toggling the control mode switch once. 1 PIC: Inform crew members of the situat ion by calling “CONTROL REGAINED” PIC: Safely navigate the UAS back to the landing area as quickly as possible. PIC: Perform Landing procedure (refer to Part B, 3.4).

IF THE CONNECTION WI TH THE UAS IS NOT RESTORED: After loss of signal for more than 3 sec onds, the flight controller will calculate the safest route to the hom e position and control the aircraft to return home, hovering over the GPS start point and landing automatically (refer to Appendix C or Appendix D ). Wh en the Failsafe feature is activate d, the following course of action applies: PIC: Maintain VLOS with the UAS. Observer: The observer shall ensure that the take

- off and landing area, which is where the GPS position of the UAS was defined, remains clear for the UAS to make an emergency landing. Observer: W hen the UAS strays off from the expected return path (refer to 4.1.8), inform members of the public, the police of the emergency situation, ATC of approximate height, heading, speed and flight endurance and attempt to keep safe separation between the public and the UAS. PIC: W hen the UAS has returned to its GPS sta rt point, perform shut

- down procedures of the UAS.

**4.1.2 Ai**  **rcraft battery failures** An aircraft batter y failure may occur, resulting in loss of power to multiple engines. In such a situation, refer to Appendix C for the DJI Phantom 2 and Appendix D for the DJI P hantom3

.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 24 **4.1.3 Transmitter or transmitter battery failure**  In case of a transmitter or transmitter batter y failure, the control of the UAS will be lost. The UAS shall hover automatically when communication with the controller is lost. The Fails afe feature (refer to Appendix C and Appendix D ) is activated once communication with the controller has been lost for

mo re than 3 seconds. The UAS shall use its Failsafe feature to ensure that the UAS will hover automatically and eventually return to the landing point when the signal does not restore. W hen such a situation occurs, the following steps shall be taken by the flight crew: PIC: Informs crew members of the situation by calling “CONTROL SIGNAL LOST”. PIC: Check to see if no buttons or switches have accidentally bee n pressed or switched.

IF TRANSMITTER IS NOT POW ERED ON: PIC: Swap batteries to see if the transmitter can be powered back on with a different batter y. Keep checking with different batteries

IF THE CONNECTION WI TH THE UAS IS RESTORED: PIC: Regain control of the UAS by toggling the control mode switch once. 2 PIC: Inform crew members of the situation by calling “CONTROL REGAINED” PIC: Safely navigate the UAS back to the landing area as quickly as possible. PIC: Perform Landing procedure (refer to Part B, 3. 4)

IF THE CONNECTION WI TH THE UAS IS NOT RESTORED: After loss of signal for more than 3 seconds, the flight controller will calculate the safest route to the hom e position and control the UAS to return home, hovering over the GPS start point and landing automatically. Wh en the Failsafe feature is activated, the following course of action applies: PIC: Maintain VLOS with the UAS. Observer: The observer shall ensure that the take

- off and landing area, which is where the GPS position of the UAS is defined re ma ins clear for the UAS to make an emergency landing. Observer: W hen the UAS strays off from the expected return path (refer to 4.1.8), inform members of the public, the police of the emergency situation, ATC of approximate height, heading, speed and flig ht endurance and attempt to keep safe separation between the public and the UAS. PIC: W hen the UAS has returned to its GPS start point, perform shut

- down procedures of the UAS.

**4.1.4 Ma**  **licious or accidental interference with control frequency** Even though it is highly unlikely that malicious interference with the control frequency may occur during the operation (refer to Part B, 2.6), one cannot exclude this situation from happening. Interference with the control frequenc y m ay result in a situation in which the s ignal is lost (refer to Part B, 4.1.1) or may

result in otherwise unexpected behavior of the UAS. There are two situations that should be considered when interference with the control frequency is identified:

Situation 1: Malicious interference Wh en m alic ious interference is suspected or identified the following course of action applies: PIC: Informs crew members of the situation by calling “CONTROL INTERFERENCE” Observer: Call the local police and local air traffic control to advise them of approximate he ight, heading, speed and flight endurance. PIC: Maintain VLOS with the aircraft and be ready to regain control if/when the interference stops. Observer: Keep operating area safe for members of the public by informing and instructing them, closely watching the flight path of the UAS. Observer: Lookout for possible suspects in the operating area that might be interfering with the controls.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 25 IF/ WH EN THE INTERFERENCE WI TH THE UAS STOPS DURING FLIGHT: Inform crew members of the situation by calling “CONTROL REG AINED” Safely navigate the UAS back to the landing area as quickly as possible. Perform Landing procedure (refer to Part B, 3.4). Tal k with local police about the situation and possible suspicions.

Situation 2: Accidental interference PIC: Informs crew m em bers of the situation by calling “CONTROL INTERFERENCE” PIC: Maintain VLOS with the aircraft and be ready to regain control if/when the interference stops, closely watching the flight path of the UAS. Observer: Keep operating area safe for members of the public by informing and instructing them.

Note: W hen signal interference occurs, the flight controller may activate the Failsafe feature (refer to Appendix C or Appendix D ) and will calculate the safest route to the home position and control the UAS to r eturn home, hovering over the GPS start point and landing automatically.

**4.1.5 Pilot incapacitation**  An em ergency situation may occur in which the pilot is incapacitated and may therefore not be able to operate the UAS. In such a situation, it depends on the comp osition of the flight crew which course of action applies:

Situation 1: 1 PIC (incapacitated), 1 Observer, 1 Payload operator Pa yload operator: Calls “PILOT INCAPACITATED”. Pa yload operator: Toggles the Failsafe switch on the controller (refer to Appendix C or Appendix D ). This activates the Failsafe feature, which ensures the UAS safely reaches the landing area and auto

lands itself. 1) Pa yload operator: Makes sure the landing area is safe and free of any p ublic for the UAS to safely auto

- land. Observer: Calls emergency services that will assist the PIC. Observer: Checks whether the PIC is in a stable condition and otherwise applies first

- aid techniques to help the PIC. Observer: If/

Wh en the incapacitated PIC is in a stable condition, the observer shall ensure a safe operating area by informing and instructing members of the public if needed.

Situation 2: 1 PIC (incapacitated), 1 Observer Observer: Toggl es the Failsafe switch on the controller (refer to Appendix C or Appendix D ). This activates the Failsafe feature, which ensures the UAS safely reaches the landing area and auto

- lands itself. Observer: Calls emergency services that will assist the PIC. Ob server: Checks whether the PIC is in a stable condition and otherwise applies first

- aid techniques to help the PIC. Observer: Attempts to get help from members of the public if possible that can take over helping the PIC. Observer: Makes sure the landing a rea is safe and free of any public for the UAS to safely auto

- land.

**4.1.6 Ai**  **rcraft incursion** An aircraft incursion may occur when another operator or aircraft breaches the operating limitations (Appendix C or Appendix D ) of the UAS. The following course of act ion applies: All crew members: If a crew member notices a possible aircraft incursion, the call “AIRCRAFT INCURSION” is made to notify all crew members of the situation. PIC: Attempt to prevent aerial collision by keeping VLOS with the UAS and directing it away from the other aircraft.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 26 Observer: Informs the PIC about the position and course of the other aircraft so the PIC can respond accordingly. Observer: Observes the operating area to identify possible other operators that might control the other aircra ft. If the operator is found, he can be instructed to land his/her aircraft.

**4.1.7 View incursion**  During the operation, the PIC may lose its VLOS with the UAS. This emergency procedure shall be initiated when the view incursion lasts longer than three seconds (a s estimated by the PIC). If this situation occurs, the following course of action applies: PIC: Bring the aircraft in a hover position by not touching the controls. PIC: Informs the crew of the situation by calling “VLOS LOST” Observer: Attempts to ma intain or regain VLOS with the aircraft to instruct the PIC by changing his/her position on the ground. PIC: Changes his/her own position on the ground to re

- establish VLOS with the UAS.

IF THE OBSERVER HAS VLOS W IT H THE UAS Observer: Instructs the posi tion on the ground that the PIC should take to regain VLOS. Observer: Maintains VLOS with the UAS to instruct the PIC if the UAS should need to change its position (i.e. to prevent collision with object/surroundings).

WH EN THE PIC REGAINS VLOS WI TH THE UA S PIC: Informs the crew of the situation by calling “VLOS ESTABLISHED” PIC: Safely navigate the UAS back to the landing area as quickly as possible. PIC: Perform Landing procedure (refer to Part B, 3.4)

**4.1.8 Fly away actions**  A situation might occur in which th e UAS becomes unresponsive to the flight controls of the PIC and flies away from the operating area. If this situation occurs, the following course of action applies: PIC: Informs the crew of the situation by calling “FLY A WA Y” PIC: W ait for a possible rec onnection to the UAS within a short length of time. PIC: W hile waiting, check controls to see if no buttons or switches have accidentally been pressed or switched.

IF CONTROL OF THE UAS IS REGAINED: PIC: Inform crew members of the situation by calling “CO NTROL REGAINED” PIC: Safely navigate the UAS back to the landing area as quickly as possible. PIC: Perform Landing procedure (refer to Part B, 3.4)

IF CONTROL OF THE UAS CANNOT BE REGAINED: Observer: Call local police to inform them of the situation. Call local air traffic control to advise them of approximate height, heading, speed and flight endurance. PIC: Keep VLOS with the UAS and attempt to follow its position Observer: Keep VLOS with the UAS and attempt to follow its position on ground. Observer: Keep surrounding area of the UAS safe for members of the public by informing and instructing them. Pa yload operator (if part of the crew): W atch the video feed received from the camera to determine the location and direction of the UAS. PIC: Attempt to re gain control of the aircraft continuously by checking the controller and batteries.

IF THE SITUATION RESULTS IN A LOSS OF POW ER Refer to Part B, 4.2 Situation 2.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 27 **4.1.9 Loss of UA**  **S** A situation may

o ccur in which the UAS is lost during the operation as the result of mechanical failure or pilot error. In this situation, the following course of action applies: 1) PIC: Informs the crew of the situation by calling “UAS LOST”. 2) PIC: Executes power

- off procedure on the flight controller to possibly stop the engines if these are still running. 3) Observer: Makes way to the crash site as quickly as possible. 4) Observer: Calls em ergency response services if needed and informs local police about the situation. 5) Observer & PIC: Secure the area where the UAS has com e down by ke eping the me mb ers of the public at a safe distance of at least 50 meters. 6) PIC: Initiates accident investigation procedure (Refer to part A

– 15).

**4.1.10 Loss of flight controller**  A situation may occur in which the PIC loses the ability to control the UAS with the flight controller. A possible cause for this situation is a technical failure of the flight controller itself. If this occurs, execute the emergency procedure as described in Part B, 4.1.3. It is also possible that the controller is hijacked. If this situation oc curs, the following course of action applies: 1) PIC: Informs crew members of the situation by calling “CONTROL HIJACK” 2) Observer: Call the local police to and local air traffic control to advise them of approximate height, heading, speed and flight endurance. 3) PIC: Attempt to maintain VLOS with the UAS and negotiate with the suspect to regain the controller. 4) Observer: Keep operating area safe for members of the public by informing and instructing them, closely watching the flight path of the UAS. 5) All flight crew: W ait for local police to respond to the situation and assist them in any way they request. Ensure the safety of the public and personal safety.

IF/ WH EN CONTROL IS REGAINED DURING FLIGHT: I. Inform crew members of the situation by calling “CONTROL REGAI NED” II. Safely navigate the UAS back to the landing area as quickly as possible. III. Perform Landing procedure (refer to Part B, 3.4) IV. Tal k with local police about the situation and suspicions.

**4.1.11 Public encroachment**  During the operation, the UAS and the flight team may attract the attention from members of the public in the operating area. Even though CNT shall take precautionar y m easures (refer to Part A, 2.5) to lim it the chances of public encroachment, the situatio n may still occur. If the situation occurs, the following procedure applies: 1) Observer: Notifies the PIC by calling “PUBLIC ENCROACHMENT” of the situation on ground. 2) PIC: Maintains VLOS with the UAS and is only concerned with the safe operation of the UAS. The PIC makes sure to position the UAS in a holding position at a safe distance from the public. 3) Observer: Ensures the safety of the PIC and thereby control of the UAS by making sure the PIC does not get distracted from flying the UAS. 4) Observer (and payloa d operator): Wh en the safety of the PIC is guaranteed, the observer shall inform and instruct members of the public to clear the area.

WH EN THE OBSERVER MANAGES TO CLEAR THE AREA: I. Observer: Notifies the PIC by calling “PUBLIC CLEAR”. II. PIC: Safely navigate the UAS back to the landing area as quickly as possible.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 1 st January 201 5 28 III. PIC: Perform Landing procedure (refer to Part B, 3.4)

WH EN THE OBSERVER DOES NOT MANAGE TO CLEAR THE AREA: I. Observer: Notifies PIC by calling “PUBLIC WO N’T CLEAR” II. Observer: Keeps the PIC focused on controlling the UAS and informs the PIC about possible landing areas. III. PIC: Notify the flight crew of the intention to make an emergency landing by calling “IMMEDIATE LANDING” IV. PIC: Initiate landing procedure immediately. Wh en a predetermined landing area is nearby that is clear of any members of the public, the PIC will attempt to land the UAS in this area. Otherwise, the PIC shall identify the nearest safe area to land the aircraft safely. V. PIC: Communicate the location of the landing area to the observer. VI. O bserver: Attempt to keep the intended landing area clear to ensure the safety of members of the public and the flight team. VII. PIC: Safely land the UAS in the landing area and perform shut

- down procedures (Refer to Part B, 3.5)

**4.1.12 Fire**  A situation may occur in which the UAS catches fire during the operation. If a fire is suspected by any

me mb er of the flight team or a member of the public, the following course of action applies:

1) All flight crew: Make sure the PIC is notified of the situation by calling “FIRE”. 2) PIC: Notify the flight crew of the intention to make an emergency landing by calling “IMMEDIATE LANDING” 3) Observer: Informs the PIC about possible landing areas. 4) PIC: Initiate landing procedure immediately. Wh en a predetermined landing area is nearby, the P IC will attempt to land the UAS in this area. Otherwise, identify the nearest safe area to land the aircraft. 5) PIC: Communicate the location of the landing area to the observer. 6) Observer: Clear the intended landing area to ensure public safety. Make sure to ensure personal safety as well and never position yourself directly under the UAS. 7) Observer: Keep operating area safe for members of the public by informing and instructing them, closely watching the flight path of the UAS. 8) PIC: Attempt to maneuver the U AS in such a way that it never flies above any members of the public or a member of the flight team. 9) PIC: Safely land the UAS in the landing area and perform normal shut

- down procedures (Refer to Part B, 3.5).



### INTENTIONA **LLY LEFT BLA NK** **Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 29 

### AP **PENDIX A** 

**– SITE SURVEY, OPERA**  **TION A ND FLIGHT CHECKLISTS** 

A 1: Pre

- site survey



### SITE NAM **E JO**  **B NUM**  **BE**

**R DATE**  LA TI TU DE & LO NGI TU DE:
ft



### TEAM

PI LO T I N CO MMA ND : OBSERV ER: V EH IC ULAR A CCESS: YE S NO
U AV REG IS TRA

TI ON : H EL PER 1 : H EL PER 2 :



### LOCATION **IT EM**  **A CT**  **IO N**  **(U**

**se sky**  **dem on light, google**  **e ar**  **th & m**  **et che**  **ck )**  

### F **IN DI**  **NG**

A IR SPA CE W hat is the A irs pac e? (A ,C ,D ,E,F,G ) - Do I need A TC perm is si on?

TERRA IN W hat is the Terrain? (Flat, M ountainous , Boggy)

PROX IM IT IE S O ther A ir cr aft (A er odr om es , H eli Pads , M odel Sites )

H AZAR DS L iv e Firing, H igh Int ens ity R adio Tr ans mission s, G as Ve nt ing

RESTRI CTI ON S N uc lear Power Stations , Pris ons

SEN SI TI VIT IE S N ature R es erves , Rec re ational A re as , By e Law s

PEO PLE Loc al H abitation (D o w e need to Letter Drop)

LI VE STOCK Loc al Farm s

PERM IS SI ON Loc al A uthority, Land O wn er, M ilitary Spac e

A CCESS Public Right of W ay, G ates & Roads

FOOTPA

TH S Public Footpaths , Bridal Paths

A LTERN AT E A lternative O perational / Take O ff Sites

RI SK REDU CT IO N C an th e job be done at a not her time to a vo id Scho ol times etc

W EA TH ER 24 hour forec as t

N OT AM S A ny Not ic e to A ir me n that m ay effec t operations



### PRE NOTIFICATIO **NS** I f N otified D ate, Tim e & C ontac t N am e LO CA L A IR TR AF FI C CON TRO L:
REG IO NAL A IR TRA FFI C CON TR OL : M IL IT AR Y CO NT RO L:
N OT IC E TO A IR ME N: 

# PRE **SI TE**  **S URV**  **EY**

D OW LOA DE D MAP T O GROUNDS TA TIO N: ( Ti ck) A LTI TU TU DE FROM

SEA LEV EL:
W ORK REQU IR ED:
D AT E W OR K REQU IR ED:**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 30**I T** **E M** **A C** **T I** **O N** **/ C** **H E** **C K** **T I** **C K** AirframeCheckCondition&Airworthiness**I T** **E M** **A C** **T I** **O N** **/ C** **H E** **C K** **T I** **C K** CameraMountCheckCondition&FunctionalityGroundStation&LeadsCheckCondition&FunctionalityFlightController/Transmitter(s)CheckFunctionalityCameraMonitor&LeadsCheckCondition&FunctionalityCalibrationPlatformCheckConditionA/VReceiver&LeadsCheckCondition&FunctionalityTelemetryReceiver&LeadsCheckCondition&Functionality**I T** **E M** **A C** **T I** **O N** **/ C** **H E** **C K** **T I** **C K** Laptop&LeadsCheckCondition&FunctionalityCamera(s)&Lens(s)CheckCondition&FunctionalityMobilePhone&EmergencyNo'sCheckCondition&FunctionalityCameraConnectionLeadsCheckConditionAnemometerCheckCondition&QuantityCameraMemoryCardsCheckCondition&SpaceFirstAidKit&FireExtinguisherCheckCondition&ContentsCameratoAirframeLanyardCheckCondition&SecurityCrewIdentificationCheckRequirements&QuantityCameraAttachmentBoltCheckConditionFluorescentJacket(s)/HardHatsCheckCondition&QuantityTwoWayRadiosCheckCondition,Charge&Function**I T** **E M** **A C** **T I** **O N** **/ C** **H E** **C K** **T I** **C K** Clothing(Boots,Coat,Gloves)CheckConditionMultiFunctionBatteryChargerCheckCondition&FunctionalityAirNavigationMapCheckConditionRequiredChargerLeadsCheckConditionChecklists,Manuals&LogbooksCheckCondition&CurrentBatteryCheckerCheckFunctionalityNotepad&PensCheckConditionSiteAssessmentFormCheckCondition**I T** **E M** **A C** **T I** **O N** **/ C** **H E** **C K** **T I** **C K** Signs,SafetyTape,ConesCheckCondition&QuantityScrewdrivers(Flat/CrossDrive)CheckConditionAllenKeysCheckCondition**I T** **E M** **A C** **T I** **O N** **/ C** **H E** **C K** **T I** **C K** Pliers(Standard/LongNose)CheckConditionFlightBatteryPacksCharge&CheckConditionCableTies(VariousSizes)CheckCondition&QuantityTransmitterBatteryPacksCharge&CheckConditionSideCuttersCheckConditionCameraBatteryPacksCharge&CheckConditionNylockPropellerNutsCheckCondition&QuantityGroundStationBatteryCharge&CheckConditionSpareProps.(Tractor&Pusher)CheckCondition&QuantityChargerBatteryPacksCharge&CheckConditionSmallSocketSetCheckConditionMobilePhoneBatteryCharge&CheckCondition**E M** **B A** **R K** **A T** **I O** **N C** **H E** **C K** **L I** **S T**  A 2 : Embarkation checklist**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 31 

### A **3: A rrival checklist**  

# ARRIVAL CHECKLIST **ITEM AC**  **TION / CHECK TICK** 

SITE SURVEY CARRY OUT SITE SURVEY WI TH OBSERV ER FLIGHT PLAN / BRIEF CONFIRM FLIGHT PLAN & BRIEF CREW

, OBSERVER & CLIENT AIRFRAME UNLOAD & CHECK AIRFRAME FOR ANY DAMAGE IN TRANSIT CAMERA ATTATCH TO PLATFORM & FIT SAFETY LANYARD A/V CONNECTION INSERT A/V PLUG AND SECURE PROPELLERS C HECK SECURING NUTS FOR TIGHTNESS (Replace if Removed) CALIBRATION PLATFORM POSITION AS REQUIRED & ENSURE LEVEL WI TH SPIRIT LEVEL GROUND STATION SETUP, S WI TCH ON AND TEST OPERATION A/V MONITOR SETUP, S WI TCH ON AND TEST OPERATION CREW I DENTIFICATION BADGES ISSUE AS REQUIRED

HARD HAT / FLOURESCENT JACKETS ISSUE AS REQUIRED

TW O WA

Y RADIOS ISSUE AS REQUIRED FIRST AID KIT POSITION TO BE EASILY ACCESSIBLE & INFORM CREW OF LOCATION FIRE EXTINGUISHER POSITION TO BE EASILY ACCESSIBLE & INFORM CREW OF LOCATION CREW / HELPERS POSITIONAS REQUIRED TO MAINTAIN SAFE FLYING ZONE CORDENS, SIGNS & SAFETY TAPE SETUP AS REQUIRED TO MAINTAIN SAFE OPERATION**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 32 

### A **4: On**

**- site**  **survey**

**checklist**



## DAT **E WIND SPEED** 

KN OTS



## PILO **T: TE**  **MP**

**. DI**  **RECT**

**ION OB**  **SERVER:** *C



## ITEM **CHECK FINDING** 
O BSTRU CTI ON S

V IE W LI MIT AT IO NS A nything that m ay

im pair line of s ight vis ion PEO PLE I s a C or don r equired or s om e kind of c ro wd c ontrol LI VE ST OCK A ny A nim als or W ildlife SU RFA CE Flat S ur fac e, Rough, Sloped, W et PERM IS SI ON Do W e Have the Land O wners Perm is si on PU BLI C Public Ri ght of W ay, Footpaths , G ates A IR TRA FFI C Do W e Need & or H av e C learanc e COM MU NIC AT IO N Tw o W ay Ra dios Required PROX IM IT Y A re W e Far E nough A

wa y from Buildings etc

. TA KE O FF A REA W here is the Safes t Convenient Pos ition LA ND ING A REA W here is the Safes t Convenient Pos ition O PERA TI ON AL Z ON E A

re there A

ny Haz ards or O bs truc tions EM ERG EN CY

A REA W here is the Safes t Convenient Pos ition H OL DI NG AR EA W here is the Safes t Convenient Pos ition



## CONT **ACT NUM BE** 

**RS**
PI LO T: O BSERV ER: CLI EN T: LO CA L P OL IC E: LO CA L HO SPI TA L: LO CA L A IR TR AF FI C CON TROL : EU RO US C:

N OT ES: 

# ON **SIT E SU**  **RV EY** 

M as ts , w ires , Buildings , Train Lines , Trees , Lakes

, Ri ver s, Canals or I ndus trial H az ar ds**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 33 

### A **5: Pre**

**- flight checklist** 


# PRE **FLI GH**  **T C**

**HE CKL**  **IS T**  **ITEM ACT**  **IO N**  **/ C HE**  **CK TI**  **CK**

AI RFRA ME CHECK FO R DA MA GE, W EAR, TI GHTN ES S O F FI TTI NGS , CO ND IT ION A ND SE CU RE FI TM ENT OF PR OPE LLER S A ND SE CU RE A TTA TC HME NT OF CA MERA FL IG HT B ATTER Y NO TE BA TTER Y NUMBER IN BA

TTERY LO GBO OK, R EC OR D PRE -FL IG HT B ATTER Y POWE R % A ND FI T I NTO A IR FRA ME (No L ower t ha n 9 0% ) TRA NS MI TTER (S) SW IT CH O N, CHE CK BA TTER Y P OWE R I S W IT HI N SA FE PA RAMETERS , ENSURE TR IM S A RE NUETRAL AND ALL S WI TC HES A RE I N TH ERE CO RRE CT POSI TI ON S CA MERA SW IT CH O N AND CO NF IR M CO RRE CT O PE RA TI ON AI RFRA ME ENS URE AI RCRA FT I S L EVEL ON THE CA LI BRA TI ON PL AT FOR M FL IG HT B ATTER Y CA LL " CL EA R P RO PS " A ND CO NNECT FLI GHT BATTERY SE LF DI AGNO STI C WA IT FO R DI AGNO ST IC TO FI NI SH & G PS L OC K T O BE ESTABL IS HED (Fl ash in g Bl ue L ig ht ) MON IT OR CHECK FUNCT IO N & QU ALI TY OF A /V L IN K FRO M CA MERA CA LI BRA TI ON MO VE LEF T TRA NS MI TTER STI CK T O TO P L EFT CO RN ER & WA IT FO R BE EP SA VE CA LI BRA

TI ON MO VE LEF T TRA NS MI TTER STI CK T O TO P R IG HT CO RN ER & WA IT FO R BE EP CA MERA P LATF OR M TES T FO R CO NTR OL A ND OPE RA

TI ON TELEMETRY LI NK ENS URE GRO UND STATI ON A ND TR ANS MI TTER DI SPL AYS AR E CO NNEC TED FL IG HT PL AN LO AD I N FLI GHT P LAN FROM GRO UND STA TI ON I F RE QU IR ED (Be ep for E ach Wa ypoi nt ) CA MERA START RECO RDI NG AI RCRA FT A LI GNMENT REP OS IT IO N AI RCRA FT I N TAK E OFF A RE A ON L EVEL GRO UND FA CI NG I NTO WIN D CRE W, PU BL IC & CL IE NT ENS URE ALL C REW , PU BL IC & CL IE NT AR E I N CORRE CT SA FE POSI TI ON S CL EAR ENC E DO WE HA VE CL ER ENCE FRO M A IR TRA FFI C CON TR OL I F REQUI RE D? POWE R UP CA LL " TA KIN G OF F " A ND START MO TO RS (L ef t Tr an sm it ter Sti ck t o Bot to m Ri gh t Cor ne r) TAK E O FF TAK E ON E FI NAL QU IC K L OOK A RO UND , CHECK W IT H O BSERV ER THA T THEY AG REE IT I S SA FE TO FL

Y, POWE R UP A ND TA KE O FF COM MUNI CA

TI ON TH RO UGHO UT ENTI RE FL IG HT STA Y IN A UD IA BL E CO NTAC T W IT H O BSE RVER, LI STEN FO R BA

TTERY WA RNI NG S, A IR SPA CE I NFRI NGEMENTS O R P UBLI C ENC RO AC HMENTS LAND IN G BEFO RE LAND IN G, CHE CK WI TH OB SE RVER, HO VER O VER L AND IN G A RE A. TA KE A QU IC K L OOK BEL OW A IR CRA FT A ND CA LL " LA ND ING " A ND TH EN LAND

.**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 34 

### A **6: Post**

**- flight checklist** 



# PO **ST FLI**  **GH T C**  **HE CKL**  **IS T**  **ITE M**  **ACT IO**  **N / C**  **HE CK**  **TI CK** 

TO UC HDO WN UP ON TO UCHDO WN EMMI DI ATELY STO P MO TO RS (L ef t Tr an sm it ter St ic k t o Bott om

Lef t Cor ne r) POWE R DO WN WA LK TO A IR CRA FT , DI SCON EC T FLI GHT BA

TTERY AND C ALL " SAFE "
REMO VAL REMO VE AI RCRA FT FRO M LA ND IN G AR EA
DA TA R EC OR DI NG RECO RD FL IG HT T IM E DE TAI LS IN PI LO TS LO GBO OK & BA TTERY LO GBO OK
TRA NS MI TTER SWI TC H O FF T RA NSMI TTER
CA MERA ST OP R EC OR DI NG AND SW IT CH O FF
AI RFRA ME CHECK FO R DA MA GE, WE AR , TI GHTNESS O F FI TTI NGS, CO NDI TI ON A ND SECURE

FI TMENT OF PROPE LLER S A ND SE CU RE A TTATCHMENT O F CA MERA BA TTERY REMO VE FLI GHT BA TTERY FRO M A IR CRA FT

, CHE CK RE SI DU AL BATTERY %, RECO RD DETAI LS I N BATTERY LO GBO OK & PL AC E O N CHA RGE I N LI PO SA FE B AG PR OV ID ED THAT TH E BA

TTERY I S N OT

W AR M (I f So A llo w to Cool )
ME MO RY CA RD REMO VE FRO M CA MERA AND BA CK U P T O GRO UND ST ATI ON
REV IE W REV IE W IM AG ES A ND DI SCU SS WI TH CREW A ND O R CL IE NT IF REQ UI RE D**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 35



### AP **PENDIX B** 

**– RECORDS FOR EA**  **CH FLIGHT**

**B 1: A**  **ircraft Pilot and Crew Log Cloud Nine Technologies, LLC**  Operations Manual

Issue 1

. 0 : 1 st January 201 5 36 

### B **2. Incident Log**



### INCIDENT LOG

**Date of**  **In ci**  **dent Time of** 

**incident In** 

**jurie s/**  **Dam ag**  **e In**  **ci de**  **nt de**  **tai ls**  **Ac ti**  **on t ak**  **en / I ncident**  **Report Notes** 

e.g. Ongoi ng I nve st ig at io n**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 37 

### B **3: Maintenance Log**

**MA IN**  **TENANCE LOG**

DA TE RE ASO N FOR

MAI NT ENANC E WO RK DO NE PAR TS R EPL AC ED SYST EM T EST ED YES OR N O NOT ES**Cloud Nine Technologies, LLC** Operations Manual

Issue 1

. 0 : 1 st January 201 5 38 

### B **4: Battery**

**Charge Log**

BAT TE RY NUM BER BAT

TE RY R ESI DUA L % BEFO RE C HA RGE DA TE O F CHA RGE CHA RGE I NP UT

mAh FLI GHT

DURA TIO N PR E- FLI GHT

BAT TE RY C HA RGE % NOT ES 

### BA **TTERY CHARGE LOG Cloud Nine Technologies, LLC**  Operations Manual

Issue 1

. 0 : 1 st January 201 5 39 

### B **5: Software Update Log**

**SO FTWARE UPDATE LOG** 

DA TE CURRE NT

SO FT WAR E/FI RM WAR E VER SI ON UPDA TE D

SOFT WAR E/FI RM WAR E VER SI ON SU CCE SFU L INS TA LLA TI ON YES OR N O SYST EM T EST ED

YES OR N O NOT ES