1

Drone/UAS Practice Group 35 E Wacker Drive Suite 1875 Chicago, IL 60601 Tel. 312.201.8310 Jeffrey@Antonelli

- Law.com

U.S. Department of Transportation February 1, 2016 Docket Management System 1200 New Jersey Ave S.E. Washington, D.C. 20590

Re: Request for Exemption unde r Section 333 of the FAA Modernization and Reform Act of 2012 and Part 11 of the Federal Aviation Regulations from Certain Provisions of 14 C.F.R.

Showing Animals Respect and Kindness, Inc.

Dear Sir or Madam:

Pursuant to Section 333 of the FAA Modern ization and Reform Act of 2012 (the Reform Act) and 14 C.F.R. Part 11, Antonelli Law files this petition for exemption on behalf of Showing Animals Respect and Kindness, Inc. (SHARK)

, an operator of Small Unmanned Aircraft Systems (“UAs”) for the commercia l purposes of aerial photography and videography documenting animal cruelty . Specifically, petitioner seeks an exemption from the Federal Aviation Regulations (“FARs”) listed in Appendix A to allow commercial operation of its UA , so long as such operations are conducted within and under the conditions outlined herein or as may be established by the FAA in a grant of this petition. This request is substantially similar to dozens of other aerial photography and videography petitions previously approved, and s hould be considered under the expedited summary grant procedure.

Approval of the exemption for petitioner will allow operation of the Freefly Cinestar 8 Octocopter for the proposed uses in Class G airspace nationwide, or as otherwise prescribed by an Air Traffic Organization (ATO) issued COA. The UA covered by this petition have been previously approved for the proposed uses in the exemption grants identified in Sec tion VII of the petition. The UA covered by this petition are small battery

- powered craft, weighing no more than 14.3 lbs. (6.52 kg)

, inclusive of battery a nd payload. Operation of the UA under the strict conditions proposed below will provide an equivalen t level of safety, as Congress intended, while still allowing commercial op erations. Operations using this UA are far safer than conventional operations conducted with helicopters and fixed

- wing aircraft that weigh thousands of pounds, carry large amounts of highly flammable fuel, and operate in close proximity to the ground, trees, infrastructure, and people.

Congress directed the FAA to consider seven factors in deciding whether to approve Section 333 exemption petitions

- size, weight, speed, operation al capability, proximity to airports, proximity to populated areas, and operation within visual line of sight. In this case, each factor3 Table of Contents I. Publishable Summary

................................ ................................ ................................ ............ 5

II. Petitioner’s Contact Information

................................ ................................ ........................... 5

III. Proposed Operations

................................ ................................ ................................ .............. 6

A. The UAs

................................ ................................ ................................ ......................... 6

B. The Crew

................................ ................................ ................................ ........................ 7

C. Flight Conditions

................................ ................................ ................................ ............ 7

D. Flight Operations

................................ ................................ ................................ ............ 7

IV. Aircraft and Equivalent Level of Safety

................................ ................................ ................ 8

VI. Proposed Conditions of the Exemption

................................ ................................ ................. 8

VII. Public Interest and Safety

................................ ................................ ................................ ...... 11

VIII. Regulations from Which Exemption is Requested

................................ .............................. 13 Appendix A: FARs as to which SHARK wishes t he same determination to be made as has been made previously.

................................ ................................ ................................ ........... 134 Exhibit List

Exhibit 1: SHARK Pilot Operating Manual

........................... Submitted confidentially to the FAA

Freefly Cinestar 8 Octocopter

Exhibit 2: SHARK Air frame Specifications

........................... Submitted confidentially to the FAA Exhibit 3 : Freefly CineStar 8 Build Manual

.......... Submitted separately due to upload restrictions Exhibit 4 : Flight Control Boa rd Manual

................................ ................................ ....................... 15 Exhibit 5 : GPS Board Manual

................................ ................................ ................................ ...... 29 Exhibit 6: Navigational Board Manual

.................. Submitted separately due to upload restrictions Exhibit 7: Power Distribution Board Manual

........ Submitted separately due to upload restrictions Exhibit 8 : Graupner MX20 Tx Manual

................. Submitted separately due to upload restrictions Exhibit 9 : JRP2930 Manual

................................ ... Submitted separately due to upload restrictions Exhibit 10 : MikroKopter Tool Manual

.................. Submitted separately due to upload restrictions Exhibit 11: MK Tool Settings Manual

................... Submitted separately due to upload restrictions Exhibit 12: QuadroPower MotorQC

- 3328

............. Submitted separately due to upload restrictions Exhibit 13: APC 13 x 6.5E Propeller

..................... Submitted separately due to upload restrictions Exhibit 14: Stinger 5.8 GHz Pro 250mw AVD Transmi tter

................................ .............................

................................ ................................ ................ Submitted separately due to upload restrictions Exhibit 15: Yellowjacket 5.8 Diversity Receiver

................................ ................................ .............

................................ ................................ ................ Submitted separately due to upload restrictions Exhibit 16: XBee Pro 900 RPSMA

