February 26th, 2016

Mr. James Williams

Manager, Flight Standards Service

Unmanned Aircraft Systems Integration Office 

Federal Aviation Administration

800 Independence Avenue, SW 

Washington, DC 20591

U.S. Department of Transportation, Docket Operation 

West Building Ground Floor, Room w12-140

1200 New Jersey Avenue, SE 

Washington, DC 20590

Re: Request for exemption from multiple regulatory provisions to allow the use of small 

unmanned aerial systems on land controlled by clients of Elevated Robotic Services Inc.

(ERS) for the purposes of aerial data collection, including aerial imaging and remote 

sensing and surveying. Please note that Elevated Robotic Services Inc. has been 

operating safely in Canada for over 2 years and is currently permitted to operate sUAS 

in Canada under SFOC (Special Flight Operation Certificate) permits.

Dear Mr. Williams:

Elevated Robotic Services Inc. (ERS) respectfully requests an exemption from several 

provisions of Title 14 of the Code of Federal Regulations (C.F.R.) to permit the use of 

small unmanned aerial systems (sUAS) for the purposes of aerial data collection, 

including aerial imaging and remote sensing and surveying. This request is motivated 

primarily by the desire to maximize safety and efficiency in operations. While an 

exemption would not eliminate the current need for some ground surveying to be 

completed, or some aerial imaging to be acquired via manned aircraft, it would allow 

ERS to broadly survey assets and operations with sUAS, resulting in a safer and more 

efficient surveying process. Furthermore, having the ability to operate a sUAS for the 

purposes of aerial imagery will allow our clients to receive a bird’s eye view of their 

current construction projects for the purpose of historical record keeping and construction 

monitoring as well as marketing material. Accordingly, the grant of an exemption is 

consistent with Congress’ intent, reflected in Section 333 of the FAA Modernization and 

Reform Act of 2012 (Modernization Act),1 that safe systems be permitted in the national 

airspace prior to the issuance of final regulations governing general use of these systems.2 

A summary of this request suitable for publication in the Federal Register is provided as 

Appendix A.

Appendix B provides the manufacturers information regarding the design, aircraft 

performance, and fail-safe features. We have provided manufacturer information related 

to operating limitations, normal and emergency procedures, and maintenance and 

inspection procedures. As we add aircraft designs, we will update this appendix 

appropriately.

Appendix C Provides Elevated Robotic Services Inc. Maximum proposed altitudes and 

airspace coordination procedures. 

Appendix D provides Elevated Robotic Services Inc. Project Process and Standard 

Jeremy McCalla

Business Development Manager

Elevated Robotic Services Inc.

119 14ST NW Calgary Alberta T2N 1Z6

+1 403 689 9437

Jeremy@elevatedrs.com
Operating Procedures required for this petition. (Please note a reference is made to 

appendix A in this section. In regards to this section, Appendix A is the contact 

information for the FSDO’s)

1 P.L. 112-95, 126 Stat 11, February 14, 2012.

2 Section 333(b) (2) specifically contemplates that the FAA may issue a certificate of waiver upon a finding that a type 

of UAS, as a result of its size, weight, speed, operational capacity, proximity to airports and populated areas, and 

operations within visual line of sight do not create a hazard to users of the NAS or the public or pose a threat to national 

security.
Background Information

ERS is in the business of obtaining aerial imagery using sUAS for our clients. The aerial 

imagery or data is analyzed and processed into useful information for our clients. ERS 

clients look to us for Safe Operations of sUAS considering our expertise and experience 

operating sUAS in Canada. We have developed specific ERS Safe UAS Operational 

Procedures and are SECOR (Small Employer Certificate of Recognition) a safety 

certification awarded to compliant companies in Alberta Canada1. Increasingly, we have 

clients looking to operate sUAS for the purpose of aerial data collection aerial imagery. 

sUAS Operations:

Aerial Surveying

Aerial Imagery and Videography

As part of this application, ERS is requesting FAA Exemption for sUAS operations 

for aerial data collection for the purpose of aerial surveying and aerial imaging / 

videography. 

As part of this application, ERS is requesting the ability to operate sUAS in the 

entirety of the United States of America for an in definite period under the 

regulations and permissions awarded in the application. 

Regulatory Basis for Exemption Request

In addition to the waiver authority provided in §333 of the Modernization Act, the FAA 

may grant an exemption under 49 U.S.C. §44701(f) if it has determined that such an 

exemption is in the public interest. The FAA has imposed a separate requirement in its 

procedural regulations, providing that the petitioner shall explain why granting the 

exemption would not adversely affect safety or how the exemption would provide at least 

an equivalent level of safety as compliance with the underlying regulation. In this case, 

approval of this exemption would advance the public interest by significantly enhancing 

the safety and efficiency of aerial image collection for the purposes of aerial surveying 

and aerial imagery / videography and by providing the FAA with valuable user 

experience on sUAS in a context with appreciable economic and societal benefits. As

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

sUAS under tightly controlled conditions, thus ensuring that operations will not have an 

adverse impact on safety. The operations manual ERS uses has been used in over 2 years 

of operations in Canada and ERS staff have recorded 300+ hours of sUAS flight times. 

Granting an Exemption is in the Public Interest. The safety and efficiency of Surveying 

and aerial imagery is heavily dependent upon the ability to quickly obtain aerial data in 

less than hospitable environments where ground crews are unable to access terrain easily

and using manned aircraft is cost prohibitive. Using an sUAS for surveying and aerial 

imagery has been proven to be cost effective solution to manned aircraft and provides 

clients with exceptional deliverables. Furthermore, using sUAS in surveying operations 

limits the amount of time ground survey crews are exposed to the environment they are 

working in, limits the amount of piles and unstable terrain survey crews need to walk 

through or over and saves a company time and money. 

As a result, pursuant to federal regulations and company policy, our client’s survey

 

1

https://www.acsa-safety.org/secor.php SECOR is a safety recognition program awarded by the Alberta 

Construction Safety Association. 
crews routinely survey vast amounts of ground and hire manned aircraft to take aerial 

images. At present, this work is done primarily by company personnel in

motor vehicles, on foot, or in specialized equipment. This is often a labor-intensive and 

sometimes arduous job. While our clients do all they can to work as safe as possible, 

there is an irreducible element of risk involved whenever employees are required to go 

out in the field, climb on piles, or work with heavy machinery like a plane or helicopter.

Employees may need to climb over or onto structures, which can be slippery, rough, 

and/or exposed to the elements. Some features, such as gravel piles, are high above the 

ground and often unstable. Equipment moving through survey or construction zones can 

increase risk as well, especially in high-traffic areas. While the use of sUAS for aerial 

data collection does not eliminate these risks entirely (as it is an additive safety

measure), it would reduce the risks to employees by allowing for remote aerial review.

Additionally, the dispersed locations of many of our potential clients – in many instances 

far from sizeable population centers – means that visual inspection in all instances by 

company personnel can be inefficient. Aerial data collection by traditional fixed wing 

aircraft is impractical because the required altitudes for safe flight reduce visibility below 

meaningful levels – it is simply not possible to receive accurate data from such heights. 

Helicopters present better vantage points; however manned helicopters are much costlier, 

subject to human safety and carry highly explosive jet fuel making them impractical for 

deployment. By using sUAS for aerial data collection, ERS will be able to substantially

upgrade its capacity to provide clients with accurate, meaningful, cost effective, and safe 

aerial data. Thus, the use of sUAS has the potential to improve efficiency, resulting in 

faster and safer delivery of goods, energy & natural resources vital to the U.S. economy.
Granting an Exemption will not Adversely Affect Safety

ERS notes that there is no applicable standard for an equivalency determination. Some 

have argued that the appropriate standard is that for model aircraft, noting that their 

operations, if conducted for recreational purposes, would fall completely within the 

allowable operations for model aircraft. We believe it is difficult to argue that there is 

sufficient correlation between model operations controlled by the Academy of Model 

Aeronautics and the ones contemplated by ERS. At the same time, it is clear that 

equivalency cannot be established for traditional, manned civil aircraft because the design 

and use profiles between traditional aircraft and sUAS are simply too different. As such, 

we believe it makes more sense to focus on why the contemplated operations would not 

adversely affect safety, which is all that §11.81(e) requires.

Granting an exemption will not adversely affect safety. ERS is looking to conduct sUAS 

operations over client owned or controlled land, solely during daylight hours, at 

altitudes at or below 400ft AGL, following VFR rules and within VLOS (Visual line of 

Sight). Please see our operations manual in Appendix B which identifies how we 

acquire land owner permission and how we ensure we operate only in safe conditions. 

In general, sUAS operations are intended to be conducted in areas distant from both 

congested areas and airports. Moreover, because of the inherent risks presented by

standard aerial data collection operations, our clients and ERS have already taken steps 

to secure property against unauthorized public access. For example, al lands we operate 

on are privately owned and in general have only one road with a gate accessing the 

lands. The gate may be closed to prevent unwanted members of the public to be 

anywhere near the flight. Again please see appendix B for our sight security procedures.

The nature of operations anticipated by ERS requires that the sUAS be flown at 

relatively low altitudes and relatively low speeds. ERS expects that in most instances, 

the sUAS will be flown at or below 400ft AGL and no more than 87 Knots or (100

miles per hour). Accordingly, the risk of interference with another aircraft is minimal. 

Around controlled aerodromes coordination with the control tower will determine the 

maximum altitude to be flown, with a maximum of 400 ft unless requested otherwise by 

the control tower. The FAA has final say in maximum altitudes and all altitudes will be set 

before with the FAA.

For uncontrolled aerodromes flights will be limited to 300 ft AGL within 3 nm, and 400 ft 

AGL between 3 nm and 5 nm, unless within the approach path. Flights within the 

approach path will be limited to 100 ft AGL within 3 nm, to a maximum of 300 ft AGL 

between 3 nm and 5 nm. Should an aircraft be heard or seen within the 5 nm of the 

aerodrome the UAV operator will return the UAV home to land or land immediately, 

whichever is necessary to give right of way to the aircraft. (Please see Appendix C for 

airspace coordination procedures)

Before flight and every 20 min of flight the UAV operator will broadcast a position update 

to ensure all aircraft in the area are notified. The position update shall follow the format:

“’aerodrome name’ traffic, this is UAV1, operating ‘distance’ nm ‘direction’ of 

‘aerodrome name’ at ‘altitude’ AGL. Any conflict please advise”

example: “Grimshaw airport traffic, this is UAV1 operating at 2 nm SW of Grimshaw 

airport at 200 ft AGL. Any conflict please advise.”
Approval of exemptions allowing commercial operations of sUASs for aerial data 

collection for the purpose of aerial surveying and aerial imagery / videography will 

enhance safety by reducing risk. Conventional operations, using jet or piston power 

aircraft, operate at extremely low altitudes and in extreme proximity to people and 

structures; and present the risks associated with vehicles that weigh in the neighborhood 

of 4,000lbs., carrying large amounts of jet A or other fuel (140 gallons for jet 

helicopters). In contrast, a sUAS weighing fewer than 55 lbs. and powered by batteries 

eliminates virtually all of that risk given the reduced mass and lack of combustible fuel 

carried on board. The sUAS is carried to the work site. The sUAS will carry no 

passengers or crew and, therefore, will not expose them to the risks associated with 

manned aircraft flights.

The operation of small UASs, weighing less than 55 lbs., conducted in the strict 

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

of the exemptions requested herein, including 333 Aircraft Exemption Status exempting 

the applicant from conventional aircraft requirements and allowing commercial

operations. These lightweight aircraft operate at slow speeds, close to the ground, and in 

a controlled environment and, as a result, are far safer than conventional operations 

conducted with turbine helicopters operating in close proximity to the ground and 

people.

The safety of those on the ground is protected by the fact that no one will be allowed into 

the area without the permission of the company. Security will be established for the flight 

area as part of the pre-flight control as outlined in the operations manual. Each individual 

within the secure area will be briefed prior to flight and will consent to being in the area. 

All others will be excluded from the area.

ERS initially intends to use a dedicated staff for sUAS operations. All operations will be 

within visual line-of-sight (i.e., no more than approximately 0.5 miles from the 

manipulator of the controls, or pilot in command (PIC). Each PIC will conduct at least 

three take-offs and landings with the sUAS on which he or she is trained every 90 days. 

ERS’s PIC’s have undertaken CCUVS2(Centre for Canadian Unmanned Vehicle 

Systems) training and are qualified thru a combination	of	aeronautical	knowledge,	UAS	

airmanship	skills,	and	verification	through	testing	of	flight	ability	before	operations	have	

commenced.	Depending on the type of operation, additional ground-based visual 

observers may be employed as well. These observers will be within constant visual line 

of sight and in constant contact with the PIC. The visual observers will assist the PIC in 

avoiding objects near the sUAS. ERS pilots currently have 300+ flight hours of sUAS 

operations in Canada. 

There are no standards for either Private or Commercial sUAS pilot certificates. The safe 

operation and control of the UAS as described in this application does not depend on the 

type of FAA license held by the PIC. Given the restricted and controlled airspace within 

which operations will take place, the key factors needed by the PIC are knowledge of the 

airspace within which the operation will take place and how that airspace fits into the 

National Airspace System (NAS). That knowledge can be and is gained primarily

through ground school and not through flight training in fixed wing or rotor aircraft, nor 

is it dependent on the acquisition of a commercial or private pilot’s certificate. Those 

 

2

http://www.ccuvs.com/
certificates demonstrate knowledge of the factors and skills needed for the safe operation 

of those types of aircraft (fixed wing or rotorcraft). It cannot be assumed that a 

commercial pilot, approved to operate a helicopter or fixed wing aircraft, has the skill or 

ability to safely operate a small unmanned aerial vehicle, operating at 400 AGL or lower, 

within strictly controlled pre-approved airspace. Besides knowledge of airspace 

regulations, dexterity in the control and operation of the sUAS acquired from actual 

operation of the aircraft is the most important factor in establishing an equivalent level of 

safety.

If the PIC has acquired the necessary knowledge of airspace requirements, the relevant 

issues are (1) where the aircraft will be flown, (2) the size of the aircraft relative to what 

is being used today to accomplish the same mission, and (3) what precautions will be 

taken to ensure the safety of those in the area of operation. ERS proposes the aircraft be 

operated within a secure environment; and that no one be allowed to enter the secure 

environment unless they are part of the operation, have been fully briefed of the risks 

prior to operation of the sUAS, and have consented to the risks associated with being in 

the operating area. Should there be a mishap, the sUAS being flown pose significantly

less of a threat than the helicopters and fixed wing aircraft now being employed because 

they are a fraction of the size, carry no flammable fuel, do not carry crew or passengers, 

and pose an infinitesimal risk to others. This is in stark contrast to conventional aircraft 

that are flown to the site, carry explosive fuel, carry passengers and crew, and operate in 

a much larger area.

Minimum requirements for the PIC include:

1) A minimum of 200 flight cycles and 25 hours of total time as a sUAS pilot and 

at least 10 hours logged as a sUAS pilot with a similar sUAS type (single blade or 

multirotor, or fixed wing);

2) A minimum of 5 hours as sUAS pilot with the make and model of sUAS to be 

utilized for operations under the exemption and 3 take offs and landings in the 

preceding 90 days;

3) Have undergone a qualification process as specified in the Flight Operations & 

Procedures Manual consisting of a knowledge & skill test of the aircraft to be 

used.

ERS uses commercially available sUAS Components for sUAS. These sUAS systems 

will be tested for quality & safety in our test facility before being deployed to the field. 

The sUAS is less than 55 lbs. fully loaded, carries neither a pilot nor passenger, and 

operates exclusively within a secured area. We have a routine maintenance schedule to 

verify that the sUAS will remain in safe and operational condition. Please see 

Appendix B, for Specific Types of sUAS.

Notes Regarding: 14 C.F.R. Part 21, Subpart H

In	accordance with the	statutory criteria	provided in	Section 333 of	PL	112---95 in	

reference	to	49	USC	44704,	and	in	consideration	of	the	size,	weight,	speed,	and	limited	

operating	area	associated	with	the	aircraft	and	its	operation,	we	request	that	this				

aircraft	exemption	meets	the	conditions	of	Section	333.	Therefore,	if	granted	Section					

333	relief	of	14	CFR	part	21,	and	any	associated	noise	certification	and	testing	

requirements	of	part	36,	is	not	necessary.
Notes Regarding: 14 C.F.R. § 45.23 (b). Marking of the Aircraft

Given the size of the sUAS, two-inch lettering will be impossible. UAS will	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 will be	as	

large as practicable.

Notes Regarding: 14 CFR § 91.7(a) Civil Aircraft Airworthiness

ERS’s request is based on the fact that no airworthiness certificate will be issued for the 

UAS. ERS’s UAS will not require an airworthiness certificate in accordance with 14 

CFR part 21, Subpart H. Based on the fact that an airworthiness certificate will not be 

issued, exemption from § 91.7(a) is not necessary.

Notes Regarding: 14 CFR § 91.9(b)(2) Civil aircraft flight manual, marking & placard 

Certifications required, the original intent of these regulations was to display an aircraft’s 

airworthiness, certification, and registration documents so they would be easily available 

to inspectors and passengers. Based on the FAA Memorandum subject “Interpretation 

regarding whether certain required documents may be kept at an unmanned aircraft’s 

control station,” dated August 8, 2014, the requested relief from 14 CFR §§ 91.9(b)(2) 

and 91.203(a) and (b) is not necessary.

Notes Regarding: §91.109 Flight instruction; Simulated instrument & certain flight tests 

Small UASs, by their design, do not have fully functional dual controls. Flight control is 

accomplished through the use of a control box that communicates with the aircraft via 

radio communications. Aircraft being considered for use by ERS allow the UAS 

Instructor to place the aircraft into ‘loiter’ mode (fixed altitude stationary hold). In the 

