1

Saint Francis University

Unmanned Air Systems

Operations Manual

2

Change Log

Revision Date Summary of Changes

May 3, 2019 Original document published

May 17, 2019

Updated 1.1(3), 4.1(1), 6.2(3) to reflect

new FAA recreational flight rule; updated

introduction to part 7.

June 21, 2019 Updated 7.1 to resolve contradictory

statement

August, 7 2019 Updated 7.3 and 11.4 to reflect changes in

the SFU policy “Use of UAS”

3

1. Introduction ------------------------------------------------------------------------------------------------ 4

1.1. References --------------------------------------------------------------------------------------------------- 4 1.2. Terms and Abbreviations -------------------------------------------------------------------------------- 4

2. UAS Operations Manager ------------------------------------------------------------------------------- 6

2.1. General -------------------------------------------------------------------------------------------------------- 6 2.2. Duties and Responsibilities ----------------------------------------------------------------------------- 6 2.3. Delegation of Duties --------------------------------------------------------------------------------------- 6

3. Document Precedence and Distribution ------------------------------------------------------------- 7

3.1. General -------------------------------------------------------------------------------------------------------- 7 4. Flight Authorization -------------------------------------------------------------------------------------- 8

4.1. Educational Use of UAS ----------------------------------------------------------------------------------- 8 5. Air Vehicle Requirements ------------------------------------------------------------------------------- 9

5.1. Aircraft Registration and Marking -------------------------------------------------------------------- 9 5.2. UAS Functional Check Flights and Readiness for Flight ------------------------------------------ 9 5.3. Weight & Balance Marking ------------------------------------------------------------------------------ 9 5.4. Documentation ------------------------------------------------------------------------------------------- 10

6. Aircrew ----------------------------------------------------------------------------------------------------- 11

6.1. General ------------------------------------------------------------------------------------------------------ 11 6.2. Pilot ---------------------------------------------------------------------------------------------------------- 11 6.3. Visual Observer ------------------------------------------------------------------------------------------- 11 6.4. Sensor Operator ------------------------------------------------------------------------------------------ 12 6.5. Mission Director ------------------------------------------------------------------------------------------ 12 6.6. Contractors, Students and non-Regular Employees -------------------------------------------- 12

7. Flying Site Requirements ------------------------------------------------------------------------------- 13

7.1. Flying Site Preparation --------------------------------------------------------------------------------- 13 7.2. Day of Flight ----------------------------------------------------------------------------------------------- 14 7.3. Maintaining Separation from Non-participants ------------------------------------------------- 15 7.4. Training and Maintenance Flight Requirements ------------------------------------------------ 15

8. Flight Operations ---------------------------------------------------------------------------------------- 16

8.1. Advanced Preparations--------------------------------------------------------------------------------- 16 8.1.1. Flight Packet ----------------------------------------------------------------------------------------- 16

8.1.2. UAS Airworthiness --------------------------------------------------------------------------------- 17

8.2. Pre-Flight Planning & Brief ---------------------------------------------------------------------------- 17 8.3. In-Flight Procedures ------------------------------------------------------------------------------------ 19 8.4. Shutdown/Post-Flight ---------------------------------------------------------------------------------- 20

9. Abnormal and Emergency Flight Operations ------------------------------------------------------ 21

9.1. Emergency Procedures --------------------------------------------------------------------------------- 21 10. Tracking -------------------------------------------------------------------------------------------------- 22

11. Reporting Requirements ------------------------------------------------------------------------------ 23

11.1. Report Format ------------------------------------------------------------------------------------------- 23

4

1. Introduction

1. This operations manual governs Saint Francis University Unmanned Air Systems outdoor

operations in support of research and operations.

2. The purpose of this operations manual is twofold: first, to capture in one document the

combination of rules of and regulations governing UAS operations through FAA, state, and

Saint Francis University (SFU) into a single place; second, to guide the individual Saint

Francis University operator who seeks to fly UAS in achieving safe operations in full

compliance.

3. The development of UAS technology and accompanying policy is extraordinarily dynamic,

with changes to both occurring on a monthly basis. Therefore, this operations manual will be

a living, breathing document, undergoing regular change. Operators will need to verify prior

to each operation that they are complying with current policy.

4. This operations manual is accompanied by a series of checklists and additional packets (e.g.,

Mishap Plan) along with the SFU UAS Operations website for planning, tracking and