....................... Submitted separately due to upload restrictions

Exhibits 1 and 2 has been submitted to the FAA confidentially and is not available to the public.

Exhibits 3 and 6

- 16 have been submitted separately to Regulations.gov due to upload restrictions.5

I. Publishable Summary

Pursuant to 14 C.F.R. §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(h); 14 C.F.R. 43.7; 14 C.F.R. 43.11; 14 C.F.R. 45.11; 14 C.F.R . 45.27; 14 C.F.R. 45.29; 14 C.F.R. 91.7(a); 14 C.F.R. 91.9(b)(2); 14 C.F.R. 91.9(c); 14 C.F.R. 91.103(b)(2); 14 C.F.R. 91.105; 14 C.F.R. 91.109; 14 C.F.R. 91.113(b); 14 C.F.R. 91.119 (c); 14 C.F.R. 91.121; 14 C.F.R. 91.151(a); 14 C.F.R. 91.203(a) and (b); 14 C.F.R. 215; 14 C.F.R. 91.403; 14 C.F.R. 91.405(a); 14 C.F.R. 91.407(a)(1); 14 C.F.R. 409(a)(1) and (2); and 14 C.F.R. 91.417(a) and (b) to operate commercially small unmanned aircraft systems (UAs) ( 1 4.3 lbs . or less).

Approval of the exemption requested by petitioner will allow commercial operation of the CineStar 8 Octocopter for the purposes of aerial photography and videography documenting animal cruelty in Class G airspace nationwide, unless otherwise prescribed by an ATO

- issued COA. The requested exemption should be granted because operation of small UAs weighing no

more than 14.3 lbs. (6.52 kg)

, inclusive of battery and payload , conducted in the strict conditions outlined below, will provide an equivalent level of safety, while still allowing commercial operations. The lightweight aircraft covered by the exemption are far safer than conventional operations conducted with helicopters and fixed

- wing aircraft weighing thousands of pounds and carrying large amounts of h ighly flammable fuel, and operating in close proximity to the ground and people. The seven factors Congress directed the FAA to consider when approving Section 333 exemption petitions

- size, weight, speed, operational capability, proximity to airports, pr oximity to populated areas, and operation within visual line of sight

– each support the request. In particular, the aircraft are small, and will operate at slow speeds, and close to the ground. The substantial increase of safety and decrease of risk to hu man life, coupled with the low risk use of UAs to conduct these operations, weigh heavily in favor of granting the exemption.

II. Petitioner’s Contact Information

Steve Hindi President Showing Animals Respect and Kindness, Inc. PO Box 28 Geneva, IL 60134

Counsel for Petitioner: Jeffrey J. Antonelli Antonelli Law 35 E Wacker Drive, Suite 1875 Chicago, IL 60601 Tel: 312

- 201

- 8310 Email: jeffrey@antonelli

- law.com6

III. Proposed Operations

A. Petitioner

SHARK is a registered 501(c)(3) nonprofit organization dedicated to publicly ousting animal abusers. After recording instances of animal abuse, often with long

- range lenses and night vision technology, SHARK publishes the footage to expose the abusers to the public a t large. SHARK’s main activities include opposing animal cruelty in bullfighting, rodeos, and live pigeon shoots. For more information on SHARK and its stances on animal cruelty, please visit their website at http://www.sharkonline.org/

.

B. The UA

The requested exemption will permit petitioner to operate the CineStar 8 Octocopter . This UA has been previously approved for commercial operation in, among others, the exemption grants identified in Section VII below

. The specific conditions of the proposed exemption that relate t o the characteristics of the UA are numbers 1, 5, and 16

- 20 in Section V below. Each has been adopted or imposed by the FAA in numerous previous grants of Section 333 exemption petitions.

T he CineStar 8 Octocopter have the ability to hover and move in the vertical and horizontal planes simultaneously. The UA will have the following specifications or equivalent:

Airframe Freefly CineStar 8 Octocopter Control System Mikrokopter Flight

- Ctrl V2.1 ME+ACC Upgrade

. Maximum Operating Speed 29 knots Maximum Flight Time 30 minutes Maximum Weight 14.3 lbs. (6.52 kg)

Transmitter Graupner HoTT MX

- 12

. Receiver Graupner Receiver GR

- 12 HoTT

Motor QuadroPower Motor QC03328 Propellers Four APC 13 x 6.5EP and Four APC 13.6.5E Propellers

Data Link XBee Pro 900 RPSMA

Video Link Stinger 5.8GHz Pro 250mw AVD Transmitter

Batteries 4 x 4S 5450 mAh Lithium Polymer Batteries Telemetric Display Telemetric data is displayed through the dedicated Ground Control Station.7

Automatic Return to Home If Tx signal is lost for more than three seconds and the UA is under 65 ft. (20 m.) AGL, the UA will rise to 65 ft. AGL, travel horizontally to the predesignated home spot, then land. If the UA is above 65 ft. AGL , travel horizontally to the predesignated home spot, hover for 15 seconds, then land.

