' ' 

CURRAN & CURRAN LAW 

662 ENCINITAS BLVD. SUITE 260. ENCINITAS. CALIFORNIA 92024 

TELEPHONE 760. 634. 1229 FACSIMILE 760. 634. 0729 

August28,2015 

U.S. Department of Transportation 

Docket Management System 

1200 New Jersey Ave., SE 

Washington, DC 20590 

- ; "MICHAEL D. CURRAN, ESQ., ATP 

'.: S,USAN M. CURRAN, ESQ. 

Re: Exemption Request; Section 333 of the FAA Modernization & Reform Act and 

Part 11 of the Federal Aviation Regulations from 14 C.F.R. 45.23(b);14 CFR Part 

21;14 CFR 61.113 (a) & (b); 91.7 (a); 91.9 (b) (2); 91.103(b); 91.109; 91.119; 

91.121; 91.151 (a); 91.203(a) & (b); 91.405 (a); 91.407(a) (1); 91.409 (a) (2); 

91.417 (a) & (b). 

Dear Sir or Madam: 

Petitioner Mark D. Willis, Consulting hereby petitions the Secretary of Transportation 

and Federal Aviation Administration ("FAA") for exemption to the above referenced and below 

more fully described Federal Aviation Regulations, (''FARs") that currently may, or may not 

apply to the recreational/commercial operations of model aircraft/small unmanned aerial 

vehicles/systems ("SUAV"). 

1. Prefatory Statement to Petition 

In June, 1981, the FAA published an advisory circular, AC 91-57, (an advisory 

publication giving non-regulatory information/guidance. Advisory circulars do not create or 

change regulations and are not binding on the public.) AC 91-57 was entitled "Model Aircraft 

Operating Standards" and gave non-regulatory suggestions to model aircraft operators on 

suggested procedures for operating their models. This was the sole publication by the FAA 

which addressed SUAV for the next nearly 25 years. 

In September 2005, the FAA appeared to turn its' attention toward unprecedented 

attempts at regulating model aircraft specifically the more modern SUAV. The FAA, for the 

first time in history now termed these devises as Unmanned Aerial Systems ("UAS") seemingly 

to align with their attempts at enforcement. The FAA published "AFS-400 UAS POLICY 05-01 

-Unmanned Aircraft Systems Operations in the U. S. National Airspace System- Interim 

Operational Approval Guidance." This interim internal FAA memo expressly confirms that 

"[t]his policy is not meant as a substitute for any regulatory process." Still, it purported to 

"require" a Certificate of Authorization ("GOA") or Waiver to use SUAVS. The new FAA policy 

relied for legal/regulatory "authority" on the non-regulatory, AC 91-57 

Page 1 of 20 
' . 

. . 

In February, 2007 the FAA, published a 2007 "policy statement" in the Federal Register. 

The 2007 Policy Statement started by defining "unmanned aircraft" as "a device that is used or 

intended to be used, for flight in the air with no onboard pilot" and it purported to include "a 

remotely controlled model airplane used for recreational purposes." The FAA termed these 

devices "UAS" and then purported to articulate the new FAA "policy" for "UAS" operations was 

that "no person may operate a "UAS" in the National Airspace System without specific 

authority." For the first time ever, the 2007 Notice purported to articulate two new alleged 

"rules": (1) Model aircraft can no longer be operated for a "business" purpose; and (2) a Model 

aircraft operated for a business purpose requires a COA, or special Certificate of Operating 

Authority and therefore is subject to the FAR's. 

Thereafter beginning in 2007 and continuing to present based on these two new FAA 

internal "policies" and without citing to any actual federal law, or FARs, the FAA then sent 

various cease and desist notices to model aircraft/SUAVS operators indicating their activity 

was not authorized and describing the COA process and threatening to impose a $10,000 fine 

if they did not comply with the new FAA policies which the FAA indicated created a "ban" on 

using SUAVS for a "business/commercial purpose." The FAA's current position is the 

business/commercial use of SUAVS is "not authorized." 

In 2012, following the FAA's attempts to regulate using internal policy memos, Congress 

enacted the Federal Aviation Administration Reform and Modernization Act, ["FRMA"]. The 

FRMA allows the Secretary of Transportation to "exempt" SUAVS from existing Federal Law, 

FARs to the extent any federal law or FAR actually currently apply to SUAVS. 

Recently, on February 15, 2015 in Washington, D.C. at just after 10 a.m. EST, the FAA 

released their proposed rules for small SUAVS incorporating them into the National Airspace 

System ["NAS"]. These are proposed rules that have yet to go through the statutory Federal 

Rule making process to actually become law, but at present they are instructive for current 

model aircraft!SUAV recreational and commercial operators. They include staying below 500 

ft. AGL, below 100 mph, staying out navigable airspace, staying away from airspace 

surrounding airports, seeing and avoiding other aircraft, taking a FAA knowledge test and a 

number of other common sense proposed rules, that this firm believes will ultimately govern 

SUAVS operations. See, http://www.faa.gov/regulations_policies/rulemaking/media/021515_ 

sUAS_Summary.pdf 

Most recently, Petitioner is aware the FAA has granted similar exemptions across the 

country for aerial photography and other uses that benefit the public and enhance aviation 

safety. 

Petitioner at all times has and currently operates their SUAVS following the safety 

guidelines of AC 91-57. 

Petitioner respectfully makes this request as suggested by the FMRA and the FAA. 

Ill 

Page 2 of 20 
2. Petition for Exemption 

With the above preface, pursuant to Section 333 of the FAA Modernization and Reform 

Act of 2012 ("FMRA") and 14 C.F.R. Part 11, Petitioner Mark D. Willis, Consulting, requests 

exemption to use SUAVs to map archaeological landscapes and individual archaeological 

sites, monitor environmental conditions in and around construction zones and associated 

areas of interest, to assist and augment traditional ground survey, to safely map and monitor 

Recognized Environmental Conditions as part of Environmental Site Assessments. 

In addition, Petitioner intends to use the SUAVs for aerial photography/ inspection/ 

mapping including but not limited to the following; aerial photography/ inspection/mapping 

services for Archaeological sites as well as aerial photography/ inspection/mapping for roads, 

pipelines and pipeline corridors, cell towers, wind farms, and for general land management all 

in non-navigable airspace, using non-intrusive recording devices, operation in otherwise 

unrestricted US States/Territories; to allow commercial operation of its SUAVS, so long as 

such operations are conducted within and under the conditions outlined herein, or as may be 

established by the FAA, or as required by Section 333. 

3. Name and Address of the Petitioner 

Mark Willis Consulting is a professional archaeological, ethnographic, paleontological, 

and historical consulting service that primarily maps archaeological landscapes and individual 

archaeological sites, monitors environmental conditions in and around construction zones and 

associated areas of interest, assists and augments traditional ground survey, safely maps and 

monitors Recognized Environmental Conditions as part of Environmental Site Assessments 

and operates in compliance with the National Historic Preservation Act and other regulations. 

Contact information/person: 

Mark DeWayne Willis 

835 Zappa Drive 

Cedar Park, Texas 78613 

willis.arch@gmail.com 

512-593-2199 mobile 

512-461-7982 mobile 

4. Public Interest 

As described more fully below, the requested exemption would permit the operation of 

SUAV under controlled conditions in airspace that is 1) limited 2) predetermined; and 3) 

controlled as to access. The exemption would also provide safety enhancements to the 

already safe operations within the aerial mapping, inspection and photography industry 

presently using conventional aircraft by using small, unmanned and relatively inexpensive 

SUAV. 

Page 3 of 20 
Approval of this exemption would thereby enhance safety and fulfill the Secretary of 

Transportation's (the FAA Administrator's) responsibilities to" ... establish requirements for the 

safe operation of such aircraft systems in the national airspace system." Section 333(c) of the 

FMRA. By authorizing E384/Phantom operations, the FAA would advance the public 

interest by reducing the number of manned aircraft in the NAS; reducing air and noise 

pollution; reducing the risk to life and property on the ground; and increasing agricultural 

economic growth. 

Petitioner asserts that allowing E384/Phantom operations would reduce the burden on 

air traffic controllers; would reduce air and noise pollution from the manned aircraft that would 

otherwise be used; would reduce fuel use, as the E384/Phantom is battery-powered unlike the 

manned aircraft it would replace; and would reduce the risk to life and property on the ground, 

as the E384/Phantom contains no pilot and is constructed of a small, lightweight foam 

airframe. 

Finally, the petitioner asserts that the high-resolution image data generated from 

E384/Phantom would provide scientists with important information that would assist efforts in 

aerial photography/inspection/mapping including but not limited to the following; aerial 

photography/inspection/mapping services for Archaeological sites as well as aerial 

photography/inspection/mapping for roads, pipelines and pipeline corridors, cell towers, wind 

farms, and for general land management all in non-navigable airspace, using non-intrusive 

recording devices. 

The petitioner asserts that all of this would result in a major increase in economic 

growth, which would be in the public interest. 

5. Precedent for Granting Exemption for E384/Phantom 

There is a precedent for the requested exemption using the same SUAV, the E384 in 

the matter of the petition of PRAVIA, LLC On January 29,2015 the FAA granted/issued 

Exemption No. 11166, Regulatory Docket No. FAA-2014-0790. There are numerous grants 

across the country using the DJI Phantom 2 series of SUAV. 

The E384 SUAV is manufactured by Event 38 located in Akron, Ohio. The system 

consists of a lightweight battery operated aircraft, ground control station, and associated data 

link equipment. The E384 airframe is constructed of EPO foam with a carbon fiber tail and 

weighs 5.9 lbs. with a wingspan of 6.2 ft. and total length of 4.3 ft. The E384 is powered by two 

lithium polymer batteries that drive an electric propeller. It is hand launched, has maximum 

flight time of 100 minutes, and operates at a cruising speed of 27 mph. The ground control 

station consist of a Turnigy 9XR remote and PC computer which have a maximum data link 

range of 5.4 NM. If the E384 loses link with the ground control station or detects a low battery 

state at any time it will initiate a return-to-launch sequence. 

The E384 has extensive flight experience and a history of operational success 

overseas, including flights by over one hundred professional operators on 6 continents. Jt has 

been used in Uganda to survey potential land for the construction of a hydroelectric power 

Page 4 of 20 
plant. It has also been used in Greece by the National Technical University of Athens to study 

open-pit mining. In Belize the Fishery Department started routine flights with the E384 to track 

illegal fishing in protected waters. More recently in the United States the E384 was flown over 

three days at the Cleveland Airshow, demonstrating its ability to safely integrate and operate in 

the NAS. 

For Petitioner's checklists please see Ex. 1 Attached. For additional information on the 

E384, reference Ex. 2 (E384 Operations Manual), which specify manufacturing information, 

aircraft performance, operating limits, normal and emergency procedures, fail-safe features, 

and maintenance and inspection procedures. 

Petitioner also requests exemption to operate the DJI Phantom 2 group of SUAVS a 

class and category of SUAVs well known to the FAA. The DJI Phantom 2 Operations Manual 

is attached as Ex. 3. 

/II 

/II 

Ill 

Page 5 of 20 
6. Regulations Petitioner Petitions for Exemption, If Such Regulations Apply to SUAVS 

14 CFR Part 21 14 C.F.R. 91.109 14 CFR 91.405 (a) 

14 C.F.R. 45.23(b) 14 C.F. R. 91.119 14 CFR 407 (a) (1) 

14 CFR 61.113 (a) & (b) 14 C.F.R. 91.121 14 CFR 409 (a) (2) 

14 C.F.R. 91.7 (a) 14 CFR 91.151 (a) 14 CFR 417 (a) & (b) 

14 CFR 91.9 (b) (2) 14 CFR 91.203 (a) & (b) 

14 C.F.R. 91.103 

This exemption application is expressly submitted to fulfill Congress' goal in passing 

Section 333 (a) through (c) of the Reform Act. This law directs the Secretary of Transportation 

to consider whether certain unmanned aircraft systems may operate safely in the national 

airspace system ("NAS") before completion of the rulemaking required under Section 333 of 

the FMRA. In making this determination, the Secretary is required to determine which types of 

SUAVS/UAS do not create a hazard to users of the NAS, or the public, or pose a threat to 

national security in light of the following: 

A. The SUAV size, weight, speed, and operational capability; 

B. Operation of the SUAVS in close proximity to airports and populated areas; and 

C. Operation of the SUAVS within visual line of sight of the operator. FMRA § 333 (a). 

Lastly, if the Secretary determines that such vehicles "may operate safely in the national 

airspace system, the Secretary shall establish requirements for the safe operation of such 

aircraft in the national airspace system." /d. §333(c) (emphasis added). The Petitioner 

interprets this provision to place the duty on the Secretary/FAA Administrator to not only 

process applications for exemptions under section 333, but for the Secretary/Administrator to 

affirmatively craft conditions for the safe operation of the SUAVS, if it should be determined 

that the conditions set forth herein do not fulfill the statutory requirements for approval. 

The Federal Aviation Act expressly grants the Secretary/FAA Administrator the authority 

to issue exemptions. This statutory authority, by its terms, includes exempting civil aircraft, as 

the term is defined under §401 01 of the Act, which currently may or hereafter may include 

SUAVs, from the requirement that all civil aircraft must have a current airworthiness certificate. 

The Secretary/FAA Administrator may grant an exemption from a requirement of a 

regulation prescribed under subsection (a) or (b) of this section or any sections 44702-44716 

of this title if the Secretary/FAA Administrator finds the exemption in the public interest. 49 

U.S.C. §44701 (f) See also 49 USC §44711 (a); 49 USC §44704; 14 CFR §91.203 (a) (1 ). 

The Petitioner's SUAV described hereinabove are both fixed wing electric motor type 

configuration as well as multi-rotorcraft equipped with an on board NAZA computer 

stabilization controller and GPS, return to home and other safety features, weighting 55 lbs or 

less and most typically less than 10 lbs., including camera/payload. They operate, under 

normal conditions, at speeds of 5-40 KIAS and at speed of no more than 50 KIAS and have 

the capability to hover and move in the vertical and horizontal plane independently/ 

Page 6 of 20 
simultaneously. They will operate in line of sight and will operate only within the areas 

described herein. Such operations will insure that the SUAVS will "not create a hazard to 

users of the NAS or the "public" as described in the FMRA §333(b). 

Given the small size of the SUAV involved, and the limited environment within which 

they will operate, the Petitioner falls squarely within that zone of safety (an equivalent level of 

safety) in which Congress envisioned that the FAA must, by exemption, allow commercial 

operations of SUAV to commence immediately. Also, due to the size of the SUAVS and the 

restricted areas in which the relevant SUAV will operate, approval of the application presents 

no national security issue. 

Given the clear direction in FMRA §333, the authority contained in the Federal Aviation 

Act, as amended, the strong equivalent level of safety surrounding the proposed operations, 

and the significant public benefit, including enhanced safety, reduction in environmental 

impacts (including reduced emissions associated with allowing SUAV for filming operations 

rather than full-sized aircraft, the grant of the requested exemptions is in the public interest. 

Accordingly, the Petitioner respectfully requests that the FAA grant the requested exemption 

without delay. 

7. Limitations and Conditions 

The Petitioner proposes that the exemption requested herein be issued pursuant the 

limitations and conditions listed herein. These conditions/limitations provide for an even higher 

level of safety to operations under the current regulatory structure which apply to actual 

certificated aircraft because the proposed operations represent a safety enhancement to the 

already very safe SUAV filming operations conducted by recreational SUAVS and conventional 

aircraft. 

Petitioner's primary m1ss1ons include but are not limited to aerial 

photography/inspection/mapping services for Archaeological sites as well as aerial 

photography/inspection/mapping for roads, pipelines and pipeline corridors, cell towers, wind 

farms, and for general land management all in non-navigable airspace, using non-intrusive 

recording devices, operation in otherwise unrestricted US States/Territories; hereby applies for 

an exemption from the listed Federal Aviation Regulations ("FARs") to allow commercial 

operation of its SUAVs, so long as such operations are conducted within and under the 

conditions outlined herein or as may be established by the FAA as required by Section 333. 

Petitioner's primary operational locations shall be in the continental United States. 

These limitations and conditions to which Petitioner agrees to be bound when 

conducting business/commercial operations under this FAA issued exemption are consistent 

with the Administrators previous grant of Exemption include: 

1) Operations authorized by this grant of exemption are limited to the following aircraft 

described in the operating documents which are both a fixed wing E384 and DJI Phantom 2 

Page 7 of 20 
quad-rotor aircraft weighing approximately 5 pounds, any other aircraft will require a new 

petition or a petition to amend this grant. 

2) SUAV operations under this exemption are limited to conducting operations for the 