reporting, that together constitute the full UAS Operations Program.

1.1. References

1. FAA Part 107 Summary: https://www.faa.gov/uas/media/Part_107_Summary.pdf

2. FAA Advisory Circular 107-2:

https://www.faa.gov/documentlibrary/media/advisory_circular/ac_107-2.pdf

3. FAA Notice 84 FR 22552, Exception for Limited Recreational Operations of Unmanned

Aircraft: https://www.federalregister.gov/documents/2019/05/17/2019-10169/exception-

for-limited-recreational-operations-of-unmanned-aircraft

1.2. Terms and Abbreviations

Term Definition

COA Certificates of Waiver or Authorization (COA). COA is an authorization issued

by the Air Traffic Organization to a public operator for a specific UAS activity.

CFR Code of Federal Regulations (FAA regulations are under title 14, or 14 CFR)

PIC Pilot in Command

VO Visual Observer

NOTAM Notice to Airmen

FCF Functional Check Flight

NTSB National Transportation Safety Board

FAA Federal Aviation Administration

UAS Unmanned Aerial System

SO Sensor Operator

5

6

2. UAS Operations Manager

2.1. General

1. The University shall designate an individual to serve as the UAS Operations Manager. This

individual shall be responsible for and have authority over all UAS operations conducted

under this Manual. The UAS Operations Manager shall report to the Vice President for

Academic Affairs and the Office of Student Development.

2.2. Duties and Responsibilities

1. Develop and maintain the University’s UAS Operations Manual.

2. Promote UAS operations in support of the University mission that are safe, effective, and efficient.

3. Ensure that University faculty, staff, and students participating in University UAS operations comply with federal, state and local laws, applicable waivers, authorizations or letters of agreement, and this Manual.

4. Serve as the University’s primary point of contact with the FAA for issues relating to use of UAS on University Property or as part of University-Affiliated Activity.

5. Ensure compliance with FAA/NTSB reporting requirements.

6. Maintain records required under this manual and conduct periodic inspections of required

logbooks and forms to ensure accuracy and completeness.

2.3. Delegation of Duties

1. The UAS Operations Manager may delegate duties and responsibilities under this Manual to

qualified personnel at the University.

7

3. Document Precedence and Distribution

3.1. General

1. Along with applicable sections of 14 CFR and state and local laws, operators will comply

with this manual and operating manuals for the UAS. The latter items will likely overlap in

content, so in the event of a conflict, the precedence is this operating manual, then the UAS-

specific operating manual.

2. A master copy of the current version of this Manual will be maintained by the UAS

Operations Manager. A copy of this Manual will be furnished to

a. The Pilot-in-Command (PIC)

b. Visual Observers (VO)

c. Sensor Operators (SO)

d. Mission Directors (MD);

e. Maintenance Personnel;

f. Any other University faculty, staff or student necessary for the safe conduct of flight

operations or flight planning.

3. It is the responsibility of all persons receiving copies of this Manual to ensure that they are

current and have all revisions. The latest version will be readily available on the SFU UAS

Share site.

8

4. Flight Authorization

1. The FAA only governs outdoors flight. Indoors flight at Saint Francis University is governed

by the policy entitled “Use of Unmanned Aircraft Systems (UAS)”.

4.1. Educational Use of UAS

1. FAA regulation concerning the educational use of UAS follows directly from the definitions

of 14 CFR 107 operations (e.g., flying in support of Saint Francis University sponsored

research or operations) and recreational operations (e.g., anything specifically done for

recreation). There are no exceptions (at the present time) for any specific, educational uses

of UAS. If you are not a licensed operator flying under 14 CFR 107 regulations, be sure to

comply with the following:

a. Fly only for fun or recreation

b. Follow the safety guidelines of a model aircraft community-based

organization

c. Fly at or below 400 feet when in uncontrolled airspace (Class G)

d. Fly within visual line-of-sight, meaning you as the drone operator use your

own eyes and needed contacts or glasses (without binoculars), to ensure you can see

your drone at all times.

e. Never fly near other aircraft.

f. Never fly over groups of people, public events, or stadiums full of people.

g. Never fly near or over emergency response efforts.

9

5. Air Vehicle Requirements

5.1. Aircraft Registration and Marking

1. All aircraft operated on the property of Saint Francis University or by its employees must be

registered with the FAA in accordance with 14 CFR 107.13 (as applicable), and have