C. The Crew

The crew will consist of a pilot in command (PIC) and a visual observer (VO). The PIC and VO will have been trained in operation of UAs generally and received up

- to

- date information on the UA to be operated pursuant to this grant. The PIC will have, at a m inimum, a sport pilot license and either a third class medical certificate or a U.S. driver’s license.

The specific conditions of the proposed exemption that relate to the training and characteristics of the crew are numbers 3 and 6

- 9 in Section V below. Each has been adopted or imposed by the FAA in numerous previous grants of Section 333 exemption petitions.

For more information regarding the flight crew and t raining, please refer to Exhibit 1: SHARK Pilot Operating Manual, Section 3

– Flight Training.

D. Flight Conditions

The UA will be used for aerial photography and videography documenting animal cruelty in Class G airspace (unless otherwise prescribed by an ATO

- issued COA) under 400 feet above ground level (“AGL”) and under control led conditions over restricted property. Petitioner will work with the local FSDO when planning operations. Petitioner will only operate the UA in visual meteorol ogical conditions (VMC). The UA will at all times be no less than 500 feet below and no less t han 2,000 feet horizontally from a cloud, and petitioner will not conduct operations unless visibility is at least 3 statute miles from the PIC. The flight crew will always make a safety assessment of the risk of every operation, and will only operate when it is determined that no hazards are present.

The specific conditions of the proposed exemption that relate to the fl ight conditions in which the UA will be operated are numbers 2, 4, 16, and 28

- 29 in Section V below. Each has been adopted or imposed b y the FAA in numerous previous grants of Section 333 exemption petitions.

E. Flight Operations

The purpose of the UA flights for which exemption is requested will be for aerial photography and videography documenting animal cruelty . Every UA flight will use at minimum a two person flight crew: a PIC and a VO.

The specific conditions of the proposed exemption that relate to flight operations are numbers 11

- 12, 17

- 25, and 32

- 34 in Section V below. Each has been accepted or imposed by the FAA in numerous previous grants of Section 333 exemption petitions.

For more information regarding flight operations, please refer to the following sections of Exhibit 1: SHARK Pilot Operating Manual:8

Section 1

– Safety Information Section 4

– N ormal Operations Section 5

– Emergencies

IV. Aircraft and Equivalent Level of Safety

Petitioner proposes that the exemption apply to UAs that have the characteristics and that operate with the limitations proposed herein. These limitations provide for a level of safety at least equivalent to or higher than manned aircraft operations under the current regulatory structure. Section V below identifies the limitations and conditions to which petitioner agrees to be bound when conducting commercial operations under a grant of this petition. Appendix A contains a matrix connecting (i) the specific proposed condition with (ii) the FAR provision for which it provides an equivalent level of safety and (iii) one or more recent Section 333 exemption grants in which the FAA recognized this equivalent level of safety.

Approval of the commercial operations outlined in this petition presents no national security issue. The PIC will possess, at minimum, a sport pilot’s certificate, and therefore he or she will have been subject to security screening by the Department of Homeland Security.

V. Proposed Conditions of the Exemption

1. The UA , including battery and technical payload, will weigh no more than approximately 14.3 lbs. (6.52 kg)

.

2. UA operations under this exemption wi ll be limited to conducting operations for the purposes of aerial photography and videography documenting animal cruelty in Class G airspace nationwide, unless otherwise prescribed by an ATO

- issued COA.

3. Flights will be operated within line of sight of a PIC and VO.

4. Flights will be operated at an altitude of no more than 400 feet AGL, as indicated by the procedures specified in the operating documents. All altitudes reported to ATC must be in feet AGL.

5. The UA will not be flown at an indicated airspeed e xceeding 29 knots.

6. Minimum flight crew for each operation will consist of the UA PIC and a VO.

7. The PIC will possess at a minimum sport pilot license and either a third class medical certificate or a U.S. driver’s license.

8. The petitioner will not permit any PIC to operate the UA unless the PIC meets its qualification criteria and demonstrates the ability to safely operate the UA in a man ner consistent with how the UA will be operated under this exemption, including evasive and emergency maneuvers and mai ntaining appropriate distances from persons, vessels, vehicles and structures. PIC qualification flight hours and currency will be logged in a manner consistent with 14 CFR §61.51(b). A record of the PIC training will be documented and made available upon request by the Administrator. Training operations will only be conducted during dedicated training sessions. During training, proficiency, and experience

- building flights, all persons not essential9

for flight operations will be considered nonparticipants, and the PIC will operate the UA with appropriate distance from nonparticipants in accordance with 14 CFR § 91.119.

9. The VO will not perform any other duties beyond assisting the PIC with seeing and avoiding other air traffic and other ground based obstacl es/obstructions, and will not be permitted to operate the camera or other instruments.

10. The PIC will be designated before the flight and will not be allowed to transfer his or her designation for the duration of the flight. The PIC will ensure that the VO can perform the functions prescribed in these conditions and the operating documents.