event of the student losing control, the UAS Instructor can quickly and via alternate 

equipment (equipment not in the hands of the student) place the aircraft into a mode that 

then allows the instructor to bring the aircraft back into control and back to the predetermined and/or safe landing location.

ERS does not describe training scenarios in which a dual set of controls would be 

utilized or required, i.e. dual flight instruction, provided by a flight instructor or other 

company-designated individual, that would require that individual to have fully

functioning dual controls. Rather, ERS evaluates the qualification of its PICs based on 

their experience with the UAS to be operated and verifies through testing, in lieu of 

formalized training. As such, ERS does not seek relief from 14 CFR § 91.109.

Notes Regarding § 14 CFR 91.119(b)

Relief from § 14 CFR 91.119(b), operation over congested areas, is not applicable, 

because ERS’s operations will only be conducted within the secured area described 

herein.
ERS Safety Operations & Procedures Overview:

TechnologyConsiderations:

Best-in-class, tried and proven technologies that are in advanced iterations. Software from 

highly-reputable industry partners will include features -

1. Auto descent (landing) if communication signal were to be severed. If the sUAS 

loses communications, the sUAS will have capability to return to a pre-determined 

location within the Security Perimeter andland.

2. Auto descent (landing) if battery were to drop lower than nominal level.

3. Flights will be terminated at 30% battery power reserve.

4. Live video for operator gives real-time positioning feedback. In other words, we 

can monitor the scene from the vehicle's perspective for collision avoidance, and to 

maintain spatial orientation.

5. The sUAS will have the capability to abort a flight in case of unpredicted obstacles 

or emergencies.

6. On-Screen-Display (OSD) contains operating information to ascertain vehicle 

health at all times: speed, altitude, number of GPS satellites (when available), 

heading and voltage.

7. GPS lock supplies for return-to-home (RTH). Should Command and Control (C2) 

link failures occur (highly improbable), vehicle returns automatically to the point of 

launch.

8. Altitude information will be provided to the sUAS pilot via a digitally encoded 

telemetric data feed, which downlinks from the aircraft to a ground-based on-screen 

display. This altitude information will be generated by equipment installed on board 

the aircraft, using GPS triangulation, or digitally encoded barometric altimeter, or 

radio altimeter, or any combination thereof. Prior to each flight, a zero altitude 

initiation point will be established and confirmed for accuracy by the pilot.

Mechanical/Physical:

1. We will fly line-of-sight (LOS) only. The vehicle will always remain in direct LOS 

to the pilot, thus eliminating the concern of signal severance (flying behind 

objects/walls).

2. The sUAS will weigh less than 55 lbs and travel at less than 50 knots.

3. Batteries should far exceed the capacity required for actual flight time.

4. Flights will be operated at an altitude of no more than 400 feet AGL.

5. Fireproof bags for storage and charging of high capacity Lipo batteries on-site.

6. UA operated under this exemption will be marked in accordance with 14 CFR	

part 45 or as otherwise authorized by the FAA.

Personnel:

1. Spotters ensure safe operation and act as a redundant set of eyes for operators 

(pilot, gimbal op, director)

2. Radio spectrum analysis for interference on the frequencies utilized for vehicle 

control/communication.

3. A briefing will be conducted in regard to the planned sUAS operations prior to 

each day’s activities. It will be mandatory that all personnel who will be performing 

duties within the boundaries of the safety perimeter be present for this briefing.

4. The operator will obtain the consent of all persons involved in the sUAS operations
and ensure that only consenting persons will be allowed within 100 feet of the flight 

operations.

5. Observer and pilot will at all times be able to communicate by voice.

6. Written and/or oral permission from the relevant property holders will be obtained.

7. Pilot and observer will have been trained in operation of UAS generally and 

received up-to-date information on the particular UAS to be operated.

Operations:

1. The unmanned aircraft (UA) must weigh less than 55 pounds (25 Kg), 

including energy source(s) and equipment. Operations authorized by this petition 

of exemption are limited to the following aircraft described in Appendix B. 

Proposed operations of any other aircraft will require a new petition or a petition 

amendment to this request.

2. The UAS may not be flown at a ground speed exceeding 87 knots.

3. Flights must be operated at an altitude of no more than 400 feet above ground 

level (AGL), as indicated by the procedures specified in the operator’s manual. 

All altitudes reported to ATC must be in feet AGL.

4. The UA must be operated within visual line of sight (VLOS) of the 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 medical 

certificate.

5. All operations must utilize a visual observer (VO). 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.

6. The operator’s manual included as Appendix C and this petition of exemption 

must be maintained 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 operator’s manual, the conditions and limitations 

herein take precedence and must be followed. Otherwise, the operator must 

follow the procedures as outlined in its operator’s manual.

The operator may update or revise its operator’s manual. 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. If the operator 

determines that any update or revision would affect the basis for which the FAA 

grants this petition for exemption, then the operator must petition for amendment 

to their exemption. The FAA’s UAS Integration Office (AFS-80) may be 

contacted if questions arise regarding updates or revisions to the operator’s 

manual.

7. Prior to each flight the PIC must inspect the UAS 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 aircraft is prohibited from operating until the necessary

maintenance has been performed and the UAS is found to be in a condition for 

safe flight. The Ground Control Station, if utilized, must be included in the 

preflight inspection. All maintenance and alterations must be properly 

documented in the aircraft records.

8. Any UAS 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 in accordance with the operator’s manual. 

The PIC who conducts the functional test flight must make an entry in the UAS 

aircraft records of the flight. The requirements and procedures for a functional test 

flight and aircraft record entry must be added to the operator’s manual.

9. The operator must follow the manufacturer’s UAS aircraft/component, 

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

When unavailable, aircraft maintenance/component/overhaul, replacement, and 

inspection/maintenance requirements must be established and identified in the 

operator’s manual. At a minimum, requirements for the following must be 

included in the operator’s manual:

a. Actuators / Servos;

b. Transmission (single rotor);

c. Powerplant (motors);

d. Propellers;

e. Electronic speed controller;

f. Batteries;

g. Mechanical dynamic components (single rotor);

h. Remote command and control;

i. Ground control station (if used); and

j. Any other components as determined by the operator;

10. Prior to operations conducted for the purpose of aerial data collection and 

imagery, the PIC must have accumulated and logged, in a manner consistent with 

14 CFR § 61.51(b), a minimum of 200 flight cycles and 25 hours of total time as a 

UAS rotorcraft pilot and at least 10 hours logged as a UAS pilot with a similar 

UAS type (single blade, multirotor, or fixed wing). Prior documented flight 

experience that was obtained in compliance with applicable regulations may 

satisfy this requirement. Training, proficiency, and experience-building flights 

can also be conducted under this petition of exemption to accomplish the required 

flight cycles and flight time. During training, proficiency, and experience-building 

flights, all persons not essential for flight operations are considered 

nonparticipants, and the PIC must
operate the UAS with appropriate distance from nonparticipants in accordance 

with 14 CFR § 91.119.

11. Prior to operations conducted for the purpose of aerial data collection and 

imagery, the PIC must have accumulated and logged, in a manner consistent with 

14 CFR § 61.51(b), a minimum of five hours as UAS pilot operating the make 

and model of UAS to be utilized for operations under the exemption and three 

take-offs and three landings in the preceding 90 days. Training, proficiency, 

experience- building, and take-off and landing currency flights can be conducted 

under this petition of exemption to accomplish the required flight time and 90-

day currency. During training, proficiency, experience-building, and take-off and 

landing currency flights all persons not essential for flight operations are 

considered nonparticipants, and the PIC must operate the UA with appropriate 

distance from nonparticipants in accordance with 14 CFR § 91.119.

12. Prior to any flight operations authorized by this petition of exemption, the PIC 

and VO must have successfully completed a qualification process, as outlined in 

the operator’s manual. As this is a requirement stipulated by the operator, the test 

must be developed and implemented by a qualified person designated at the sole 

discretion of the operator. A record of completion of this qualification process 

must be documented and made available to the Administrator upon request.

13. Prior to operations conducted for the purpose of aerial data collection and 

imagery, a flight demonstration, administered by an operator-approved and -

qualified pilot must be successfully completed and documented. This documentation 

must be available for review upon request by the Administrator. Because the 

knowledge and airmanship test qualifications have been developed by the operator, 

and there are no established practical test standards that support a jurisdictional 

FAA FSDO evaluation and approval of company designated examiners, the 

petitioner will conduct these tests in accordance with the operator’smanual.

14. The UAS may not be operated directly over any person, except authorized and 

consenting personnel, below an altitude that is hazardous to persons or property on 

the surface in the event of a UAS failure or emergency.

15. Regarding the distance from participating persons, the operator’s manual has 

safety mitigations for authorized and consenting personnel. At all times, those 

persons must be essential to the operations.

16. Regarding distance from nonparticipating persons, the operator must ensure that

no persons are allowed within 100 feet of the area except those consenting to be 

involved and necessary for the operations. 
17. If the UAS loses communications or loses its GPS signal, the UAS must return to

a pre-determined location within the security perimeter and land or be recovered in

accordance with the operator’smanual.

18. The UAS must abort the flight in the event of unpredicted obstacles or 

emergencies in accordance with the operator’s manual.

19. Each UAS operation must be completed with 30% battery power remaining.

20. The operator must obtain an Air Traffic Organization (ATO) issued Certificate of 

Waiver or Authorization (COA) prior to conducting any operations under this petition 

of exemption. This COA will also require the operator to request a Notice to Airman 

(NOTAM) not more than 72 hours in advance, but not less than 48 hours prior to the 

operation.

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

22. The operator has developed procedures to document and maintain a record of

the UAS maintenance, preventative maintenance, alterations, status of 

replacement/overhaul component parts, and the total time in service of the UAS. 

These procedures are in the operator’smanual.

23. Each UAS operated under this exemption must comply with all manufacturer 

Safety Bulletins.

24. The preflight inspection must account for all discrepancies, i.e. inoperable

components, items, or equipment, not covered in the relevant preflight inspection

sections of the operator’s manual.

25. Before conducting operations, the radio frequency spectrum used for operation 

and control of the UA must comply with the Federal Communications Commission 

(FCC) or other appropriate government oversight agency requirements.

26. At least three days before scheduled operations, the operator of the UAS affected 

by this exemption must submit a written Plan of Activities to the local FSDO with

jurisdiction over the area of proposed operations. The 3-day notification may be 

waived with the concurrence of the FSDO. The plan of activities must include at 

least the following:

a. Dates and times for allflights;

b. Name and phone number of the operator for the UAS

operations conducted under this petition of exemption;

c. Name and phone number of the person responsible for the on-scene 

operation of the UAS;

d. Make, model, and serial or N-number of UAS to beused;

e. Name and certificate number of UAS PICs involved in the operation;

f. A statement that the operator has obtained permission from property 

owners and/or local officials to conduct the operation; the list of those who

gave permission must be made available to the inspector upon request;
g. Signature of exemption-holder or representative; and

h. A description of the flight activity, including maps or diagrams of any area, 

city, town, county, and/or state over which the operation will be conducted

and the altitudes essential to accomplish the operation.

27. The documents required under 14 CFR §§ 91.9 and 91.203 must be available to 

the PIC at the Ground Control Station of the UAS any time the aircraft is operating. 

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

enforcement official uponrequest.

28. The UAS must remain clear and yield the right of way to all other manned 

operations and activities at all times (including, but not limited to, ultralight vehicles, 

parachute activities, parasailing activities, hang gliders,etc.).

29. UAS 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.

30. The UAS may not be operated by the PIC from any moving device or vehicle.

31. The UAS 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.

32. The UAS may not operate in Class B, C, or D airspace without written approval 

from the FAA. The UAS may not operate within 5 nautical miles of the geographic 

center of a non-towered airport 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 NOTAM as required by the operator’s 

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

the Administrator upon request.

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

boundaries of the operational area as defined by the applicable COA 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. Further flight operations may not 

be conducted until the incident, accident, or transgression is reviewed by AFS-80 and 

authorization to resume operations isprovided.
Support for Petition for Exemption

In accordance with the procedural requirements of 14 C.F.R. §11.81, ERS provides the 

following information:

Contact Information:

Jeremy McCalla

Business Development Manager

Elevated Robotic Services Inc.

119 14ST NW Calgary Alberta T2N 1Z6

+1 403 689 9437

Jeremy@Elevatedrs.com

Regulatory Provisions from which ERS seeks an Exemption

ERS believes it may need an exemption from the following provisions to 

conduct the contemplated operations. In some instances, relief is needed because relief 

from another provision renders compliance with the regulation at hand infeasible.

333 Aircraft Exemption Status 

14 C.F.R. §61.113(a) and (b)

14 C.F.R. §91.119(c)

14 C.F.R. §91.121

14 C.F.R. §91.151

14 C.F.R. §91.405(a)

14 C.F.R. §91.407(a)

14 C.F.R. §91.409(a)(1)&(2)

14 C.F.R. §91.417(a)&(b)

ERS believes an exemption is only needed from the above-listed regulatory

provisions. To the extent that the FAA believes that additional relief is required for ERS

to conduct the operations described here, we request an exemption from any such 

regulatory provisions as well.3

3 For example, 14 C.F.R. §91.417(a) imposes certain maintenance record keeping requirements “as 

applicable”. Since none of the underlying requirements (e.g., inspection intervals) can be met and will 

require an exemption, ERS believes a separate exemption should not be required for §91.417(a).
The Extent of Requested Relief and the Reasons Relief is Needed

Section 333 Aircraft Exemption Status:

Section 333 of the Modernization Act authorizes the FAA to exempt aircraft from the 

requirement for an airworthiness certificate based on a consideration of the size, weight, 

speed, operational capability of the particular UAS, as well as its proximity to airports and 

populated areas. An analysis of these criteria demonstrates that the sUAS operated without an 

airworthiness certificate in the areas and under the conditions contemplated by ERS will be 

at least as safe, or safer, than a conventional aircraft (fixed wing or rotorcraft) operating with

an airworthiness certificate without the conditions proposed in this request.

The sUAS is less than 55 lbs. fully loaded, carries neither a pilot nor passenger, and operates 

exclusively within a secured area. Unlike other civil aircraft, operations under this exemption 

will be tightly controlled and monitored by the operator and observer. Operations will be 

conducted in compliance with the FAA and with local public safety requirements to provide 

security for the area of operation. These safety enhancements provide an expanded degree of 

safety to the inspectors over conventional operations. Lastly, application of these same 

criteria demonstrates that there is no credible threat to national security posed by the sUAS, 

due to its size, speed of operation, location of operation, lack of explosive materials and 

inability to carry a substantial externalload.

Given the size and limited operating area associated with the aircraft to be utilized by the 

Applicant, this meets the requirements of an equivalent level of safety under Part 11 and 

Section 333 of the Reform Act. The Federal Aviation Act (49 U.S.C.§44701 (f)) and 

Section 333 of the Reform Act both authorize the FAA to exempt aircraft from the 

requirement for an airworthiness certificate, upon consideration of the size, weight, 

speed, operational capability, and proximity to airports and populated areas of the 

particular sUAS. 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.
14 C.F.R. §61.113(a) and (b)

§61.113 Private pilot privileges and limitations: Pilot in command.

(a) Except as provided in paragraphs (b) through (h) of this section, no person 

who holds a private pilot certificate may act as pilot in command of an aircraft 

that is carrying passengers or property for compensation or hire; nor may that 

person, for compensation or hire, act as pilot in command of an aircraft.

(b) A private pilot may, for compensation or hire, act as pilot in command of 

an aircraft in connection with any business or employment if:

(1) The flight is only incidental to that business or employment; and

(2) The aircraft does not carry passengers or property for compensation or 

hire.

*****

ERS anticipates initially using a cadre of specially trained staff to conduct the 

sUAS operations. While these individuals will not hold commercial pilot licenses, the 

sUAS will not carry property for compensation or hire since they will be used solely to 

acquire data; however, the employees’ operation of the sUAS will not be incidental to 

their employment with ERS, and they will be compensated for such work. Without an 

exemption, the pilot would be required to hold a commercial pilot certificate under 

§61.133. However, the risk associated with the contemplated operations is less than the 

risk posed by a traditional aircraft. The sUAS will fly at altitudes well below the 

permissible limits for other civil aircraft, eliminating the risk to other aircraft, and within 

a geographical envelope under the sole control of ERS clients. Accordingly, the risk 

would be limited to ERS personnel, who will be appropriately outfitted in safety gear, 

and ERS client’s property on the ground. Requiring a commercial pilot certificate would 

provide no appreciable safety benefit and would needlessly impose additional cost on 

ERS. Because the contemplated operations would not comply with §61.113(b)(1) and 

none of the other exceptions to paragraph (a) apply, relief is needed from both paragraphs 

(a) and (b).
14 C.F.R. 91.119(c)

§91.119 Minimum safe altitudes: General.

Except when necessary for takeoff or landing, no person may operate an 

aircraft below the following altitudes:

***

(c) Over other than congested areas. An altitude of 500 feet above the surface, 

except over open water or sparsely populated areas. In those cases, the aircraft 

may not be operated closer than 500 feet to any person, vessel, vehicle, or 

structure.

*****

ERS submits that the only relief it requires from §91.119 is from the minimum 

altitudes listed in paragraph (c). Relief is required from paragraph (c) for fixed wing 

operations because surveying conducted at 500 feet or higher is insufficiently distinct to 

be meaningful. Since operations at this altitude also pose a heightened risk of collision 

with another aircraft, safety can only be assured through the grant of an exemption. The 

anticipated fixed wing and rotocraft operations should be adequately addressed by

paragraph (d) (1). Additionally, relief should not be needed from paragraph (a) because 

an emergency landing of the aircraft due to a power failure will not create an undue 