identification markings in accordance with 14 CFR part 45, subpart C or part 47.1 The

registration number only needs to be located on the UAS – it does not need to be visible

from the exterior.

a. If the UAS is required to be registered with the FAA, the aircraft must also be

registered with the University.

5.2. UAS Functional Check Flights and Readiness for Flight

1. 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 check flight (FCF) prior to conducting further operations. FCFs may only be

conducted by a PIC with a VO and must remain at least 200 feet from other people. The

FCF must be conducted in such a manner so as to not pose an undue hazard to persons and

property.

a FCFs are defined as a non-revenue flight which has the sole purpose of checking for

the correct airborne function of certain aircraft systems.

2. The operator is responsible for maintaining and inspecting the UAS to ensure that it is in a

condition for safe operation.

3. Prior to each flight, the PIC must conduct a pre-flight inspection and determine the UAS is

in a condition for safe flight. The pre-flight inspection must account for all potential

discrepancies, e.g., inoperable components, items, or equipment.

4. The operator must follow the UAS manufacturer’s maintenance, overhaul, replacement,

inspection, and life limit requirements for the aircraft and aircraft components.

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

bulletins.

5.3. Weight & Balance Marking

1. All UAS shall be marked with CG limits on the airframe. PIC shall verify UAS is within

weight & balance limitations prior to flight.

1 https://www.faa.gov/uas/registration/

10

5.4. Documentation

1. UAS-Specific Manuals include all manuals and publications provided by the relevant UAS

manufacturer (or generated if operating an SFU-designed and fabricated UAS). Examples

include:

a. User Manuals

b. Instruction Manuals

c. Training Manuals

d. Flight Manuals

e. Operations Manuals

f. Pilot Operating Handbooks

g. Component Maintenance Manuals

h. Service/Safety Bulletins

i. Service Information Letters

2. The UAS and all control systems necessary for flight shall be operated and maintained in

accordance with the most recent revision of the relevant UAS-Specific Manual.

11

6. Aircrew

6.1. General

1. The term “aircrew” includes pilots, observers, sensor operators, mission directors and any

other personnel necessary for the safe conduct of flight operations.

2. The University may rely upon prior training and experience for purposes of qualifying

aircrew, to the extent that prior training and experience meets the minimum requirements of

this Manual.

3. All Flight Personnel must be in a condition fit to perform their duties safely under this

Manual. No person may act as a member of the Flight Personnel if they are under the

influence of any drug, alcohol, or medication likely to impair their performance of duties.

6.2. Pilot

1. The Pilot of the UAS shall be the Pilot-in-Command (PIC) and who is directly responsible

for, and is the final authority as to, the operation of that aircraft.

2. If required, the PIC must hold a valid UAS license as described by 14 CFR 107 Subpart C.

3. The PIC must successfully complete the SFU UAS Compliance Test prior to flight. This

does not replace the FAA knowledge test required for recreational pilots.

4. The PIC shall demonstrate knowledge of the particular UAS’s normal and emergency

operating procedures prior to flight operations.

6.3. Visual Observer

1. The Visual Observer (VO) is responsible for assisting the PIC in maintaining situational

awareness and complying with his/her “see-and-avoid” duties. All flights under 14 CFR 107

require a VO. Observers must maintain sufficient proximity to the PIC and to the flight

operation to exercise “see-and-avoid” activities by scanning the area around the UAS for

potentially conflicting traffic or other hazards to the safety of the flight.

2. The VO must successfully complete the SFU UAS Compliance Test prior to flight.

3. VOs must maintain verbal contact with the PIC at all times and be able to advise the PIC of

any hazards that arise during flight. Electronic messaging or texting is not permitted during

flight operations.

4. The VO, with vision that is unaided by any device other than corrective lenses, shall maintain

visual contact with the aircraft as well as diligent visual lookout for any airborne or ground-

based threats.

5. Prior to acting as a VO, the person shall demonstrate to the PIC the following:

12

a. Sufficient knowledge of the airspace in which the flight will be performed to permit

them to adequately assess the risks posed by other aircraft or objects. At a minimum,

Observers will have training in the rules and responsibilities described in 14 C.F.R.

107 Subpart B.

b. A thorough understanding of all normal, and emergency operational aspects of the

UAS being flown.

6.4. Sensor Operator

1. Sensor Operators control and direct any remote sensing equipment or mission payloads

carried by the UAS.