11. A briefing will be conducted in regard to the planned UA operations prior to each day’s activities. It will be mandatory that all personnel who will be performing duties in connection with the operations be present for this briefing.

12. Prior to each flig ht, the PIC will inspect the UA , including the Ground Control Station, to ensure it is in a condition for safe flight. If the inspection reveals a condition that affec ts t he safe operation of the UA

, the PIC will not operate the UA until the necessary maintenance has been performed and the UA is found to be in a condition for safe flight. All maintenance and alterations will be properly documented in the aircraft records.

13. Petitioner will conduct a functional flight test on any UA that has undergone maintenance or alterations that affect the UA operation or flight characteristics, e.g. replacement of a flight critical component. The PIC who conducts the functional test fligh t will make an entry in the aircraft records.

14. The petitioner will carry out its maintenance, inspections, and record keeping requirements, in accordance with the UA manufacturer’s aircraft/component, maintenance, overhaul, replacement, inspection, and life limit requirements set forth in the operating documents. Maintenance, inspection, alterations, and status of replacement/overhaul component parts will be noted in the aircraft records, including total time in service, description of work accomplished, and the signature of the authorized person returning the UA to service. The authorized person will make an entry in the aircraft record of the corrective action taken against discrepancies discovered between inspections.

15. The UA will be operated within vi sual line of sight (VLOS) of the PIC and VO at all times. This requires the PIC to be able to use human vision unaided by any device other than corrective lenses. PIC and VO will at all times be able to communicate verbally. They will not be permitted to u se electronic messaging or texting to communicate during flight operations.

16. The PIC will not begin 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 prepare to land with at least 25% battery power remaining.

17. Actual total flight time for each operational flight will result in no less than a 25% battery

reserve.

18. The UA will have the capability to abort a flight in case of unexpected obstacles or
emerge ncies.10

19. The UA will be programmed so that if it loses communications or loses its GPS signal, it will return to a pre

- determined location within the planned operating area and land or be recovered in accordance with the operating documents

20. If the UA and its radio control link disconnect during flight, the system’s failsafe protection will be triggered and the multirotor will return to home and land automatically, rather than flying off uncontrollably or landing at an unknown location.

21. The operating docu ments required under 14 CFR §§ 91.9 and 91.203 will be maintained and available to the PIC at the Ground Control Station of the UA any time the UA is operating. These documents will be made available to the Administrator or any law enforcement official
upo n request. If a discrepancy exists between the conditions and limitations in the exemption grant and the procedures outlined in the operating documents, the grant conditions and limitations will take precedence and will be followed. Otherwise, the petition er will follow the procedures outlined in its operating documents. If it updates or revises its operating documents, it will present updated and revised documents to the Administrator upon request. If the petitioner determines that any update or revision w ould affect the basis upon which the FAA granted the exemption, then the Petitioner will petition for an amendment to the grant of exemption.

22. Petitioner will obtain written and/or oral permission from the landowners/authorized agents of the landowners ov er which flights will be conducted.

23. Petitioner will obtain all required permissions and permits from territorial, state, county or city jurisdictions, including local law enforcement, fire, or other appropriate governmental agencies.

24. UA operations will not be conducted during night, as defined in 14 CFR § 1.1. All operations will be conducted under visual meteorological conditions (VMC). Flights will not be conducted under special visual flight rules (SVFR).

25. The petitioner will obtain an Air Traffic O rganization (ATO) issued Certificate of Waiver or Authorization (COA) prior to conducting any operations under the grant of exemption. Petitioner will request a Notice to Airman (NOTAM) not more than 72 hours in advance, but not less than 24 hours prior to the operation. All operations will be conducted in accordance with airspace requirements in the ATO issued COA, including class of airspace, altitude level and potential transponder requirements.

26. The UA will not be operated within 5 nautical miles of a n airport reference point as denoted on a current FAA

- published aeronautical chart unless a letter of agreement with that airport’s management has been obtained, and the operation is conducted in accordance with a NOTAM as required by the operator’s COA. A ny letter of agreement with the airport management will be made available to the Administrator upon request.

27. The UA will 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.

28. All operations shall be conducted in Class G airspace or as otherwise prescribed in an ATO issued COA.11

29. All aircraft operated in accordance with this exemption will be identified by serial number, registered in accordance with 14 CFR part 47, and have id entification (N

- Number) markings in accordance with 14 CFR part 45, Subpart C. Markings will be as large as practicable.

30. Before conducting operations, petitioner will ensure that the radio frequency spectrum used for operation and control of the UA compl ies with the Federal Communications Commission (FCC) or other appropriate government oversight agency requirements.

31. The UA will remain clear and yield the right of way to all manned aviation operations and activities at all times.

32. The UA will not be operated by the PIC from any moving device or vehicle.

33. Petitioner will conduct all flight operations at least 500 feet from all nonparticipating persons, vessels, vehicles, and structures unless one of the following three conditions is met:

a. Barriers or structures are present that sufficiently protect nonpa rticipating persons from the UA and/or debris in the event of an accident. The petitioner will ensure that nonparticipating persons remain under such protection. If a situation arises where nonparticipa ting persons leave such protection and are within 500 feet of the UA, the PIC will ensure that flight operations cease immediately. b. The aircraft is operated near vessels, vehicles or structures where the owner/controller of such vessels, vehicles or struct ures 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.

c. Operations nearer to the PIC, VO, operator trainees or essential persons do not p resent an undue hazard to those persons per § 91.119(a).

34. Petitioner will report any incident, accident, or flight operation that transgresses the lateral or vertical boundaries of the operational area as defined by the applicable COA to the FAA's UAS Inte gration Office (AFS

- 80) within 24 hours. Petitioner will report accidents to the National Transportation Safety Board (NTSB) per instructions contained on the NTSB Web site: www.ntsb.gov

.

VI. Public Interest and Safety

The planned UA use will increase ground safety for aerial photography and videography documenting animal cruelty . This type of data collection has previously been performed by manned aircraft or by individuals on the ground. Both are more time consuming an d are more expensive than using UAs. Use of manned aircraft also poses enhanced risk to the pilot and onboard crew, who would be several hundred feet in the air.

The enhanced safety and reduced environmental impact achieved using UAs and carrying
no pass engers or crew, rather than a manned aircraft of significantly greater mass, carrying crew in addition to flammable fuel, gives the FAA good cause to find that the UA operation enabled by this exemption is in the public interest.

Satisfaction of the crite ria provided in Section 333 of the Reform Act of 2012

– size, weight, speed, operating capabilities, proximity to airports and populated areas and operation within visual line of sight and national security

– provide more than adequate justification for th e12

grant of the requested exemption allowing commerci al operation of petitioner’s UA for aerial photography and videography documenting animal cruelty pursuant to SHARK’s rules of operation.

The FAA has previously determined that using UAs for commercial purposes similar to aerial photography and videography documenting animal cruelty , such as filmography and media production, is in the public interest.

The FAA has determined that using the CineStar family for these similar purposes is in the public inte rest in the following Exemption Nos.: Exemption No. 11251 (filmmaking, cinematography and videography... wildlife and forestry monitoring); Exemption No. 11408 (electronic news gathering); Exemption No. 12092 (operations in the film industry, TV production s...); Exemption No. 12352 (journalism and news gathering); Exemption No. 12473 (aerial photography, motion picture filming, and videography) Exemption No. 12496 (filmmaking, cinematography, videography... wildlife and forestry monitoring); Exemption No. 1 2517 (media production); Exemption No. 12697 (aerial photography, videography, cinematography...) Exemption No. 12831 (filmmaking, cinematography, videography, photography... wildlife and forestry monitoring); and Exemption No. 12872 (motion picture and te levision operations and aerial data collection).13

VII. Regulations from Which Exemption is Requested

Appendix A: FARs as to which SHARK wishes the same determination to be made as has been made previously.

FAR Provision Applicable condition(s) in

Section 5 of petition FAA Exemption Decision

21(h) 1, 2, 3, 4, 5, 16, 25, 28, 29 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 43.7 13, 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 43.11 12 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 45.11 29 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 45.27 29 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 45.29 29 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 1210 7, 12422, 12474

, 13365, 13366 91.7(a) 12 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.9(b)(2) 22 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.9(c) 30 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.103(b)(2) 3, 9, 15, 16, 17, 18, 19, 20 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.105 6 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.109 7, 8 Nos. 11252, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12422, 12474, 13365, 13366 91.113(b) 3, 31 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.119(c ) 4, 33 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 1336614

FAR Provision Applicable condition(s) in

Section 5 of petition FAA Exemption Decision

91.121 4 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.151(a) 16, 17 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.203 (a) and (b) 22 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.215 25, 26 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.403 12, 13, 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.405(a) 12, 13, 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.407(a)(1) 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.409(a)(1) 12, 13, 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.409(a)(2) 12, 13, 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.417(a) 12, 13, 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12068, 12080, 12107, 12422, 12474

, 13365, 13366 91.417(b) 12, 13, 14 Nos. 11252, 11396, 11467, 11745, 11797, 11905, 11945, 12040, 12 068, 12080, 12107, 12422, 12474, 13365, 13366

# en/FlightCtrl_ME_2_5

16

LotharF MikroKopter.de

# Contents

1 Flight Ctrl V2.5...........................................................................................................................................1/12

2 Connections.................................................................................................................................................2/12 2.1 connections Top............................................................................................................................2/12 2.2 connections Bottom......................................................................................................................2/12 2.3 Connecting Molex ........................................................................................................................3/12

3 Connection Diagram...................................................................................................................................4/12 3.1 Connection Serial Port (SV1).......................................................................................................4/12 3.2 Connection SV2............................................................................................................................4/12 3.3 Connection SV3............................................................................................................................5/12 3.4 Connection SV4............................................................................................................................5/12