hazard to persons or property on the surface. As noted in the explanation of why an 

exemption will not adversely affect safety, ERS clients has exclusive use of the land over 

which the sUAS will be operated, and public access is restricted. It also has exclusive 

use of significant portions of land adjacent to the client owned land. ERS’s Clients 

tightly control access to land and have the ability to assure that no individuals 

unassociated with the planned operations are on the affected land. As such, the risk of 

injury is minimal. ERS does not contemplate conducting operations over congested 

areas, so relief is not requested from paragraph (b).

14 C.F.R. 91.121

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

Altitude information will be provided to the sUAS pilot via a digitally encoded telemetric 

data feed, which downlinks from the aircraft to a ground-based on-screen display. This 

altitude information will be generated by equipment installed on board the aircraft, using 

GPS triangulation, or digitally encoded barometric altimeter, or radio altimeter, or any 

combination thereof. Prior to each flight, a zero altitude initiation point will be established 

and confirmed for accuracy by the pilot.
14 C.F.R. 91.151

§91.151 Fuel requirements for flight in VFR conditions.

(a) No person may begin 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.

(b) No person may begin a flight in a rotorcraft 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, to 

fly after that for at least 20 minutes.

*****

Operating the sUAS in a pre-defined area with less than 30 minutes of reserve 

fuel does not raise the type of risk contemplated by §91.151, i.e., that an aircraft could 

run out of fuel in the event it has to be flown to an alternate airport or circle the planned 

airport in the event of unanticipated conditions. ERS does not intend to use the sUAS for 

point-to-point flights and will not operate the sUAS beyond visual line of sight. Nor will 

the sUAS require an airport in order to land. Rather, ERS will operate the sUAS using 

pre-planned flight paths (taking into account weather conditions) designed to allow the 

sUAS to fly to the point of intended landing. As such, there is no need for a time- based 

excess fuel requirement. Rather it should be sufficient to require only as much additional 

excess flight capacity as necessary to safely land the sUAS. We believe that a 30% 

battery reserve is more than sufficient to meet this objective.
14 C.F.R. 91.405(a), 91.407(a) (1), 14 C.F.R. 91.409(a) (1)&(2) and 14 C.F.R. 91.417(a) & (b)

§91.405 Maintenance required.

Each owner or operator of an aircraft –

(a) 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;

*****

§91.407 Operation after maintenance, preventive maintenance, 

rebuilding, or alteration.

(a) No person may operate any aircraft that has undergone maintenance, 

rebuilding, or alteration unless –

(1) It has been approved for return to service by a person authorized under

§43.7 of this chapter;

*****

§91.409 Inspections.

(a) Except as provided in paragraph (c) of this section, no person may operate 

an aircraft unless, within the preceding 12 calendar months, it has had 

(1) An annual inspection in accordance with part 43 of this chapter and has 

been approved for return to service by a person authorized by §43.7 of this 

chapter; or

(2) An inspection for the issuance of an airworthiness certificate in 

accordance with part 21 of this chapter.

*****

§91.417 (a) & (b)

*****

ERS believes that an exemption from these three maintenance requirements is 

appropriate because the FAA has not developed maintenance standards that would allow 

an operator to meet the part 91 maintenance requirements. In particular, there are no 

individuals authorized by the FAA to approve a sUAS for return to service under

§91.407(a) or to conduct the initial airworthiness and annual return to service inspections 

required by §91.409(a). ERS will maintain the aircraft as instructed in the owner’s 

manual and ASTM F2909, where applicable, and will not operate the aircraft until it has 

reasonably determined that any needed repairs have been made. However, because of the 

technical impossibility of meeting the requirements of §§91.405(a), 407(a), 409(a) and 

417(a)&(b), we believe an exemption from these provisions is appropriate.

Please do not hesitate to contact me at the phone number or via the e-mail address 

provided above should you have any questions or concerns.

Respectfully submitted,

Jeremy McCalla

Business Development Manager, Elevated Robotic Services

+1 403 689 9437

jeremy@elevatedrs.com
Appendix A

Summary for Federal Register Publication

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

Federal Register should the FAA determine that publication is needed.

Petitioner: Elevated Robotic Services Inc (ERS)

Sections of 14 C.F.R. Affected:

333 Aircraft Exemption Status

14 C.F.R. §61.113(a) and (b)

14 C.F.R. §91.119(c)

14 C.F.R. §91.121

14 C.F.R. §91.151

14 C.F.R. §91.405(a)

14 C.F.R. §91.407(a)

14 C.F.R. §91.409(a)

14 C.F.R. §91.417(a)&(b)

Description of Relief Sought:

Petitioner seeks relief from the requirements of 333 Aircraft Exemption Status, 14 

C.F.R., 61.113(a)&(b)), 91.119(c), 91.121, 91.151, 91.405(a), 91.407(a), 91.409(a), and

91.417(a)&(b) to conduct sUAS operations over ERS Client’s owned or controlled land, 

solely during daylight hours, for the purposes of aerial data collection, including aerial 

imaging and remote sensing and surveying. In general, sUAS operations are intended to 

be conducted in areas remote from both congested areas and airports. The sUAS is to be 

flown no higher than 400ft AGL. Accordingly, the risk of interference with other aircraft 

is minimal.
Appendix B

UAV TECHNICAL DATA AND MAINTENANCE PROCEDURES INCLUDING FAILSAFES

"A complete description, including all pertinent flight data on the aircraft to be flown."

Describe the UAV and associated systems, including: 

a. The manufacturer, make and model of the UAV system including three view drawings or 

photographs of the aircraft. 

Sensefly eBee Micro RPAS
b. Category (e.g. fixed wing, rotary wing, airship, etc.); 

Fixed wing

c. Composition (e.g. graphite, composites, etc.); 

EPP foam, carbon structure & composite parts

d. Measurements (e.g. wingspan, fuselage length, rotor diameter, etc.); 

Length 51 cm

Wing Span 96 cm

e. Weight (e.g. maximum gross take-off weight, empty weight, payload weight, etc.); 

Flight Weight 670 g

Max Weight 750 g

f. Type of propulsion system (make and model) (e.g. electric, turboprop, turbofan; rear or 

forward mount, etc.); 

Electric, Nominal static thrust: 0.63 kgf (6.2 N)

g. Fuel /Energy system (e.g. battery type, AVGAS, capacity, etc.); 

The propulsion system is comprised of one brushless DC electric motor which has a max output of 

approximately 75 W. This motor is used with a two bladed propeller. It is powered by a 3 cell LithiumPolymer 2200 mAmps battery.

Lithium ion batteries will be transported in the manufacturer’s case. They are not to be left unattended or in 

extreme temperatures. 

When transporting by air special care must be given to declare the batteries and comply with all airline 

protocols for transportation.

h. Method of take-off/ launch (e.g. taxi and take-off, pneumatic catapult, hand-launched, 

etc.); 

The Sensefly eBee Micro RPAS is hand-launched. It must always be launched against the wind in order to 

limit the required ground velocity. The take-off location is automatically selected as the emergency 

landing spot (home waypoint) and will be clear of obstacle in a 40-metre radius.

i. Method of landing / recovery (e.g. approach and runway landing, parachute, belly/skid 

landing, skyhook, etc.); 

By default, the Sensefly eBee Micro RPAS lands by gliding down, circling around a waypoint 

with a minimum radius of 30 metres, until it reaches the ground. Since slight deviations from 

the waypoint trajectory are possible, especially in windy conditions, the landing zone will be 

free of obstacle within a radius of 50 metres.

When there is not enough room for a circular landing or in windy conditions a linear landing 

is preferable.
j. Navigation equipment/capability (e.g. visual, GPS, etc.); 

GPS

k. Electronic surveillance equipment (e.g. transponder (modes, etc.), ADS-B, etc.); 

Software to detect other SenseFly eBee’s in the vacinity.

l. Flight sensors (e.g. barometric altimeter, airspeed indicator, icing detection, etc.); 

Barometric altimeter, airspeed indicator 

m. Redundant systems (e.g. flight controls, avionics, flight termination system, etc.);

The SenseFly eBee is set up to automatically return to home in case of Link Loss, strong winds, low battery, 

poor GPS coverage and will climb in case of detected ground proximity. The flight may be terminated at any 

point by the pilot in command by inputting a land now feature. 

Visual detectability (e.g. lighting (position, anti-collision), high visibility paint scheme, etc.); and

Black with neon yellow trip for high visibility paint scheme.

Flight data on the aircraft to be flown: 

a. Performance (e.g. operating speeds, climb and descent rates, maximum altitude, 

maximum range, maximum endurance, etc.); and 

Max. single flight coverage eBee: 12 km2 (4.6 mi2)

Nominal endurance (flight time) eBee: 50 minutes
Nominal cruise speed 40-90 km/h (11-25 m/s or 25-56 mph)

b. Operating Limitations (e.g. winds (wind shear, gusts), cross-winds, temperatures, day, 

night, icing, etc.). 

Wind resistance up to 45 km/h (12 m/s)

The Control Station, including: 

a. Control method (e.g. manual flight, pre-programmed, tethered, autoland, etc.); 

All command and control is done through the ground station, shown in Figure 4. The pilot can adjust 

Sensefly eBee Micro RPAS course and altitude using Sensefly eBee Micro RPAS specific software installed on 

a laptop. The operator can command waypoint tracking through the ground station map interface. 

Commands are sent to the vehicle via a 2.4 Ghz radio link, which is hardwired to the laptop. The laptop is 

kept in a locked office or locked truck when not in use and is monitored continuously by the operator when 

in use.

b.

c. Control Station Configuration

d. The Sensefly eBee Micro RPAS has a hand held controller to use for manual landings if 

desired. It can also be used in an emergency to take control of the Sensefly eBee Micro 

RPAS should there be a need to take evasive action during flight. It is not recommended 

for normal flight use. The pilot in control will have the hand held controller ready at all 

times to take such action if required.
e. Flight Instrumentation (e.g. attitude, altitude, airspeed, heading, present position, 

navigation etc., and method of displaying the information);

Battery charge, altitude above take-off and above mean sea level, attitude, heading, present 

position, radio link strength, wind speed, flight time are all displayed on the control station 

throughout the flight. 

f. Systems diagnostic and monitoring information (e.g. low battery, fuel status, critical 

systems failure, visual and audio warnings, etc.); 

The drone can encounter two types of error messages while flying: In-flight warnings and Critical 

failures. In-flight warnings typically indicate a dangerous situation such as a low battery, barometer 

malfunction, out of working area or strong winds and typically result in a Security action such as a 

return to the Home waypoint. In-flight warnings appear in blue or yellow in the Flight Monitoring 

tab. Critical failures occur only when the drone’s ability to fly is severely compromised, such as a 

loss of GPS signals or an empty battery. The situation will be displayed in red in the Status section of 

the Flight Monitoring tab. When a critical failure arises, the drone will immediately perform an 

emergency landing.

g. Environmental warnings (e.g. icing, rain, terrain, etc.); 

Strong winds, temperature out of range, terrain detected are all shown as in-flight warnings on the 

control station.

h. Redundant systems (e.g. back-up computer displays, back-up power supply); 

Battery backup is available in the truck or through a portable battery pack that can be connected to 

the ground control station laptop. Two laptops are also standard to have on-site. 
i. Control station power source (e.g. generator, power grid, rechargeable ); 

Laptop battery and recharging station (as above).

j. Equipment in the control station (e.g. lights for night operations, fire extinguisher); and 

Fire extinguisher, first aid kit.

k. Control station security (e.g. capable of being locked). 

When not in use the control station is kept in the work vehicle, which is locked at all times when 

unattended. The control station is not left over night in the work vehicle. 

The Command and Control Links including: 

a. C2/data bands and frequencies (e.g. Very High Frequency (VHF) band, Ku-Band, Ultra 

High Frequency (UHF) Satellite Communication (SATCOM), Geostationary satellites, 

etc.); 

2. Ground modem:

3. • Frequency: 2.4 GHz

4. • Range70: approx. 3 km

5. • Certification: FCC Part 15.247, IC RSS210, CE

6. Remote control:

7. • Frequency: 2.4 GHz

8. • Range: approx. 1 km

9. • Certification: CE, FCC

a. Radio range of the control links; 

See above.

b. Lost Link indications (e.g. "off flags", signal strength indicators, etc.); 

Data link strength is shown on the ground modem and on the ground control station. If link is lost the 

UAV automatically returns home. 

c. Measures for preventing or mitigating radio frequency interference; and 

Radio link quality is monitored before and after take-off as well as throughout the flight.

d. Single or dual redundant control links. 

Single

Voice Communications including: 

a. Primary method of communicating with ATC and other airspace users (e.g. radio relay 

through the air vehicle, fixed based transmitter, etc.); 

Primary method of communicating with ATC and other airspace users will be through the use of an 

aeronautical radio. 

b. Backup communication capability (e.g. landline, cell phone, etc.); 
All ground crew will have their cellular devices on them and have emergency phone numbers already 

preprogrammed into their phones as well as on the emergency checklist.

c. Communication latencies (e.g. able to perform ATC directed actions without delay, etc.); 

and 

The spotter will be in charge of speaking with and communicating with ATC. The spotter will communicate 

with ATC through the use of an aeronautical radio or cellular phone. The spotter will be able to verbally 

communicate ATC commands to the Pilot in Command of the UAV without hesitation. 

d. Communication system used for the pilots, ground support personnel and observers to 

communicate with each other.

Other than traditional verbal communication, all ground crews will have received ground school training 

from CCUVS and will be familiar with necessary hand signals if verbal communication is unavailable. 

On top of using verbal communication and nonverbal communication. Spotters and ground crew may also 

communicate through hand held radios. 

Payload(s) including: 

a. Payload limitations (e.g. impact on flight envelope, how conflicts are managed when 

aircraft and payload operational limits differ, etc.);

Canon point and shoot camera that is specifically fitted to the UAV, preventing any interference with 

aircraft limitations or flight envelope.

b. Dangerous payloads (e.g. pyrotechnics, explosives, lasers, pesticides, etc.); 
No dangerous payloads will be carried.

c. Secondary purposes of payload (e.g. camera controls the flight path of the UAV, etc.); 

and 

None.

d. Increase to crew workload (e.g. pilot operating UAV and payload, etc.). 

None, camera control is set on the ground control station and controlled automatically by the 

autopilot during flight. Any additions images that need to be taken can be set on the control station 

by the UAV operator without increased workload (UAV can be set to hold position if needed).

UAV System Airworthiness and Continuing Airworthiness 

a. UAV system designed to facilitate control of the UAV by the pilot and provide clear 

indications of UAV flight status; 

All command and control is done through the ground station, shown in Figure 4. The pilot can adjust 

Sensefly eBee Micro RPAS course and altitude using Sensefly eBee Micro RPAS specific software installed on 

a laptop. The operator can command waypoint tracking through the ground station map interface. 

Commands are sent to the vehicle via a 2.4 Ghz radio link, which is hardwired to the laptop. The laptop is 

kept in a locked office or locked truck when not in use and is monitored continuously by the operator when 

in use.

a.

b. Control Station Configuration

c. The Sensefly eBee Micro RPAS has a hand held controller to use for manual landings if 

desired. It can also be used in an emergency to take control of the Sensefly eBee Micro 

RPAS should there be a need to take evasive action during flight. It is not recommended 

for normal flight use. The pilot in control will have the hand held controller ready at all 

times to take such action if required.
b. a means for the UAV to remain within its flight envelope; 

The Sense Fly Ebee is equipped with geo fencing. The UAV cannot operate outside of its flight envelope. If 

the UAV reaches the yellow barrier, the UAV will automatically return to the home point and await 

instructions. 

c. redundancy of flight critical components to ensure safe recovery of the UAV (e.g. 

automatic landing/recovery systems, flight termination systems, etc.);

Automatic landing feature in case of emergency. Flight may be terminated at any point by the UAV pilot. The 

UAV will automatically land upon completion of the mission or if out of flight area boundaries, command link 

loss, GPS loss, Radio link loss, or if weather conditions are outside of operational range. 
d. operational history - accident rate as compared to total hours flown by the aircraft type. 

Corrective action taken to prevent future failures; 

All flight files are logged and uploaded onto the Laptop after flight. All flight logs are then simplified and 

reported in ERS UAV log books. 

e. authorizations issued by other civilian or military authorities. 

The senseFly eBee has become the first fixed-wing system to be designated a ‘compliant small UAV’ by 

Transport Canada—a distinction that moves organizations that use this drone a critical step closer to 

achieving Compliant Operator status.

UAV System Maintenance 

The Certificate applicant must describe how the UAV system is being maintained, including: 

a. maintenance and inspection manuals; 

Before every flight, the eBee is inspected for damage. All flight controls and ground stations are inspected to 

ensure proper functionality. 

a) Safety	Checklists

Pre-flight safety checklist

□ The area is clear of all persons not related to the operation of the flight.

□ The flight path does not intersect any government roads.

□ Site reconnaissance has taken place to ensure that no power lines or other infrastructure will intersect the flight path.

□ Clear area of 80m radius is available for landing and takeoff.

□ Cloud ceiling is not less than 1000ft AGL.

□ No precipitation is present or forecast for the duration of the flight.

□ Visibility is not less than 2 Statute miles in all directions.

□ Ground control emergency checklist has been filled out and made available to flight personnel.

□ Authorities have been contacted that flight is about to commence (if applicable). Name________________ Phone__________

Sensefly Aircraft checklist

□ Check the foam central body and wings for cracks or other damage.

□ Verify that the pitot probe is properly attached to the airframe and that the holes in the probe are free of obstructions.

□ Verify that the ground sensor is free of obstructions and that the sensor’s lens is clean.

□ Verify that the wing struts are not split or damaged in any way.

□ Verify that the tubes within the Central Body that hold the wing struts are not cracked or damaged in any way.