2. Sensor Operators do not have the authority to require the PIC to maneuver the aircraft in

any unsafe manner, or in any manner that violates the CFRs.

3. Sensor Operators must follow all direction from the PIC.

4. Prior to flying, Sensor Operators must demonstrate to the PIC that they are familiar with the

contents of this Manual, as well as the UAS-Specific Manual for the UAS to be flown.

6.5. Mission Director

1. The Mission Director (MD) is an optional role; a person responsible for the overall conduct

of the event. An example of a MD is a scientist employing a UAS for remote sensing, who is

not qualified as a PIC or is not serving as the pilot during the event.

2. The MD does not have the authority to require the PIC to maneuver the aircraft in any

unsafe manner, or in any manner that violates the CFRs.

3. The MD shall not direct the VOs. The VOs remain responsible to the PIC.

4. Prior to flying, the MD must demonstrate to the PIC that they are familiar with the contents

of this Manual, as well as the UAS-Specific Manual for the UAS to be flown.

6.6. Contractors, Students and non-Regular Employees

1. If a student is flying in an educational capacity as per Section 4.1, then they are covered

under the FAA hobbyist rules for flying. If the student is flying under a funded research

project, then they fall under the requirements of 14 CFR 107 (e.g., license, currency,

medical).

2. All faculty, including adjunct faculty and faculty not being compensated, fall under 14 CFR

107 unless they are supporting students as outlined in 4.1.

3. Contractors are permitted to operate Saint Francis University UAS, but must comply with

the Saint Francis University UAS Operations Manual (as applicable). Additionally, the

contractor must meet insurance requirements.

13

7. Flying Site Requirements

Please note that, while the following requirements are necessary for SFU operations, no

requirements in this section supersede FAA regulations. It is the responsibility of the PIC to

ensure compliance with FAA regulations for all operations.

7.1. Flying Site Preparation

1. Prior to flying at a site, the following must be established:

a. The site must be at private or controlled-access property with documented

permission from the property owner/controller or authorized representative (email is

acceptable).

b. All operations require identifying a take-off zone, landing zone, and lost

link/emergency termination zone prior to flight. These zones may be the same

location or different locations depending on the needs of the mission.

c. To operate at an airport without an operating control tower, you need radio

capability to announce operations in accordance with the FAA Aeronautical

Information Manual (AIM) 4-1-9 Traffic Advisory Practices at Airports without

Operating Control Towers.

d. The PIC must submit the following information to the UAS Operations Manager,

Campus Police, and the Office of Student Development:

i Name of the PIC

ii Contact information of the PIC

iii Date of intended flight

iv Projected beginning/end time of flight

v Location of intended flying field

1 If not on SFU property: the lat-long coordinates of the bounding

polygon for the flying site must be provided to the UAS Operations

Manager, via coordinate list or shapefile suitable for use in a GIS

application

2 If on SFU property, the name of the intended flight area (as designated

on the Restricted Area map)

vi Make/model of aircraft to be flown

vii Copy of authorization for flight in a Restricted Area (if applicable)

14

2. If the UAS will be flying in any restricted area (as designated by the UAS Operations

Manager), the PIC is required to provide written permission from the applicable facilities

director. These directors are named as follows:

a. Athletics facilities and fields: Assistant Director of Athletics for Facilities and

Operations

b. Academic buildings, University Mall area: Vice President for Academic Affairs

c. Residence Halls, JFK Student Center, and all other facilities: Dean, Office of

Student Development

3. Use of the unmanned aircraft system for video or electronic surveillance must comply with

Saint Francis University’s Media Photography Video Policy. All use of UAS for this purpose

must submit to the following approval process prior to use. Written verification from each

person or department named is required to gain approval for flight.

a. Verification of compliance with Media Photography Video Policy: Marketing

b. Verification of compliance with Use of Unmanned Aircraft Systems Policy:

UAS Operations Manager

c. Verification of Title IX compliance: SFU Title IX Coordinator

d. Approval of flight mission: Vice President for Academic Affairs (students, faculty,

and staff) or SFU Risk Manager (third party operators)

4. UAS shall not be used to monitor or record areas where there is a reasonable expectation of

privacy. These areas include but are not limited to restrooms, locker rooms, individual

residential rooms, changing or dressing rooms, and health treatment rooms.

5. UAS shall not be used to monitor or record residential hallways, residential lounges, or the

insides of campus daycare facilities.