4 Receiver Connections.................................................................................................................................6/12 4.1 Standard PPM receiver.................................................................................................................6/12 4.2 Spektrum Satellit receiver.............................................................................................................6/12 4.3 Jeti receiver...................................................................................................................................7/12 4.4 HoTT receiver...............................................................................................................................7/12 4.5 Futaba S.Bus receiver...................................................................................................................8/12

5 Circuit diagram...........................................................................................................................................9/12

6 Other..........................................................................................................................................................10/12

7 Settings.......................................................................................................................................................11/12

8 Specifications.............................................................................................................................................12/12 en/FlightCtrl_ME_2_5

i

# 1 Flight Ctrl V2.5

The !Flight-Ctrl V2.5 is now equipped with a new pressure sensor and a more powerful ACC sensor. Now we have a significantly better height control and flights are possible up to 5000mtr. The FlightCtrl V2.5 is shipped with:

already assembled cables for: • a PPM Sum signal receiver • and a Telemetry connection • already installed with the latest software • fully tested for functionality •

INFO: You can use the FlightCtrl V2.5 only with the MikroKopter Software since Version V2.00d !

TIPP: Below you can download a finished setting for the FlightCtrl where all functions are already set.

New thing on the FlightCtrl V2.5:

new Air pressure sensor (with light / wind protection) • new ACC-Sensor • better altitude control • less sensitive to vibrations (all Axis) • Altitude sensor work now up to 5000m • LEDs on the switching outputs • Voltage up to 6S (25V) • Protection resistors to the servo outputs • 400uF for better voltage regulation on the power supply • Note: Not compatible with older firmware versions! •

1/12

# 2 Connections

2.1 connections Top

Molex connector:

GND (FC und Summer) 1. + Buzzer2. I2C Bus (D) 3. I2C Bus (C) 4. +12V (battery voltage) 5.



## 2.2 connections Bottom

10-pol connection strip (for MK-USB or to connect NaviCtrl) 1. 6-pol connection strip (Servo2 / Servo3) 2. 6-pol connection strip (Servo4 / Servo5) 3. 6-pol connection strip (SPI to NaviCtrl) 4. 6-pol connection strip (Servo1 / switching outputs Out1/Out2) 5. Connection Lipo (Plus) (not needed if you use the Molex connection) 6. Connection Lipo (Minus) (not needed if you use the Molex connection) 7. JETI+HOTT - Solder bridge. To send the telemetry data to a HoTT or Jeti transmitter. (Factory default) 8.

2/12Solder pads Tx, Rx, 3V, G (GND), 5V (See "Receiver Connections")

9. Air pressure sensor (with light / wind protection) 10. Connection Buzzer (BUZ-/BUZ+) (not needed if you use the Molex connection) 11. Connection PPM Sum signal receiver (GN=brown, +5=red, PPM=orange) 12. I2C connection (D/C) for BL-Ctrl (not needed if you use the Molex connection) 13. DC/DC converter 5V Recom (supply FlightCtrl) (Factory default) 14. DC/DC converter 5V Recom (supply Servos) (Factory default) 15.



## 2.3 Connecting Molex

suitable Molex connector for "XL" power distributor in the shop suitable Molex cable for "XL" power distributor in the shop

INFO: MK is switched on by connecting in the Lipo. en/FlightCtrl_ME_2_5

3/12

# 3 Connection Diagram

3.1 Connection Serial Port (SV1)

3.2 Connection SV2

Top row (outputs OUT1/OUT2)

Pin1: 100mA switching output NPN Open Collector e.g. for Shuttercable. Programmable in KopterTool with OUT1.

Pin3: +5 Volt

Pin5: 100mA switching output NPN Open Collector e.g. for LEDs. Programmable in KopterTool with OUT2.

Bottom row: Nick servo output

Pin2: Servo1 output (for Nick-Servo camera mount) ( Setting KopterTool )

Pin4: +5 Volt

4/12Pin6: GND / Minus

Note: The servo outputs are activated only after the gyros are calibrated (Throttle up + yaw left).



## 3.3 Connection SV3

Top row (Servo 3)

Pin1: Servo3 output

Pin3: +5 Volt

Pin5: GND / Minus

Bottom row: Roll servo output

Pin2: Servo2 output ( Setting KopterTool )

Pin4: +5 Volt

Pin6: GND / Minus



## 3.4 Connection SV4

Top row (Servo 5)

Pin1: Servo5 output

Pin3: +5 Volt

Pin5: GND / Minus

Bottom row (Servo 4)

Pin2: Servo5 output

Pin4: +5 Volt

Pin6: GND / Minus en/FlightCtrl_ME_2_5

5/12

# 4 Receiver Connections

Please be sure that the correct receiver is set in the settings under "Channels".


## 4.1 Standard PPM receiver

z.B.

DSL4TOP (35/40MHz) • R6107SP Futaba 2,4GHz •

Connection:

PPM - Sum signal
Pad Function cable collor
GN GND/Minus black or brown

+5 Plus 5V red

PPM data line orange

To enlarge - click the image 

## 4.2 Spektrum Satellit receiver

Connection:

Connection to 2nd serial interface
Pad Function cable collor
G GND/Minus black
3V Plus 3V orange