purpose of aerial photography and inspection for various industries. 

3) The SUAV may not be flown at an indicated airspeed exceeding 50 knots. 

4) The SUAV must be operated at an altitude of no more than 400 feet above ground 

level (AGL), as indicated by the procedures specified in the operating documents. All altitudes 

reported to ATC must be in feet AGL. 

5) The SUAV must be operated within visual line of sight (VLOS) of the operator/pilot in 

command (PIC) at all times. This requires the PIC to be able to use human vision unaided by 

any device other than corrective lenses, as specified on the PIC's FAA-issued airman medical 

certificate. 

6) All operations must utilize a visual observer (VO). The UA must be operated within 

the visual line of sight (VLOS) of the PIC and VO at all times. The VO may be used to satisfy 

the VLOS requirement as long as the PIC always maintains VLOS capability. The VO and PIC 

must be able to communicate verbally at all times. Electronic messaging or texting is not 

permitted during flight operations. The PIC must be designated before the flight and cannot 

transfer his or her designation for the duration of the flight. The PIC must ensure that the VO 

can perform the functions prescribed in the operating documents. 

7) The VO must not perform any other duties beyond assisting the PIC with seeing and 

avoiding other air traffic and other ground based obstacles/obstructions, and is not permitted to 

operate the camera or other instruments. 

8) The operating documents and this grant of exemption must be accessible during 

SUAV operations and made available to the Administrator upon request. If a discrepancy 

exists between the conditions and limitations in this exemption and the procedures outlined in 

the operating documents, the conditions and limitations herein take precedence and must be 

followed. Otherwise, the operator must follow the procedures as outlined in its operating 

documents. The operator may update or revise its operating documents. It is the operator's 

responsibility to track such revisions and present updated and revised documents to the 

Administrator upon request. The operator must also present updated and revised documents 

if it petitions for extension or amendment to this grant of exemption. If the operator determines 

that any update or revision would affect the basis upon which the FAA granted this exemption, 

then the operator must petition for an amendment to its grant of exemption. The FAA's UAS 

Integration Office (AFS-80) may be contacted if questions arise regarding updates or revisions 

to the operating documents. 

9) Prior to each flight, the Operator/PIC must inspect the SUAV to ensure it is in a 

condition for safe flight. If the inspection reveals a condition that affects the safe operation of 

the UAS, the UAS is prohibited from operating until the necessary maintenance has been 

Page 8 of 20 
performed and the UAS is found to be in a condition for safe flight. The Ground Control 

Station must be included in the preflight inspection. All maintenance and alterations must be 

properly documented in the aircraft records. 

1 0) Any SUAV that has undergone maintenance or alterations that affect the UAS 

operation or flight characteristics (e.g. replacement of a flight critical component) must undergo 

a functional test flight. The Operator/PIC who conducts the functional test flight must make an 

entry in the aircraft records. 

11) The pre-flight inspection section in the operating documents must account for all 

potential discrepancies (e.g., inoperable components, items, or equipment, not already 

covered in the relevant sections of the operating documents). 

12) The operator/PIC must follow the SUAV manufacturer's aircraft/component, 

maintenance, overhaul, replacement, inspection, and life limit requirements. 

13) The operator/PIC must carry out its maintenance, inspections, and record keeping 

requirements, in accordance with the operating documents. Maintenance, inspection, 

alterations, and status of replacement/overhaul component parts must be noted in the aircraft 

records, including total time in service, description of work accomplished, and the signature of 

the authorized person returning the SUAV to service. 

14) Each SUAV operated under this exemption must comply with all manufacturer 

Safety Bulletins. 

15) The authorized person must make an entry in the aircraft record of the corrective 

action taken against discrepancies discovered between inspections. 

16) The Operator/PIC must possess at least a recreational pilot airman certificate and at 

least a current third class medical certificate. The PIC must also meet the flight review 

requirements specified in 14 CFR § 61.56 in an aircraft in which the PIC is rated on his or her 

pilot certificate. 

17) The operator may not permit any Operator/PIC to operate the SUAV unless the PIC 

meets the operator's qualification criteria and demonstrates the ability to safely operate the 

SUAV in a manner consistent with how the SUAV will be operated under this exemption, 

including evasive and emergency maneuvers and maintaining appropriate distances from 

persons, vessels, vehicles and structures. PIC qualification flight hours and currency must be 

logged in a manner consistent with 14 CFR § 61.51 (b). The Operator/PIC must ensure that the 

VO is trained appropriately in order to fulfill her or her duties. A record of training must be 

documented and made available upon request by the Administrator. Flights for the purposes 

of training the operator's/PICs and VOs (training, proficiency, and experience-building) are 

permitted under the terms of this exemption. However, training may only be conducted during 

dedicated training sessions. During training, proficiency, and experience-building flights, all 

persons not essential for flight operations are considered nonparticipants, and the PIC must 

Page 9 of 20 
operate the UA with appropriate distance from nonparticipants in accordance with 14 CFR § 

91.119. 

18) SUAV operations may not be conducted during night, as defined in 14 CFR § 1.1. 

All operations must be conducted under visual meteorological conditions (VMC). Flights under 

special visual flight rules (SVFR) are not authorized. 

19) The SUAV may not operate within 5 nautical miles of an airport reference point as 

denoted on a current FAA-published aeronautical chart unless a letter of agreement with that 

airport's management is obtained, and the operation is conducted in accordance with a Notice 

to Airmen (NOT AM), as required by the operator's Certificate of Waiver or Authorization 

(COA). The letter of agreement with the airport management must be made available to the 

Administrator upon request. 

20) The SUAV may not be operated less than 500 feet below or less than 2,000 feet 

horizontally from a cloud or when visibility is less than 3 statute miles from the PIC. 

21) If the SUAV loses communications or loses its GPS signal, it must return to a 

predetermined location within the planned operating area and land or be recovered in 

accordance with the operating documents. 

22) The Operator/PIC must abort the flight in the event of unpredicted obstacles or 

emergencies in accordance with the operating documents. 

23) The Operator/PIC is prohibited from beginning a flight unless (considering wind and 

forecast weather conditions) there is enough power to fly at normal cruising speed to the 

intended landing point and land the UA with 25% battery power remaining. 

24) The operator must obtain an Air Traffic Organization (ATO) issued COA prior to 

conducting any operations under this grant of exemption. This COA will require the operator to 

request a NOT AM not more than 72 hours in advance, but not less than 48 hours prior to the 

operation. All operations shall be conducted in accordance with airspace requirements in the 

ATO issued COA including class of airspace, altitude level and potential transponder 

requirements. 

25) All aircraft operated in accordance with this exemption must be identified by serial 

number, registered in accordance with 14 CFR part 47, and have identification (N Number) 

markings in accordance with 14 CFR part 45, Subpart C. Markings must be as large as 

practicable. 

26) Before conducting operations, the radio frequency spectrum used for operation and 

control of the SUAV must comply with the Federal Communications Commission (FCC) or 

other appropriate government oversight agency requirements. 

27) The operator/PIC is required to keep a copy of the SUAV manufacturer's operating/ 

flight manual and all other operating documents in a location accessible to the PIC, during 

Page 10 of 20 
'• 

flight operations. These documents must be made available to the Administrator or any law 

enforcement official upon request. 

28) The SUAV must remain clear and yield the right of way to all other aviation 

operations and activities at all times. 

29) The SUAV may not be operated by the Operator/PIC from any moving device or 

vehicle. 

30) The SUAV may not be operated over congested or densely populated areas. 

31) Flight operations must be conducted at least 500 feet from all nonparticipating 

persons, vessels, vehicles, and structures unless: 

a. Barriers or structures are present that sufficiently protect nonparticipating persons 

from the UA and/or debris in the event of an accident. The operator must ensure that 

nonparticipating persons remain under such protection. If a situation arises where 

nonparticipating persons leave such protection and are within 500 feet of the SUAV, flight 

operations must cease immediately and/or; b. The aircraft is operated near vessels, vehicles or 

structures where the owner/controller of such vessels, vehicles or structures has granted 

permission and the PIC has made a safety assessment of the risk of operating closer to those 

objects and determined that it does not present an undue hazard, and; c. Operations nearer to 

the PIC, VO, operator trainees or essential persons do not present an undue hazard to those 

persons per§ 91.119(a). 

32) All operations shall be conducted over private or controlled-access property with 

permission from the property owner/controller or authorized representative. Permission from 

property owner/controller or authorized representative will be obtained prior to the beginning of 

every flight. 

33) Any incident, accident, or flight operation that transgresses the lateral or vertical 

boundaries of the operational area as defined by the applicable GOA must be reported to the 

FAA's UAS Integration Office (AFS-80) within 24 hours. Accidents must be reported to the 

National Transportation Safety Board (NTSB) per instructions contained on the NTSB Web 

site: www.ntsb.gov. 

8. Description of Regulations Which May Apply From Which Petitioner Requests 

Exception 14 C.F.R. Part 21, Subpart H: Airworthiness Certificates 14 C.F.R. §91.203 (a) 

(1) 

Subpart H, entitled Airworthiness Certificates, establishes the procedural requirements 

for the issuance of airworthiness certificates as required by FAR §91.203 (a) (1 ). Given the 

size and limited operating area associated with the SUAVS to be utilized by the Petitioner, an 

exemption from Part 21 Subpart H meets the requirements of an equivalent level of safety 

under Part 11 and Section 333 of the FMRA. The Federal Aviation Act (49 U.S.C.§44701 (f)) 

and Section 333 of the FMRA both authorize the FAA to exempt aircraft from the requirement 

Page 11 of 20 
for an airworthiness certificate, upon consideration of the size, weight, speed, operational 

capability, and proximity to airports and populated areas of the particular SUAVS. In all cases, 

an analysis of these criteria demonstrates that the UAS operated without an airworthiness 

certificate, in the restricted environment and under the conditions proposed will be at least as 

safe, or safer, than a conventional aircraft (fixed wing or rotorcraft) operating with an 

airworthiness certificate without the restrictions and conditions proposed. 

The SUAV's to be operated hereunder is less than 55 lbs. fully loaded, is by definition 

unmanned and carries neither a pilot nor passenger, carries no explosive materials or 

flammable liquid fuels, and operates exclusively within a limited flight area. Unlike other civil 

aircraft, operations under this exemption will be tightly controlled and monitored by the 

PIC/Operator and will also remain within the requirements of, and in compliance with, local 

public safety requirements. These safety enhancements, which already apply to civil aircraft 

provide a greater degree of safety to the public and property owners than conventional 

operations conducted with airworthiness certificates issued under 14 C.F.R. Part 21, Subpart 

H. Lastly, application of these same criteria demonstrates that there is no credible threat to 

national security posed by the UAS due to its size, speed of operation, location of operation, 

lack of explosive materials or flammable liquid fuels, and inability to carry a substantial external 

load. 

14 C.F.R. § 45.23 (b). Marking of the Aircraft 

The regulation requires; When marks include only the Roman capital letter "N" and the 

registration number is displayed on limited, restricted or light-sport category aircraft or 

experimental or provisionally certificated aircraft, the operator must also display on that aircraft 

near each entrance to the cabin, cockpit, or pilot station, in letters not less than 2 inches nor 

more than 6 inches high, the words "limited," "restricted," "light-sport," "experimental," or 

"provisional," as applicable. 

Even though the SUAV will have no airworthiness certificate, an exemption may be 

needed as the SUAV will have no entrance to the cabin, cockpit or pilot station on which the 

word "Experimental" can be placed. Given the size of the SUAVS, two-inch lettering will be 

impossible. The word "Experimental" will be placed on the fuselage in compliance with §45.29 

(f). The equivalent level of safety will be provided by having the SUAVS marked on its 

fuselage as required by §45.29 (f) where the pilot, observer and others working with the 

SUAVS will see the identification of the SUAV as "Experimental." The FAA has issued the 

following exemptions to this regulation to Exemptions Nos. 10700, 8738, 10167 and 10167 A. 

14 C.F.R. § 61.113 (a) & (b): Private Pilot Privileges and Limitations: Pilot in Command. 

Sections 61.113 (a) & (b) limit private pilots to non-commercial operations. Because the 

SUAVs are unmanned and will not carry a pilot or passengers, the proposed operations can 

achieve the equivalent level of safety of current operations by requiring the PIC operating the 

aircraft to have a FAA ground school rather than a commercial pilot's license to operate this 

small SUAVS. Unlike a conventional aircraft that carries the pilot and passengers, the SUAVS 

is remotely controlled with no living thing on board. The area of operation is controlled and 

Page 12 of 20 
restricted, and all flights are planned and coordinated in advance. The level of safety provided 

by the requirements included herein exceed that provided by a single individual holding a 

commercial pilot's certificate operating a conventional aircraft. The risks associated with the 

operation of the SUAVS are so diminished from the level of risk associated with commercial 

operations contemplated by Part 61 when drafted, that allowing operations of the SUAVS as 

requested with a private pilot as the PIC exceeds the present level of safety achieved by 14 

C.F.R. §61.113 (a) & (b). 

14 C.F.R. §91.7(a): Civil aircraft airworthiness. 

The regulation requires that no person may operate a civil aircraft unless it is in 

airworthy condition. As there will be no airworthiness certificate issued for the aircraft, should 

this exemption be granted, no FAA regulatory standard will exist for determining airworthiness. 

Given the size of the aircraft and the requirements contained herein for the use of safety check 

lists prior to each flight, an equivalent level of safety will be provided. 

14 C.F.R. § 91.9 (b) (2): Civil Aircraft Flight Manual in the Aircraft. 

Section 91.9 (b) (2) provides: No person may operate a U.S.-registered civil aircraft ... 

(2) For which an Airplane or Rotorcraft Flight Manual is not required by §21.5 of this 

chapter, unless there is available in the aircraft a current approved airplane or Rotorcraft Flight 

Manual, approved manual material, markings, and placards, or any combination thereof. 

The SUAVS, given its size and configuration has no ability or place to carry such a flight 

manual on the aircraft, not only because there is no pilot on board, but because there is no 

room or capacity to carry such an item on the aircraft. 

The equivalent level of safety will be maintained by keeping the SUAVS operation 

manual and appropriate checklists at the ground control point where the pilot flying the SUAVS 

will have immediate access to it. The FAA has issued the following exemptions to this 

regulation: Exemption Nos. 8607, 8737, 8738, 9299, 9299A, 9565, 95658, 10167, 10167A, 

10602, 32827, and 10700. 

14 C.F.R. § 91.103: Pre-flight action 

This regulation requires each pilot in command to take certain actions before flight to 

insure the safety of flight. As FAA approved rotorcraft flight manuals will not be provided for 

the aircraft an exemption will be needed. An equivalent level of safety will be provided as set 

forth hereinabove. The PIC will take all actions including reviewing weather, flight battery 

requirements, landing and takeoff distances and aircraft performance data before initiation of 

flight using appropriate checklists. 

Ill 

Page 13 of 20 
14 C.F.R. §91.109: Flight instruction: 

Section 91.103 provides that no person may operate a civil aircraft (except a manned 

free balloon) that is being used for flight instruction unless that aircraft has fully functioning 

dual controls. 

SUAV's and remotely piloted aircraft, by their design do not have fully functional dual 

controls. Flight control is accomplished through the use of a radio transmitter that 

communicates with the aircraft via a receiver in the SUAVS. The FAA has approved 

exemptions for flight training without fully functional dual controls for a number of aircraft and 

for flight instruction in experimental aircraft. See Exemption Nos.5778K & 9862A. The 

equivalent level of safety provided by the fact that neither a pilot nor passengers will be carried 

in the aircraft and by the size and speed of the aircraft. 

14 C.F.R. §91.119: Minimum safe altitudes 

Section 91. 119 establishes safe altitudes for operation of civil aircraft. Section 91.119 

(d) allows helicopters to be operated at less than the minimums prescribed, provided the 

person operating the helicopter complies with any route or altitudes prescribed for helicopters 

by the FAA. This exemption is for a SUAVS and the exemption requests authority to operate at 

altitudes up to 400 AGL underneath navigable airspace and in class E and G airspace 

maintaining safe separation from actual aircraft, an exemption may be needed to ailow such 

operations. 

The equivalent level of safety will be achieved given the size, weight, speed of the UAS 

as well as the location where it is operated. No flight will be taken without the permission of 

the property owner or local officials. Because of the advance notice to the property owner and 

participants in the filming activity, attempts will be made to contact all affected individuals 

regarding the planned flight operations. Compared to flight operations with aircraft or rotorcraft 

weighting far more than the maximum 551bs. proposed herein, and the lack of flammable fuel, 

any risk associated with these operations is far less than those presently presented with 