6. UAS shall not be used to monitor or record sensitive institutional or personal information

that may be found, for example, on an individual's workspaces, on computer or other

electronic displays.

7.2. Day of Flight

1. The following steps are required:

a. Permission to fly at the site from the owner reconfirmed (verbal or written).

b. Check to see if there are any NOTAMs issued by other parties that would impact on

the safety of the proposed flight

c. Weather must be confirmed visual meteorological conditions and have the ability to

operate no less than 500’ below and 2,000’ horizontally from clouds, and have 3

15

statute miles visibility from the PIC. The forecasted surface winds must also be less

than the rated wind resistance for the UAS.

d. Prior to operation, all flight zones (takeoff, landing, lost comms/terminate) shall be

cleared of all nonparticipating persons. Markings and other appropriate measures will

be taken to ensure that persons do not enter these areas while the operation is in

progress.

7.3. Maintaining Separation from Non-participants

1. All Flight operations must be conducted at least 200 feet from all nonparticipating persons

(The PIC, VO, operator trainees or essential persons are not considered nonparticipating

persons under this exemption), vessels, vehicles, and structures unless:

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

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

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

where nonparticipating persons leave such protection and are within 200 feet of the

UAS, flight operations must cease immediately in a manner ensuring the safety of

nonparticipating persons; and

e. The owner/controller of any vessels, vehicles, or structures has granted permission

for operating closer to those objects and the PIC has made a safety assessment of the

risk of operating closer to those objects and determined that it does not present an

undue hazard.

7.4. Training and Maintenance Flight Requirements

1. If it is a training flight, then there is a 200’ standoff requirement from all nonparticipating

persons, vessels, vehicles, or structures. Also, the flight requires sufficient altitude to allow

for, if a power unit fails, an emergency landing without undue hazard to persons or property

on the surface.

2. Functional test flights may only be conducted by a PIC with a VO and must remain at least

200 feet from other people. The functional test flight must be conducted in such a manner

so as to not pose an undue hazard to persons and property.

16

8. Flight Operations

1. This section covers the events leading up to flight operations, their conduct, and post-flight

requirements. The focus is on the flow of events, with many of the details covered in the

related sections, e.g., site-specific or aircrew-specific details.

2. The development of UAS technology and accompanying policy is extraordinarily dynamic,

with changes to both occurring on a monthly basis. Therefore, this operations manual will be

a living, breathing document, undergoing regular change. Operators will need to verify

prior to each operation that they are complying with current policy.

3. Flight operations will either be for normal operations, for maintenance, or for training. A

normal flight operation is any flight that is not conducted for training or maintenance

purposes. Each has slightly different restrictions on who, where, and what conditions they

may be flown.

4. The PIC is prohibited from beginning a flight unless (considering wind and forecast weather

conditions) there is enough available power for the UAS to conduct the intended operation

and to operate after that for at least two minutes or with the reserve power recommended by

the manufacturer if greater.

8.1. Advanced Preparations

1. Prior to flight operations at a site, the flying site must the requirements of Section 7, the

UAS must meet the requirements of Section 5, and the aircrew must meet the requirements

of Section 6.

2. The operator will confirm permission to operate at the site for each flight event.

8.1.1. Flight Packet

1. All flight operations shall have a Flight Packet with them. The Flight Packet shall contain:

a. Name and certificate number (as applicable) of the PIC;

b. A Sectional Map or covering the geographic location of the flights (if outdoors and not

on SFU property);

c. Other maps as required to ensure compliance;

d. Contact information for key personnel to include the University UAS Operations

Manager, Saint Francis University police, and local first responders such as fire and

rescue or police;

f. This Operating Manual;

g. Pilot Operating Handbook for the AVs, along with any other manuals required to

operate the AVs or their payloads;

17

h. Contact information for local ATC controlling facility (if applicable);

i. The COA governing the flight (if applicable);

j. The application for the governing COA (if applicable);

k. The NOTAM for the flight operations (if applicable);

l. Documentation verifying that permission has been given to fly from a particular site (if

applicable).

2. The Flight Packet should be kept with the PIC at the ground control station during flight

operations.

8.1.2. UAS Airworthiness

1. Prior to each flight the PIC shall inspect the UAS to ensure it is in a condition for safe flight.

If provided, the PIC shall use the manufacturer’s preflight checklist for inspecting the UAS.

If a manufacturer’s checklist is not provided, the PIC is responsible for adapting the