RX data line gray

To enlarge - click the image

Siehe auch: Spektrum

6/12

## 4.3 Jeti receiver

Connection:

PPM - Sum signal + Telemetry connection
Pad Function cable collor
GN GND/Minus black or brown

+5 Plus 5V Rot

PPM data line orange
RX Telemetry connection arbitrarily
JET Solder bridge for Telemetry -

To enlarge - click the image

See also: JetiDuplex


## 4.4 HoTT receiver

The HoTT receiver is also connected to the PPM and the RX pad. To send the telemetry data to the transmitter, the solder bride "JETI+HoTT" have to be closed. More information how to connect, set and use a HoTT Transmitter/receiver can be found here: HoTT

Connection:

PPM - Summensignal + Telemetrieanschluss
Pad Funktion cable collor
GN GND/Minus black or brown

+5 Plus 5V red

PPM Datenleitung orange
RX Telemetrieanschluss arbitrarily
JET Solder bridge for Telemetry -

To enlarge - click the image en/FlightCtrl_ME_2_5

7/12

## 4.5 Futaba S.Bus receiver

You can connect a S.Bus receiver with a Signal-Inverter on the FlightCtrl. Here you can order the needed inverter: Shoplink

Please set the receiver to "normal" mode (The LED of the receiver will be short red if you power up the receiver), do not set to "High-Speed" (Receiver LED is Green/Red (or orange) if you power up the receiver)

Connection:

Connection to 2nd serial interface
Pad Funktion cable collor

5V Plus 5V red
G GND/Minus black or Brown

RX Datenleitung orange

To enlarge - click the image en/FlightCtrl_ME_2_5

8/12

# 5 Circuit diagram

The use of the MikroKopter software is only allowed on original hardware.

9/12

# 6 Other

The Bootloader of the FC2.5 is not for free. • If you have damage the Atmega you can buy a new one include bootloader here: here • Please do not use a ISP programmer to upgrade the FlightCtrl. This can clear the Bootloader. •

10/12

# 7 Settings

Here you can download the latest SW Version and a setting for the FlightCtrl where all is set: Download

.

Here you can see the channel setting:

(To enlarge -> click on image)

11/12

# 8 Specifications

3S-6S • 2 adjustable outputs with LED indicator on FlightCtrl • 5 Servo output • Connections for Set Navigation • Altitude sensor (up to 5000m) •

KategorieMK-Baugruppe/de •

12/12

# en/MKGPS

16

HolgerB MikroKopter.de

# Contents

1 MkGPS.........................................................................................................................................................1/15

2 MKGPS Version 1.0...................................................................................................................................2/15

3 MKGPS Version 2.1...................................................................................................................................3/15 3.1 LEDs.............................................................................................................................................3/15

4 Installation...................................................................................................................................................4/15

5 Initial Functionality tests............................................................................................................................5/15

6 GPS Fix........................................................................................................................................................6/15

7 Improvement of the signal strenght by using the GPS-Shield................................................................7/15

8 Show the MK-GPS Data.............................................................................................................................8/15

9 NMEA..........................................................................................................................................................9/15 9.1 Activate NMEA............................................................................................................................9/15

10 Schematic.................................................................................................................................................10/15

11 Configuration..........................................................................................................................................11/15 11.1 Download..................................................................................................................................11/15 11.2 Settings Store/Re-store (only for Experts)................................................................................11/15 11.2.1 Ublox Datacenter.............................................................................................................11/15 en/MKGPS

i

# 1 MkGPS

The MKGPS is a GPS-receiver for the Mikrokopter.

Together with the NaviControl the following features are possible:

autonomous position hold (Position-Hold or just PH) • fly bach to start point (Coming Home or just CH) • Fly 3D-Waypoints ( Waypoints ) • Logging the flight onto the SD-Card • showing the actual position and speed on the 'OSD'-screen in the KopterTool • showing the actual distance and speed on the JetiBox • Pointing the camera to a specific point: PointOfInterest •

1/15

# 2 MKGPS Version 1.0

the antenna has to be sticked onto the PCB and the conection pin needs to be soldered (only the one pin) •

set the solderjumper to (Passiv) • the LED on top of the module starts lighting after power-up and starts flashing when GPS signal is good •

2/15

# 3 MKGPS Version 2.1

New Chipset: LEA-6S • The Antenna is already mounted and soldered in the MKGPS2.1 • the USB-connector is not used and not assembled • the solderjumper is set to 'Passive' (If there is no solderbridge please set a solderbridge yourself) • the MKGPS 2.1 can be used on NaviControl 1.x and 2.0 since software Version 0.22 •



## 3.1 LEDs

the green LED on the bottom side starts lighting after powrt up and light all the time • The LED on the top-side only lights after the module was initialized from the NC (since NC-Software 0.22) •

the LED on the top-side starts flashing when GPS signal is good •

3/15

# 4 Installation

The Antenna needs to points upwards. There is a small arrow in one of the corners. Please point this towards Motor#1 (front). Install the included cable between MKGPS and NaviCtrl