□ Verify that the power cables within the battery compartment are well insulated and not damaged.

Sensefly ground control station checklist

□ Wind speed at ground level is less than 25 km/h.

□ GPS position on screen.

□ Data link is strong.

□ Flight deck responsive to pitch/yaw/roll.

□ Wind speed showing on ground control station.

□ Battery is 95% or above.

□ Ground proximity indicator is active.

□ Current status is "ready for takeoff".

□ Current temperature is within operating limits of the aircraft.
b. maintenance and inspection plan/schedule; 

TYPE OF EQUIPMENT TYPE OF INSPECTION SCHEDULE

Company Vehicles Operators checklist daily

Preventative maintenance Every 8000 km / manufacturers 

recommendation

UAV Operators checklist Before every flight

Preventative maintenance Manufacturers recommendation

Complete inspection After a major incident / 

manufacturers recommendation

Repair After a major incident / when failure 

occurs

Batteries Replacement When battery life becomes too low 

or when bulging occurs

GNSS Complete inspection Annually 

c. who established the maintenance schedule (e.g. UAV manufacturer); and 

UAV Manufacturer 

d. the keeping of maintenance records (e.g. aircraft, components, control station, C2 link, 

etc). 

The company safety management system specifies the following maintenance system. Records are 

kept in accordance with the safety management system for all maintenance done.

The following schedule is based on average working conditions. Most of the items listed are 

checked daily during pre-start inspection. However, the time between maintenance will be shortened 

when operating vehicles in the following conditions:

 Extreme hot or cold temperatures

 Extremely dusty areas

 Extremely rough terrain 

Always refer to the Manufacturer’s specifications and adjust the schedule accordingly. 

TYPE OF EQUIPMENT TYPE OF INSPECTION SCHEDULE

Company Vehicles Operators checklist daily

Preventative maintenance Every 8000 km / manufacturers 

recommendation

UAV Operators checklist Before every flight
Preventative maintenance Manufacturers recommendation

Complete inspection After a major incident / 

manufacturers recommendation

Repair After a major incident / when failure 

occurs

Batteries Replacement When battery life becomes too low 

or when bulging occurs

GNSS Complete inspection Annually 

In the field maintenance is recorded in each UAV log book. Minor maintenance is done by the field personnel 

who were trained by ERS. This includes replacing propellers, fixing small chips and tears, tightening screws, 

exchanging for spare parts that are included, software/firmware updates, etc. Major repairs must be taken 

to the reseller or other personnel qualified by manufacturer. This includes crash landings (check of the inside 

components must be done), broken parts that are not included as spare parts, engine mount repair, etc. 

UAV TECHNICAL DATA AND MAINTENANCE PROCEDURES

CAR 8.6 623.65(d)(3)(f)

"A complete description, including all pertinent flight data on the aircraft to be flown."

Notes: The depth of information that needs to be provided varies depending on the size and complexity of the 

UAV system.Where the purpose of the SFOC application involves test bed aircraft where components are 

intended to be swapped, it may be necessary to issue more than one (1) SFOC unless this action does not 

dramatically change the performance characteristics of the UAV system and/or the risks associated with the 

operation.All information provided in the SFOC application shall use standard aviation related units of 

measure (e.g. nautical miles per hour (nm/hr), feet (ft), etc.)

Note: If you wish to apply for the operation of more than one type of UAV, cut and paste the following section 

and fill it in for each individual UAV type requested.

Describe the UAV and associated systems, including: 

n. The manufacturer, make and model of the UAV system including three view drawings or 

photographs of the aircraft. 

DJI Phantom 3 professional
o. Category (e.g. fixed wing, rotary wing, airship, etc.); 

Rotary Wing - Quadcopter

p. Composition (e.g. graphite, composites, etc.); 

Mold injection plastic

q. Measurements (e.g. wingspan, fuselage length, rotor diameter, etc.); 

Dimensions:

 Width: 25 cm 

 Length: 25 cm 
 Top Diameter: 35 cm

 Height: 20 cm

r. Weight (e.g. maximum gross take-off weight, empty weight, payload weight, etc.); 

Weight and payload:

 Helicopter w/battery: 1280 g

 Payload capacity: 1350 g

 Max take-off weight: 2592 g

s. Type of propulsion system (make and model) (e.g. electric, turboprop, turbofan; rear or 

forward mount, etc.); 

Rotor Blades

 Rotor Blade Material: Molded plastic

 Rotor Diameter: 590mm including propellers

 Rotor Covers: Yes

Electric Motors

 Brushless Motors: 4

 Configuration: Direct Drive (One Motor per Rotor)

 Safety Features: GPS position hold, go home & land function or Fully Autonomous, 

 Voltage: 6 V

t. Fuel /Energy system (e.g. battery type, AVGAS, capacity, etc.); 

Rechargeable Helicopter Battery

 Cell Chemistry: Lithium Polymer

 Battery voltage: 80mA @6 V shown in data display on GCS

 Capacity: 4480 mAh

 Recharge Time: Approx. 90 minutes (after typical flight)

Note: where the UAV system uses Lithium batteries or any other type of energy source that is considered a 

Dangerous Good, the applicant must describe in detail the procedures to be used when transporting and 

storing the Dangerous Goods to and from the job site. Refer to Appendix B below for further guidance in 

complying with all of the regulations as set out in the Transportation of Dangerous Goods Act. Please include 

your surface, sea and air transportation procedures as applicable.

Lithium ion batteries will be transported in the manufacturer’s case. They are not to be left unattended or in 

extreme temperatures. 

When transporting by air special care must be given to declare the batteries and comply with all airline 

protocols for transportation

u. Method of take-off/ launch (e.g. taxi and take-off, pneumatic catapult, hand-launched, 

etc.); 

Vertical take-off

v. Method of landing / recovery (e.g. approach and runway landing, parachute, belly/skid 

landing, skyhook, etc.); 
Vertical landing

w. Navigation equipment/capability (e.g. visual, GPS, etc.); 

GPS

 GPS used for: Position Hold, Location & Velocity Data

Position navigation lights

 Green (back) and red (front) navigation lights, or yellow (back) and red (front) navigation lights

x. Electronic surveillance equipment (e.g. transponder (modes, etc.), ADS-B, etc.); 

RF Communications

ii. 2.4GHz – 2.483GHz Data Link 

a. Link Type: Helicopter to Ground & Ground to Helicopter (Two-Way)

b. Frequency: 868 Mhz + 2.4 Ghz

c. Data Link Channel Selection: Automatic (13 Channels)

iii. 2.4GHz Video Link 

a. Range varies with environment (~700 m LOS)

b. Flight sensors (e.g. barometric altimeter, airspeed indicator, icing detection, etc.); 

Barometric altimeter, airspeed indicator, compass, GPS location, Geofencing.

c. Redundant systems (e.g. flight controls, avionics, flight termination system, etc.);

The Phantom will enter failsafe mode when its connection to the remote controller is lost. The flight control 

system will automatically control the aircraft to return to home and land to prevent injury or damage. The 

system will return home at a preset height (default is 20 meters) to avoid collision with objects. It will then 

land vertically in the home location. 

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 3 Assistant software).