conventional aircraft. In addition, the low-altitude operations of the SUAVS will ensure 

separation between these SUAVS operations and the operations of conventional aircraft that 

must comply with Section 91.119. 

14 C.F.R. §91.121 Altimeter Settings 

This regulation requires each person operating an aircraft to maintain cruising altitude 

by reference to an altimeter that is set " ... to the elevation of the departure airport or an 

appropriate altimeter setting available before departure." As the SUAVS may not have a 

barometric altimeter, but instead a GPS altitude read out, an exemption may be needed. An 

equivalent level of safety will be achieved by the operator, pursuant to the Manual and Safety 

Check list, confirming the altitude of the launch site shown on the GPS altitude indicator before 

flight. 

Ill 

Page 14 of 20 
14 C.F.R. § 91.151 (a): Fuel Requirements for Flight in VFR Conditions 

Section 91.151 (a) prohibits an individual from beginning "a flight in an airplane under 

VFR conditions unless (considering wind and forecast weather conditions) there is enough fuel 

to fly to the first point of intended landing, and, assuming normal cruising speed- (1) During 

the day, to fly after that for at least 30 minutes; or (2) At night, to fly after that for at least 45 

minutes." 

The battery powering the E384 SUAV provides approximately between 80-100 minutes 

of powered flight. The Phantom 2 provides approximately 25 minutes of flight time. To meet 

the 30 minute reserve requirement in 14 CFR §91.151, SUAV in the E352 flights would be 

limited to approximately 70 minutes in length and unable in the Phantom. Given the limitations 

on the SUAV proposed flight area and the location of its proposed operations within a 

predetermined area, a longer time frame for flight in daylight or night VFR conditions is 

reasonable. 

Petitioner believes that an exemption from 14 CFR §91.151 (a) falls within the scope of 

prior exemptions. See Exemption 10673 (allowing Lockheed Martin Corporation to operate 

without compliance with FAR 91.151 (a)). Operating the SUAVS in controlled area where only 

people and property owners or official representatives who have signed waivers will be 

allowed, with less than 30 minutes of flight operation time, does not give rise to the type of 

risks that Section 91.151 (a) was intended to alleviate particularly given the size and speed of 

the SUAVS. Additionally, limiting SUAV flights would greatly reduce the utility for which the 

exemption will be granted. 

Petitioner believes that an equivalent level of safety can be achieved by limiting flights 

to landing with no less than 25% of battery power remaining. This restriction would be more 

than adequate to return the SUAVS to its planned landing zone from anywhere within its 

limited operating area. Similar exemptions have been granted to numerous other operations. 

14 C.F.R. §91.203 (a) and (b): Carrying Civil Aircraft Certification and Registration 

The regulation provides in pertinent part: 

(a) Except as provided in § 91.715, no person may operate a civil aircraft unless it has 

within it the following: 

(1) An appropriate and current airworthiness certificate .... 

(b) No person may operate a civil aircraft unless the airworthiness certificate required by 

paragraph (a) of this section or a special flight authorization issued under §91.715 is displayed 

at the cabin or cockpit entrance so that it is legible to passengers or crew. 

The SUAV fully loaded weighs no more than 55 lbs and typically less than 20 lbs. And is 

operated without an onboard pilot. As such, there is no ability or place to carry certification 

and registration documents or to display them on the SUAV. 

Page 15 of 20 
An equivalent level of safety will be achieved by keeping these documents at the ground 

control point where the pilot flying the SUAV will have immediate access to them, to the extent 

they are applicable to the SUAV. The FAA has issued numerous exemptions to this 

regulation. A representative sample of other exceptions includes Exemption Nos. 9565, 9665, 

9789, 9789A, 9797, 9797A, 9816A, and 10700. 

14 C.F.R. §91.405 (a); 407 (a) (1); 409 (a) (2); 417(a) & (b): Maintenance Inspections 

These regulations require that an aircraft operator or owner "shall have that aircraft 

inspected as prescribed in subpart E of this part and shall between required inspections, 

except as provided in paragraph (c) of this section, have discrepancies repaired as prescribed 

in part 43 of this chapter ... ," and others shall inspect or maintain the aircraft in compliance with 

Part 43. 

Given that these section and Part 43 apply only to aircraft with an airworthiness 

certificate, and the requirements of pre-flight inspection required herein, these sections will not 

apply to the applicant. Routine and pre-flight maintenance will be accomplished by the 

operator. An equivalent level of safety will be achieved because these SUAVS are very limited 

in size and will carry a very small payload and operate only in restricted areas for limited 

periods of time. If mechanical issues arise the SUAV can land immediately and given its small 

size poses very little risk to persona or property. The operator will ensure that the SUAV is in 

working order prior to initiating flight, perform required maintenance, and keep a log of any 

maintenance performed. Moreover, the operator is the person most familiar with the aircraft 

and best suited to maintain the aircraft in an airworthy condition to provide the equivalent level 

of safety. 

9. Publication Summary 

Pursuant to 14 C.F.R. Part 11, the following summary is provided for publication in the 

Federal Register, should it be determined that publication is needed: 

Petitioner seeks an exemption from the following rules: 

14 C.F.R. §21, subpart H; 14 C.F.R 45.23(b);14 C.F.R. §§ 61.113( a) & (b);91.7 (a); 

91.9 (b) (2);91.1 03(b);91.1 09; 91.119; 91.121; 91.151 (a);91.203(a) and (b); 91.405 (a); 

91.407 (a) (1 ); 91.409 (a) (2); 91.409 (a) (2) and 91.417 (a) & (b) to operate 

commercially a SUAVS vehicle (551bs or less) for Aerial Photography Operations. 

Approval of exemptions allowing commercial operations of SUAV for aerial 

photography/Inspection for the following; Business Operations: over land, water-ways, and 

oceans; operation over/in non restricted National Parks, National Forests, flight in nonnavigable airspace, using non-intrusive recording devices, operation in otherwise unrestricted 

US States/Territories will enhance safety by reducing risk. Conventional film operations, using 

jet or piston power aircraft, operate at extremely low altitudes, just feet from the subject being 

filmed, and in extreme proximity to people and structures; and present the risks associated 

with vehicles that weigh in the neighborhood of 4,0001bs, carrying large amounts of jet A or 

Page 16 of 20 
other fuel. In addition such actual certificated aircraft must fly to and from the film location. In 

contrast, a SUAV weighing fewer than 55 lbs., and powered by batteries rather than fuel, 

eliminates virtually all of that risk. The SUAV is driven/carried to the film set, not flown. The 

SUAV will carry no passengers or crew and, therefore, will not expose any crew to the risks 

associated with manned aircraft flights. 

The operation of SUAV, weighing less than 55 lbs., conducted in the strict conditions 

outlined above, will provide at least an equivalent level of safety supporting the grant of the 

exemptions requested herein, including exempting the Petitioner from the requirements of Part 

21 and allowing commercial operations. These lightweight aircraft operate at slow speeds, 

close to the ground, and in a line of sight, relatively sterile environment and are, as a result, far 

safer than conventional operations conducted with actual aircraft/helicopters operating in close 

proximity to the ground and people. 

10. Privacy 

All business/commercial flights which occur over private or controlled access property 

will be with the property owner's prior consent and knowledge. Filming will be of people who 

have also consented to being filmed or otherwise have agreed to be in the area where filming 

will take place. Petitioner will not infringe on any individual or landowner privacy rights. 

Limited nighttime operations may be conducted. Nighttime as defined FAR's in Section 

is as follows 1.1. "Night means the time between the end of evening civil twilight and the 

beginning of morning civil twilight, as published in the American Air Almanac, converted to 

local time." Night operations may be conducted by the SUAVS following the guidelines above 

and provided such operations have sufficient lighting so that Petitioner/Operator maintains 

visual line of sight. Allowing SUAVS this exemption will provide a far safer nighttime filming 

alternative to the current full size aircraft operations. 

11. Conclusion 

The FAA's purported "ban" on business/commercial SUAV operations has actually had 

the current effect of causing American skies to be less safe. There are many actual 

certificated pilots who are exceptionally qualified to fly SUAV with their SUAV experience, 

private, commercial or ATP pilot training, licenses and instructor ratings. However, these 

experienced operators and licensed pilots familiar with the FARs, airspace and safe operating 

procedures are currently reluctant to commercially operate model aircraft!SUAVS or be 

involved, for fear of the FAA seeking an enforcement action against them or their actual pilot's 

licenses. 

Presently, during the pendency of these issues, it defies safety or regulatory logic that 

according to the FAA's current alleged "ban" on business operations of SUAVS, your average 

enthusiastic 12 year old, who's well meaning Father bought him a quadcopter SUAV equipped 

with a camera, can operate his SUAVS wherever he wants and take whatever recreational 

video/pictures subject only to the suggestions of FAA AC 91-57 and yet an FAA certificated 

private/commerciai/ATP pilot cannot be paid to use a far higher quality and equipped SUAVS 

Page 17 of 20 
to take an aerial photo or aerially inspect a farmers field, despite the significant improvement in 

safety over non-pilots operating SUAVS recreationally and real aircraft used for aerial 

photography. 

Satisfaction of the criteria provided in Section 333 of the FMRA of 2012, and requiring 

the SUAV PIC to have or obtain medical certificate and a actual pilots license and considering 

the small size, weight, speed, operating capabilities, limited operations in proximity to airports 

and populated areas and operation within visual line of sight and national security- all of 

which provide more than adequate justification for the grant of the requested exemptions 

allowing business/commercial operation of applicant's SUAVS for aerial photography/ 

Inspection as requested herein. 

If this firm can be of any further assistance in processing this request, or you have any 

other questions or concerns, please do not hesitate to contact me directly, in writing. 

Michael D. Curran, Esq./ATP/CFII/MEI 

cc: James Williams, FAA 

Dan Ngo, FAA 

Page 18 of 20 
Ex. 1. 

Preflight Checklists 

Inspect Vehicle 

1. Check props 

2. Check screws 

3. Check Radio 

4. Check body/arms for cracks 

5. Prepare log book 

Checklists 

6. Review mission/Check review weather 

7. Check/test batteries record voltages 

8. Prepare nav/gps system 

9. Radio RX/TX distance test/Check timers 

10. Satellite localization/lock 

Narrative Descriptions. Inspect the vehicle for previous damage like cracked chassis, loose props, 

motors and wires, this will ensure the safe operation of the vehicle and not a catastrophic failure of 

parts. Tighten all screws and record which ones are becoming loose over time. This will indicate 

problems with the vehicle structure and you should use more CA or thread locking liquid to keep this 

problem to a minimal. If you are repeatedly tightening the screws in the same spot then there is a 

problem with the screw hole and should be tapped or corrected. Prepare a logbook, this will ensure that 

you are recording the proper flight times and will indicate battery health, saving you from a failure and 

possible loss of vehicle. Pull out the document you use for logging your flight fill out the information that 

is most important: date, time, and mission information. Weather affects the performance of a vehicle 

and should be calculated to ensure proper weights given to your flight and battery time totals. Weather 

information to include as follows: Temperature, wind speed, maximum gusts, ambient temperature, 

humidity, dew point, barometric pressure, and any solar information that can effect your GPS. Review 

your mission so that you know exactly what you plan to do and what data you will gather. Check and 

test your batteries so that you have sufficient power for your mission. If you followed this checklist your 

batteries should have been charged the last time you put your vehicle away. Turn on the navigation 

system if applicable and verify the appropriate settings to localize the satellite signal. Check for solar 

flare information and gps outages in your area connected to your mission. 

II. Before Flight 

1. Turn on transmitter; Check set flight mode 

2. Set throttle down 

3. Clear flight area 

Page 19 of 20 

G.l 
4. Connect battery on the vehicle 

5. Verify indicator lights for proper indications/GPS locks 

6. Start motors 

7. Throttle up slowly 

8. Maintain visual separation from all obstructions 

Narrative Descriptions: You should always be near your transmitter so that in the case of a failure you 

can control the vehicle to the best of your abilities and get the vehicle safely to the ground. First turn the 

transmitter on, with the throttle turned all the way down. Next walk over to the vehicle that you plan to 

fly clear area and connect the battery. You should connect the battery in a way that does not disturb the 

vehicle from sitting on the ground, when you plug the vehicle up it is calibrating the flight system and 

powering up safely. When the lights give proper indications it is safe to either pick up the vehicle safely 

and move it or walk away from it with your controller in your hand. To begin your flight move the sticks 

up slowly until the vehicle leaves the ground maintain visual separations from people, buildings, 

obstructions, other UAV/aircraft. 

Ill. Post Flight/After Landing 

1. Unplug battery on vehicle while near the controller 

2. After battery is unplugged turn off the controller 

3. Fill out log books 

Narrative Descriptions: Once the vehicle has returned to the ground, walk over with your controller and 

disconnect the wire to the vehicle battery, this will essentially kill the power and render the vehicle in the 

safe to transport mode. Next you can power the controller off to save the battery life. Return the vehicle 

to a safe place and then locate your logbooks and recover your data. 

IV. Debrief 

1. Fill out logs 

2. Complete calculations for batteries and flight times 

3. Put away gear, vehicle and log books 

Page 20 of 20 
UNMANNED SYSTEMS 

E384 Operations Manual 
UNMANNED SYSTEMS 

Table of Contents 

Setup 

Getting Started 

Charging the Batteries 

Telemetry Connection 

Adjusting Declination 

Firmware Download 

Assembly 

Tail Asembly 

Wing Asembly 

Propeller Assembly 

Camera & Battery Installation 

Mission Planning 

Mission Planning Overview Part 1 

Mission Planning Overview Part 2 

Auto Takeoff 

FBWA Takeoff 

Planning a Mapping Mission 

Auto Land 

FBWA Land 

Geotagging Utility Part 1 

Geotagging Utility Part 2 

E384 Operations 

Transmitter modes 

NX11 00 Operations Part 1 

NX1100 Operations Part 2 

S 110 Operations Part 1 

S11 0 Operations Part 2 

E384 Procedures 

Pre-Field Checklist 

Preflight Checklist 

Flight Procedure Summary 

Flight Procedure Summary Part 2 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 
UNMANNED SYSTEMS 

Getting Started 

The following pages will act as a guide through the E384 experience, and serve as an 

important tool throughout its continued use. If questions or suggestions arise, do not 

hesitate to contact us for a quick resolution. 

All E384 users must download E38 Mission Planner found through the following link--

https://www.event38.com/Articles.asp?ID=270 

If you are located beyond the USA start with Firmware Download. 

If you are in the USA follow through to Charging the Batteries. 

1 
UNMANNED SYSTEMS 

Charging the Batteries 

Step 1: 

To charge your batteries, plug in your battery 

charger and add the banana to XT-60 cable 

ofl the right side as shown in the picture 

below. 

Step 2: 

To charge the sooomAh battery, plug it directly into the XT60-banana plug that is connected to the charger. Plug the balancer into 

the co ndi terminal. 

Step 3: 

Plug the power cord into the left side of the 

charger. 

Step 4: 

If LiPo charge is not selected when you 

power on the charger press the Batt Type 

(the left-most button) until it says LiPo then 

press the start button on the far right. 

StepS: 

After selecting LiPo pressing the start button 

again wilt allow you to change the amps. 

Change this according to the battery you are 

charging by going left or right using the two 

buttons in between Batt Type and Start. 

Charge the sooomAh battery at 6.0A. 

Step 6: 

After selecting the correct amount of amps, 

press start again. This will allow you to 

change the number of cells. The sooomAh 

battery is labeled a 4 cell battery, so charge 

it at 45. 

Step 7: 

After choosing the proper amps and cells 

hold the start button. Then after the battery 

check press start again to start the charge. 

When the battery is full the charger will 

beep. 

2 
UNMAN:NED SYSTEMS 

Telemetry Conection 

Step 1: 

To connect we will first power on the transmitter, followed by the aircraft~ We wilt allow 

ten seconds or so for the aircraft to initialize. 

Step 2: 

Plug in the cable from your ground side telemetry system to the computer. 

If you are using the RFD900 make sure pin 

one receives the black wire from the FTDI 

cable. 

If you have the old style 433 make sure the 

black wire goes to the GND pin. 

The new style 3DR telemetry systems simply 

connect with a MicroUSB cable. 

Step 3: 

Open Mission Planner and choose the Com 

Port that comes up when plugging ill the telemetry (it may take a few minutes for the 

Com Port to show up). Set baud rate to 57600. 

Step 4: 

Press Connect and you should have your 

wireless connection. 

3 
;.~· .... ··.· ... · ... ·.···.·;. M!J 

UNMANNED SYSTEMS 

Adjusting Declination 

The Earth's magnetic field varies significantly depending on your location relative to the poles. To adjust for the 