checklist provided on the SFU UAS Operations website.

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

3. The Ground Control Station, if used, must be included in the preflight inspection.

8.2. Pre-Flight Planning & Brief

1. The following topics will be covered in a pre-flight brief. For situations where the

conditions warrant (e.g., change in mission, crew, weather, site) the brief will be

repeated. All participants in the event must participate in the brief, at a minimum via

voice, ideally in person.

2. General

3. Type of flight: training, maintenance, or normal. Note appropriate restrictions

4. UAS status

i. Power

ii. CG

iii. Recent maintenance

5. Aircrew

i. Ratings

18

ii. Currency

iii. Training/currency requirements

6. Site

i. Permissions

ii. Boundaries

iii. Permanent and temporary obstacles

iv. Special restrictions

v. Nonparticipating personnel

vi. Nearby airports or areas of air traffic

7. COA operating under, and its restrictions (if applicable).

8. Launch and recovery information.

9. Active NOTAMs

3. Mission

1. Primary mission

2. Secondary mission

3. Times on and off mission

4. Crew coordination (who does what during the mission)

4. Weather

1. Current observation

2. Weather forecast covering the event

3. Verify VFR weather minimums are in place

4. Impact of weather on operations

5. Communications

1. Participants

2. Frequencies if radio required

19

3. Other communications means between participants (note: PIC and VO must

communicate audibly)

6. Navigation and Flight Planning

1. Departure

2. Mission route

3. Recovery

7. Crew Coordination (who does what and when)

1. Taxi/Takeoff/Launch

2. Enroute/climbout

3. Mission-specific tasks

4. Recovery/landing

8. Emergencies

1. Mission abort criteria

2. Aborted launch

3. Loss of power on takeoff

4. Loss of power at altitude

5. Lost comms – autopilot

6. Lost comms – manual

7. Landing emergencies

8. Contaminated site (personnel, vehicles)

9. Abort for manned aircraft or other AVs in operating area

8.3. In-Flight Procedures

1. All flight operations will be conducted in accordance with the applicable UAS-Specific

Manual.

2. All Flight Personnel shall remain at their station during takeoff, landing, recovery, and other

critical phases of flight, except when performing those duties required for the safe operation

of the aircraft.

20

3. The PIC shall continuously ensure that the UAS maintains a 2 minute power reserve, or the

reserve power recommended by the manufacturer if greater. The PIC shall terminate the

flight and land the UAS at any time it appears that the required battery reserves cannot be

maintained. When terminating a flight, the primary concern shall be the safety of

nonparticipating persons.

4. Manned operations always have the right of way. The UAS must remain clear and give way

to all manned aviation operations and activities at all times.

5. The UAS may not be operated by the PIC from any device or vehicle that is in motion.

6. For tethered UAS operations, the tether line must have colored pennants or streamers

attached at not more than 50 foot intervals beginning at 150 feet above the surface of the

earth and visible from at least one mile. This requirement for pennants or streamers is not

applicable when operating exclusively below the top of and within 250 feet of any structure,

so long as the UAS operation does not obscure the lighting of the structure.

7. The PIC must abort the flight in the event of unpredicted obstacles or emergencies.

8. If the UAS loses communications or loses its GPS signal, the UAS must return to a

predetermined location within the private or controlled-access property.

9. When operating in the vicinity of an airport without an operating control tower, announce

your operations in accordance with the FAA Aeronautical Information Manual (AIM) 4-1-9

Traffic Advisory Practices at Airports without Operating Control Towers.

8.4. Shutdown/Post-Flight

1. UAS shutdown and post flight actions will be taken in accordance with the UAS-Specific

Manual.

2. If the final flight of the period, deactivate the NOTAM (as applicable). Note: NOTAMs can

span multiple days, so only deactivate if the all flying activities are complete.

3. In the event of an incident, the PIC shall complete the Incident Report Form located on-line

at the SFU UAS Operations website, and will notify the UAS Operations Manager prior to

notifying the FAA (if applicable). If the UAS Operations Manager cannot be reached, then

send immediately to the FAA (if applicable).

4. In the event of a mishap, the PIC shall activate the Post-Mishap Plan (as described in section

12 of this document) and follow its procedures and timelines to the letter.

21

9. Abnormal and Emergency Flight Operations

9.1. Emergency Procedures

1. In an emergency situation involving the safety of persons or property, which requires