(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.
a. The DJI Phantom 3 professional is programmed with an electronic geo-fencing mechanism that 

can be adjusted in altitude and horizontal distance. The DJI Phantom 3 professional can be 

programmed to return to place of origin.

Visual detectability (e.g. lighting (position, anti-collision), high visibility paint scheme, etc.); and 

The Phantom is designed to be detectable by providing a white body with red markings on two arms to 

indicate the phantom is facing forward. Furthermore, the phantom has LED lights which flash green, yellow, 

and red to not only make the phantom visible but also to indicate what flight mode it is in and whether or 

not it has enough satellites to operate in full GPS flight assisted mode. 

Flight data on the aircraft to be flown: 

c. Performance (e.g. operating speeds, climb and descent rates, maximum altitude, 

maximum range, maximum endurance, etc.); and 

AIRCRAFT

Supported Battery DJI 4480 mAh 15.2Vs LIPO4’s

Weight (Battery & Propellers Included) 1280g

Hover Accuracy ( Ready to fly) Vertical: 0.1 – 0.5m; Horizontal: 

1.5m

Max Yaw Angular Velocity 200/s

Max Tiltable Angle 35

Max Ascent / Descent Speed Ascent: 5m/s; Descent: 3m/s

Max Flight Speed Up to 16 m/s

Diagonal Motor-Motor Distance 350mm

GIMBAL

Working Current Static: 750mA; Dynamic: 900mA

Control Accuracy ±0.03°

Controllable Range Pitch : -90°-0°

Maximum Angular Speed Pitch : 90°/s

CAMERA

Operating Environment Temperature 0°C-40°C

Sensor Size 1/2.3"

Effective Pixels 12.4 Megapixels

Resolution 4000×3000

HD recording 1080p30 & 720p

Recording FOV 110° / 85°

REMOTE 

CONTROL

Operating Frequency 2.400 GHz-2.483 GHz

Communication Distance (Open Area) CE Compliance: 400m; FCC 

Compliance: 800m

Receiver Sensitivity (1%PER) -93dBm

Transmitter Power CE Compliance: 25mW; FCC 

Compliance: 100mW

Working Voltage 1.2 A @7.4 V

Battery 6000 mAh LiPo 2S

RANGE

EXTENDER

Operating Frequency 2412-2462MHz

Communication Distance (Open Area) 500-700m

Transmitter Power 20dBm

Power Consumption 2W

d. Operating Limitations (e.g. winds (wind shear, gusts), cross-winds, temperatures, day, 

night, icing, etc.). 

Max Winds: 8m/s

Temperatures: 0°C-40°C
The Control Station, including: 

l. Control method (e.g. manual flight, pre-programmed, tethered, autoland, etc.); 

The DJI Phantom 3 professional can be controlled manually or pre-programmed to fly automatically using 

way point navigation. The GCS includes a hand held controller and a tablet/phone with DJI Phantom 3 

professional flight programming software and payload controls. 

Automated flight can be programmed using the tablet/phone and the DJI go App. Waypoint mapping using 

GPS is programmed on a satellite map and the route is uploaded to the autopilot. Once in autopilot mode 
the Phantom will continue to each way point. At anytime, the pilot can take control of the phantom by 

toggling the S1 switch and taking the phantom out of way point navigation mode. 

The DJI Phantom 3 professional has a hand held controller to use for manual landings and take offs. The 

return to home function on the Phantom will automatically land the Phantom for the pilot. The pilot may at 

any point take over control of the UAV when the return to home function is activated.

A hybrid control method allows the pilot to use a GPS hold to steady and maintain position. It also assists the 

pilot with manual operation as the pilot only needs to use left, right, up, down, forward and back and the 

GPS corrects any variations. This method is safer than full manual flight and is recommended when 

automated flight is not possible. All ERS staff are not permitted to fly in full manual mode and that mode is 

locked in the DJI assistant software. 

Flight Instrumentation (e.g. attitude, altitude, airspeed, heading, present position, navigation etc., and method 

of displaying the information); 

All instrumentation is shown on the control station tablet/phone which is conencted to the DJI go 

App. 

m. Link quality

n. Battery status (also shown with lights on the UAV itself)

o. Orientation

p. Present position on map

q. Altitude

r. Speed 

s. Direction

t. Flight path

Systems diagnostic and monitoring information (e.g. low battery, fuel status, critical systems failure, 

visual and audio warnings, etc.); 

The DJI Phantom 3 professional constantly monitors its battery state. The voltage is displayed on the control 

tablet in the form of a percentage. One short beep is a low battery warning. Critical battery is signaled by a 

long beep and upon the operator failing to take action the UAV will land automatically on the current spot to 

avoid any loss of power on the return flight. The lights on the UAV also show flashing red. All ERS staff are 

instructed to land the DJI in their desired location when the battery percentage reaches 30%. 

Environmental warnings (e.g. icing, rain, terrain, etc.); 

None

Redundant systems (e.g. back-up computer displays, back-up power supply); 

Rechargeable batteries, backups on site. 

Control station power source (e.g. generator, power grid, rechargeable ); 

Rechargeable battery. The work truck is equipped with plugins and an inverter. 

Equipment in the control station (e.g. lights for night operations, fire extinguisher); and 
Fire extinguisher, first aid kit, flashlights and truck lights for lighting in the dark. 

Control station security (e.g. capable of being locked). 

The controller is kept in a locked office or locked truck when not in use. During use the 

controller is used by the operator only. Connection via two controllers is not possible.

The Command and Control Links including: 

C2/data bands and frequencies (e.g. Very High Frequency (VHF) band, Ku-Band, Ultra 

High Frequency (UHF) Satellite Communication (SATCOM), Geostationary satellites, 

etc.); 

The Phantom 3 professional remote controller is a wireless communication device using the 2.400 GHz2.483 GHz frequency band. Remote controller and phantom are paired before delivery. 

Definitions:

Compliance Version: The Phantom 3 professional Remote Controller is compliant with CE and FCC (see the 

FCC ID) regulations.

Radio range of the control links; 

CE compliant devices have an effective communication range of 2000 meters in open spaces due to power 

limitations. (This range can be set to less to ensure VLOS operations) Be sure to watch your fight distance as 

the phantom 3 professional will enter failsafe mode (auto-landing or go home and land) if it flies beyond this 

range.

Lost Link indications (e.g. "off flags", signal strength indicators, etc.); 

Critical issues occur extremely rarely. If GPS is lost and does not re-establish in a predetermined time, the 

system will:

 Automatically switch to manual flight mode and/or,

 Manual landing at its current location is possible if a connection to the Ground (or handheld) control 

station cannot be re-established or,

 Auto-return home for auto landing. 

If the data link is lost the quadcopter will then auto descend at a defined rate of 3 meters per second straight 

down subject to wind, enter fail safe mode, and return to home at 20 meters AGL until it reaches its home 

location and descends for landing.

Measures for preventing or mitigating radio frequency interference; and 

The DJI Phantom 3 professional uses 2.400 GHz-2.483 GHz frequency for the quadcopter control and 

2.4GHZ for the FPV, telemetry and DJI GO App. Since most wireless frequencies operate on 2.4 GHz, the 

phantom 3 professional avoids using the same frequency with their controls as with other wireless 

frequencies and avoids the problem of interference with flight control and command links. 

Single or dual redundant control links. 

 2.400 – 2.483GHz Data Link 
o Link Type: Helicopter to Ground & Ground to Helicopter (Two-Way)

o Frequency: 868 MHz + 2.4 GHz

o Data Link Channel Selection: Automatic (13 Channels)

Voice Communications including: 

e. Primary method of communicating with ATC and other airspace users (e.g. radio relay 

through the air vehicle, fixed based transmitter, etc.); 

Primary method of communicating with ATC and other airspace users will be through the use of an 

aeronautical radio. 

f. Backup communication capability (e.g. landline, cell phone, etc.); 

All ground crew will have their cellular devices on them and have emergency phone numbers already 

preprogrammed into their phones as well as on the emergency checklist.

g. Communication latencies (e.g. able to perform ATC directed actions without delay, etc.); 

and 

The spotter will be in charge of speaking with and communicating with ATC. The spotter will communicate 

with ATC through the use of an aeronautical radio or cellular phone. The spotter will be able to verbally 

communicate ATC commands to the Pilot in Command of the UAV without hesitation. 

h. Communication system used for the pilots, ground support personnel and observers to 

communicate with each other.

Other than traditional verbal communication, all ground crews will have received ground school training 

from CCUVS and will be familiar with necessary hand signals if verbal communication is unavailable. 
On top of using verbal communication and nonverbal communication. Spotters and ground crew may also 

communicate through hand held radios. 

Payload(s) including: 

e. Payload limitations (e.g. impact on flight envelope, how conflicts are managed when 

aircraft and payload operational limits differ, etc.);

As mentioned above, The DJI Phantom 3 professional has an integrated payload which cannot be changed 

and therefore no explosives, lasers, pesticides, pyrotechnics or any other payload may be mounted to the 

UAV.

f. Dangerous payloads (e.g. pyrotechnics, explosives, lasers, pesticides, etc.); 

No dangerous payloads will be carried.

g. Secondary purposes of payload (e.g. camera controls the flight path of the UAV, etc.); 

and 

The camera is unable to control the flight path in the DJI Phantom 3 professional. The camera does offer the 

Pilot in Command a first person view of what the camera is seeing which is displayed in the app displayed on 

the pilot’s cell phone or tablet; however, the camera has no control over where the UAV is flying and 

complete control remains in the hands of the Pilot in Command. Control remains in the hands of the Pilot in 

Command. 

h. Increase to crew workload (e.g. pilot operating UAV and payload, etc.). 

In the case of the DJI Phantom 3 professional, the Pilot in Command has the ability to operate the UAV and 

camera. The camera is operated via the DJI Go APP which comes with the Phantom. The pilot also has the 
This image cannot currently be displayed.

ability to give the mobile device with the app to another person who can then control the camera, allowing 

the pilot to focus on flying. In this case, an additional ground crew member would be needed and utilized as 

a spotter. 

If the pilot in command is operating both the UAV and the camera, they must do so only in GPS mode, 

meaning the UAV will hover in place if no controls are inputted into the controller. If GPS mode is lost, the 

pilot in command will no longer operate the camera and will initiate landing protocols. 

UAV System Airworthiness and Continuing Airworthiness 

Note: Other than small UAVs operated VLOS, TC does not currently define the matters to be taken into 

account for the design of UAVs and associated systems. Use of the term "airworthy" in this document means 

"in a fit and safe state for flight" but may not mean in conformity to a type definition.

The Certificate applicant must describe how they have determined that the aircraft and the system are 

airworthy, including: 

f. UAV system designed to facilitate control of the UAV by the pilot and provide clear 

indications of UAV flight status; 

All command and control is done through the ground station (DJI controller) and the DJI go App which is 

uploaded on the user’s smart phone or tablet 

as shown to the left. The pilot can adjust the 

Phantoms course, altitude, and flight modes 

by inputting controls on the controller. The DJI 

GO App displays the flight mode the Phantom 

is in, the course it is heading and all other 

relevant flight information. The flashing LED 

lights also indicate which flight mode the DJI 

phantom is in. The operator can input way 

points in the DJI go app and can upload those 

way points to the Phantom for way point 

navigation flight. The phantom is controlled via 

the controller 2.400 GHz and 2.483GHz radio 

frequency. The controller is kept in a locked 

office or truck when not in use. 

g. a means for the UAV 

to remain within its flight envelope; 

The DJI Go App has electronic geo fencing as well as no fly zones built into its software. The software does 

not allow the DJI to enter certain areas as well as enter areas the pilot has (fenced off). No fly zones are 

updates with every new software installment. The DJI Go App also allows the pilot to set maximum altitudes, 

maximum speeds, and maximum distances away from the controller the Phantom is able to fly. 
h. redundancy of flight critical components to ensure safe recovery of the UAV (e.g. 

automatic landing/recovery systems, flight termination systems, etc.);

Automatic landing feature in case of emergency. Flight may be terminated at any point by the UAV pilot and 

landed manually in a safe location or initiate the return to home feature. The UAV will automatically begin to 

return to home if there is a command link loss, GPS loss, or radio link loss. 

i. operational history - accident rate as compared to total hours flown by the aircraft type.

Corrective action taken to prevent future failures; 

All flight files are logged and uploaded onto the Laptop after flight. All flight logs are then simplified and 

reported in ERS UAV log books. 

j. authorizations issued by other civilian or military authorities. 

Worldwide leader in drone manufacturing. 
UAV System Maintenance 

The Certificate applicant must describe how the UAV system is being maintained, including: 

a. maintenance and inspection manuals; 

Before every flight the Phantom is inspected for damage and the ground control stations are inspected for 

functionality. These inspections are logged and stored. 

Pre-flight safety checklist

□ The area is clear of all persons not related to the operation of the flight.

□ The flight path does not intersect any government roads.

□ Site reconnaissance has taken place to ensure that no power lines or other infrastructure will intersect the flight path.

□ Clear area of 80m radius is available for landing and takeoff.

□ Cloud ceiling is not less than 1000ft AGL.

□ No precipitation is present or forecast for the duration of the flight.

□ Visibility is not less than 2 Statute miles in all directions.

□ Ground control emergency checklist has been filled out and made available to flight personnel.

□ Authorities have been contacted that flight is about to commence (if applicable). Name________________ Phone__________

DJI Aircraft checklist

□ Body and landing gear damage free and secured.

□ Rotor struts and blades free of damage, attached and secured.

□ Gimbal and sensor attached, on and full range of motion. 

□ Batteries attached and secure. Indicator shows full battery.

□ Aircraft and gimbal responsive to full range of motion. 

□ Wiring insulated, attached and secured by cap. 

DJI Ground control station checklist

□ Sufficient satellites for take-off (>6).

□ Wind speed at ground level is less than 25 km/h.

□ Compass calibration is valid. If not, calibrate compass according to manufacturer’s directions.

□ Wind speed showing on ground control station.

□ Batteries are 95% or above.

□ Ground proximity indicator is active.

□ Current status is "ready for takeoff".

□ Current temperature is within operating limits of the aircraft.

b. maintenance and inspection plan/schedule; 

k. Always refer to the Manufacturer’s specifications and adjust the 

schedule accordingly. 

TYPE OF EQUIPMENT TYPE OF INSPECTION SCHEDULE

Company Vehicles Operators checklist daily

Preventative maintenance Every 8000 km / manufacturers 

recommendation

UAV Operators checklist Before every flight

Preventative maintenance Manufacturers recommendation

Complete inspection After a major incident / 

manufacturers recommendation

Repair After a major incident / when failure 

occurs

Batteries Replacement When battery life becomes too low 
or when bulging occurs

GNSS Complete inspection Annually 

a. who established the maintenance schedule (e.g. UAV manufacturer); and 

UAV Manufacturer 

b. the keeping of maintenance records (e.g. aircraft, components, control station, C2 link, 

etc). 

The company safety management system specifies the following maintenance system. Records are 

kept in accordance with the safety management system for all maintenance done.

The following schedule is based on average working conditions. Most of the items listed are 

checked daily during pre-start inspection. However, the time between maintenance will be shortened 

when operating vehicles in the following conditions:

 Extreme hot or cold temperatures

 Extremely dusty areas

 Extremely rough terrain 

Always refer to the Manufacturer’s specifications and adjust the schedule accordingly. 

TYPE OF EQUIPMENT TYPE OF INSPECTION SCHEDULE

Company Vehicles Operators checklist daily

Preventative maintenance Every 8000 km / manufacturers 

recommendation

UAV Operators checklist Before every flight

Preventative maintenance Manufacturers recommendation

Complete inspection After a major incident / 

manufacturers recommendation

Repair After a major incident / when failure 

occurs

Batteries Replacement When battery life becomes too low 

or when bulging occurs

GNSS Complete inspection Annually 

In the field maintenance is recorded in each UAV log book. Minor maintenance is done by the field personnel 

who were trained by ERS. This includes replacing propellers, fixing small chips and tears, tightening screws, 

exchanging for spare parts that are included, software/firmware updates, etc. Major repairs must be taken 

to the reseller or other personnel qualified by manufacturer. This includes crash landings (check of the inside 

components must be done), broken parts that are not included as spare parts, engine mount repair, etc. 

COA

A Certificate of Authorization must be obtained before beginning operations. A COA is very similar to an 
SFOC in Canada. In order to receive a Certificate of Authorization, the applicant must first posses a 333 

exemption file number and register all UAS with the FAA. Once these actions are completed, ERS must 

ensure a COA is issued for operations. For general information on COAs, please contact 9-AJV-115-

UASOrganization@faa.gov. Please Click Here to view a sample COA application. Please Click Here to file for 

a COA. A COA must be issued before operations may be conducted. As soon as this exemption is applied for 

Elevated Robotics will begin the process of obtaining a COA. 

Appendix C

Maximum Altitudes and Airspace Coordination

i. The altitudes and routes to be used on the approach and departure to and from the 

area where the operation will be carried out - CAR 8.10 623.65(d)(3)(j) 

Altitudes and routes will be determined on site via the UAV operator and ground supervisor to ensure 

maximum safety. Project processes for specific air space management will be followed to ensure safe 

operations. 

Unless otherwise stated during communications with Nav Canada, or any other applicable persons involved in 

the filing of NOTAMS, max altitude to be flown will be 400ft AGL. Each airspace will have the maximum 

altitude to be flown in listed below. 

ii. The location and height above ground of all obstacles in the approach and departure 

path to the areas where the operation will be carried out

Altitudes and routes will be determined on site via the UAV operator and ground supervisor to ensure 

maximum safety. Project processes will be followed to ensure safe operations. UAV pilot and ground 

supervisor will ensure a minimum of 20M (60 foot) buffer zone between the UAV and any ground 

obstacles while on approach or departure. Project process ensures landing and takeoff zones are 

clear of obstacles. 

Max altitude will be 400 ft. AGL.

iii. The altitudes and routes to be used while carrying out the operation

Altitudes will be limited to 400 ft AGL. NOTAMS will be filed and procedures for safe operations on top 

of all existing procedures will be discussed with Nav Canada. 

Around controlled aerodromes coordination with the control tower will determine the maximum altitude 

to be flown, with a maximum of 400 ft unless requested otherwise by the control tower. Nav Canada 

has final say in maximum altitudes and all altitudes will be set before with Nav Canada.

For uncontrolled aerodromes flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 

3 nm and 5 nm, unless within the approach path. Flights within the approach path will be limited to 

100 ft AGL within 3 nm, to a maximum of 300 ft AGL between 3 nm and 5 nm. Should an aircraft be 

heard or seen within the 5 nm of the aerodrome the UAV operator will return the UAV home to land or 

land immediately, whichever is necessary to give right of way to the aircraft. 

Before flight and every 20 min of flight the UAV operator will broadcast a position update to ensure all 

aircraft in the area are notified. The position update shall follow the format:

“’aerodrome name’ traffic, this is UAV1, operating ‘distance’ nm ‘direction’ of ‘aerodrome name’ at 

‘altitude’ AGL. Any conflict please advise”

example: “CSA3 Sturgeon Community Hospital Heliport traffic, this is UAV1 operating at 2 nm SW of 

Sturgeon Community Hospital Heliport airport at 200 ft AGL. Any conflict please advise.” 

Please Note: ColasCanada understands the general rule Transport Canada applies to operations within 5nm 

of any aerodrome. However, ColasCanada feels we have the training and coordination procedures to operate 

at higher altitudes than 100ft AGL within 5nm of any aerodrome. ColasCanada will be able to use their 

coordination procedures to ensure safe operations within 5nm of any aerodrome. ColasCanada will ensure a 
good working relationship with NAV Canada as well as private operators of aerodromes within 5nm of 

operaitons. Please see the proposed max altitudes within 5nm of any aerodrome as listed in each airspace to 

be operated in. It is the ultimate decision of Transport Canada to limit altitudes and ColasCanada will comply 

with any decision Transport Canada makes in regards to maximum altitudes in airspaces and will comply with 

any stipulations outlined in this SFOC. 

Note: As a general rule, flights within 5nm of any aerodrome will be limited to 100 

feet AGL. Flights outside of 5nm will normally only be permitted as high as 400 feet 

AGL. Flights higher than these altitudes will require the applicant to demonstrate to 

the Minister how the additional safety risks of higher flights will be mitigated.

AIRSPACE COORDINATION PROCEDURES (see Appendix A below)

Please specify your proposed coordination and operating procedures for each type of airspace listed 

below:

Note: For site specific applications, identify the type of airspace you plan to operate in and the 

specific procedures you intend to follow. For standing SFOC’s (blanket geographic areas) you must 

identify the types of airspace and your procedures for operations within each type. If you do not 

intend to work in a particular type of airspace, please indicate this in the space provided. For all 

applications, indicate the maximum proposed altitude and specific contact numbers in the case of site 

specific applications. For standing areas, include the method that will be used to determine who to 

contact for coordination. 

i. Class A and Class B airspace

Not to be operated in

iii. General Built-up areas procedures

a. The UAV shall not be operated within any built-up or populated area unless written 

permission from the local governing authorities has been given’

b. The UAV shall not be operated within 100 feet horizontally of any person, structure or 

vehicle not directly associated with the operation of the UAV unless written permission 

has been obtained;

c. The UAV shall not be operated within 100 feet horizontally of any public roadway, right of 

way, or public access route unless a security plan is in place that is capable of precluding 

public access or incursion within 100 feet horizontally of the UAV;

d. The UAV shall not be operated within 500 feet horizontally of any public owned areas 

including parks, playgrounds or other public spaces without a security plan in place that is 

capable of precluding public access or incursion within 500 feet horizontally of the UAV;

e. The UAV shall not be operated within 500 feet horizontally of any schools during normal 

school hours or whenever the school is occupied; and

f. The UAV operation shall be terminated immediately if a risk of public incursion of the 

operation area is evident or likely to occur.

iv. Class G airspace (outside of built-up areas and outside of 5nm from any aerodromes)

Maximum Altitude for class G airspace (outside of built-up areas and outside of 5nm from any aerodromes) 

will be 400ft AGL. 

A. Mission Planning 

During the following steps are taken:

1. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.
2. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

3. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

4. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

5. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

6. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

7. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

8. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

9. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

10. ERS staff have proper PPE for the operations area

11. Emergency procedures are filled out with necessary data

12. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission” folder

B. Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

1. Check that NOTAM was issued as required by checking HERE

2. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

3. Tailgate meeting 

4. Emergency procedures reviewed

5. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

6. Ensure proper site security has been completed

7. ERS staff have proper PPE
8. Complete safety checks

9. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

10. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

11. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

12. Flights conducted according to flight parameters

13. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

14. Other data (GPS, etc) collected

1. Flight	Parameters

All UAS operations will follow these conditions: 

v. Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, 

unless within the approach path. Flights within the approach path will be limited to 100 ft 

AGL within 3 nm, to a maximum of 300 ft AGL between 3 nm and 5 nm. 

vi. Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will 

return the UAV home to land or land immediately, whichever is necessary to give right of 

way to the aircraft. 

vii. Will comply with Aeronautics Act and FARs.

viii. No one suspected of or being fatigued shall operate the UAV.

ix. No one shall operate the UAV within 8 hours of consuming alcohol.

x. UAV shall give way to manned aircraft.

xi. UAV personnel will be fully trained in operations, emergencies and recovery and will be over 

the age of 18.

xii. Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the 

flight. 

xiii. Flights will be conducted according to the roles and responsibilities outlined by ERS 

management. 

xiv. Adequate liability insurance will be maintained.

xv. UAV will remain within visual line of sight of pilot and clear of cloud. 

xvi. An observer will be appointed for all flights. They will maintain a lookout for anything 

approaching the operating area or airspace and will inform UAV operator immediately.

xvii. Emergency procedures will be available and filled in for all flights, including FSDO shift 

manager and local airports (see checklist attached).

xviii. An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

xix. Any occurrences shall be reported by the following day:

a. Flights out of bounds.

b. Unintended contact with persons, structures, vehicles or wildlife.

c. Any injury as a result of the operation.

xx. SFOC will be known to all personnel involved in operations. 

xxi. All UAV system equipment required for safe flight operations must be serviceable.

xxii. Operations will be documented. 

xxiii. VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

xxiv. Class G airspace (within built-up areas)
Maximum Altitude for class G airspace (within built-up areas) will be 400ft AGL.

C. Mission Planning 

During the following steps are taken:

13. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

14. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

15. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

16. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

17. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

18. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

19. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

20. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

21. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

22. ERS staff have proper PPE for the operations area

23. Emergency procedures are filled out with necessary data

24. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission” folder

D. Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

15. Check that NOTAM was issued as required by checking HERE

16. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +
b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

17. Tailgate meeting 

18. Emergency procedures reviewed

19. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

20. Ensure proper site security has been completed

21. ERS staff have proper PPE

22. Complete safety checks

23. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

24. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

25. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

26. Flights conducted according to flight parameters

27. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

28. Other data (GPS, etc) collected

1. Flight	Parameters

All UAS operations will follow these conditions: 

 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.

 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including FSDO shift manager and 

local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.

o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 
 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

xxv. Class G airspace (within 5nm of an aerodrome)

Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. All flights in this airspace will be coordinated 

with Nav Canada as per this document to ensure safe operations. 

E. Mission Planning 

During the following steps are taken:

1. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

2. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

3. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

4. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

5. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

6. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

7. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

8. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

9. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

10. ERS staff have proper PPE for the operations area

11. Emergency procedures are filled out with necessary data
All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission” folder

1. NOTAMs

A NOTAM shall be filed at least 48 hours in advance for any operation under this Exemption that is within 

controlled airspace and/or within five (5) nautical miles of an uncontrolled aerodrome in either controlled or 

uncontrolled airspace unless directed otherwise by the Air Traffic Service Unit Manager or the Military Air 

Traffic Service Unit responsible for that airspace.

NOTAMs are issued by calling AFSS (1-877-4-US-NTMS) for the region being operated in. The following are 

examples of information that the UAV operator should provide to the applicable ATS unit: 

 Intended date, time and duration of the operation; 

 Type of UAV including its size, weight and colour; 

 Lat and long of the operation area (optional but preferred: include an image of the area);

 Vertical and horizontal boundaries of the area of operation; 

 Contact name and number for the UAV operator; 

The following units and measurements are acceptable:

 All distances and units of measure for aviation purposes shall be listed and communicated in NM, 

Nautical Miles, feet or inches. Below two nautical miles, distances from aerodromes may be 

identified with decimals. Distances below one nautical mile may be identified in feet or in nautical 

mile (1 NM=1.151 miles, 1 NM=1.852 km, 1KM = 0.54 NM).

 Distances should be measured from the aerodrome facility reference point, as listed in the CFS (see 

9.2.1), or from a listed Aviation Navigation facility such as a VOR or NDB.

 All altitudes and elevation measurements for aviation purposes shall be listed and communicated in 

feet. (1 meter = 3.281 feet). Specify feet AGL (above ground level) or ASL (above sea level).

 All position locations for aviation purposes shall be expressed in the following formats’:
o For Planning and NOTAMs; in non-GPS Lat/Long, as expressed in Deg.Min.Sec. (eg; N53 18 36 

W113 34 46). 

o For Emergency coordination with ATS units, in a position report expressed by distance in NM 

and direction in compass rose points from the nearest published Aerodrome/Heliport. (eg; 

4.5NM E-N-E of CYQL)

The date the NOTAM was filed should be noted in the “Mission” folder.

 Cancelling a NOTAM:

o If you are unable to operate and need to cancel a NOTAM please contact AFSS (1-877-4-USNTMS) with coordinates of NOTAM and NOTAM reference number. If NOTAM is ongoing, 

please cancel the NOTAM for the days you will not be operating only. 

F. Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

1. Check that NOTAM was issued as required by checking HERE

2. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

3. Tailgate meeting 

4. Emergency procedures reviewed

5. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

6. Ensure proper site security has been completed

7. ERS staff have proper PPE

8. Complete safety checks

9. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

10. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

11. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

12. Flights conducted according to flight parameters

13. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

14. Other data (GPS, etc) collected

1. Flight	Parameters

All UAS operations will follow these conditions: 

 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.
 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including Nav Canada shift 

manager and local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.

o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 

 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

xxvi. Class G airspace (within 1nm of an aerodrome)

Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. All flights in this airspace will be coordinated 

with Nav Canada as per this document to ensure safe operations. 

G. Mission Planning 

During the following steps are taken:

25. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

26. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

27. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

28. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

29. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

30. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 
b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

31. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

32. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

33. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

34. ERS staff have proper PPE for the operations area

35. Emergency procedures are filled out with necessary data

36. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission folder” 

NOTAMs

A NOTAM shall be filed at least 48 hours in advance for any operation under this Exemption that is within 

controlled airspace and/or within five (5) nautical miles of an uncontrolled aerodrome in either controlled or 

uncontrolled airspace unless directed otherwise by the Air Traffic Service Unit Manager or the Military Air 

Traffic Service Unit responsible for that airspace.

NOTAMs are issued by calling AFSS (1-877-4-US-NTMS) for the region being operated in. The following are 

examples of information that the UAV operator should provide to the applicable ATS unit: 

 Intended date, time and duration of the operation; 

 Type of UAV including its size, weight and colour; 

 Lat and long of the operation area (optional but preferred: include an image of the area);

 Vertical and horizontal boundaries of the area of operation; 

 Contact name and number for the UAV operator; 
The following units and measurements are acceptable:

 All distances and units of measure for aviation purposes shall be listed and communicated in NM, 

Nautical Miles, feet or inches. Below two nautical miles, distances from aerodromes may be 

identified with decimals. Distances below one nautical mile may be identified in feet or in nautical 

mile (1 NM=1.151 miles, 1 NM=1.852 km, 1KM = 0.54 NM).

 Distances should be measured from the aerodrome facility reference point, as listed in the CFS (see 

9.2.1), or from a listed Aviation Navigation facility such as a VOR or NDB.

 All altitudes and elevation measurements for aviation purposes shall be listed and communicated in 

feet. (1 meter = 3.281 feet). Specify feet AGL (above ground level) or ASL (above sea level).

 All position locations for aviation purposes shall be expressed in the following formats’:

o For Planning and NOTAMs; in non-GPS Lat/Long, as expressed in Deg.Min.Sec. (eg; N53 18 36 

W113 34 46). 

o For Emergency coordination with ATS units, in a position report expressed by distance in NM 

and direction in compass rose points from the nearest published Aerodrome/Heliport. (eg; 

4.5NM E-N-E of CYQL)

The date the NOTAM was filed should be noted in the “Mission” folder.

 Cancelling a NOTAM:

o If you are unable to operate and need to cancel a NOTAM please contact AFSS (1-877-4-USNTMS) with coordinates of NOTAM and NOTAM reference number. If NOTAM is ongoing, 

please cancel the NOTAM for the days you will not be operating only. 

Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

29. Check that NOTAM was issued as required by checking HERE
30. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

31. Tailgate meeting 

32. Emergency procedures reviewed

33. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

34. Ensure proper site security has been completed

35. ERS staff have proper PPE

36. Complete safety checks

37. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

38. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

39. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

40. Flights conducted according to flight parameters

41. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

42. Other data (GPS, etc) collected

Flight	Parameters

All UAS operations will follow these conditions: 

 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.

 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including FSDO shift manager and 

local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.
o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 

 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

xxvii. Class F airspace (CYA)

Not to be operated in

xxviii. Class F airspace (CYR)

Not to be operated in

xxix. Any Class of Department of National Defense (DOD) controlled airspace

Not to Be operated in

Note: The Certificate applicant is responsible for working with appropriate military authorities 

to gain access to the Base/Range airspace and prepare their operating procedures to the 

satisfaction of the applicable Range Control Officer and/or the Base/Wing Commander. 

SFOC’s that permit operations within any military airspace will be contingent on the approval 

of DND.

DND requires that the Certificate applicant provide both their approved SFOC and 

Base/Range authorization letter to 1 CAD for verification a minimum of 30 days prior to the 

intended date of operations. Upon confirmation of a valid SFOC and applicable Canadian 

Forces Base range access approval, 1 CAD will issue a letter of endorsement

xxx. Class F airspace (CYD)

Not to be operated in

ii. Class C Tower control zone 

Operations will be limited to 400ft AGL unless otherwise stated by Air traffic service manager in charge of 

airspace to be coordinated in or by Nav Canada as per NOTAM requirements. 

H. Mission Planning 

During the following steps are taken:

37. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

38. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

39. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

40. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

41. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.
42. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

43. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

44. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

45. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

46. ERS staff have proper PPE for the operations area

47. Emergency procedures are filled out with necessary data

48. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission folder” 

NOTAMs

A NOTAM shall be filed at least 48 hours in advance for any operation under this Exemption that is within 

controlled airspace and/or within five (5) nautical miles of an uncontrolled aerodrome in either controlled or 

uncontrolled airspace unless directed otherwise by the Air Traffic Service Unit Manager or the Military Air 

Traffic Service Unit responsible for that airspace.

NOTAMs are issued by calling AFSS (1-877-4-US-NTMS) for the region being operated in. The following are 

examples of information that the UAV operator should provide to the applicable ATS unit: 

 Intended date, time and duration of the operation; 

 Type of UAV including its size, weight and colour; 

 Lat and long of the operation area (optional but preferred: include an image of the area);

 Vertical and horizontal boundaries of the area of operation; 

 Contact name and number for the UAV operator; 
The following units and measurements are acceptable:

 All distances and units of measure for aviation purposes shall be listed and communicated in NM, 

Nautical Miles, feet or inches. Below two nautical miles, distances from aerodromes may be 

identified with decimals. Distances below one nautical mile may be identified in feet or in nautical 

mile (1 NM=1.151 miles, 1 NM=1.852 km, 1KM = 0.54 NM).

 Distances should be measured from the aerodrome facility reference point, as listed in the CFS (see 

9.2.1), or from a listed Aviation Navigation facility such as a VOR or NDB.

 All altitudes and elevation measurements for aviation purposes shall be listed and communicated in 

feet. (1 meter = 3.281 feet). Specify feet AGL (above ground level) or ASL (above sea level).

 All position locations for aviation purposes shall be expressed in the following formats’:

o For Planning and NOTAMs; in non-GPS Lat/Long, as expressed in Deg.Min.Sec. (eg; N53 18 36 

W113 34 46). 

o For Emergency coordination with ATS units, in a position report expressed by distance in NM 

and direction in compass rose points from the nearest published Aerodrome/Heliport. (eg; 

4.5NM E-N-E of CYQL)

The date the NOTAM was filed should be noted in the “Mission” folder.

 Cancelling a NOTAM:

o If you are unable to operate and need to cancel a NOTAM please contact AFSS (1-877-4-USNTMS) with coordinates of NOTAM and NOTAM reference number. If NOTAM is ongoing, 

please cancel the NOTAM for the days you will not be operating only. 

Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

43. Check that NOTAM was issued as required by checking HERE
44. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

45. Tailgate meeting 

46. Emergency procedures reviewed

47. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

48. Ensure proper site security has been completed

49. ERS staff have proper PPE

50. Complete safety checks

51. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

52. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

53. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

54. Flights conducted according to flight parameters

55. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

56. Other data (GPS, etc) collected

Flight	Parameters

All UAS operations will follow these conditions: 

 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.

 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including FSDO shift manager and 

local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.
o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 

 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

iii. Class D Tower control zone 

Operations will be limited to 400ft AGL unless otherwise stated by Air traffic service manager in charge of 

airspace to be operated in or by Nav Canada as per NOTAM requirements. 

I. Mission Planning 

During the following steps are taken:

49. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

50. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

51. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

52. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

53. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

54. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

55. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

56. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

57. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

58. ERS staff have proper PPE for the operations area
59. Emergency procedures are filled out with necessary data

60. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission folder” 

NOTAMs

A NOTAM shall be filed at least 48 hours in advance for any operation under this Exemption that is within 

controlled airspace and/or within five (5) nautical miles of an uncontrolled aerodrome in either controlled or 

uncontrolled airspace unless directed otherwise by the Air Traffic Service Unit Manager or the Military Air 

Traffic Service Unit responsible for that airspace.

NOTAMs are issued by calling AFSS (1-877-4-US-NTMS) for the region being operated in. The following are 

examples of information that the UAV operator should provide to the applicable ATS unit: 

 Intended date, time and duration of the operation; 

 Type of UAV including its size, weight and colour; 

 Lat and long of the operation area (optional but preferred: include an image of the area);

 Vertical and horizontal boundaries of the area of operation; 

 Contact name and number for the UAV operator; 

The following units and measurements are acceptable:

 All distances and units of measure for aviation purposes shall be listed and communicated in NM, 

Nautical Miles, feet or inches. Below two nautical miles, distances from aerodromes may be 

identified with decimals. Distances below one nautical mile may be identified in feet or in nautical 

mile (1 NM=1.151 miles, 1 NM=1.852 km, 1KM = 0.54 NM).

 Distances should be measured from the aerodrome facility reference point, as listed in the CFS (see 

9.2.1), or from a listed Aviation Navigation facility such as a VOR or NDB.

 All altitudes and elevation measurements for aviation purposes shall be listed and communicated in 

feet. (1 meter = 3.281 feet). Specify feet AGL (above ground level) or ASL (above sea level).

 All position locations for aviation purposes shall be expressed in the following formats’:
o For Planning and NOTAMs; in non-GPS Lat/Long, as expressed in Deg.Min.Sec. (eg; N53 18 36 

W113 34 46). 

o For Emergency coordination with ATS units, in a position report expressed by distance in NM 

and direction in compass rose points from the nearest published Aerodrome/Heliport. (eg; 

4.5NM E-N-E of CYQL)

The date the NOTAM was filed should be noted in the “Mission” folder.

 Cancelling a NOTAM:

o If you are unable to operate and need to cancel a NOTAM please contact AFSS (1-877-4-USNTMS) with coordinates of NOTAM and NOTAM reference number. If NOTAM is ongoing, 

please cancel the NOTAM for the days you will not be operating only. 

Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

57. Check that NOTAM was issued as required by checking HERE

58. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

59. Tailgate meeting 

60. Emergency procedures reviewed

61. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

62. Ensure proper site security has been completed

63. ERS staff have proper PPE

64. Complete safety checks

65. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

66. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

67. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

68. Flights conducted according to flight parameters

69. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

70. Other data (GPS, etc) collected

Flight	Parameters

All UAS operations will follow these conditions: 

 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.
 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including FSDO shift manager and 

local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.

o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 

 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

iv. Class E control zone

Operations will be limited to 400ft AGL unless otherwise stated by Air traffic service manager in charge of 

airspace to be operated in or by Nav Canada as per NOTAM requirements. 

J. Mission Planning 

During the following steps are taken:

61. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

62. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

63. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

64. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

65. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

66. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)
67. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

68. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

69. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

70. ERS staff have proper PPE for the operations area

71. Emergency procedures are filled out with necessary data

72. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission folder” 

NOTAMs

A NOTAM shall be filed at least 48 hours in advance for any operation under this Exemption that is within 

controlled airspace and/or within five (5) nautical miles of an uncontrolled aerodrome in either controlled or 

uncontrolled airspace unless directed otherwise by the Air Traffic Service Unit Manager or the Military Air 

Traffic Service Unit responsible for that airspace.

NOTAMs are issued by calling AFSS (1-877-4-US-NTMS) for the region being operated in. The following are 

examples of information that the UAV operator should provide to the applicable ATS unit: 

 Intended date, time and duration of the operation; 

 Type of UAV including its size, weight and colour; 

 Lat and long of the operation area (optional but preferred: include an image of the area);

 Vertical and horizontal boundaries of the area of operation; 

 Contact name and number for the UAV operator; 
The following units and measurements are acceptable:

 All distances and units of measure for aviation purposes shall be listed and communicated in NM, 

Nautical Miles, feet or inches. Below two nautical miles, distances from aerodromes may be 

identified with decimals. Distances below one nautical mile may be identified in feet or in nautical 

mile (1 NM=1.151 miles, 1 NM=1.852 km, 1KM = 0.54 NM).

 Distances should be measured from the aerodrome facility reference point, as listed in the CFS (see 

9.2.1), or from a listed Aviation Navigation facility such as a VOR or NDB.

 All altitudes and elevation measurements for aviation purposes shall be listed and communicated in 

feet. (1 meter = 3.281 feet). Specify feet AGL (above ground level) or ASL (above sea level).

 All position locations for aviation purposes shall be expressed in the following formats’:

o For Planning and NOTAMs; in non-GPS Lat/Long, as expressed in Deg.Min.Sec. (eg; N53 18 36 

W113 34 46). 

o For Emergency coordination with ATS units, in a position report expressed by distance in NM 

and direction in compass rose points from the nearest published Aerodrome/Heliport. (eg; 

4.5NM E-N-E of CYQL)

The date the NOTAM was filed should be noted in the “Mission” folder.

 Cancelling a NOTAM:

o If you are unable to operate and need to cancel a NOTAM please contact AFSS (1-877-4-USNTMS) with coordinates of NOTAM and NOTAM reference number. If NOTAM is ongoing, 

please cancel the NOTAM for the days you will not be operating only. 

Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

71. Check that NOTAM was issued as required by checking HERE
72. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

73. Tailgate meeting 

74. Emergency procedures reviewed

75. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

76. Ensure proper site security has been completed

77. ERS staff have proper PPE

78. Complete safety checks

79. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

80. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

81. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

82. Flights conducted according to flight parameters

83. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

84. Other data (GPS, etc) collected

Flight	Parameters

All UAS operations will follow these conditions: 

 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.

 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including FSDO shift manager and 

local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.
o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 

 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

v. Mandatory Frequency control zone (MF)

Will not be operated in

vi. Aerodrome Traffic Frequency zone (ATF)

Will not be operated in

vii. Privately owned, unlicensed, unregistered Aerodrome Procedures

Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. All flights in this airspace will be coordinated 

with Nav Canada as per this document to ensure safe operations. 

K. Mission Planning 

During the following steps are taken:

73. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

74. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

75. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

76. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

77. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

78. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

79. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

80. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 
description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

81. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

82. ERS staff have proper PPE for the operations area

83. Emergency procedures are filled out with necessary data

84. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission folder” 

NOTAMs

A NOTAM shall be filed at least 48 hours in advance for any operation under this Exemption that is within 

controlled airspace and/or within five (5) nautical miles of an uncontrolled aerodrome in either controlled or 

uncontrolled airspace unless directed otherwise by the Air Traffic Service Unit Manager or the Military Air 

Traffic Service Unit responsible for that airspace.

NOTAMs are issued by calling AFSS (1-877-4-US-NTMS) for the region being operated in. The following are 

examples of information that the UAV operator should provide to the applicable ATS unit: 

 Intended date, time and duration of the operation; 

 Type of UAV including its size, weight and colour; 

 Lat and long of the operation area (optional but preferred: include an image of the area);

 Vertical and horizontal boundaries of the area of operation; 

 Contact name and number for the UAV operator; 
The following units and measurements are acceptable:

 All distances and units of measure for aviation purposes shall be listed and communicated in NM, 

Nautical Miles, feet or inches. Below two nautical miles, distances from aerodromes may be 

identified with decimals. Distances below one nautical mile may be identified in feet or in nautical 

mile (1 NM=1.151 miles, 1 NM=1.852 km, 1KM = 0.54 NM).

 Distances should be measured from the aerodrome facility reference point, as listed in the CFS (see 

9.2.1), or from a listed Aviation Navigation facility such as a VOR or NDB.

 All altitudes and elevation measurements for aviation purposes shall be listed and communicated in 

feet. (1 meter = 3.281 feet). Specify feet AGL (above ground level) or ASL (above sea level).

 All position locations for aviation purposes shall be expressed in the following formats’:

o For Planning and NOTAMs; in non-GPS Lat/Long, as expressed in Deg.Min.Sec. (eg; N53 18 36 

W113 34 46). 

o For Emergency coordination with ATS units, in a position report expressed by distance in NM 

and direction in compass rose points from the nearest published Aerodrome/Heliport. (eg; 

4.5NM E-N-E of CYQL)

The date the NOTAM was filed should be noted in the “Mission” folder.

 Cancelling a NOTAM:

o If you are unable to operate and need to cancel a NOTAM please contact AFSS (1-877-4-USNTMS) with coordinates of NOTAM and NOTAM reference number. If NOTAM is ongoing, 

please cancel the NOTAM for the days you will not be operating only. 

Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

85. Check that NOTAM was issued as required by checking HERE

86. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

87. Tailgate meeting 

88. Emergency procedures reviewed

89. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight Briefing.

90. Ensure proper site security has been completed

91. ERS staff have proper PPE

92. Complete safety checks

93. Automated missions: load flight plan provided in “Mission” folder. Adjust according to weather, site 

security and safety requirements. 

94. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to weather, 

site security and safety requirements.

95. Contact control tower within 30 minutes of commencement of flight operations when operating in 

any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

96. Flights conducted according to flight parameters

97. Contact control tower after flight operations are complete when operating in any ATC controlled 

airspace. 

98. Other data (GPS, etc) collected
Flight	Parameters

All UAS operations will follow these conditions: 

 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.

 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including FSDO shift manager and 

local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.

o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 

 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

Appendix D

Please see the attached Confidential & Proprietary: Elevated 

Robotic Services Inc. Project Processes and Standard 

Operating Procedures

ERS	Project	Process

II. Project Process Overview

Elevated Robotic Services follows a project process that ensures all safety and regulatory requirements are 

considered before, during and after operations. 
The project process is:

1. Requirement Gathering

2. Mission Planning

3. Mission Completion

4. Post-Mission Check

5. Processing

6. Deliverables

7. Project Closure

A. Requirement Gathering 

This involves assessing the client’s needs and determining the proper mission and equipment to deliver the 

required results. 

1. Understanding of client’s problem

2. Creation of mission specs to deliver required solution

B. Mission Planning 

During the following steps are taken:

85. Plan mission flight using flight software for the UAV or Google maps to address mission specs