.
The connecting plug towards NaviCtrl should be inserted into socket NAV (Can be seen in the above picture next to the ublox module). Whilst insertion into the USB socket does not cause any damage, there would be no transfer of GPS data towards the NaviCtrl !

The black area around the antenna patch is also needed for GPS reception and must remain free. • A plastic cover must not directly touch the GPS patch. •

4/15

# 5 Initial Functionality tests

connect NaviCtrl via MKUSB to the PC • with on the MikroKopter • Open the KopterTool - klick onto 'MKGPS'. The parameter GPS-Data Counter should be continually increasing – this indicates that the GPS is correctly connected and data is being correctly read. •

Only MKGPS Version 2.x: after swithing on the MikroKopter the NC initalizes the GPS-Module (after 3-5 second). If the top-LED goes on, the communication to the module is good. •

5/15

# 6 GPS Fix

A GPS Fix is indicated by a flashing LED on the MKGPS.

During the first start-up, the NaviCtrl will build a complete Almanac/Index. This contains satellite positions and paths. A complete cycle to build this Almanac takes 12.5 minutes.

Based on the last known position the fix will from then on be built up much quicker.

If the fix takes a longer time, it could be that the small battery on the GPS board is too weak. The battery is normally charged to about 3V. The battery is always charged when the GPS module is in operation. If the battery voltage is significantly lower than 3.0 V, it can be charged by providing power to the GPS module. One way is through the Naviboard's USB port (with the MKGPS connected). The ribbon cable to the FC should be removed. Another method is to power the MKGPS with 5V on one of the "5V-Pads" on the edge and 0V on ground (GND). Charging takes about 24 hours.

The purpose of the battery is to keep the ephemerides in RAM and the realtime clock running after power off to shorten the re-aquire time.

Information: GPS_Compendium(GPS-X-02007).pdf

6/15

# 7 Improvement of the signal strenght by using the GPS-Shield

http://gallery.mikrokopter.de/main.php/v/tech/GPS_Shield1.jpg.html

This is an enlargement of the ground-plane of the GPS-Receiver to increase the signal strenght. Also it shields the antenna against electro magnetic fields of the other electronics.

See also: GPS-Shield

7/15

# 8 Show the MK-GPS Data

Start KopterTool and swith to MKGPS (connect the MKUSB to the NC)

Now you see GPS-data and signal strenth

Warning: to not do this during flight - the navigation will stop then.

8/15

# 9 NMEA

The NC firmware can provide the NMEA output standarts:

GPGGA • GPRMC •


## 9.1 Activate NMEA

Insert a SD card in the NC • Enter the desired timing in the SETTINGS.INI on the SD-Card in the NC • The NC will start sending NMEA frames with 57600bd on the debug interface • if you want to use it in your camera: the Uart Output is Pin No. 9 •

See also:

http://aprs.gids.nl/nmea/ • http://wiki.mikrokopter.de/en/Firmware-2.02#NMEA_Output_on_the_NC-Interface •

9/15

# 10 Schematic

Schematic in PDF

10/15

# 11 Configuration

Since Navi-Ctrl software version 0.22a the MKGPS is auto-configured during the startup phase.

A manual configuration is not necessary and also not recomended.

the MKGPS 2.1 has a ROM-based LEA-6S chipset. The configuration will be lost after power down

The following information for the manual configuration of the MKGPS is only for experts.

Warning: A misconfiguration can cause a lock out and an access to the MKGPS is not possible anymore. The auto configuration feature will fail also in this case.

To disable the auto-configuration feature the Navi-Ctrl needs a MicroSD-Card in the slot. After startup the software creates a configuration file named SETTINGS.INI on the card. Removing the card from the slot and opening the file with a text editor on the PC the SETTINGS.INI can be modified. The entry GPSAUTOCONFIG = 1 must be changed to GPSAUTOCONFIG = 0 and the card has to be put back into the slot at the Navi-Ctrl permanently.


## 11.1 Download

The gps configuration software can be downloded here U-Blox-Center . The uBlox config file is transferred into the LEA-4H via USB or serial port. 

## 11.2 Settings Store/Re-store (only for Experts)

11.2.1 Ublox Datacenter

The KopterTool has a feature to make a transparent communication for the uBlox-Tool

Simply hold the 'ALT'-Button when klicking onto 'EXIT'

Close the KopterTool and open the Ublox-Tool. select the COM-Port (same as the MKUSB) and change the baudrate to 57600Bd.

Now the behavior of the NaviCtrl is transparent to us. Launch the U-blox Datacenter and open the serial port: •

11/15•

. Select GPS Configuration:

• en/MKGPS

12/15•

. Load the configuration file:

• en/MKGPS

13/15•

. Select the Store configuration checkbox.

• Click File >> GPS: •

•

. Configuration is flashed into the MKGPS: • en/MKGPS

14/15•

ToDo : more to be done here

•

KategorieMK-Baugruppe/en •

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++

en/MKGPS

15/15