offset in your location, we'll change the magnetic declination parameter until the heading shown on Mission 

Planner matches the heading of your plane 

Step 1: 

Power on the R/C Transmitter then power on 

the E384. (This should be done with the battery, wings, and other components installed 

and ready for flight.) 

Be sure not to set the E384 near any large 

metallic objects as the compass is very sensitive and can be affected by local magnetic 

disturbances. Once initialized, set it on the 

ground at a known heading. it can be any direction as long as it's known. If no directions 

are known for certain, you can use visual 

cues that would be visible on Google Earth. 

For example, you can point the nose to be 

perpendicular to your street or parallel with 

the edge of your house. 

Step 2: 

Connect to the E384 by telemetry in Mission 

Planner. 

Once connected, you'll see an airplane icon 

at roughly your current location. If you're 

inside, you may need to go near a window or 

put the E384 outside in order to get a GPS fix. 

There will be a red line emerging straight forward from the icon, that is the direction the 

autopilot thinks it's facing. Knowing the real 

direction, we can now adjust and iterate the 

magnetic declination until the red line is 

pointing in the same direction we know the 

E384 to be pointing. 

Step 3: 

Take a mental note of approximately how 

many degrees off the true direction the red 

line is pointing. Now click on Initial Setup-> 

Mandatory Hardware -> Compass 

Step 3: 

lfthe red line was counterclockwise of the 

true direction, add the approximate number 

of degrees you noted before to the current 

value, type that in and then switch back to 

Flight Data. 

Wait at least 30 seconds between iterations, 

it takes some time for the direction to 

update. If the red line was spun clockwise 

relative to the true direction, subtract. Negative values are ok but they should not exceed 

180 degrees in either direction. 

Example: 

Initial setting, I've set the E384 down lining 

up with the edge of my building. 

Now after adding 45 degrees to the declination value, it's very close to parallel with the 

edge. I'll make one more adjustment for another 2-3 degrees but this is close enough already. Aim to be within 5 degrees of the true 

heading. 

4 
UNMANNED SYSTEMS 

Firmware Download 

For customers outside of the USA, firmware must be loaded onto the E384. 

Step 1: 

Go to the below link to download the E384 firmware 

below. 

http:// eve nt38.wi kispates.co m I Firmware+ Download 

Step 2: 

Plug the micro USB cable connected to the computer 

into the autopilot. 

Step 3: 

Open Mission Planner. Go to Initial Setup» Install 

Firmware. 

Step 4: 

Follow the steps given to download the E384 Firmware. 

5 
UNMANNED SYSTEMS 

Tail Assembly 

Step 1: 

Fit the elevator on top ofthe tail, and slide the 

elevator toward the rudder. 

Step 2: 

Connect the servo lead on the elevator to the 

servo extension. 

Step 3: 

Take the servo wires from the tail and place them 

into the body of the E384. 

Step 4: 

Push the carbon rod all the way into the body, 

the notches on the rod will catch on the orange 

tube at the furthest point. 

Step 5: 

Tighten the three screws on the body to keep the 

tail tightly in place 

Step 6: 

Fish the elevator and rudder cables through the 

hole on the top and connect the elevator to 

output channel2 and the rudder to output channel4. 

Be sure the top pin receives the black wire on 

your Pixhawk. 

6 
UNMANNED SYSTEMS 

Wing Assembly 

Step 1: 

Slide the rod into one wing, and then the other. 

Step 2: 

Connect the servo wires to the splitter originating from main out channel one on the Pixhawk, 

either wing can go into either side of the splitter. 

Step 3: 

Fit the wings into the body, avoid squeezing the 

servo wires in between the wings and the body. 

Step 4: 

Attach rubber bands as follows ... 

(Use two rubber bands for safety.) 

7 
UNMANNED SYSTEMS 

Propeller Assembly 

Step 1: 

Place the propeller on to the bolt with the lettering on the propeller facing the motor. 

Step 2: 

Place the washer on the bolt. Make sure the side 

of the washer with the larger face is against the 

propeller. 

Step 3: 

Then, tighten the nut to bolt very tightly securing 

the propeller and washer. If this bolt is too loose 

the propeller may fall off during a flight. 

8 
m m!l 

UNMANNED SYSTEMS 

Installing Camera & Batteries 

Step 1: 

Place the battery into the plane, after checking 

the center of gravity you may need to adjust the 

location of the batteries. 

Step 2: 

Insert the camera. 

Step 3: 

Attach the nose hatch. 

Step 4: 

Check the center of gravity by putting a finger on 

each wing at the rear of the Styrofoam insert 

under the wings and making sure it is Level or 5 

degrees nose down at most. 

The red line in the following picture shows the 

proper center of gravity. 

Step 5: 

If the center of gravity is off, correct this by 

moving the battery forward or backward on the 

velcro and then re-check the center of gravity. 

9 
UNMANNED SYSTEMS 

Mission Planning Options 

The E384 is fully capable of performing fully autonomous missions. When using the E384, fully manual 

(FBW-A) flight is also an option. The E384 can use combination of manual (FBW-A) flight and autonomous 

flight. Examining the flight options will allow the user to choose the best solution for the intended use. 

--The discussion begins with a fully autonomous mission. 

-The Ground Station Manager plans a mission with an Auto TakeoffWP, a Land WP, and anything in between. 

The user in charge of physically throwing the E384 (the "Launcher") will prepare himself, in a ready-to-launch 

position. The Ground Station Manager will change the mode to AUTO (either using the transmitter, or using 

the ground station computer). The Ground Station Manager will communicate to the Launcher of the mode 

change. The Launcher launches the E384 firmly at about a 15 degree angle into a headwind. The E384 realizes 

it has been launched and begins turning the motor. The E384 begins gaining altitude until it has reached the 

takeoff altitude. The E384 proceeds by traveling to the next WP. It continues through the WPs until it has 

reached the final WP, the Land WP. The E384 touches down. The E384 Flight Crew briefly celebrates another 

successful collection of data. One member ofthe E384 Flight Crew travels to the E384. The member disconnects the battery for safe transportation. 

The advantage of the fully autonomous flight is apparent. Minimal user input is needed, as the E384 takes 

care of itself. It is important to discuss further the Auto Takeoff and Auto Land process. 

-Auto Takeoff will be perfect, so long as the Launcher launches the E384 without too much error. Errors can 

be seen if the E384 is launched with a large bank angle. Errors can be seen if the E384 is launched with a 

pitch angle that is too great or not great enough. Errors can be seen if the E384 is not launched strongly 

enough, or if the E384 is thrown downwind. The E384 should by gliding out of the users hand. While the 

E384's Auto Takeoff has room for errors, it is possible to have too many Launcher errors for a clean takeoff. 

-Auto Land is a useful tool. The Ground Station Manager sets WP's to reduce the altitude, followed by a Land 

WP. There are two aspects involved in Auto Land that should be realized. 

The first aspect is that the Ground Station Manager must be diligent. The Ground Statioo Manager must be 

sure to follow proper landing procedure to maintain a high probability of success. 

The second is that there are uncontrollable factors in play. Google Maps (or other "Maps") will not maintain 

perfectly accurate terrain. This means that it is important to allow for a landing strip that offers some forgiveness. Another factor of note is altitude. The altitude will not be perfect for two major reasons. The E384 

considers om altitude to be that of the altitude where it was given power. If the landing strip is of different 

altitude than that of the start up altitude, it must be taken into account. The other altitude factor is the E384 

altitude readings. There may be discrepancies between actual altitude and E384 altitude readings. The E384 

could touch down before intended, or glide past the intended landing target. Again, it is important to choose 

a landing strip that offers some forgiveness. 

%The user can take manual (FBW-A) control of the E384 at any time. The E384 mode will be switched to 

FBW-A and the pilot will control the E384.% 

--Attention is turned toward a fully manual (FBW-A) flight. 

-The Ground Station Manager may or may not have planned a mission. The Launcher prepares to throw the 

E384. The Launcher communicates with the pilot until preparedness is reached. The Launcher throws the 

E384. The Pilot increases throttle and begins increasing altitude. The Pilot manually (FBW-A) controls the 

E384 at all times. The Pilot flies in any manner deemed necessary. The Pilot brings the E384 down for a landing. 

10 
UN:MANNED SYSTEMS 

Mission Planning Options (Continued) 

-While a fully manual (FBW-A) flight will not yield data collection, it can increase the Pilot's flight skill. This 

may prove valuable in situations where a manual (FBW-A) takeoff or landing is ideal. 

-FBWA takeoff will hold one advantage if the Pilot is skilled. With a skilled Pilot, this will allow the Launcher 

to commit more errors while still finding success. 

-FBWA landing holds an advantage if the Pilot is skilled. With a skilled Pilot the E384 may land more accurately. 

--Lastly, combination flight is discussed. 

-The E384 Flight Team may decide manual (FBW-A) flight is ideal in certain situations. The scenario considered is that of manual (FBW-A) takeoff, automatic survey, followed by manual (FBW-A) landing. In this scenario the Pilot performs a manual takeoff. After communicating with the rest of the Flight Crew, the E384 is 

placed into AUTO. The E384 flies the pre-programmed survey WPs. When the E384 completes the mission it 

will return to the area that it was given power and proceed by circling that area at 100m altitude. The Pilot 

regains manual (FBW-A) control when the mode is switched to FBW-A. This is done either from the ground 

station computer, or from the Pilot's transmitter. The Pilot maintains control and brings the E384 down for a 

landing. 

-All combinations of manual (FBW-A) and autonomous flight can be realized. 

--In conclusion, the E384 can fly fully autonomously, fully manual (FBW-A), and a combination of autonomous and manual (FBW-A) flight. With a skilled pilot at the helm, the E384 can takeoff and land under harsher conditions than an automatic takeoff and automatic landing. 

Now that mission planning understanding has been increased, the stages of flight and the WP layout will be 

detailed. 

11 
UNMANNED SYSTEMS 

Auto Takeoff 

Step 1: 

Enter the Flight Plan screen of Mission Planner. 

Before setting any WP click the Add Takeoff WP 

button on the right. 

Step 2: 

When prompted, enter the desired takeoff altitude. It is recommended that your takeoff altitude equal that of your surveying altitude. 

Step 3: 

The next prompt will be pitch angle. It is recommended to set this to 35. 

The resulting WP will be shown under the Waypoints bar. Notice there will not be a takeoffWP visible on 

the map. 

Proceed by constructing the Survey( Grid) portion of the Mission Planning. 

The TakeoffWP will initiate when the E384 is in AUTO and the ground speed is above 3 m/s (which suggest 

the E384 being launched). 

Step 4: 

The Launcher should pick the E384 up and hold it, fully prepared to launch. One hand is placed on the 

bottom of the fuselage near the camera opening to guide the throw. The other hand is the launching hand. 

The launching hand is placed on the tail, with the index finger or more on the back ofthe tail. Never put 

body parts near the propeller when the battery is plugged in! 

The Launcher should communicate to the Ground Station Manager that he is prepared. The Ground Station 

Manager shall then change the mode to Auto, using either the RC transmitter or the actions tab under the 

HUD. The Ground Station Manager confirms that the mode is Auto. The Launcher proceeds by launching the 

E384 firmly at an angle of approximately 15 degress. Always throw the E384 against the wind for best results. 

When the E384 reads 3 m/s ground speed, the motor will begin rotating. The E384 will attempt to hold 

heading during takeoff. When it reaches the takeoff altitude it will turn and travel to the second WP. 

12 
UNMANNED SYSTEMS 

FBWA Takeoff 

Step 1: 

The Launcher holds the E384 up, keeping the 

propeller as far away as possible. 

Step 2: 

One hand is placed on the bottom of the fuselage near the camera opening to guide the throw. 

Step 3: 

The other hand is the launching hand. The 

launching hand is placed on the tail, with the 

index iinger or more on the back of the tail. 

Step 4: 

The Pilot should have the transmitter in hand. 

Throttle up to 60%. 

Step 5: 

The launcher throws the E384 firmly at an angle 

of about 15 degrees with the wind at the nose of 

the plane. 

Step 6: 

After the release, the pilot increases the throttle 

and pulls up on the elevator to climb. 

Climb to about 100m. After climbing to a safe altitude, the mode may be changed for autonomous flight. 

13 
UNMANNED SYSTEMS 

Planning a Mapping Mission 

Step 1: 

Go to the Flight Plan tab and find the area you 

intend to survey. 

Step 2: 

CLick Add Polygon em the right and enclose your 

area of interest. 

When in "Add Polygon" mode simply Left dick to 

add as many points as you desire. If you left click 

and hold a polygon point you can drag it (likewise with way points). If you need to delete a 

polygon point you can simply right click on the 

point and click on "Delete WP" (likewise with way 

points). 

Step 3: 

Click Survey (Grid). Choose your camera. Change 

your altitude for desired ground resolution. 

Choose your angle, based on wind direction. 

Choose your "start from" based on wind direction. Choose your sidelap/overlap (60% recommended). 

Step 4: 

Click the accept buton. 

You will notice "Stats on the right." Make sure 

"Flight Time" is reasonable, under 100 minutes. 

If you are using the Canon SX260 you will need to 

set the proper settings for your mission, based 

on the Flight Time. (See SX260 Operations). 

14 
UNMANNED SYSTEMS 

Auto Landing 

In this page Autonomous flight is planned from start to finish. Brief mentions will be made of Auto Takeoff 

and Planning a Mapping Mission. Check out those pages to fill in the details. 

Step 1: 

to the Flight Plan screen. The mission has been 

planned by first settihgthe Auto Takeoff WP, then 

adding a polygon and using the auto WP function. Because the TakeoffWP disappears we see 

that the first visible WP is WP 2~ 

In this scenario the wind is moving from North to 

South. During landing a headwind is ideal. 

Step 2: 

WP must be added to accomplish two tasks. They 

must change the direction of the E384 so that it 

will be landing with a headwind. They must also 

reduce altitude safely. When reducing altitude, 

always avoid flying too closely to obstacles. To 

add WP manually, first left click the Clear Polygon 

function. Now left click anywhere on the map to 

add a WP. Change altitude by changing the value 

of the Alt column in the row of the WP number 

desired. Change the last WP command to Land. 

Change the Land WP altitude to om. 

In this example, obstacles do not come into play. The design ofWP 38,39 and 40 is to set the E384 on the proper landing path 

and reduce altitude. We remember that the wind is traveling from North to South in this example. WP 41 is our Land WP at Om 

altitude. Also notice the Grad% column. 

When developing a landing procedure; 

1. Decide landing path based on wind. 

3. Set a WP procedure. 

2. Estimate the obstacle heights. 

4. Adjust altitudes. 

5. Set Land command. 6. Adjust the WP altitude or location in order to achieve usable Grad 

%. 

--The maximum magnitude of Grad% is near 30% with a 5 mph headwind .. 

--The maximum magnitude of Grad% between your Land WP and the previous WP should be kept below 10% 

To upload the WPs to the E384, connect to Mission Planner and left click the Write WP button. After the WP have been written, 

press the Read WP button. The Read WP button will clear the WP on your Flight Data screen and add the WP that are stored 

on the E384. Read WP allows confirmation that the WPs on the E384 are correct. 

15 
UNMANNED SYSTEMS 

FBWA Landing 

Step 1: 

During descent keep throttle very low, and no 

throttle at all if speed is maintained. 

Step 2: 

Land with the wind at the nose of the E384 to 

slow it down. Bring the E384 down and land on 

its belly. 

Step 3: 

Go to the E384 and unplug the battery. 

When you are sure the battery is unplugged you 

may disassemble. 

16 
UNMANNED SYSTEMS 

Geotagging Utility 

Step 1: 

Open mission planner and go to the flight data screen. Select the Telemetry Log tab on the display. 

Step 2: 

Click the Tlog > KML or Graph button. 

Step 3: 

This will open a new window as shown below. Next Select the Convert to CSV button. 

Step 4: 

Select the Telemetry log from the flight you wish to GeoTag and select open. 

Step 5: 

The log will then be converted into a CSV file. The CSV file will save under the same directory that 

you have selected your Telemetry Log from. 

Now that we have the CSV file we are able to GeoTag our pictures with the Event38 Image Utility. 

Continued on the next page 

17 
UNMANNED SYSTEMS 

Geotagging Utility (Continued) 

Step 1: 

Open the Event38 Image Utility application. 

Step 2: 

Select Image Utilities then select GeoTagV2. 

Step 3: 

Select the Image Path and Log File path. 

To select the correct image path select the directory or folder containing the photos that you wish 

to Geo Tag. 

To select the log file path find the CSV file you converted in the earlier steps of this manual. 

Then click process. 

Step 4: 