a. Plan boundaries 

b. Check for roads, buildings, towers, anything that may interfere with the flight. 

c. Altitudes and routes are saved as a flight plan for field personnel.

86. Check airspace to be flown in and closest airport. Use American Flight Supplement and Aeronautical 

Charts. Record on checklist.

87. Check all parameters are within Exemption, adjust mission or apply for COA if necessary

88. Coordinate with the proper FAA FSDO by contacting them at least 72 hrs in advance of operations.

(Please see Appendix A for full list of contact information)

89. Contact and obtain approval from proper authorities. Contact government agency, city, municipality, 

parks or military body if required. Authorities to be contacted are the ones whose land is being flown 

over or used for any portion of the mission or whose airspace will be flown in.

90. Contact ATC a minimum of 24 hrs in advance, unless FSDO will coordinate with them directly. 

Agreement needs to be given by ATC prior to filing a NOTAM. Provide all information needed for a 

NOTAM, plus a screenshot of the location from Google Earth. 

a. Contact information found in Appendix A or otherwise in the AFS (also contained in the 

ForeFlight app) per tower control zone. 

b. Add contact information for ATC (name and number) to Pre-flight Checklist. (Please note: 

see Appendix A for contact information for all FSDO’s)

91. Issue NOTAM unless otherwise requested by FSDO. Ensure 72 hrs minimum before flight, preferably 

4-5 days’ notice.

92. Obtain standard operating procedures signed from client

a. Prior to operations the client and/or land owner will be given a copy of the Standard 

Operating Procedures document for their review. Consensus to the contract conveys they 

have read and understood the SOPs. The covering letter contains the date and location to be 

flown. The SOP addresses items such as permission of the land owner to fly over the site

(private or public), requests that all personnel be off the site during the flight itself and a 

description of factors that will require a postponement of the mission (i.e. if any of the SFOC 

conditions cannot be met)

b. In the case of flights over private land done for government purposes proof of legislative 

rights to perform such flights must be provided. No objection rather than permission. Silence 

is implied permission. 

93. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations
a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

94. ERS staff have proper PPE for the operations area

95. Emergency procedures are filled out with necessary data

96. All documents (location, driving directions, mission area, mission specs, flight plan, on-site contact 

info/procedures, emergency procedures and checklists) into “Mission folder” 

1. NOTAMs

A NOTAM shall be filed at least 48 hours in advance for any operation under this Exemption that is within 

controlled airspace and/or within five (5) nautical miles of an uncontrolled aerodrome in either controlled or 

uncontrolled airspace unless directed otherwise by the Air Traffic Service Unit Manager or the Military Air 

Traffic Service Unit responsible for that airspace.

NOTAMs are issued by calling AFSS (1-877-4-US-NTMS) for the region being operated in. The following are 

examples of information that the UAV operator should provide to the applicable ATS unit: 

 Intended date, time and duration of the operation; 

 Type of UAV including its size, weight and colour; 

 Lat and long of the operation area (optional but preferred: include an image of the area);

 Vertical and horizontal boundaries of the area of operation; 

 Contact name and number for the UAV operator; 

The following units and measurements are acceptable:

 All distances and units of measure for aviation purposes shall be listed and communicated in NM, 

Nautical Miles, feet or inches. Below two nautical miles, distances from aerodromes may be 

identified with decimals. Distances below one nautical mile may be identified in feet or in nautical 

mile (1 NM=1.151 miles, 1 NM=1.852 km, 1KM = 0.54 NM).
 Distances should be measured from the aerodrome facility reference point, as listed in the CFS (see 

9.2.1), or from a listed Aviation Navigation facility such as a VOR or NDB.

 All altitudes and elevation measurements for aviation purposes shall be listed and communicated in 

feet. (1 meter = 3.281 feet). Specify feet AGL (above ground level) or ASL (above sea level).

 All position locations for aviation purposes shall be expressed in the following formats’:

o For Planning and NOTAMs; in non-GPS Lat/Long, as expressed in Deg.Min.Sec. (eg; N53 18 36 

W113 34 46). 

o For Emergency coordination with ATS units, in a position report expressed by distance in NM 

and direction in compass rose points from the nearest published Aerodrome/Heliport. (eg; 

4.5NM E-N-E of CYQL)

The date the NOTAM was filed should be noted in the “Mission” folder.

 Cancelling a NOTAM:

o If you are unable to operate and need to cancel a NOTAM please contact AFSS (1-877-4-USNTMS) with coordinates of NOTAM and NOTAM reference number. If NOTAM is ongoing, 

please cancel the NOTAM for the days you will not be operating only. 

C. Mission Completion 

Mission completion is the field work. It involves checking the previous steps, conducting the flight safely and 

gathering any ground data required. It is comprised of the following steps:

99. Check that NOTAM was issued as required by checking HERE

100. Check weather forecast using NOAA Graphical Forecast and/or METAR for location nearest 

operations

a. Visibility 3 km +

b. Cloud base > 1000 ft AGL or at least 500 ft AGL above flight altitude

c. Wind < UAV specs

i. Winds are checked on site using an anemometer.

101. Tailgate meeting 

102. Emergency procedures reviewed

103. Client & personnel are briefed on mission/COA. All observers have received the Pre-Flight 

Briefing.

104. Ensure proper site security has been completed

105. ERS staff have proper PPE

106. Complete safety checks

107. Automated missions: load flight plan provided in “Mission” folder. Adjust according to 

weather, site security and safety requirements. 

108. Manual missions: fly within parameters provided in “Mission” folder. Adjust according to 

weather, site security and safety requirements.

109. Contact control tower within 30 minutes of commencement of flight operations when 

operating in any ATC controlled airspace. 

a. Contact information on Pre-Flight Checklist or in United States Flight Supplement. 

110. Flights conducted according to flight parameters

111. Contact control tower after flight operations are complete when operating in any ATC 

controlled airspace. 

112. Other data (GPS, etc) collected

1. Flight	Parameters

All UAS operations will follow these conditions: 
 Flights will be limited to 300 ft AGL within 3 nm, and 400 ft AGL between 3 nm and 5 nm, unless 

within the approach path. Flights within the approach path will be limited to 100 ft AGL within 3 nm, 

to a maximum of 300 ft AGL between 3 nm and 5 nm. 

 Should an aircraft be heard or seen within the 5 nm of the aerodrome the UAV operator will return 

the UAV home to land or land immediately, whichever is necessary to give right of way to the 

aircraft. 

 Will comply with Aeronautics Act and FARs.

 No one suspected of or being fatigued shall operate the UAV.

 No one shall operate the UAV within 8 hours of consuming alcohol.

 UAV shall give way to manned aircraft.

 UAV personnel will be fully trained in operations, emergencies and recovery and will be over the age 

of 18.

 Flights shall be conducted in a safe manner and not over unsafe areas that may disrupt the flight. 

 Flights will be conducted according to the roles and responsibilities outlined by ERS management. 

 Adequate liability insurance will be maintained.

 UAV will remain within visual line of sight of pilot and clear of cloud. 

 An observer will be appointed for all flights. They will maintain a lookout for anything approaching 

the operating area or airspace and will inform UAV operator immediately.

 Emergency procedures will be available and filled in for all flights, including FSDO shift manager and 

local airports (see checklist attached).

 An aeronautical radio operator’s license ROC-A and equipment will be used to monitor and 

communicate on the appropriate frequency during operations.

 Any occurrences shall be reported by the following day:

o Flights out of bounds.

o Unintended contact with persons, structures, vehicles or wildlife.

o Any injury as a result of the operation.

 SFOC will be known to all personnel involved in operations. 

 All UAV system equipment required for safe flight operations must be serviceable.

 Operations will be documented. 

 VTOL or landings and take-offs are conducted into wind as much as possible considering the 

surrounding area. No downwind landings will be conducted unless in an emergency. 

a) Operations	with	multiple	UAVs

Not to be done until approved procedures are in place.

2. Site	Security

Site security is required for any flight, whether for training purposes or commercial activities. The security 

measures outlined below will be done for all flights where conditions are present. 

a) All	missions:

 UAV must be airworthy.

 Take-off and landing area will be marked accordingly. 

 Access via roads to the site must be obstructed and secured whenever possible (private roads only).

 All access must be blocked as much as possible. For commercial sites this involves informing all client 

personnel of the restricted area via the Standard Operating Procedures. 

b) If	the	public	is	present:

This includes flights for special events or demonstrations.

 Redundant UAV systems must be used (fixed wing that can glide and still be operated after engine 

failure or a multi-rotor that can have an engine failure and yet maintain flight). 

 Maintain distance from public and/or spectators.

 GPS assist shall be used outdoors.
 Testing of communications links shall be done in the area prior to event. 

 Blade guards for rotary aircraft whenever possible.

 “Caution: UAV in operation” warning signs around the area. 

c) Operations	within built-up	areas:

 Experienced UAV operator only.

 Redundant UAV systems must be used (fixed wing that can glide and still be operated after engine 

failure or a multi-rotor that can have an engine failure and yet maintain flight). 

 Automatic return home must be set for data link loss.

 Permission from city or municipality is required.

 Persons may not be identifiable in deliverables unless consent is given.

 Use extra care when setting up control station to maintain visual line of sight during flight. Watch for 

interference from buildings. 

 “Caution: UAV in operation” warning signs around the area. 

d) Indoor	operations:

 Experienced UAV operator only as no GPS assist is possible.

 People not associated are protected by a barrier capable of stopping the UAV.

e) If	roads	will	be	crossed:

 Flights within 100 ft of public roads may only be conducted if personnel are stationed 1 km away 

from the intersecting flight path down public roads on either way. They must be equipped with 

radios to alert the pilot of vehicles and/or pedestrians. At such time the pilot must restrict the flight 

to areas not within 100 ft of roads. 

 “Caution: UAV in operation” warning signs around the area.

f) If	wildlife or	birds present:

 Refer to Bear and Cougar Awareness documents.

 Maintain a watch on birds and avoid attacks using built in avoidance or manual maneuvers.

g) Pre-flight	Briefing

All observers will receive a pre-flight briefing. This will be done as follows:

1. Tailgate meeting points.

2. Take-off and landing areas – marked and may not be entered.

3. Observer areas – stay within marked observer areas.

4. Do not distract the pilot. Talk to the spotter when needed.

5. During landing watch the UAV at all times and stay within the observer area. Pilot will warn you 

when it is time to land.

6. If you see anyone or anything entering the zones that should not please tell spotter.

7. Review Emergency Procedures

3. Emergency	Contingency	Plan

Prior to any operations ERS will have known coordinates and numbers of all emergency services. If an 

emergency occurs, local authorities will be informed immediately. Elevated Robotic Services will always have 

available the local emergency and air authority contact numbers at every location. In addition, ERS operators 

are licensed to operate on Air Radio frequencies should that ever be required. A first aid kit, fire extinguisher 

and safety glass will be will be available and on site at each location.

In the unlikely scenario of the UAS going rogue, the procedures outlined below (carried by personnel on site 

at all times) will be actioned immediately by ERS. The following emergency plan will be carried out. 

All aspects of this required action will be provided in the pre-flight safety brief provide before each flight.

a) Emergency	Procedures

FSDO contact information can be found in Appendix A
All fields must be completed prior to each flight and carried by flight personnel at all times

Ground Control Station Emergency Contacts and Responsibilities in case of rouge UAV or emergency.

Pilot role

1. Activate "go land" button on flight deck. (this will send the message to the aircraft to land in the predefined landing area 

communication is resumed).

2. Assess whether the redundant systems & safeguards have been activated. (is the aircraft returning home as it leaves the working 

buffer?).

3. Repeat steps 2 & 3.

4. If control is regained, terminate mission and ensure that the UAV is landed as soon as safe to do so.

Ground supervisor role

1. Warn all personnel in area of the situation.

2. Issue PAN call on appropriate frequency. Include:

a. Current location.

b. Description of the issue and aircraft involved.

c. Estimate the heading, altitude, speed and endurance of UAV based on information from the pilot and observations.

3. If within controlled airspace. Contact local airport. Ph [Company Phone] and provide the following:

a. Current location.

b. Description of the issue and aircraft involved.

c. Estimate the heading, altitude, speed and endurance of UAV based on information from the pilot and observations.

4. If within uncontrolled airspace. Warn local aircraft by contacting FSDO [Manager] and provide the following.

a. Current location.

b. Description of the issue and aircraft involved.

c. Estimate the heading, altitude, speed and endurance of UAV based on information from the pilot and observations.

5. Contact 911 with the following information.

a. Current location.

b. Description of the issue and aircraft involved.

c. Estimate the heading, altitude, speed and endurance of UAV based on information from the pilot and observations.

d. Follow any instructions provided by 911.

6. Dispatch recovery service to flight follow and respond to situation. First aid kit and fire extinguisher must be present.

Emergency contact information:

Shift manager at FSDO # [Manager]

Closest airport _____________________ at _____ nm

Closest airport ATC (if applicable) # [Company Phone]

Closest airport radio frequency _________________MHz

Radio frequency to be monitored __________________MHz

Class of Airspace being operated in _______________

b) Safety	Checklists

Pre-flight safety checklist

□ The area is clear of all persons not related to the operation of the flight.

□ The flight path does not intersect any government roads.

□ Site reconnaissance has taken place to ensure that no power lines or other infrastructure will intersect the flight path.

□ Clear area of 80m radius is available for landing and takeoff.

□ Cloud ceiling is not less than 1000ft AGL.

□ No precipitation is present or forecast for the duration of the flight.

□ Visibility is not less than 2 Statute miles in all directions.

□ Ground control emergency checklist has been filled out and made available to flight personnel.

□ Authorities have been contacted that flight is about to commence (if applicable). Name________________ Phone__________

Sensefly Aircraft checklist

□ Check the foam central body and wings for cracks or other damage.

□ Verify that the pitot probe is properly attached to the airframe and that the holes in the probe are free of obstructions.

□ Verify that the ground sensor is free of obstructions and that the sensor’s lens is clean.

□ Verify that the wing struts are not split or damaged in any way.

□ Verify that the tubes within the Central Body that hold the wing struts are not cracked or damaged in any way.

□ Verify that the power cables within the battery compartment are well insulated and not damaged.

Sensefly ground control station checklist

□ Wind speed at ground level is less than 25 km/h.
□ GPS position on screen.

□ Data link is strong.

□ Flight deck responsive to pitch/yaw/roll.

□ Wind speed showing on ground control station.

□ Battery is 95% or above.

□ Ground proximity indicator is active.

□ Current status is "ready for takeoff".

□ Current temperature is within operating limits of the aircraft.

DJI Aircraft checklist

□ Body and landing gear damage free and secured.

□ Rotor struts and blades free of damage, attached and secured.

□ Gimbal and sensor attached, on and full range of motion. 

□ Batteries attached and secure. Indicator shows full battery.

□ Aircraft and gimbal responsive to full range of motion. 

□ Wiring insulated, attached and secured by cap. 

DJI Ground control station checklist

□ Sufficient satellites for take-off (>6).

□ Wind speed at ground level is less than 25 km/h.

□ Compass calibration is valid. If not, calibrate compass according to manufacturer’s directions.

□ Wind speed showing on ground control station.

□ Batteries are 95% or above.

□ Ground proximity indicator is active.

□ Current status is "ready for takeoff".

□ Current temperature is within operating limits of the aircraft.

c) Termination	of	Flight

A deliberate and controlled termination of the flight will result in the UAV being landed as soon as safely 

possible at the original landing area or immediately if necessary to avoid collision. Termination of flight will 

take place if any of the following criteria are met:

 Other aircraft are observed entering into the operating area where a conflict may arise.

 The UAV deviates from its flight plan.

 The UAV is lost from visual contact.

 Data link is lost for more than 30 seconds.

D. Post-Mission Check

 Post flight UAV check

 Equipment check

 On-site quality checks – post flight quick processing

 Upload data and completed forms into “Field In” folder for office personnel. Handover Moment 2

1. Log	Book

Log books are kept digitally per UAV. The following is an example of an entry in the log books. It is completed 

after each flight.

Maintenance is recorded in the log book. Minor maintenance is done by the field personnel who were 

trained by ERS. This includes replacing propellers, fixing small chips and tears, tightening screws, exchanging 

for spare parts that are included, software/firmware updates, etc. Major repairs must be taken to the 

reseller or other personnel qualified by manufacturer. This includes crash landings (check of the inside 
components must be done), broken parts that are not included as spare parts, engine mount repair, etc. 

E. Processing

 Processing is done in the office by GIS personnel using the data uploaded by the field crews.

F. Deliverables

 Deliverables are given to the client. Handover Moment 3

 Follow up with the client to obtain satisfaction ratings. 

G. Project Closure 

This step must be done. Project documentation is required to be filed. 

 Ensure all permissions, approval emails/letters and field documents are filed (digitally).

 Complete invoicing

 Ensure payments are received in full.

III. Roles	and	Responsibilities

UAV Pilot

 Aviate, navigate, communicate!

 Know your UAV and ask if you are not sure

 Air radio

 Visual contact with drone

 Look out for aircraft

 Look out for personnel

 Maintain clear landing area

 Emergency procedures – pilot duties

 Communicate with spotter and payload operator

 Pre-flight checklist

Payload Operator

 Operate payload

 Communicate with pilot and spotter

 If payload operator is also the pilot the payload operation must be automated or require little to no 

input while the UAV is in motion. Conducting duties as the payload operator shall not affect the 

person’s ability to control the aircraft and must not negatively impact their workload as the UAV 

pilot. 

Observer

 Visual contact with drone

 Look out for aircraft

 Look out for personnel

 Maintain clear landing area

 Communicate with pilot and payload operator

 Emergency procedures – ground supervisor duties