immediate decisions and actions, the PIC or any other appropriate Flight Personnel member

may take action that is considered necessary under the circumstances to ensure safety. Flight

personnel may deviate from prescribed operations procedures and methods, weather

minimums, CFRs, this Manual, etc., to the extent necessary, in the interest of safety. Flight

Personnel shall keep the appropriate ATC facilities fully informed when an in-flight UAS

emergency could potentially impact operations of aircraft in navigable airspace.

9.2. Investigations

2. The University shall investigate and document any such deviations. The investigation will be

led by the UAS Operations Manager or their designated representative, with support from

other expertise as required.

9.3. Post-Mishap Plan

1. The Post-Mishap Plan, under separate cover, guides all of the immediate actions that need to

occur in response to a mishap event, either incident or accident. The Post-Mishap Plan

integrates with other policies on campus, which should be followed accordingly.

2. In the event of a mishap, the PIC will execute the immediate action checklist in the Post-

Mishap Plan.

22

10. Tracking

1. Saint Francis University UAS operations tracking will be accomplished through a set of

applications located at the SFU UAS Operations website. The applications will enable

tracking of on-campus flights by aircrew, site, air vehicle, and date. All records required to be

kept under this Manual will be maintained by the UAS Operations Manager.

23

11. Reporting Requirements

1. In the event of an accident during 14 CFR 107 operations, the operator/Saint Francis

University is required to notify the FAA. All accidents (including both 14 CFR 101 and 14

CFR 107 operations) must be reported to Campus Police immediately. Key definitions:

a. Accident: Unmanned aircraft accident means an occurrence associated with the

operation of any public or civil unmanned aircraft system that takes place between

the time that the system is activated with the purpose of flight and the time that the

system is deactivated at the conclusion of its mission, in which:

i. Any person suffers death or serious injury (per AC 107-2 part 4.5)2; or

ii. The aircraft has a maximum gross takeoff weight of 300 pounds or greater

and sustains substantial damage.

2. The first step in any accident is to activate the Pre-Mishap Plan and follow its directions.

3. All incidents (including both 14 CFR 101 and 14 CFR 107 operations) must be reported to

Campus Police immediately. Key definition:

a. Incident: an occurrence other than an accident associated with the operation of an

aircraft, which effects or could effect the safety of operations. For UAS, this

includes occurrences such as airspace violations, property damages, and lost-link

events.

4. All accidents with injuries or property damage will also be reported to Saint Francis

University’s insurance provider through the Saint Francis University Risk Manager.

11.1. Report Format

1. A standard report form will be used for all UAS accident reports, and is available on the SFU

UAS Operations webpage. The following data elements will be in the report:

a. Report type (accident or incident)

b. Submission date

c. Event date (local)

d. Event local time

e. Exemption#/COA

f. Aircraft operator

2 https://www.faa.gov/documentlibrary/media/advisory_circular/ac_107-2.pdf

24

g. Proponent (UAS Operations Manager)

h. Submitter (PIC responsible for completing form)

i. Description of Accident

j. City

k. State

l. Reference to geographical point

m. Latitude/Longitude

n. Flight # on Day of Incident

o. Flight Duration (total # of minutes in numeric)

p. Class of Airspace

q. Phase of flight

r. Weather

s. Registration number

t. Aircraft make

u. Aircraft model

v. Ground Control Station (and location if different)

w. PIC name

x. Visual Observer name

y. Other aircrew (role/name)

z. Aircraft missing (true/false)

aa. Aircraft damaged (none, minor, substantial, destroyed, unknown)

bb. Flight activity (training, FCF, specific mission)

cc. Flight phase (taxi, takeoff, approach, landing, in-flight, unknown)

dd. Lost Link Event Descriptions

ee. Deviations from ATC clearance, COA, LOA, or Exemption: Descriptions

Accident-specific Entries

25

ff. Max injury (none, minor, serious, fatal, unknown)

gg. Fatality (true/false)

hh. Flight crew injuries and type (e.g., 3/none, 2/serious)

ii. Other ground personnel injuries and type

jj. Explosives, radioactive materials, or other dangerous articles on board

kk. Pictures of accident site, aircraft, etc.

Insurance-specific Entries

ll. Witnesses (name/address/phone)

mm. Contact info of injured personnel (name/address/phone, injury, medical aid

rendered)

nn. Property damage contacts (name/address/phone, damage type, value if known)