Click okay and then navigate to the Folder containing the pictures that had been selected for GeeTagging. There will be a Text document called lmageLog.txt. 

Step 5: 

The document will contain the image name, latitude, longitude and altitude for each processed 

picture. 

18 
.m!J ~ 

UNMANNED SYSTEMS 

Transmitter Modes (Spektrum) 

With the Spektrum DX5e we can select from three different modes. Other modes can be selected using your 

ground station computer. 

The modes will be selected using the CH 5 three position switch. 

The position pushed furthest away from us (0) is 

FBWA mode. 

The position pushed furthest away from us (0) is 

FBWA mode. 

The position pulled closest to us (2) is Auto. 

Verify your modes. Power on your transmitter. Remove propeller. Power on your E384. Connect to Mission 

Planner. Cycle through the modes. In Flight Plan, the bottom right corner of the heads up display will show 

which mode is currently engaged. 

19 
·iii].,'· ... · .. ··, 

M!l 

UNMANNED SYSTEMS 

NX1100 Operations 

Step 1: 

Open Mission Planner and go to the Flight Plan 

screen 

Step2: 

Right click on the screen and select "Draw Polygon" » "Add Polygon Point". 

Step 3: 

Choose the area you wish to map by inserting 

polygon points with a left click around your area 

of interest. Then right click and go to "Auto WP" 

»"Survey (Grid)". 

Step 4: 

In the "Simple" tab use the camera drop down 

and select the "NX1000." Choose an "Angle" that 

will allow the plane to fly crosswinds. Make sure 

the box labeled "Camera top facing forward" is 

not checked. Circled in red is "Ground Resolution." 

Step 5: 

Go to the "Grid Options" tab (This tab will not be 

visible unless you check the Advanced Options 

box in the Simple tab). Choose your Start From in 

the corner that will allow you to fly your pattern 

crosswinds and make all of your turns with the 

wind at the nose ofthe plane. Standard "Overtap" and "Sidelap" is 60% for each. 

Step 6: 

Go to the "Camera Config" tab and change the 

"Focal Length" to match the focal length of your 

pancake lens. 

At the bottom of the Camera Config tab make 

sure "CAM_TRIGG_DIST" is checked. 

Step 7: 

Go back to the "Simple" tab. Choose an altitude 

that corresponds to the "Ground Resolution" that 

you desire (be sure to check the attitude ceiling 

in your area). Then press "Accept" to transfer 

those WP to the "Flight Data" screen. 

20 
UNMANNED SYSTEMS 

NX1100 Operations (Continued) 

Step 1: 

Pull up the green Waypoints bar on the bottom 

of the screen and verify they are as expected. 

After the first WP in yourpolygon there shoud be 

a DO_SET_CAM_TRIG'-DIST WP. After the last WP in 

your polygon you should see another 

DO_SET_CAM_TRIG_DIST WP. 

Step 2: 

Press the green Write WPs button on the right 

wheri your E384 is powered on and connected to 

Mission Planner. This will send the WPs to the 

E384. Read the WP from the E384 by pressing the 

Read WPs. Then look through the WPs again to 

make sure all the WP are as desired. 

Step 3: 

Turn your NX1100 on in P mode, we have configured your NX1100 for optimum performance in P 

mode. Connect the MicroUSB coming from channel Aux Out 5 on the Pixhawk to your NX1100. 

In Auto mode the plane will take pictures based 

on your parameters. 

Step 4: 

After the flight connect a MicroUSB from your 

computer to your Pixhawk. Choose the correct 

Com Port, and set the baud rate to 115200. Go to 

the "Terminal" screen on Mission Planner and 

press the green "Connect" button. Now press the 

"Log Download" button. 

Step 5: 

Choose the latest log and press "Download These 

Logs". After completion close the "Log" window. 

Hold Ctrl on your keyboard and press the letter 

"F" on your keyboard. 

Step 6: 

Click on "Geo ref images." 

Step 7: 

Choose "Cam Message Synchro." Press "Browse 

Log" and choose the log we just downloaded 

from the APM. Press "Browse Pictures" and 

choose the pictures from the mission. Press 

"Pre-process" and wait for it to be completed. 

Then press "GeoTag Images." After this step is 

complete a separate set of images that are geotagged will be created for you. 

21 
UNMANNED SYSTEMS 

5110 Operations 

Step 1: 

Open Mission Planner and go to the Flight Plan 

screen. 

Step 2: 

Click the Add Polygon button on the right. Left 

click on the map to enclose the area you are 

mapping with the polygon then click the "Survey 

(Grid)" Button. 

Step 3: 

Change the camera option to Canon 5110 and 

click Accept. You will notice that two DO_-

CAM_TRIGG_DIST WP have been automatically 

added. 

The first box reads 43. After the first WP is 

reached this will tell the camera to take a picture 

every 43m the E384 travels. 

DO_CAM_TRIGG_DIST is also the last WP in my 

survey. The first box reads 0. When the E384 

reaches the last WP it will tell the camera to stop 

Step 4: 

Write and read your WPs. 

Step 5: 

After running through your preflight checklist 

. plug the cable from your Pixhawk port Aux Out 5 

into your 5110. 

Step 6: 

Turn on the 5110 and press the shutter button to 

open the lens. 

Step 7: 

Press the blue play button. 

Step 8: 

Press the shutter again and the text on the display should read "waiting on USB signaL" 

Step 9: 

Place the camera in your E384. 

If at some point during your flight you have 

reached greater than 50m altitude and later decrease altitude below 30m the tens on the 5110 

will automatically close. If you need to abort flight 

before reaching SOm you can close the lens by 

going to the actions tab under the HUD in Flight 

Data and pressing the close camera lens button. 

22 
UNMANNED SYSTEMS 

5110 Operations (Continued) 

Step 1: 

Connect a MicroUSB cable from your computer to 

the Pixhawk. Choose the correct Com Port, and 

set the baud rate to 115200. 

Step 2: 

Go to the "Terminal" screen on Mission Planner 

and press the green "Connect" button. 

Step 3: 

Press the "Log Download" button. If you have not 

cycled power since your flight, choose the last 

log and press download these logs. 

Step 4: 

Run the Event38.1mage.Utility Application. 

Step 5: 

Click IMAGE UTILITIES» Geo Tag. 

Step 6: 

Click Select next to Image Path and choose your 

folder containing your images. 

Step 7: 

Click Select next to Log File Path and choose 

your dataflash log from your flight. 

Step 8: 

Click Process. After a few seconds a pop up 

should appear letting you know processing is 

complete and a new set of tagged photos will be 

included within your image folder. 

23 
UNMANNED SYSTEMS 

Pre-Field Checklist 