Safety - EVERYONE!

 Monitor proper radio frequency

 Visual monitoring of air traffic and other potential hazards

 Radio contact between ERS staff as needed

 Monitor wind speed & weather conditions

 Flight duty time limitations and rest periods 

o maximum 14 hours of work per day

o maximum 8 hours of flight per day

o minimum 8 hours of rest between shifts
IV. Training	Program

The training program is outlined in a separate document, but involves the completion of all of the above 

steps. The steps are reviewed in the office and in the field to ensure personnel know their equipment and 

the procedures through and through. 

The project process is covered, as well as the following steps per UAV that are important during mission 

completion:

 Overview of the UAV PowerPoint/video/demo.

 Hardware overview & assembling the UAV. 

 Airframe checks & pre-flight procedures.

 On-site maintenance & airworthiness.

 UAV technical specifications and limitations as specified by manufacturer.

 Introduction to flight software.

 Install the drivers and test communications link(s).

 Updating firmware.

 Create sample flight plans. 

 Review in flight commands.

 Partner up pilot/spotter.

 Flight training:

o Choosing a take-off and landing area

o Take-off/launching

o Visual scanning techniques

o Radio practice

o Landing procedures

 Rapid processing/quality check of flight data.

 Organizing flight data.

Observers must be aware of their observer duties prior to the mission. All duties and emergency procedures 

must be reviewed. As well, visual scanning techniques, weather limitations and special SFOC conditions need 

to be discussed. 

The following external training programs must be completed as well:

CCUVS – UAV Operator Certificate

Radio operator license ROC-A

Standard First Aid with CPR

Other safety permits as required per site (WHMIS, H2S Alive, Confined Spaces, etc.)

V. ERS	Landowner	Authorization	and	Standard	Operating	

Procedures

Elevated Robotics Services Inc. and [Company] agree to the following:

Deliverables 

1. Description of service: Click here to enter text.

2. Products: Click here to enter text.

3. These deliverables will be sent to: [Manager]
Rate

4. Fee for service: As described in fee estimate Click here to 

enter text.

Prioritized Dates for Service

5. First choice: Click here to enter text.

6. Alternative second choice: Click here to enter text.

7. Alternative third choice: Click here to enter text.

Authorization

8. The client agrees that permission has been obtained for Elevated Robotic Services Inc. to 

overfly and operate an unmanned vehicle on all agreed upon sites. Proof of authorization 

will be provided to ERS by the client as requested.

Agreed on behalf of Elevated Robotic Services Inc.

------------------------------------------------------------------ --------------------------------

Ellen Christopherson, Owner Date

Agreed on behalf of [Company]

------------------------------------------------------------------ --------------------------------------

[Manager] Date

Elevated	Robotic	Services	- Standard	Operating	

Procedures

Client Responsibilities

Elevated Robotic Services Inc. (ERS) created its Standard Operating Procedures to ensure 

safety, efficiency and product consistency. These operating procedures were also developed 

to conform to regulations from Transport Canada and Occupational Health & Safety. Please 

read this document carefully as it outlines the procedures needed to carry out unmanned 

aerial vehicle (UAV) operations at your site. 

Pre-Flight Co-operation

The client will designate a contact person to work with ERS in planning and scheduling the 

operation. Typically, the time commitment from the contact person will be 2 to 3 hours. 

By agreeing to the flight, the client grants permission for ERS to fly a UAV over its property. 

The client agrees to notify ERS of any conditions that may affect the flight. We will ask for 

your input on the following matters:

Identification of any transmitters operating at your site on a frequency of 2.4 GHz.

Identification of any tall obstructions in or near the site area to be flown, and an estimate of 

their height
Identification of a relatively flat take-off and landing area with minimum dimensions of 50 

metres x 50 metres, free of obstacles. If tall buildings or trees are present directly along the 

perimeter this area may need to be larger. 

Safety of Personnel beneath the Flight Path

Prior to flying the mission, it will be necessary to notify all personnel who will be operating in 

the area directly around the flight. During the flight ERS may request a temporary halt to any 

traffic and personnel beneath the flight path of the UAV. 

Training for ERS Personnel

The client will provide appropriate safety training for all ERS personnel engaged with on-site 

work.

Operations/Shut-downs on Mission Day

ERS may request the following during UAV flights:

Temporary shut-off of RF equipment near the flight zone that operates on a frequency of 2.4 

GHz. This is the frequency used to communicate with the UAV and must be free of 

interference.

Temporary shut-off of any equipment that may send unwanted debris into the flight path 

(sprayers, chippers, etc.). Airborne debris will detrimentally affect the quality of data and 

hence the information we are able to provide.

Temporary removal of personnel and a halt to any traffic or machinery operating directly 

under the flight path. Flights are typically short, but should not be conducted over personnel 

not directly involved in the flight operations.

The take-off and landing zone will be marked by ERS personnel and must be kept clear of 

personnel and equipment during all UAV operations.

ERS - On-site Responsibilities/Procedures 

Regulations & Emergencies

All flights are conducted in accordance with ERS flight procedures. These include pre-flight 

checks, in-flight checks and post-flight checks. ERS personnel are trained in emergency 

measures in the unlikely event of a malfunction. 

Approval from Transport Canada is required for ever flight. ERS will apply for these 

approvals, but note that for some types of flights may require lead times of several weeks.

Limitations

To protect our personnel, your personnel, the aviation industry and the general public we 

only operate under safe conditions. If these conditions are not present, we will not fly. We 

will notify you as soon as possible if we think the conditions are not suitable and be assured 

we will work with you to move the operations to the most suitable alternate day.

Weather 

Flying unmanned aerial vehicles (UAVs) is conditional on the weather. Infrequently, this may 

require the flight to be done earlier or postponed for hours or even days. Alternate days 

should be specified in the event wind, precipitation or space irradiation prevent a safe flight.

Temperature affects equipment and personnel. ERS can only operate UAVs in temperatures 

between -20° and +40° Celsius, including the wind chill factor. Wind conditions must be 

below the maximum operating limits for the UAV. These vary per UAV, but generally they 

winds should not exceed 30 km/h. Precipitation, cloud coverage and visibility also affect
operations and operations may be rescheduled due to any of these reasons.
VI. Common	Technical	Problems	FAQ

A. During flight

Q: My camera malfunctioned during flight. How do I fix it?

A: Replace the battery and check if the SD card is locked. 

Q: The drone shows a log malfunction. How do I fix it?

A: Restart the drone.

Q: The data link disconnected. What do I do?

A: Data link loss will trigger return to home function on UAV. Clear landing area and attempt to 

regain communications. 

Q: The data link disconnected. How do I fix it?

A: Carefully inspect data link to ensure no damage is present. Test link on ground by carrying UAV 

away from data link transmitter to determine when connection is lost. If not lost, ensure no radio 

equipment is operating in the area before attempting flight again. 
VII. Appendix	A

Office Address Phone Service Area Contact Website

Alabama & NW 

Florida

1500 Urban 

Center Drive

(205) 876-1300 Service Area Contact Website

Birmingham, AL 

35242

Anchorage 300 West 36th 

Avenue

(907) 271-2000 Service

Area (PDF)

Contact Website

Anchorage, AK 

99503

Fairbanks 4419 Airport Way (907) 474-0276 Service

Area (PDF)

Contact Website

Fairbanks, AK 

99709

Juneau 3032 Vintage Park 

Boulevard

(907) 586-7532 Service

Area (PDF)

Contact Website

Juneau, AK 99801

Scottsdale 17777 North 

Perimeter Drive

(480) 419-0330 Service

Area (PDF)

Contact Website

Scottsdale, AZ

85255

Little Rock1701 

Bond Street

1701 Bond Street 

Little Rock, AR 

72202

(501) 918-4400 Service Area

(PDF)

Contact Website

Oakland 1420 Harbor Bay 

Parkway

(510) 748-0122 Service

Area (PDF)

Contact Website

Alameda, CA 

94502

Fresno 4955 East 

Anderson

(559) 454-0286 Service

Area (PDF)

Contact Website

Fresno, CA 93727

Los Angeles 15000 Aviation 

Boulevard,

(310) 725-6600 Service

Area (PDF)

Contact Website

Lawndale, CA 

90261

Long Beach 5001 Airport 

Plaza Drive

(562) 420-1755 Service

Area (PDF)

Contact Website

Long Beach, CA 

90815

Riverside 6961 Flight Road (951) 276-6701 Service

Area (PDF)

Contact Website

Riverside, CA 

92504
Sacramento 1102 Corporate 

Way

(916) 422-0272 Service

Area (PDF)

Contact Website

Sacramento, CA 

95831

San Diego 8525 Gibbs Drive (858) 502-9882 Service

Area (PDF)

Contact Website

San Diego, CA 

92123

San Jose 1250 Aviation 

Avenue

(408) 291-7681 Service

Area (PDF)

Contact Website

San Jose, CA 

95110

Van Nuys 16501 Sherman 

Way

(818) 904-6291 Service

Area (PDF)

Contact Website

Van Nuys, CA 

91406

Denver 26805 East 68th 

Avenue

(800) 847-3808 Service

Area (PDF)

Contact Website

Denver, CO 80249

Bradley FSDO 1699 King Street,

Suite 210 Enfield,

CT 06082

(860) 386-1800 Service 

Area (PDF)

Contact Website

Washington

FSDO

13873 Park 

Center Road Suite 

475 Herndon, VA

2071

(703) 230-7664 Service Area

(PDF)

Contact Website

S. Florida 

(Miramar)

2895 SW 145 Ave

Hollywood, FL 

33027

(954) 641-6000 Service

Area (PDF)

Contact Website

Orlando 5950 Hazeltine (407) 812-7700 Service

Area (PDF)

Contact Website

Orlando, FL 32822

Tampa 5601 Mariner 

Street

(813) 287-4900 Service

Area (PDF)

Contact Website

Tampa, FL 33609

Atlanta 107 Charles W. 

Grant Parkway

(404) 474-5100 Service

Area (PDF)

Contact Website

Atlanta, GA 30354

Honolulu 135 Nakolo Place 

Honolulu

(808) 837-8300 Service

Area (PDF)

Contact Website

Honolulu, HI 

96819
Boise 3295 Elder Street (208) 387-4000 Service

Area (PDF)

Contact Website

Boise, ID 83705

Chicago O'Hare 2300 East Devon 

Avenue

(847) 294-7900 Service

Area (PDF)

Contact Website

Des Plaines, IL 

60018

Springfield 1250 North 

Airport Drive

(217) 744-1910 Service

Area (PDF)

Contact Website

Springfield, IL 

62707

DuPage 31w775 North 

Avenue

(630) 443-3100 Service

Area (PDF)

Contact Website

West Chicago, IL 

60185

Indianapolis 1201 Columbia

Road, Suite 101

(317) 837-4400 Service

Area (PDF)

Contact Website

Plainfield, IN 

46168

Des Moines 3753 Se

Convenience Blvd. 

Ankeny, IA 50021

(515) 289-3840 Service 

Area (PDF)

Contact Website

Wichita 1801 Airport Road (316) 941-1200 Service

Area (PDF)

Contact Website

Wichita, KS 67209

Louisville 10200 Forest 

Green Blvd.

(502) 753-4200 Service

Area (PDF)

Contact Website

Louisville, KY 

40223

Baton Rouge 6100 Corporate 

Boulevard Baton 

Rouge, LA 70808

(225) 932-5900 Service 

Area (PDF)

Contact Website

Portland, Maine 412 Yellowbird 

Road Portland, 

ME 04102

(207) 780-3263 Service 

Area (PDF)

Contact Website

Baltimore 890 Airport Park 

Road Glen Burnie, 

MD 21061

(410) 787-0040 Service Area 

(PDF)

Contact Website

Boston 12 New England 

Executive Park 

Burlington, MA 

01803

(781) 238-7500 Service 

Area (PDF)

Contact Website
East Michigan 8800 Beck RoadEastside Belleville, 

MI 48111

(734) 487-7222S Service 

Area (PDF)

Contact Website

Grand Rapids 3196 Kraft 

Avenue Southeast 

Grand Rapids, MI 

49512

(616) 954-6657 Service 

Area (PDF)

Contact Website

Minneapolis-St.

Paul FSDO

6020 28th Avenue 

South

(612) 253-4400 Service

Area (PDF)

Contact Website

Minneapolis, MN 

55450

Jackson 100 West Cross 

Street

(601) 664-9800 Service

Area (PDF)

Contact Website

Pearl, MS 39208

Kansas City 901 Locust Street (816) 329-4000 Service

Area (PDF)

Contact Website

Kansas City, MO 

64106

St. Louis 10801 Pear Tree 

Lane

(314) 890-4800 Service

Area (PDF)

Contact Website

Saint Ann, MO 

63074

Helena 2725 Skyway 

Drive Helena, MT 

59602

(406) 449-5270 Service Area 

(PDF)

Contact Website

Lincoln 3431 Aviation 

Road Lincoln, NE 

68524

(402) 475-1738 Service Area 

(PDF)

Contact Website

Las Vegas 7181 Amigo 

Street

(702) 617-8500 Service

Area (PDF)

Contact Website

Las Vegas, NV 

89119

Reno 5466 Longley 

Lane

(775) 858-7700 Service

Area (PDF)

Contact Website

Reno, NV 89511

Teterboro Park 80 West (201) 556-6600 Service

Area (PDF)

Contact Website

Saddle Brook, NJ 

07663

Albuquerque 1601 Randolph 

Road Se

(505) 764-1200 Service

Area (PDF)

Contact Website

Albuquerque, NM 

87106
Farmingdale 7150 Republic 

Airport 

Farmingdale, NY 

11735

(631) 755-1300 Service Area 

(PDF)

Contact Website

New York City 990 Stewart 

Avenue Garden 

City, NY 11530

(516) 228-8029 Service Area 

(PDF)

Contact Website

Albany 7 Airport Park 

Boulevard 

Latham, NY 12110

(518) 785-5660 Service Area 

(PDF)

Contact Website

Rochester 1 Airport Way 

Rochester, NY 

14624

(585) 436-3880 Service Area 

(PDF)

Contact Website

Charlotte 3800 Arco 

Corporate Drive 

Charlotte, NC 

28273

(704) 319-7020 Service Area 

(PDF)

Contact Website

Greensboro 6433 Bryan 

Boulevard

Greensboro, NC 

27409

(336) 369-3900 Service Area 

(PDF)

Contact Website

Fargo 4620 Amber 

Valley Parkway

(701) 492-5800 Service

Area (PDF)

Contact Website

Fargo, ND 58104

Will Rogers 1300 South 

Meridian 

Oklahoma City, 

OK 73108

(405) 951-4200 Service Area 

(PDF)

Contact Website

Portland 3180 Nw 229th

Avenue Hillsboro, 

OR 97124

(503) 615-3200 Service Area 

(PDF)

Contact Website

Allentown 961 Marcon 

Boulevard

(610) 264-2888 Service

Area (PDF)

Contact Website

Allentown, PA 

18109

Harrisburg 400 Airport Road (717) 774-8271 Service

Area (PDF)

Contact Website

New Cumberland, 

PA 17070

Philadelphia 2 International 

Plaza

(610) 595-1500 Service

Area (PDF)

Contact Website

Philadelphia, PA 

19113
Allegheny 101 Towne 

Square Way

(412) 886-2580 Service

Area (PDF)

Contact Website

Pittsburgh, PA 

15227

San Juan FSDO 525 F.D.

Roosevelt Avenue

(787) 282-6500 Service

Area (PDF)

Contact Website

San Juan, PR 

00918

South Carolina 125-B Summer 

Lake Drive

(803) 765-5931 Service

Area (PDF)

Contact Website

West Columbia, 

SC 29170

Rapid City 3501 5th St. Rapid 

City, SD 57701

(605) 737-3050 Service Area 

(PDF)

Contact Website

Memphis 2847 Business 

Park Drive 

Memphis, TN 

38118

(901) 322-8600 Service Area 

(PDF)

Contact Website

Nashville 2 International 

Plaza Nashville, 

TN 37217

(615) 324-1300 Service Area 

(PDF)

Contact Website

Houston 12650 N.

Featherwood 

Dr. Suite 230 

Houston, TX 

77034

(281) 929-7000 Service Area 

(PDF)

Contact Website

North Texas 8700 Freeport 

Parkway Irving, TX 

75063

(214) 277-8500 Service Area 

(PDF)

Contact Website

Lubbock 5225 S. Loop 289,

Suite 122 

Lubbock, TX 

79424

(806) 740-3800 Service Area 

(PDF)

Contact Website

San Antonio 10100 Reunion 

Place San 

Antonio, TX 

78216

(210) 308-3300 Service Area 

(PDF)

Contact Website

Salt Lake City 1020 North Flyer 

Way

(801) 257-5020 Service

Area (PDF)

Contact Website

Salt Lake City, UT 

84116

Washington, DC 13873 Park 

Center Road 

Herndon, VA 

20171

(703) 230-7664 Service Area 

(PDF)

Contact Website
Richmond 5707 Huntsman 

Road Richmond, 

VA 23250

(804) 222-7494 Service Area 

(PDF)

Contact Website

Seattle 1601 Lind Avenue 

Sw

(425) 227-2813 Service

Area (PDF)

Contact Website

Renton, WA 

98057

Spokane 6133 East Rutter 

Avenue

(509) 532-2340 Service

Area (PDF)

Contact Website

Spokane, WA 

99212

Charleston 301 Eagle 

Mountain Road 

Charleston, WV 

25311

(304) 347-5199 Service Area 

(PDF)

Contact Website

Milwaukee 4915 South 

Howell Avenue 

Milwaukee, WI 

53207

(414) 486-2920 Service Area 

(PDF)

Contact Website

Casper FSFO Denver951 

Werner Court 

Casper, WY 82601

(800) 325-5785 Service Area 

(PDF)

Contact Website