[J Designate a Windows Laptop 

Download E38 Mission Planner 

[J Download Telemetry Radio Drivers 

[] Cache Maps 

Charge Batteries 

Flight Batteries 

Transmitter Batteries 

[J Camera Batteries 

Pack E'verything Up 

[J Flight Batteries 

[J Fuselage 

Tail 

Elevator 

Wings 

Wing Spar 

Propeller 

Transmitter 

Camera 

Ground Side Telemetry 

Laptop 

[J Rubber Bands 

[J Phillips Screwdriver 

[J Adjustable Pliers (Or Similar Tool) 

24 
UNMANNED SYSTEMS 

Preflight Checklist 

Assemble E384 

D Tail 

D Wings 

Batery 

D Camera 

D Fuselage Cover 

D Check Balance 

Power On Transmitter 

Plugin Battery 

Arm Plane 

Function Testing (FBWA Mode- Ensure 

proper response from ailerons) 

D Move right stick right 

Move right stick left 

Move right stick up 

Move right stick down 

Move left stick right 

Move left stick left 

Move left stick upwards 

D Compensation Testing (No remote used) 

D Bank Right 

D Bank Left 

Lift Nose Up 

Lift Tail Up 

D Open Mission Planner 

D Check MPAutomated Checklist 

D Review User Checklist 

D Check For Valid Waypoints 

Power On Camera In "P" Mode 

D Reinstall Camera 

25 
UNMANNED SYSTEMS 

Flight Procedure Summary 

In this section we will discuss the procedure used to collect imagery, beginning with preparations for flight. 

Start by following the E384 Pre-Field Checklist (Page 24). 

When you arrive at the field, take a note of the wind direction and speed. Avoid flying in winds above 20 

mph. When we plan a mission we want to fly crosswinds and make all our turns into the wind. Let's start the 

mission planning process. Decide whether you will be taking off manually (in FBWA) or using the automatic 

takeoff. If you are taking off manually (FBWA Takeoff- Page 13) no further action is needed.lf you are taking 

off automatically, follow Auto Takeoff (Page 12). Now plan the surveying portion of your mission (Planning a 

Mapping Mission- Page 14). Finally, decide on your landing procedure. Automatic landing follows Auto 

Land. Manual landing follows FBWA Land. 

Now we will turn our attention to the assembly ofthe E384. 

Attach the propeller (Page- 8). Attach the tail (Page- 6). Attach the wings (Page- 7). Place the batteries (but 

do not plug them in!!!) and camera into the E384 and check the balance (Page- 9). 

Go through the E384 Preflight Checklist (Page 25). 

When everything checks out properly go to the Fight Plan screen and press Write WP. After the WP have 

been written to the E384 press Read WP. This will read whatever WP the E384 has stored. Verify all the WP 

are correct. 

Start your camera and prepare for take off. 

If you are taking off manually, follow FBWA Takeoff. 

If you are using an automatic takeoffWP; 

Now the Launcher should pick the E384 up and hold it, fully prepared to launch. Never put body parts near 

the propeller when the battery is plugged in! 

The Launcher should communicate to the Ground Station Manager that he is prepared. The Ground Station 

Manager shall then change the mode to Auto, using either the RC transmitter or the actions tab under the 

HUD. The Grand Station Manager should confirm that the mode is Auto. The Launcher will then proceed by 

throwing the E384 firmly at an angle of approximately 15 degress. Always throw the E384 against the wind 

for best results. 

When the E384 reads 3 m/s ground speed, the motor will begin rotating. The E384 will attempt to hold 

heading during takeoff. When it reaches the takeoff altitude it will turn and travel to the second WP. 

26 
UNMANNED SYSTEMS 

Flight Procedure Summary (Continued} 

If you have completed a manual takeoff, and are now in RTL; 

Watch the E384 circle at least twice to make sure that it is flying properly. Now go to your computer and 

press Auto. This will start the mission. 

During the mission keep an eye on the battery voltage. The voltage will fluctuate most notably at higher 

throttle. If it no longer rises above 14.5V it is time to bring it in for a landing. During the mission pay attention to the flight path and the altitude as well. If the E384 is struggling to maintain its flight path, alterations 

to the mission may be necessary. Likewise if there is a large drop in altitude, greater than 15m, alterations 

may be necessary. 

When the E384 has reached the last WP of the survey portion of the mission it will go into RTL if there is no 

Auto Land procedure. If there is an automatic landing procedure, the E384 will proceed through those WP. 

If you are landing manually, Switch back to FBWA. You now have control. During descent keep throttle very 

low, and no throttle at all if stability is maintained. Always land with the wind at the nose of the E384 to slow 

it down. Bring the E384 down and land on its belly. 

Go to the E384 and unplug the battery. When you are sure the battery is unplugged you may disassemble. 

27 
For PHANTOM 2 Flight Controller Firmware version V3.l0 

& PHANTOM 2 Assistant version V3.8 

& PflANTOM RC Assistant version Vl.l 

2015.01 

I Vt4 

Congratulations on purchasing your new DJI product. Please thoroughly read the entire contents of this manual to 

fully use and understand the product. 

It is advised that you regularly check the PHANTOM 2 's product page at www.dji.com which is updated on a 

regular basis. This will provide services such as product information, technical updates and manual corrections. Due 

to any unforeseen changes or product upgrades, the information contained within this manual is subject to change 

without notice. 

DJI and PHANTOM 2 are registered trademarks of DJI. Names of product, brand, etc., appearing in this manual are 

trademarks or registered trademarks of their respective owner companies. This product and manual are copy 

righted by DJI with all rights reserved. 

If you have any questions or concerns regarding your product, please contact your dealer or DJI Customer Service. 

©2013-2015 DJI. All Rights Reserved.l I G3 
Content 

CONTENT ........................................................................................................................ 2 

IN THE BOX ..................................................................................................................... 4 

LEGEND .......................................................................................................................... 4 

1. PHANTOM 2 AIRCRAFT ............................................................................................... 5 

1.1 BUILT-IN FLIGHT CONTROL SYSTEM INSTRUCTIONS .••••.••.•.•....•..•..•..•..•.•.................•.••••••...•...... S 

1.2 CONNECTIONS WITH OTHER DJI PRODUCTS ............•...............•..........•......••.•.•...........•........... S 

Important Notes of Using with Other OJ/ Products ........................................................ 6 

Connections with Other OJ/ Products ............................................................................. 7 

1.3 LED FLIGHT INDICATORS DESCRIPTION ............................................................................... 11 

1.4 NOTES FOR PHANTOM 2 USING WITH OTHER DJI PRODUCTS ................................................ 12 

2 PROPELLERS ............................................................................................................... 13 

2.1 ASSEMBLY ...•.......................................................................................•..............•.......... 13 

2.2 DISASSEMBLY ................................................................................................................ 13 

2.3 NOTES ......................................................................................................................... 13 

3 REMOTE CONTROLLER ............................................................................................... 14 

3.1 POWER ON THE REMOTE CONTROLLER ............................................................................... 14 

3.2 REMOTE CONTROLLER LED INDICATOR STATUS .................................................................... 15 

3.2.1 Remote Controller Power LED Indicator Status ................................................... 15 

3.2.2 Remote Controller Battery Level Indicator Status ............................................... 15 

3.3 ANTENNA ORIENTATION .................................................................................................. 16 

3.4 REMOTE CONTROLLER OPERATION .................................................................................... 16 

3.5 LINKING THE REMOTE CONTROLLER & BUILT-IN RECEIVER ...................................................... 18 

41NTELLIGENT BATTERY ............................................................................................... 19 

4.1 CHARGING PROCEDURES .................................................................................................. 19 

4.2 INSTALL THE BATIERY ...................................................................................................... 20 

4.3 BATTERY USAGE ............................................................................................................. 20 

4.4 DESCRIPTION OF THE BATIERY LEVEL INDICATOR ................................................................... 21 

4.5 CORRECT BATTERY USAGE NOTES ...................................................................................... 22 

5 CALIBRATING THE COMPASS ...................................................................................... 23 

©2013-2015 DJI. All Rights Reserved. 2 I 
. , 

5.1 CALIBRATION WARNINGS ................................................................................................. 23 

5.2 CALIBRATION PROCEDURES .............................................................................................. 23 

5.3 WHEN RECALIBRATION IS REQUIRED ................................................................................... 23 

6 FLIGHT ....................................................................................................................... 24 

6.1 FLYING ENVIRONMENT REQUIREMENTS .............................................................................. 24 

6.2 STARTING THE MOTORS ................................................................................................... 24 

6.3 TAKEOFF/LANDING PROCEDURES ................................................................................•...... 24 

6.4 FAILSAFE FUNCTION ..............................................................................................•......... 25 

6.5 LOW BATTERY CAPACITY WARNING FUNCTION ...............................•..................................... 27 

6.6 FLIGHT LIMITS FUNCTION ................................................................................................. 27 

Max Height & Radius Limits ......................................................................................... 27 

6.7 FLIGHT LIMITS OF SPECIAL AREAS ...................................................................................... 28 

6.8 CONDITIONS OF FLIGHT LIMITS ......................................................................................... 30 

Disclaimer ..................................................................................................................... 30 

7 ASSISTANT INSTALLATION AND CONFIGURATION ...................................................... 31 

7.11NSTALLING DRIVER AND PHANTOM 2 ASSISTANT .............................................................. .31 

7.2 USING THE PHANTOM 2 ASSISTANT ON A PC .................................................................... 32 

7.3 FIRMWARE UPGRADE OF PHANTOM 2 ............................................................................. 33 

7.4 PHANTOM RC ASSISTANT DESCRIPTION ........................................................................... 33 

8 APPENDIX .................................................................................................................. 35 

8.1 SPECIFICATIONS .............................................................................................................. 35 

8.2 LED FLIGHT INDICATORS DESCRIPTION ............................................................................... 35 

©2013-2015 DJI. All Rights Reserved.3 I 
In the Box 

PHANTOM 2 Propeller Pair 

Intelligent Battery Charger Plug Set 

Screwdriver Assistant Wrench Cables 

/ 

Micro-USB Cable Screws Accessories Box 

i 

Legend 

0 Forbidden(lmportant) Caution Tip Reference 

©2013-2015 DJI. All Rights Reserved.4 I 
1 PHANTOM 2 Aircraft 

Figure 1-1 Figure 1-2 

[l]Propeller [2]Motor [3]Front Side [4]Front LEDs [5]Micro-USB Port [6]Landing Gear [?]Receiver 

Antenna [8]CAN-Bus Connector [9]LED Flight Indicators [lO]DJilntelligent Battery [ll]Compass 

1.1 Built-in Flight Control System Instructions 

The built-in flight control system is used to control the entire aircraft's functions in flight such as Pitch (forwards 

and backwards), Roll (left and right), Elevator (up and down) and Yaw (turn left or right). The flight controller 

contains the MC (Main Controller), IMU, GPS, compass, receiver. 

The IMU (Inertial Measurement Unit) has a built-in inertial sensor and a barometric altimeter that measures both 

attitude and altitude. The compass reads geomagnetic information which assists the GPS (Global Position System) 

to accurately calculate the aircrafts position and height in order to lock the aircraft in a stable hover. The receiver is 

used to communicate with the remote controller and the MC acts as the brains of the complete flight control 

system connecting and controlling all the modules together. 

The PHANTOM 2 can be configured in the Assistant, by choosing Naza-M mode or Phantom 2 mode. 

This manual is for Phantom 2 mode. Please refer to the Naza-M V2 Quick Start Manual for more 

information. 

1.2 Connections with Other DJI Products 

PHANTOM 2 is compatible with other DJI products, including ZENMUSE H3-2D and H3-3D gimbal , iOSD mini , 

Figure 1-3 

©2013-2015 DJI. All Rights Reserved.S I 
Important Notes of Using with Other DJI Products 

( l ) The video cable can provide power for the wireless video transmission module with a battery voltage 

(ll.lVNl2.6V) and a maximum current 2A. 

( 2 ) Make sure the working current of the wireless video transmission module you connect can work with an 

operational voltage between ll.1V-12.6V and the total working current of the iOSD and wireless video 

transmission module is under 2A, as an overcurrent will damage the central board's components. If the 

total current exceeds 2A, please be sure to provide power supplied from a separate power source for the 

wireless video transmission module. 

( 3 ) PHANTOM 2 uses a 2.4GHz RC system. To avoid communication interference, it's not recommended to 

use other 2.4GHz devices (including 2.4G Wi-Fi or 2.4G wireless video transmission module) except the 

2.4G Bluetooth and 2.4G Datalink. 

( 4 ) Be sure to keep the wireless video transmission module and other communicating devices away from the 

compass during installation and connection to avoid interference. 

( 5) To improve the compatibility with ZENMUSE gimbals, the latest factory deliveries of PHANTOM 2 has 

updated to the Version 2 shown below. H3-2D/H3-3D gimbal can be directly installed for the Version 2 

while for Version 1, a H3-3D adapter kit (coming soon) is required to install the H3-3D gimbal. 

Figure 1-4 

( 6 ) When using the H3-3D gimbal, please connect the 8-Pin cable of PHANTOM 2 to the GS port of H3-3D 

shown below. 

Figure 1-5 

©2013-2015 DJI. All Rights Reserved.6 I 
Connections with Other DJI Products 

( 1 ) Connecting the H3-2D and H3-3D gimbal and wireless video transmission module, the figure below uses 

H3-2D as an example. 

Figure 1-6 

( 2 ) Connecting the H3-2D and H3-3D gimbal, iOSD mini and wireless video transmission module, the figure 

below uses H3-2D as an example. 

. I Batt+ w.reless I,.--------...,....,. 

VIDEO GND video 

VIDEO transmission! 

module 1 

___ 2'~''.:tt_: I 

L----' 

Figure 1-7 

©2013-2015 DJI. All Rights Reserved_? I 

I D;.-c;;;ti-;;-;, ;; th.: Vid;;;-C-;h!-; - -~ 

I (sequence by color) 

I VIDEO I 

' -- VIDEO GND I 

f-------ll -- v.... I 

L -=--G.!::!_D ________ _ 

f:;;- ZENMUsE1 

H3-2D I 

I 

I 

I 
( 3 ) Connecting the H3-2D and H3-3D gimbal, iOSD mini and DJI specified wireless video transmission module 

A VL58, the figure below uses H3-2D as an example. 

Figure 1-8 

~ 

ZENMUSE~ H3-2D I 

r 

l 

t 

-~-- Compa-;1 

I + I lu l 0 0 I I 

I t...: 0 0 ______ ..... l 

We recommend connecting the VBat• port of the video cable to the two BATT+ ports of the AVL58 

simultaneously. The same is true of the GND port of the video cable and two BATT- ports. 

( 4) Connecting the H3-2D and H3-3D gimbal, iOSD Mark II and wireless video transmission module, the figure 

below uses H3-2D as an example. 

©2013-2015 DJI. All Rights Reserved.8 J 
-.--.-,.-n-··- -·-·----, I Description of the Video Cable I 

~ Wir'e""i:s~·id;o ;-a;;mi;si~ - ~ 

I module Transmitter specified by I 

I (sequence by color) 

VIDEO I 

I - VIDEO GND I 

I DJI(A VL58} 

I OR lr-------~~~ f Other wireless video transmission! 

I I -v.... 1 

:~ -=--G.J:P---------' 

~o~I:._To:.:;'~it~r ____ 1 

Figure l-9 

\' 

\ \ \ \ 

@. 

The diagram below illustrates the conneciton between the iOSD Mark II and the wireless video transmission module. 

,----- - 8Arr: ~--~ --....JrB:;t--- - - - - - ---, 

I BATT- I !Batt- I 

I BATT+ I B I I att+ Other wireless video 

! BATT+ !-! -----l~ Batt+ transmission module I 

I iOSD Mark II UART ! I Transmitter 1 

I UART I I I 

I AV-GND VIDEO GND I ,_ ____ __!.'t_O.!:!_Tj C:J~c:._ ________ __, 

BATTBATTUse the 8-Pin cable in the iOSD Mark II package when connecting to the DJI specified wireless video 

transmission module A VL58. 

( 5 ) Using the iPad Ground Station 

©2013-2015 DJI. All Rights Reserved.9 I 
Air End 

Ground End 

Figure l-10 

2..4GOATAUI« 

i}.tN;a1'] 

iPad Grou.nd 

Station 

Connect the Air End of 2.4G Bluetooth Datalink to a spared CAN-Bus port of iOSD if an iOSD is us 

( 6 ) Using the PC Ground Station 

AkEnd 

Grouncl End 

..... J: .. ~~,-------'""• ·.···? 

Figure l-11 

©2013-2015 DJI. All Rights Reserved.1 0 I 
1.3 LED Flight Indicators Description 

1. LED flight indicators are used to show the aircraft's current status. Once powered on, the indicators will light 

up. 

Aircraft in Normal status scriptions 

er On Self-Test 

Warming Up & Aircraft cannot take off during warming up 

Warnings and errors 

Remote Controller Signal Lost 

1st Level Low Battery Capacity Warning 

2nd Level Low Battery Capacity Warning 

Not Stationary or Sensor Bias is too big ·············-···········--··············-·············------ ···------···--·-······-···········------··---·-·-----l 

Errors & Aircraft cannot fly. 

••• • Compass data abnormal because of ferro-magnetic interference or 

the compass needs calibration. 

( 1 ) The LED indicators diagram above are for Phantom 2 mode. In Naza-M mode, LED indicators 

will work according to the Naza-M flight control system. 

( 2 ) Connect to the PHANTOM 2 Assistant for detailed information about warnings and errors. 

2. The front LEOs are for indicating where the nose of the aircraft is. They light up solid red only after the motors 

have spooled up. 

The front 

LEOs 

©2013-2015 DJI. All Rights Reserved.11 I 
1.4 Notes for PHANTOM 2 using with other DJI products 

Before using PHANTOM 2 with other DJI products, users should connecting the products correctly and upgrade 

the firmware as requirements below. 

. .· . . :··~ 

.. ·Items. to upgi:,~Cie 

P330CB (built-in 

central board) 

Zenmuse H3-2 

iOSD Mark II 

iOSD mini 

Fitro;w;:~re v.er~ions req1..1irec! ·. 

Vl.O.l.l9 or above 

CMU Vl.O 1 IMU Vl.6 or above 

V3.0l or above 

Vl.06 or above 

Assistant for upgrading · 

PHANTOM 2 

PHANTOM 2 

iOSD 

iOSD 

*The iOSD Assistant is applied to both iOSD Mark II and iOSD mini. 

©2013-2015 DJI. All Rights Reserved.12 I 

Vl.08 or above 

Vl.08 or above 

V 4.0 or above 

v4.o or above 
2 Propellers 

PHANTOM 2 uses the original 9-inch propellers which are classified by the color of each central nut. Damaged 

propellers should be replaced by purchasing new ones if necessary. 

Diagram 

Attach to the motor thread that does Attach to the motor thread that has a 

Assembly Location 

not . have . . a . black dot. bla~kdot. 

Fastening/Un-fastening Lock: Tighten the propeller in this direction. 

Instructions Unlock: Remove the propeller in this direction. 

2.1 Assembl 

1. ( Figure 2-1 ) Remove the four warning cards from the motors after you've read them. 

2. ( Figure 2-2 ) Prepare the two grey nut propellers and two black nut propellers. Make sure to match the 

black nut propellers with the correctly marked black dot motors. Tighten the propellers according to the 

fastening instructions. 

Figure 2-1 Figure 2·2 Figure2·3 

2.2 Disa~,~~~-~!.L~.~~"""'" .... , .. , .. _. __ 

( Figure 2-3 ) Keep the motor deadlocked in place with the assistant wrench (or one hand) and remove the 

propeller according to the un-fastening instructions. 

Propellers are self tightening during flight. DO NOT use any thread locker on the threads. 

2. Make sure to match the propeller nut colors with the corresponding motors. 

3. It is advised to wear protective gloves during propeller assembly and removal. 

4. Check that the propellers and motors are installed correctly and firmly before every flight. 

5. Check that all propellers are in good condition before flight. DO NOT use any ageing, chipped, or broken 

propellers. 

6. To avoid injury, STAND CLEAR of and DO NOT touch the propellers or motors when they are spinning. 

7. ONLY use original DJI propellers for a better and safer flight experience. ""•-'•-••-•••••-Ur .• ~•"C <OC-<C>O • .v •• ~'""-' o o o• " .~. '"''m~W•"•••-'~'" 

©2013-2015 DJI. All Rights Reserved.13 I 
3 Remote Controller 

The PHANTOM 2 remote controller can be configured in the PHANTOM RC Assistant. The sticks mode is Mode 2 

on delivery. 

""'' For upgraded remote controller (models: NDJ6 or NRC900), select "Upgrade Version" in Phantom Assistant. 

For basic remote controller (models: DJ6 or RC900), select "Basic Version" in Phantom Assistant. 

[ 2] ,~--"·"·~···r-F=~:::::==::;--. 

[3] 

[5]· 

Figure 3-1 

J2 

[6] .ill!. • J1 

• 

Figure 3-2 

[l]Antenna [2]Carrying Handle [3]Left Dial [4]3-Position Switch Sl [5]3-Position Switch S2 [6]Joystickl(Jl;J2) 

[7]Joystick2(J3;J4) [8]Neck Strap Attachment [9]Power Switch [lO]Power Indicator 

[ll]Battery Level Indicators LEDl/LED2/LED3/LED4 (from left to right) [l2]Trainer Port 

[l3]Battery Charge & RC Assistant Port (micro-USB port) [14] Potentiometer 

3.1 Power on the Remote Controller 

l. Set the Sl and S2 switches to the upper most position and ensure both joysticks are at 

the mid-point position. Then toggle on the power switch. 

2. Push the power switch to the right to power on the remote controller. If the power LED 

indicator is solid on, the remote controller is functioning normally. The battery level 

indicators display the current battery level. 

l. Please make sure the battery level of remote controller is enough. If the low voltage warning alert 

sounds (refer to <Remote Controller Power LED Indicator Status>), please recharge the battery as soon 

as possible. 

2. Charge the remote controller's battery by using the included micro- USB cable. Using the incorrect 

type of charging cable may cause damage. 

3. Turn off the remote controller before charging. The power LED indicator will display solid red when 

charging is in progress. The LED indicators will display solid green when the battery is fully charged. 

©2013-2015 DJI. All Rights Reserved.14 J 
3.2 Remote Controller LED Indicator Status 

3.2.1 Remote Controller Power LED Indicator Status 

None 

None 

BB---BB---BB 

•••••• B-B-B ..... . 

B--B--B ..... . 

Remote controller joysticks calibration error, need to be re·calibrate. 

Critical low voltage (from 3.45V-3.5V). Recharge the remote 

controller immediately. 

Alert will sound afterJ;:i }llinutes ofinactivity. It will stop once you 

'"'"'~ "'"'~ rem;~e,~o~tmller. 

The remote controller will power off automatically when battery voltage drops below 3.45V. Land and 

A recharge the battery as soon as possible when the low voltage alert occurs to avoid loss of control 

during flight. 

3.2.2 Remote Controller Battery Level Indicator Status 

The battery level indicators will show the current battery level during both the discharging process. The following is 

a description of the indicators. 

:The LED is solid on :The LED will blink regularly 

• :The LED is light off 

50%-75% 

25%-50% 

12.5%-25% 

0%-12.5% 

• 

©2013-2015 DJI. All Rights Reserved.15 I 
3.3 Antenna Orientation 

The remote controller's antenna should point skywards without obstructions for maximum communication range 

during flight. 

Figure 3-3 

3.4 Remote Controller 0 eration 

The operations of remote controller are based on mode 2 stick configuration. 

Definitions 

The 'stick neutral' positions and 'stick released' mean the control sticks of the remote controller are placed at 

the central position. 

To 'move the stick' means that the stick of remote controller is pushed away from the central position. 

Slide Lever is used for the pitch control of the H3-2D and H3-3D gimbal. 

---- - --- ____ / 

©2013-2015 DJI. All Rights Reserved.16 I 

Push the stick up and the aircraft will rise. 

Pull the stick down and the aircraft will descend. 

The aircraft will automatically hover and hold its 

altitude if the sticks are centered. 

Push the throttle stick above the centered (mid-point) 

position to make the aircraft take off. When flying, we 

suggest that you push the throttle stick slowly to 

prevent the aircraft from sudden and unexpected 

elevation 
~~~~~~~~~~==+ 

Position-2 Position-3 

OFF Course Lock Home 

point Lock 

©2013-2015 DJI. All Rights Reserved.17 I 

The yaw stick controls the aircraft rudder. 

Push the stick left and the aircraft will rotate counter 

clock-wise. 

Push the stick right and the aircraft will rotate 

clock-wise. If the stick is centered, the aircraft will 

remain facing the same direction. 

The yaw stick controls the rotating angular velocity of 

the aircraft. Pushing the stick further away from center 

results in a faster aircraft rotation vel.ocity. 

The pitch stick controls the aircraft's front & back tilt. 

Push the stick up and the aircraft will tilt and fly 

forward. 

Pull the stick down and the aircraft will tilt and fly 

backward. The aircraft will keep level and straight if the 

stick is centered. 

Pushing or pulling the stick further away from center 

will result in a larger tilt angle (maximum of is 35 °) and 

faster flight velocity. 

The roll stick controls the aircraft's left & right tilt. 

Push the stick left and the aircraft will tilt and fly left. 

Push the stick right and the aircraft will tilt and fly right. 

The aircraft will keep level and straight if the stick is 

centered. 

Pushing the stick further away from center will result in 

a larger tilt angle (maximum of 35 o) and faster flight 

velocity. 

51 is for compass calibration. Toggle the S1 switch from 

position-1 to position-3 and back to position-1 at least 5 

times, which will force the aircraft to enter into 

compass calibration mode. 

Users can configure position 3(bottom position) of the 

S1 switch to trigger the Failsafe in the Assistant. 

52 is the IOC mode switch. IOC (Intelligent 

Orientation Control) function can be enabled in the 

Assistant when in Naza-M mode. Only use the IOC 

function after you are familiar with flying. 
-90" 

The left dial controls the pitch of the H3-2D and H3-3D 

gimbal. The position of left dial determines the pitch 

angle relative to the horizontal level. 

Turn the left dial to the right to make the gimbal pitch 

up. 

Turn the left dial to the left to make the gimbal pitch 

down. 

The gimbal will keep its current position if the dial IS 

static. 

( 1 ) For ' Ready to Fly' the aircraft will hover when all sticks are released. 

( 2 ) For ' Ready to Fly (non-GPS)' the aircraft will only keep the altitude when all sticks are released. 

3.5 Linking the Remote Controller & Built-in Receiver 

PHANTOM 2 has a built-in receiver, the link button and indicator located on the bottom of the aircraft as illustrated 

in the Figure 3-4. 

The link between the remote controller and aircraft is already established for you so you can initially skip this 

procedure. If you ever replace the remote controller, re-establishing the link is required. 

;~~---,.-9-- Link button & 

Link indicator 

Figure 3-4 

Linking procedures 

l. Power on the PHANTOM 2. 

2. Turn on the remote controller and place it 0.5m-1m away from the aircraft. 

3. Push the link button with a thin object and hold it until the Link indicator blinks red, then release it. 

4. When the Link indicator turns solid green, the link between the remote controller and the built-in receiver 

has been successfully established. '~~~ "' m•~""~",""'""===-w'~""""'"m''"'~ 

•••••• L_ ______________ _ 

Status 

The remote controller is turned off and there is no 2.4GHz signal around, please turn 

on the remote controller . 

The receiver is ready for linking. 

lhereis 2.4GHz signal around but the remote controller is not linked with the receiv 

©2013-2015 DJI. All Rights Reserved.18 I 
lease carry out the linking procedures. 

he remote controller is linked with the receiver successfully. 

4 Intelligent Battery 

The intelligent battery is specially designed for the PHANTOM 2, with a battery capacity of 5200mAh, voltage of 

11.1V and charge-discharge management functionality. The battery should only be charged with the DJI charger. 

D 

Intelligent Battery Charger 

( 1 ) Balance Charging 

( 2 ) Capacity Display 

( 3 ) Communicating 

( 4 ) Overcharging Protection 

( 5 ) Over Discharging 

Protection 

( 6 ) Short Circuit Protection 

( 7 ) Sleep Protection 

( 8) Charging Temperature 

Automatically balance the voltage of each battery cell during charging. 

Display the current battery level. 

The main controller communicates with the battery via communication ports 

for battery voltage, capacity, current and other information. 

Charging stops C!Utomatically when the battery voltage .reaches 12.8V to 

prevent overcharging damage. 

Discharging stops automatically when the battery voltage reaches 8.4V to 

prevent over discharging damage. 

Automatically cuts off the power supply when a short circuit is detected. 

The battery will enter sleep mode after 10 minutes of inactivity to save 

power. The static current is 10nA in sleep mode when the battery is 

powered on without connecting to other devices. 

The battery will charge only when its temperature is within 0°C-55°C. If the 

Detection battery temperature is out of this range, the battery will stop charging. 

( 1 ) Before use, please read and follow the user manual, disclaimer, and the warnings on the battery. 

Users take full responsibility for all operations and usage. 

( 2 ) The battery should only be charged with the charger provided by DJI. DJI does not take any 

responsibility for operation of any charger from a third party. 

l. Connect the charger to a wall socket (Use the plug set if necessary). 

2. Connect the battery to the charger. If the current capacity of the battery is over 75%, you should power on 

the battery to begin charging. 

3. The Battery Level indicators display current capacity level as the battery charges. Please refer to battery 

©2013-2015 DJI. All Rights Reserved.19 I 
level indicator description for details. 

4. The battery is fully charged when the Battery Level indicator lights are off. Please disconnect the charger 

and battery when the charging is completed. 

_,EJ 

Wall Socket 

4.2 Install the Battery 

Push the battery into the battery compartment correctly as the following diagram shows. Make sure to push the 

battery into the compartment until you hear a 'click' sound. 

Figure 4-1 

An incorrectly inserted battery may cause one of the following to occur: (l) Bad contact. (2) Unavailable 

battery information. (3) Unsafe for flight. (4) Unable to take off. 

4.3 Battery Usage 

LED2 ··· LED3 

LEDl LED4 

Battery Level Indicator Battery Power Button 

(Built-in Battery Power indicator) 

Figure 4-2 

(l) Checking the battery level: When the battery is powered off; pressing the battery power button once will 

indicate the current battery level. Refer to< Battery Level Indicator Description> for details. 

(2) Powering on: When the battery is powered off; press the battery power button once and then press and hold for 

2 seconds to turn on the intelligent battery. 

(3) Powering off: When the battery is powered on; press the battery power button once and then press and hold for 

2 seconds to turn off the intelligent battery. 

©2013-2015 DJI. All Rights Reserved.20 I 
(4) Checking the battery life: When the battery is powered off; press and hold the battery power button for 5 

seconds to check the battery life. The battery level indicators will show the life and the battery power indicator 

will blink for 10 seconds, then all LEOs will light out and the intelligent battery will turn off. Refer to < Battery 

Level Indicator Description> for details. 

More battery information is available in the battery tab of the PHANTOM 2 Assistant. 

4.4 Description of the Battery Level Indicator 

The battery level indicators will show the current battery level during both the charging and discharging process as 

well as battery life. The following is a description of the indicators. 

:The LED is solid on :The LED will blink regularly 

:The LED is light off 

50%-75% 

75%-100% 

75%-87:5% 

62.5%-75% 

50%-62.5% 

37.5%-50% 

25%-37.5% 

12.5%-25% 

0%-12.5% 

90%-100% 

©2013-2015 DJI. All Rights Reserved.21 I 
80%-90% 

70%-80% 

60%-70% 

50%-60% 

40%-50% 

30%-40% 

20%-30% 

Less than 20% 

_4.5 Corre~t Batte!~~sa5t~~~-~tes ~~~--~~~·~·~·~···~~--~~ .. -·-···~· .. ·~·~··~~--·-~·~-~-~~--.., 

!1. Never plug or unplug the battery into the aircraft when it is powered on. 

I 

I 2. The battery should be charged in an environment that is between 0°( to 40°(. and be discharged in an 

environment that i.s between -20°( to 50°C. Both charging and discharging should be in an. envjronment 

where the relative humidity is lower than 80%. 

3. It's recommended to charge and discharge the battery thoroughly once every 20 charge/discharge cycles. 

Users should discharge the battery until there is less than 8% power left or until the battery can no longer 

be turned on. Users should then fully recharge the battery to maximum capacity. This power cycling 

procedure will ensure the battery is working at its optimal level. 

4. For long term storage please place the battery with only a 40-50% capacity in astrong battery box 

securely. We recommend discharging and charging the battery completely once every 3 months to keep it 

in good condition. The capacity should be varied in such a cycle (40%-50%}--0%-100%~(40ow50%). 

5. It's suggested you purchase a new battery after you have discharged your current battery over 300 times. 

Please completely discharge a battery prior to disposal. 

6. It's suggested that you purchase a new battery if the current battery is swollen or damaged in any way. 

7. Never try to recharge or fly with a battery that is swollen or damaged in any way. 

8. Never charge the battery unattended. Always charge the battery on a non-flammable surface such as 

concrete and never near any flammable materials. 

9. Safety is extremely important and users can get more information in the DISCLAitvtER. 

©2013-2015 DJI. All Rights Reserved.22 I 
5 Calibrating the Compass 

IMPORT ANT: Make sure to perform the Compass Calibration procedures prior to the first flight. 

The compass is very sensitive to electromagnetic interference which causes abnormal compass data and leads to 

poor flight performance or even flight failure. Regular calibration of the compass enables the compass to perform at 

its optimal level. 

5.1 Calibration Warnings 

( 1) DO NOT calibrate your compass where there is a possibility for the existence of strong 

magnetic interference such as magnetite, parking structures, and steel reinforcement 

underground. 0 ( 2) DO NOT carry ferromagnetic materials with you during calibration such as keys or cellular 

phones. 

( 3) Compass Calibration is very important; otherwise the flight control system will work abnormally. 

5.2 Calibration Procedures 

Please carry out the calibrating procedures in the flight field before flight. Please watch the quick start video of the 

PHANTOM 2 for more compass calibration details. 

Position-] [~) ,\~'f!J ) ~ ' 

Position-3 {® ,_ ...... 

Position-1-,Position-3-,Position-1 

LED Flight Indicator 

5.3 When Recalibration is required 

LED Flight Indicator 

-l~lti!12ti§(j 

-~1 

I Start vertical calibration .•• 

Position·1-,Position·3-,Position·1 

Flip on~.e 

Normal LED 

( l ) When Compass Data is abnormal, the LED flight indicator will blink alternating between red and yellow. 

( 2) Last compass calibration was performed at a completely different flying field/location. 

( 3) The mechanical structure of the aircraft has changed, i.e. changed mounting position of the compass. 

( 4 ) Evident drifting occurs in flight, i.e. the aircraft doesn't fly in straight lines. 

©2013-2015 DJI. All Rights Reserved.23 I 
6 Flight 

6.1 Flying Environment Requirements 

( 1 ) Before your first flight, please allow yourself some flight training (Using a flight simulator to 

practice flying, getting instruction from an experienced person, etc.). 

( 2 ) DO NOT fly in bad weather, such as rain or wind (more than moderate breeze) or fog. 

( 3 ) The flying field should be open and void of tall buildings or other obstacles; the steel structure 

within buildings may interfere with the compass. 

( 4 ) Keep the aircraft away from obstacles, crowds, power lines, trees, lakes and rivers etc. 

( 5 ) Try to avoid interference between the remote controller and other wireless equipment (No base 

stations or cell towers around). 

( 6 ) The flight control system will not work properly at the South Pole or North Pole. 

( 7 ) Never use the aircraft in a manner that infringes upon or contravenes international or domestic 

lays and regulations. 

6.2 Starting the Motors 

A Combination Stick Command (CSC) is used to start the motors. Push the sticks according to one of the options 

below to start motors. Once the motors have started, release both sticks simultaneously. The same CSC is used to 

stop the motors. 

A B c D 

Figure 6-1 

6.3 T akeoffJ~,~~~~ir:',9 Proced~:~res 

l. Start by placing the PHANTOM 2 on the ground with the battery level indicators facing you. 

2. Turn on the remote controller. 

3. Power on the aircraft by turning on the intelligent battery. 

4. When LED flight indicator blinks green/yellow, the PHANTOM 2 is entering Ready to Fly/Ready to Fly 

(non-GPS) mode. Start the motors with the CSC command. 

5. Push the throttle stick up slowly to lift the aircraft off the ground. Refer to <Remote Controller Operation> 

for more details. 

6. Be sure you are hovering over a level surface. Pull down the throttle stick to descend. The stick will lock into 

©2013-2015 DJI. All Rights Reserved.24 I 
place and the aircraft will descend steadily. 

7. After landing, leave the throttle stick down for 3 to 5 seconds to stop the motors. Return throttle stick to 

middle position after the motors have stopped. 

0 You SHOULD NOT execute the CSC during normal flight! This will stop the motors and cause the 

aircraft to descend rapidly and drop without any type of control. 

( 1 ) When the LED flight indicator blinks yellow rapidly during flight, the aircraft has entered into 

Failsafe mode, refer to <Failsafe Function> for details. 

( 2 ) A low battery capacity warning is indicated by the LED flight indicator blinking red slowly or 

rapidly during flight. Refer to the <Low Battery Capacity Warning Function> for details. 

( 3 ) Watch the quick start video about flight for more flight information. 

( 4 ) Aircraft and battery performance is subject to environmental factors such as air density and 

temperature. Be very careful when flying 3000 meters (9800 feet) or more above sea level, as 

battery and aircraft performance may be reduced. 

( 5 ) When used with a H3-3D gimbal, a GoPro camera, and the iOSD mini, your Phantom 2 will be very 

close to its maximum takeoff weight. It is not recommended that you attach the Phantom 2 

propeller guards at this weight. Otherwise, the aircraft will be unable to fly normally. 

6.4 Failsafe Function 

The aircraft will enter Failsafe mode when the connection from the remote controller is lost. The flight control 

system will automatically control the aircraft to return to home and land to reduce injuries or damage. The following 

situations would make the aircraft fail to receive a signal from the remote controller and enter Failsafe mode: 

( 1 ) The remote controller is powered off. 

( 2 ) The remote controller is powered on but the S1 is toggled in the position triggering the Failsafe (this must 

have been configured in the PHANTOM 2 Assistant). 

( 3 ) The aircraft has flown out of the effective communication range of the remote controller. 

( 4 ) There is an obstacle obstructing the signal between the remote controller and the aircraft, essentially 

reducing the distance the signal can travel. 

( 5 ) There is interference causing a signal problem with the remote controller. 

Failsafe works differently depending on the mode the aircraft is in when Failsafe mode is initiated whether it is in 

the Ready to Fly or Ready to Fly (non-GPS) mode. 

Ready to Fly (non-GPS) ----Automatic landing 

The flight control system will try to keep the aircraft level during descent and landing. Note that the aircraft may 

be drifting during the descent and landing process. 

Ready to Fly ---- Automatic go home and land 

The flight control system will automatically control the aircraft to fly back to the home point and land. 

©2013-2015 DJI. All Rights Reserved.25 I 
Home Point 

When the aircraft is initializing the Ready to Fly status, the aircraft will record the current GPS coordinates as 

the home point. It is recommended to lift off only after Ready to Fly status is confirmed for the safety of being 

able to fly back to home point successfully in case the Failsafe mode is initiated. 

Go Home Procedures 

1 Record Home Point. 

~--------------...,.,..... f Height over home point> 20m 

~-------------1 I Elevate to 20m 1 20m ..,.,..-

Height over home point<=20m 

LED Flight Indicator< ,jV~)(fj(_';~ 

Figure 6·2 

( 1 ) In a Failsafe situation, if less than 6 GPS satellites are found for more than 20 seconds, the aircraft 

will descend automatically. 

( 2 ) When the aircraft is landing automatically, users can control the aircraft's position and altitude if 

the remote controller signal is recovered. 

In Phantom 2 mode, users can set a new home point manually when the aircraft is in "Ready to fly" status 

as long as a home point has been recorded automatically. Quickly flipping the S2 switch of the remote 

controller from upper most to lower most positions 5 times or more will reset the current aircraft position 

as a new home point of PHANTOM 2. When successfully reset, you will see a series of rapid green blinks 

on the LED Flight Indicator. The definition of "home point" is: 

( 1 ) The home point is the place PHANTOM 2 returns to when the control signal is lost, which Js 

recorded last time. 

( 2 ) The home point is used to calculate the horizontal distance between you and the aircraft, the 

D 

distance will be displayed as t=-f if using iOSD module. 

Regaining Control during Failsafe Procedure 

Position of 

Switch Sl Position-1 

When the S1 switch is switched to Position-1, 

How to regain toggle the S1 switch to any other position once to 

control regain control. If remote controller's signal is 

recovered, control is returned back to the pilot. 

©2013-2015 DJI. All Rights Reserved.26 J 

Position-3 

Position-2 

(No tri ering the Failsafe) · 

Regain control as soon as signal is 

recovered. 
6.5 Low Battery Capacity Warning Function 

The low battery capacity warning alerts users when the battery is close to depletion during flight. When it appears, 

users should promptly fly back and land to avoid accidental damage. The PHANTOM 2 has two levels of low battery 

capacity warning. The first appears when the battery has less than 30% power and the second appears when it has 

less than 15% power. 

( 1 ) When battery power drops below 30% and LED indicator will blink red slowly. 

( 2 ) At lower than 15% the LED indicator will blink red rapidly, the PHANTOM 2 will also begin to descend and 

land automatically. After it has landed, keep the throttle stick at its lowest point or execute CSC. 

( 3 ) There is a hidden third low battery threshold in addition to the 1st and 2nd level warnings. This uses 10.65V 

as its threshold. Both this voltage threshold and the 2nd Level Low Battery Warning will trigger auto-landing. 

Altitude can be maintained if necessary by pushing up on the throttle stick. 

( 1 ) Remember to fly your PHANTOM 2 back as soon as you see a low battery capacity warning. 

( 2 ) Keeping the battery contact needles and pads clean is very important. Any dirt and dust may 

cause a communication failure. 

6.6 Flight Limits Function 

All UA V (unmanned aerial vehicle) operators should abide by all regulations from such organizations at ICAO 

(International Civil Aviation Organization) and per country airspace regulations. For safety reasons, the flight limits 

function is enabled by default to help users use this product safely and legally. The flight limits function includes 

height, distance limits. 

In Ready to Fly status, height, distance limits works together to restrict the flight. In Ready to Fly (non-GPS) status, 

only height limit works and the flying height restricted to be not over 120m. 

(1) The default parameters in the Assistant is compliant within the definitions of class G ruled by 

ICAO. (Refer to Airspace Classification to get more details). As each country has its own rules, 

make sure to configure the parameters to comply with these rules too, before using the 

PHANTOM 2. 

(2) Users in Mainland China can refer to ~fflmn~~±91{~fflVJ5!. 

Nax Height & Radius Limits 

The Max Height & Radius restricts the flying height and distance. Configuration can be done in the PHANTOM 2 

Assistant. Once complete, your aircraft will fly in a restricted cylinder. 

©2013-2015 DJI. All Rights Reserved.27 I 
Max Height 

Max Radius 

Max Height 

Figure 6-3 

The flight height is restricted to fly Warning: Height limit 

under the max height. reached. 

aircraft when it 

is powered on 

Figure 6-4 

None. 

The flight distance is restricted to fly Warning: Distance limit Rapid red flashings •••••• 

The flight height is restricted to fly Warning: Height limit reached. 

under the minor height between the None. 

Max height and 120m. 

Not limited, no warnings or LED indicators. 

(l) If the aircraft flies out of the limits, you can still control your aircraft except to fly it further away. 

,/ (2) If the aircraft is flying out of the max radius in Ready to Fly (non-GPS) status, it will fly back 

within the limits range automatically if 6 or more GPS satellites have been found. 

6.7 Flight Limits of Special Areas 

Special areas include airports worldwide. All special areas are listed on the DJI official website. Please refer to 

http://www.dji.com/fly-safe/category-mc for details. These areas have been divided into category A and category B. 

©2013-2015 DJI. All Rights Reserved.28 I 
l0.5m 

Center of 

Special 

Area 

Airspace: A,C,D 

Boundary: fl.,.£, 

£ 

Category A Category B 

Motors will not start. 

A If the Phantom flies into a special area in Ready to Fly 

(non-GPS) mode and Ready to Fly mode activates, it will 

automatically descend and land then stop its motors. 

B If the Phantom flies into a special area in Ready to Fly 

(non-GPS) mode and Ready to Fly mode activates, it will 

•••••• descend to airspace C and hover 5 meters below edge g. 

No restrictions of flight, but the Phantom will not enter 

Category A. the aircraft can fly free, but it will not enter 

c 

Airspace B through Boundary b & d. 

Around Category B sites, the phantom can fly freely, but it will 

not enter into Airspace A through Boundary§!; 

D 

No restrictions. None. 

Blue 

©2013-2015 DJI. All Rights Reserved.29 I 
Semi-automatic descent: All stick commands are available except the throttle stick command during 

the descent and landing process. tvlotors will stop automatically after landing. Users will regain control 

once the motors have stopped. There is no need to toggle the Sl switch. 

(l) When flying in the airspace (A/B/C) of restricted special area, LED flight indicators will blink red 

•••••• quickly and continue for 3 seconds, then switch to indicate current flying 

status and continue for 5 seconds at which point it will switch back to red blinking. 

(2) For safety reasons, please do not fly close to airports, highways, railway stations, railway lines, 

city centers and other special areas. Try to ensure the aircraft is visible. 

6.8 Conditions of Flight Limits 

In different working modes and flight modes, flight limits will differ according to number of GPS satellites found. 

The following table demonstrates all the cases(Y: available; x :unavailable). 

All flights are restricted by height, distance and special areas simultaneously. 

Ready to Fly (non-GPS) X X 

;:::6 y y y 

GPS 

<6 X y X 

;:::6 y y X 

A TTl. 

<6 X y X 

;:::6 X X X 

tvlanual 

<6 X X X 

Disclaimer 

Please ensure that you are kept up to date with International and Domestic airspace rules and regulations before 

using this product. By using this product, you hereby agree to this disclaimer and signify that you have read this fully. 

You agree that you are responsible for your own conduct and content while using this product, and for any direct or 

indirect consequences caused by not following this manual, violate or disregard any other applicable local laws, 

administrative rules and social habits thereof. 

©2013-2015 DJI. All Rights Reserved.30 I 
7 Assistant Installation and Configuration 

7.1 Installing Driver and PHANTOM 2 Assistant 

Installing and running on Windows 

1. Download driver installer and Assistant installer in EXE format from the download page of PHANTOM 2 

on the DJI website. 

2. Connect the PHANTOM 2 to a PC via a Micro-USB cable. 

3. Run the driver installer and follow the prompts to finish installation. 

4. Next, run the Assistant installer and follow the prompts to finish installation. 

5. Double click the PHANTOM 2 icon on your Windows desktop to launch the software. 

A The installer in EXE format only supports Windows operating systems (Win XP, Win7, WinS (32 or 64 

bit)). 

Installing and running on Mac OS X 

1. Download the Assistant installer in DMG format from the download page of PHANTOM 2 on the DJI 

website. 

2. Run the installer and follow the prompts to finish installation. 

3. When launching for the first time if use Launchpad to run the PHANTOM 2 Assistant, Launchpad won' 

allow access because the software has not been reviewed by Mac App Store. 

"Phantom" can't be :opened b.emlise iris 

from an unidentified developer. 

UM rnd Ht wnet#wi., ,.,., PM. 

4. Locate the PHANTOM 2 icon in the Finder, press the Control key and then click the PHANTOM 2 icon 

(or right-click the PHANTOM 2 icon using a mouse). Choose Open from the shortcut menu, click open in 

the prompt dialog box and then software will launch. 

5. After the first successful launch, directly launching of the software can be achieved by double-clicking 

the PHANTOM 2 icon in the Finder or using Launchpad. 

©2013-2015 DJI. All Rights Reserved.31 I 
Mr~mft 

MOO>r Type: Duad·t<>!Of X 

.f!Jl 

flocoi""' Type: D·Bus 

M~~eyr 

Mo!Ot 

-l&o Spe<>d: 

tlu\ Ott Type: 

i'\® 

Folfuaf& Methods: Go·Home .00 l.onding 

IOC 

,i:;ili!i..' 

:J'41i!i,i 

1111elligent OrieotaJlon Control: OFF 

------a-·1005 .._ ":":""'''''j'}" LMl1] _____ ._.., .. ifiOtf 4Dt ''t.~•fji••_~,,~,-~f:····· {::~~J 

... "'""'"""'""'l[iiiili) 

01-··········· 

Gimbal Switd.: 

!l•ltory' 

CUW>I Vol\ag&: 

CuireillCapac<ty: 

!'lrst l""e! Warning: 

Installer in DMG format supports only Mac OS X 10.6 or above. 

ON 

12400mV 

liS% 

30% 

15% 

Usage of PHANTOM 2 Assistant on Mac OS X and Windows are exactly the same. The Assistant pages 

appear in other places of this manual are on the Windows for example. 

1. Start up the PC, power on the PHANTOM 2, then connect the PHANTOM 2 to the PC with a Micro-USB 

cable. DO NOT disconnect until configuration is finished. 

2. Run the PHANTOM 2 Assistant and wait for the PHANTOM 2 to connect to the Assistant. Observe the 

indicators • • on the bottom of the screen. When connected successfully, the connection indicator is 

and communication indicator is blinking •. 

3. Choose [Basic] or [Advanced] configuration pages. 

4. View and check the current configuration in the [View] page. 

PHANTOM 2 a ""*' 

View configurations 

RC. Gain .. 

Gimbal. Battery 

Comn:unication 

indicator 

·"-<~~, ~ r¥ a @ i E< ~!!:: '" =~ i ~~g up~ral!e mttl: 

,., « 0C ' ~ ~ NN" "~ ~ 

R( 

Ril.,;:llr>>:!lT3,::~ !)'S!J:to' f!':< 

f.r:J;;;J>te i!.'lz:tw.:l-:s. C.o·~i::.>!!W ~!~<:l L;l;r~;;I':!};J 

liX 

lro1~l=<;~em <')(!M{as;U~ Ct.f>Y.nl :OfF 

<...m~~· 

QrJ%:-.al $w!!0. 

~..jj~;-tt'( 

ON 

C<mHrt '<Oit<;Q~ O::,m\1 

Ci.l'IJ'en1: ca~aotr ~ .. 

Function switch of Phantom 2 

and Naza-N mode 

.", Language sv.:ap 

A.ccount, software 

version 

Finnvvare upgrade 

li'iU calibration 

~This image is for reft-?reno:~ 

cn!y. P!ease refer to the 

Connt=;;·(_tion indicator · j .Ziilliillllilliillllliiillilliiiiilllllllllllllll actual user interface. 

©2013-2015 DJI. All Rights Reserved.32 I 
( l ) Users should not enable the Naza-M function before finishing Advanced Flight Maneuvers 

procedure in the " PHANTOM Pilot Training Guide". If the Naza-M mode is enabled, users can 

switch the control mode between ATTI. Mode, GPS Mode or Manual Mode, and access the 

advanced settings (e.g. IOC). In addition, the LED located on the rear frame arms will display 

Naza-M flight status indications instead of the PHANTOM 2's indicators. Do not enable the 

Naza-M mode unless you are an experienced user or guided by a professional. 

( 2 ) You can change to the Phantom 2 mode by clicking the same button used to turn on the Naza-M 

mode. This operation will disable the Naza-M mode and enable Phantom 2 mode. All parameters 

will be returned to factory settings. 

7.3 Firmware upgrade of PHANTOM 2 

Please refer to the PHANTOM 2 Assistant to install driver and PHANTOM RC Assistant, and then follow the 

procedures below to upgrade the software and firmware; otherwise the PHANTOM 2 might not work properly. 

l. An internet conf1ection is required to upgrade PHANTOM 2 's firmware. 

2. Click the [Upgrade] icon to check the current firmware version and whether the installed firmware'is the 

latest version. If not, click the relative links.to upgrade. 

3. Be sure to wait until the Assistant shows ''finished". Click OK and power cycle the PHANTOM 2 after 5 

seconds. Once the:firmware is up to date. 

PHANTOM 2 •• PhOm!'m!2 ; ""''"" T - X 

[Q. cl' t1 a :=::r:= i '0/'i~O'i Ea!!~ AIUMt:::f!4 TO!=l$ !!'/0. 

0'<- =oz ~~= "':?W@~-= ~ «~ ,; ~ ~ ~ ~ ~ h " N h N "'="=~ = " 

t.~er HMa>Ml!WJO fiU'fW1.3tl;!; ""''""" Firmware upgradable items ·w41~~~~~ Main.C®troller ... 10VM-94®.} to• t'..Jlte!1-hl':'r.»V..>$,Hl-i 

""' h">A ?.VI.£ q;rn.; 

~l!'f-PMI'ltun'i2 1?-0J)l\ 0.1l)OOf~ t.O.O:O M~Bp¢;~.:< 

"'"""" JQ.I)l)p Q:lF\:101.$1-W Ut1"l:B wrn<M-.."tr~~;: 1 ~ 1 ~$ ~"·--·· Upgrade link 

"""""""" 1.9 2:0();)~U}$ tl) Ui;<•-~~~ 

Glmt21wtl -~.8 ;t0()l:INWOO t.6 H-::<VJ:»~$ 

.... ., ,_(l.O.D 1)0;){!00€3S. 1.6JJ.C Ni:<t.::PlhN!i 

Current firmware version ··-i····~···~··· 

------------·-·---------···-·---·--·- ·-------··-·····-··---·-------, 

(l) DO NOT power off until the upgrade is finished. 

:l C 2) If the firmware upgrade failed, the main controller will enter a waiting for firmware upgrade 

status automatically. If this happens, repeat the above procedures. 

Firmware upgradable items: (l) Main Controller (2) P330CB(Main Board) (3) Receiver (4) Gimbal 

CMU (5) GimbaiiMU (6) Battery 

7.4 PHANTOM RC Assistant Description 

Please follow the procedures to finish the configuration of the remote controller. 

©2013-2015 DJI. All Rights Reserved.33 I 
1. Turn off the remote controller and find the Micro~ USB port on the bottom of it. 

2. Start up the PC, power on the remote controller, and then connect the remote controller to the PC with a 

tvlicro-USB cable. DO NOT disconnect until the configuration is finished. 

3. Run the PHANTOM RC Assistant and wait for the remote controller to connect to the Assistant. Observe 

the indicators •.• on the bottom left of the screen. When connected successfully, the connection 

indicator is and communication indicator is blinking: •. 

4.. Finish configuration in the [Main] page. 

5. Finish upgrade in the [Info] paga if necessary. 

Main Page of the 2.4GHz Remote Controller 

==r=· .. ,...,. ... ;.;;.. "" .. "'·== 

'-=="-t-""' =""4F"-= .. i ... : ._ .......... . 

PHANTOM N.C. ""~"• _ ""'"' Language swap ~ ~~< :NN=« ~~ N .N N ~ ~=~~~"""'=- ~ VN~N< X= V -·, VV =~'";,:· N~""'?~""~ V ·~~~'"'\ 

~' z 

ll'lt~ 

J The ~C<m RC Assistant ::>i.!l'tNa/e t:s 

:J llMdlt~CMfi9.lrnMdtJp'Jr<'ld~lflSO..li 

; ll'h.aili!:9cm.R.fH~&C.:.rltrOIIq.J {ti-ne 

~ 5.8GH.< ¥10 2 4<>1-lc 

Communication indicator .. ,./,.,,""·"~ 

Connection indicator· 

©2013-2015 DJI. All Rights Reserved.34 I 

... --r--- ... ~~F=.;;.c. 

--~~F=.::.c. 

.... ~:· 

.-. .................... ~::<F":J 

,... """"'''"I"'"': 3": 

.... ,,,,,,,,,,,,,,,,,,,,, ~-~~~J 

Firmware upgrade 

Account, softvJure 

version 

*This imasJe is fer 

n·:ference oniy. Please 

refer to the actual 

user interface. 
.• 

8 Appendix 

Operating environment temperature -10°( to 50°( 

Power consumption 5.6W 

Supported Battery DJI Intelligent battery 

Weight (including the battery) lOOOg 

Take-offWeight ~1300g 

Hoverl~g A~curacy (R~ad~to Fly) Vertical: 0.8m; Horizontal: 2.5m 

Max Yaw Angular Velocity 200" /s 

· Max Tilt Angl~ 35 • 

Max Ascent/ Descent Speed Ascent: 6m/s; Descent: 2m/s 

Max Flight Speed 15m/s (Not Recommended) 

Wheelbase 350mm 

Operating Frequency 2.4GHz ISM 

Communication Distance (open area) 1000m 

Receiver Sensitivity (l%PER) -97 d Bm 

Working Current/Voltage 120 mA@3.7V 

Built-in LiPo Battery Working Current/Capacity 3.7V, 2000mAh 

DJIIf1telli.gel1t Battery 

Type 

Capacity 

Charging Environment Range 

Discharging Environment Range 

Aircraft in abnormal status 

••••• 

©2013-2015 DJI. All Rights Reserved.35 I 

3S LiPo Battery 

5200mAh, 11.lV 

0°( to 40°( 

-------------------------·-----·---' 

Power On Self-Test 

Warming Up & Aircraft cannot take off during warming up 

Ready to Fly 

Ready to Fly (non-GPS) 

Warnings and errors 

Remote Controller Signal Lost 

1st Level Low Battery Capacity Warning 
• • • 

2nd Level Low Battery Capacity Warning 

Not Stationary or Sensor Bias is too big 

Errors & Aircraft cannot fly.* 

Compass data abnormal because of ferro-magnetic interference or 

the compass needs calibration. 

* Users can connect to the PHANTOM 2 Assistant to get detailed information about warnings and errors. 

©2013-2015 DJI. All Rights Reserved.36 I 
1 

2 

3 

DECLARATION OF SERVICE 

I am employed in the County of San Diego, State of California. I am over the age of 18 and 

4 not a party to the within action. My business address is 662 Encinitas Boulevard, Suite 260, 

Encinitas, CA 92024. On August 28, 2015, I served the foregoing documents, described as: 

5 

6 

7 

1. 

2. 

3. 

4. 

Exemption Request Section 333 FMRA; 

Preflight Checklists attached as Ex. 1; 

E384 Operations Manual attached as Ex. 2; and 

Phantom 2 User Manual attached as Ex. 3 

8 on the parties of interest as follows: 

9 U.S. Department of Transportation 

Docket Management System 

10 1200 New Jersey Ave., SE 

Washington, D.C. 20590 

BY U.S. MAIL 

I placed a true and correct copy of said document(s) in sealed a envelope(s) addressed 

according to the above listed parties and deposited such envelope( s) in the mail at Encinitas, 

California. The envelope(s) was/were mailed with postage thereon fully prepaid. 

I am "readily familiar" with the firm's practice of collection and processing correspondence 

for mailing. It is deposited with U.S. postal service on that same day in the ordinary course 

of business. I am aware that on motion of the party served, service is presumed invalid if 

postal cancellation date or postage meter date is more than one day after date of deposit for 

mailing in affidavit. 

STATE I declare under penalty of perjury under the laws of the State of California 

that the above is true and correct. 

FEDERAL I declare that I am employed in the office of a member of the bar of this Court 

at whose direction the service was made.