wsu research | washington state university€¦ · web view2015. 1. 6. · a prearranged plan of...

Unmanned Aircraft Systems (UAS)

Standard Operating Procedures

Version 2.0

6 January 2015

WSU UAS SOP Version 2.0

Youtube video link - https://www.youtube.com/watch?v=alrNpyTEUYQ

https://www.youtube.com/watch?v=mu799aPVyvk

Table of Contents

Sections

Section 1: General/Background/Responsibilities ………….…………………………… 3

Section 2: Training Requirements/Certifications ………….…………………………… 4

Section 3: Unmanned Aircraft Systems (UAS) Requirements/Certifications…….…….. 6

Section 4: Certificate of Authorization (COA) Process ………….……………………... 7

Section 5: Communications Systems Requirements ……………………………………. 9

Section 6: Pre-Mission/Flight Planning …………………………………………………. 10

Section 7: UAS Operations/Safety Procedures ………………………………………….. 12

Section 8: UAS Emergency Procedures …………………………………………………. 15

Section 9: Downed UAS Recovery Procedures/Environmental Impacts ………………... 17

Section 10: Privacy Rules/Considerations ……………………………………………….. 18

Section 11: Public Awareness ……………………………………………………………. 20

Section 12: Federal Aviation Administration Reporting Requirements ………………….. 21

Section 13: WSU Reporting Requirements ………………………………………………. 22

Appendices

A. COA Checklist ……………………………………………………………………….. A-1

B. List of WSU Certified Pilots/Assigned UAS Group …………………………………. B-1

C. Acronyms and Abbreviations ………………………………………………………… C-1

D. FAA References/Rules and Regulations ……………………………………………… D-1

E. Points of Contact List …………………………………………………………………. E-1

2

https://www.youtube.com/watch?v=mu799aPVyvk

https://www.youtube.com/watch?v=alrNpyTEUYQ


Section 1: General/Background/Responsibilities

This Standard Operating Procedures (SOP) document has been developed to guide and support

ongoing WSU research activities that include the use of unmanned aircraft systems (UAS). The

SOP is designed to be a ‘living’ document, with updates made on a regular basis (as driven by

changes to FAA regulations, feedback from users, and lessons learned in the field). It will serve

as the common core document, from which SOP addendums for specific UAS operations will be

developed.

This SOP represents WSU’s standing rules and procedures for all UAS users supporting WSU

funded activities. Although it has many purposes, its primary is safety of flight and risk

mitigation. It is important to keep in mind that each UAS and each UAS operating area will have

its own challenges. As such, AT NO TIME does this SOP override WSU UAS user responsibility

to ensure safety of flight. When ongoing operational use appears to require a deviation from this

SOP, or any authorized addendum thereto, the user is to cease all operations and immediately

contact the WSU UAS Operations Advisor for further guidance.

This document has been issued, and will be maintained, by the WSU UAS Operations Advisor. It

is the responsibility of all WSU staff involved with UAS operations to be fully familiar with this

document prior to beginning the UAS approval process.

This SOP was developed as a summation of operating procedures pertinent to WSU UAS

operations. It remains the responsibility of WSU UAS users to be fully aware of current FAA

directives, notices and regulations, especially those listed in Appendix D. At no time does this

SOP (or an addendum to this SOP) overrule FAA directives, notices and regulations; when a

conflict between this SOP and FAA documentation is found, report such conflicts immediately to

WSU UAS Operations Advisor for review.

3


Section 2: Training Requirements/Certifications (People Stuff)

In order to be a UAS Pilot in Command (PIC) of a Group 1 or Group 2 UAS, current FAA

requirements call for both the successful completion of the Private Pilot written examination and

a current Second Class Medical Certificate for UAS flights that are:

Below 400 feet;

No closer than 5 NM from any FAA-designated airport or heliport;

Outside of congested areas;

Occurring in sparsely populated Class G airspace; and are,

Line of sight (LOS) operations no further than ½ NM laterally from the PIC.

Other types of UAS operations require the PIC to have a minimum of a Private Pilot certificate

and are not currently authorized by WSU under this SOP.

In addition to the above, WSU UAS PIC’s must have the following training completed prior to

beginning the COA process:

Normal, abnormal, and emergency procedures in the UAS being operated;

Manufacturer-specific training (if available);

Demonstrated flight proficiency;

Certification/testing of PIC proficiency in the UAS being used for research; and,

Completion of the WSU UAS Operations Course.

Documentation of pilot training/certification requirements must be provided to the WSU UAS

Flight Operations Advisor prior to UAS users commencing the COA application process.

Required flight time can be done as part of a hobby club or through personal UAS use;

consideration for reduced flight time requirements in light of qualifying simulator activity will be

taken for consideration.

All WSU Visual Observers (VOs) must pass either the Sport Pilot or Private Pilot written

examination, as well as hold a current Second Class Medical Certificate. Additionally, VOs and

Principal Investigators (PIs) must complete the WSU UAS Operations Course prior to being

assigned/certified by WSU as a VO or PI. This will include UAS operations specific training in

communications, scanning, and reporting procedures, along with training on specific rules and

responsibilities outlined in 14 CFR 91.111 (Operating Near Other Aircraft), and 14 CFR 91.113

4


(Right-of-Way Rules). The aforementioned must be completed prior to beginning the COA

application process.

All WSU UAS PICs must show currency in their pilot certificates and log books, including all

required bi-annual certification and any associated medical certification (if required by the FAA),

prior to fulfilling the role of a WSU UAS PIC. UAS PICs without a Private Pilot certificate must

retake/pass the Private Pilot written examination every 24 months. In addition, all WSU UAS

PICs, VOs and PIs using UAS for their research must retake the WSU UAS Operations Course

every 24 months.

The Each local WSU UnitOffice of ___________ is responsible for maintaining records of all

WSU UAS PICs, VOs and PIs, including copies of all training certificates, logbook, and other

endorsements.

Note: WSU UAS training/certification requirements will be updated as changes occur to FAA

regulations, with the best interest of safe operations and risk mitigation in mind. Contact the

WSU UAS Flight Operations Advisor for the latest qualifications checklist prior to beginning the

COA process.

5


Section 3: UAS Requirements/Certifications (Aircraft Stuff)

According to FAA Directive N8900.227, “All UAS must be in an airworthy condition to conduct

flight operations in the [National Airspace System] NAS.” The FAA considers a UAS in

airworthy condition for COA purposes when:

The UAS has been issued the appropriate FAA type certificate, and/or

The UAS meets the applicable standards and requirements of the operating agency

(WSU) and is capable of operating in compliance with the applicable requirements in

FAA Federal Aviation Regulation (FAR) Part 91.

There is no set airworthiness path in place specifically for UAS; the FAA will work with WSU

UAS users in the process, since requirements for UAS will differ from manned aircraft. Further,

the size of the UAS (Group level) has a direct impact on the level of certification required for

flight.

For complex UAS systems (which must be repaired by a maintenance technician), standards must

be in place and will be reviewed by the FAA as part of the COA process. For UAS with simple

repairs required (e.g., Group 1 quadrotor blade change-out, etc.), the process can be simply

documented within the SOP Addendum for the specific UAS.

WSU Office of _________________ is responsible for reviewing all airworthiness related

documentation prior to COA submission.

6


Section 4: Certificates of Authorization (COA) Process

COAs and waivers are issued by the Air Traffic Organization (ATO) to public operators for

specific UAS activities. The FAA initiates a comprehensive review of all COA applications,

including, but not limited to, both operational and technical issues. The FAA currently targets 60

days as a turnaround time for COA review/validation, at which point the COA may be approved

as submitted, approved with provisions or limitations, denied, or, a waiver of COA requirements

issued. No WSU UAS operations are allowed until the FAA has issued an approved COA (or

waiver) to the University – there are no exceptions to this rule.

WSU COA Process

1. WSU UAS user/applicant briefs the WSU UAS Operations Advisor on his/her UAS

operational needs.

[2.] The WSU UAS Operations Advisor briefs the WSU’s Director for the Office of Grant

and Research Development (OGRD) _______________ for permission for the

applicant to proceed with required application paperwork.

2.[3.] WSU UAS user/applicant completes all required training/certifications.

[4.] WSU UAS user is provided a COA account logon by the OGRD

Director___________; user then completes the online draft COA registration form.

3.[5.] WSU UAS applicant forwards the completed draft COA and SOP addendums to the

WSU UAS Operations Advisor for review.

[6.] Once the WSU UAS Operations Advisor determines the COA and SOP addendums

are complete, meeting both FAA and WSU requirements, the final draft COA is

forwarded to the OGRD Director________________ for final approval and release to

the FAA.

4.[7.] Once received, the FAA will complete an administrative/feasibility check of the

COA.

5.[8.] If the COA passes the administrative/feasibility check, the formal COA

review/validation process begins, with approval, disapproval, and/or feedback from the

FAA approximately 60 days from the start of this step.

[9.] Once a COA has been approved, the WSU UAS user must review all COA feedback

from the FAA, review the WSU UAS SOP (and any addendums) for changes that may

have occurred during (or as a result of) the COA process, and prepare a briefing for

both the WSU UAS Operations Advisor and the OGRD Director________________ as

7


to their updated UAS operations plan. Once done, the OGRD

Director_______________ will provide the final approval for operation of the UAS

under WSU authority.

The FAA has the authority to suspend, cancel or delay activities related to a COA, if terms of the

COA have been broken or safety has been compromised in the air or on the ground. Per FAA

Directive N8900.227, this includes, but is not limited to, the following:

1. Incidents or accidents occurring during UAS operations in the National Airspace

System (NAS);

2. Habitual noncompliance with administrative requirements, such as failure to provide

the FAA with monthly reports on the number of flights, pilot duty time, or unusual

equipment malfunctions (e.g., a malfunction or failure of ground control station (GCS)

flight control hardware or software (other than loss of control link); a power plant

failure or malfunction; a deviation from any provision contained in the COA);

3. Deviations from ATC instructions, operational, or coordination issues; and

4. Events of intermittent or persistent lost-link as described in the COA or events

determined to pose as a risk to the safety of the NAS.

Under rare circumstances, the FAA may waive the requirement for a COA and grant a waiver for

operations to occur. If this does happen, all requirements set forth in the original COA and during

the WSU UAS approval process will still apply to the WSU UAS user.

8


Section 5: Communications Systems Requirements

Unless otherwise approved, all WSU UAS operations will use currently approved UAS

(uplink/downlink) frequencies. These frequencies allow for unlicensed operation in the 900 MHz,

2.4 GHz, and 5.8 GHz frequency bands. If user requirements call for operating in any band other

than the aforementioned, the WSU UAS user must apply for either a Federal Communications

Commission (FCC) Experimental Radio License or Special Temporary Authority (STA).

Because operating frequencies of UAS links must be included in the COA, the WSU UAS user

must have proof of FCC approval for operation outside of unlicensed UAS bands prior to

beginning the COA process. A primary reason for requesting use outside the normal UAS

frequency bands is possible electromagnetic interference (EMI) between UAS

communications/control systems and other communications systems being used in the assigned

UAS operating area. It is the WSU UAS user’s responsibility to survey the operational area, as

needed, to confirm whether the frequencies selected are indeed usable in the operational

environment, due to EMI, terrain, etc.

WSU UAS PICs will use UNICOM as their primary mode of routine voice communications with

ATC and aircraft in the area. The same radio transceiver used for UNICOM will also be used for

emergency operations and communications with ATC. An active WSU FCC license will be

required for operation.

The VO, PI, sensor/payload operator, or any other person charged with providing see-and-avoid

(SAA) assistance must have immediate inter-communications capabilities with each other and the

PIC. This can be via separate very high frequency (VHF) communications or via cell phone.

In addition, all WSU UAS VOs and PIs onsite must monitor the same air traffic control (ATC)

frequencies being monitored by the UAS pilot (for WSU, normally UNICOM). Although only the

PIC will communicate with ATC, monitoring of that frequency will provide additional situation

awareness to all participants during the flight event. This will require each member of the UAS

team to possess either a scanner or aviation band transceiver.

Cell phones are not authorized as a primary method of communications between the PIC and

ATC unless authorized under Special Provisions of the COA; actual UAS flight and mission

required communications usage is governed by FAA § 91.21. Any electronic device that can

reasonably be expected to interfere with UAS uplink/downlinks shall be turned off during flight

operations.

9


Section 6: Pre-Mission/Flight Planning

Preflight planning is key to safe flight operations. Before each flight, the WSU UAS PIC, VO and

PI will work through the UAS flight plan, ensuring that the designated operating area is safe for

all users within that airspace. The WSU UAS PIC, VO and PI will:

1. Check all available aviation maps/charts, weather (via the Direct User Access Terminal

Service [DUATS]) Check Notice to Airmen (NOTAM) postings, and confirm that

NOTAMs related to WSU UAS operations have been properly disseminated and

posted

2. Check the Airport/Facilities Directory (AFD) and all other available information related

to the planned flight/assigned operations area

3. Notify airport managers and/or fixed-base operators (FBOs) adjacent to the active UAS

operating area, in order to ensure maximum situation awareness of ongoing activities

between WSU UAS operations and local airport authorities

4. Confirm that WSU UAS related announcements to Automated Weather Observation

System (AWOS)/Automatic Terminal Information Service (ATIS) devices are in effect

and being properly broadcast.

5. Perform all other necessary research in due diligence to ensure safety of flight and

optimize risk mitigation.

Crop dusting aircraft are active several months of each year in and around the areas anticipated for

use by WSU UAS operators. As such, commercial agricultural aviation operators will be

identified and notified in writing of all UAS test activities that could affect their operations.

Prior to and during UAS operations in forestry areas, WSU UAS users will coordinate with the

U.S. Forest Service to de-conflict UAS activity with the Forest Service rotary wing/fixed wing

activity, including firefighting aircraft. A similar courtesy will be afforded to U.S. Department of

Defense (DoD) assets, when COA operations have been approved for operation within a Military

Operations Area (MOA).

Throughout all UAS operations, the WSU UAS PIC, VO and PI will have the authority to stop a

launch or terminate a flight.

10


AT NO TIME will WSU UAS operations take place without all assigned personnel in place, as

dictated by the approved FAA COA, this WSU UAS SOP, and any SOP addendum for the

operation.

In accordance with FAR § 91.3, the WSU UAS PIC will be directly responsible for, and is the

final authority for the operation of his or her aircraft, as approved by the FAA COA and WSU.

11


Section 7: UAS Operations/Safety Procedures

All WSU UAS flights will be flown within visual line-of-sight (LOS) of the ground-based PIC

(airborne PIC operation is not authorized by WSU at this time).

The following operational/mission management restrictions apply to WSU UAS operations:

1. The assigned PIC has primary authority over all flight operations conducted in support of

research activities. The PIC assigned to the research project is the only person with

authority to approve flight operations.

2. A single PIC must be designated at all times.

3. Handoff to another PIC is allowed, using proper handoff techniques. For example:

PIC 1: “You have the aircraft.”

PIC 2: “I have the aircraft.”

PIC 1: “You have the aircraft.”

Failure to follow a ‘closed loop’ approach is a recipe for loss of UAS control.

4. The PIC of the UAS is directly responsible for, and is the final authority of, the operation

of that UAS.

5. A PIC may control only one UAS at a time.

6. A PIC cannot serve as a PIC and a VO at the same time.

7. With the exception of initial qualification training, pilots must be qualified on the UAS

being flown (as previously addressed).

The Principal Investigator (PI) is charged with oversight of flight operations supporting his/her

research, including safety, risk mitigation, public awareness, and privacy related issues. At

anytime, the PI has authority to halt or stop UAS flight in order to maintain safety of

flight/mitigate risks.

In accordance with FAA Directive N8900.227, a Visual Observer (VO) must be positioned to

“assist the PIC, to exercise the see-and-avoid responsibilities required by §§ 91.111, 91.113, and

91.115 by scanning the area around the aircraft for potentially conflicting traffic and assisting the

PIC with navigational awareness.” For WSU UAS operations, this role of VO shall not be

performed by the PI (since the PI is focused on data collection). Daisy-chaining of VO’s (for

extended LOS) is neither recommended by the FAA nor approved by this SOP.

12


The VO shall:

1. Assist the PIC in ensuring the UAS stays within set visual LOS boundaries.

2. Perform the role of VO from a location that allows complete situation awareness of the

UAS and other aircraft within the surrounding airspace. This includes assisting the PIC in

effective control of the UAS, through:

a. Determining the UA’s proximity to all aviation activities and other ground

hazards.

b. Complying with FAA §§ 91.111, 91.113, and 91.115

c. Preventing the UAS from creating a collision hazard, and

d. Informing the PIC before losing visual contact with the UAS and/or collision

hazards.

Per FAA Directive N8900.227,

Because of field of view and distortion issues with aids to vision such as binoculars,

field glasses, night vision devices, or telephoto lenses, these are allowed only for

augmentation of the observer’s visual capability; they cannot be used as the primary

means of visual contact. When using other aids to vision, VOs must use caution to

ensure the aircraft remains within normal visual line-of-sight of the observer. These

aids to vision are not to be confused with corrective lenses or contact lenses, which

do not alter the field of view or distort vision.

In the end, ensuring LOS and safety of flight is the responsibility of the PIC: supplemental

support by UAS team members is just that – supplemental.

Any WSU UAS that does not have a fully functional (automatic) flight termination system (FTS)

will be required to have a secondary, independent FTS that can be activated manually by the UAS

PIC. As all WSU operations will occur outside of 5 nm of airport boundaries and outside of

Class B, C and D airspace, universal communications (UNICOM) will be used to control the

airspace and handle de-confliction. In addition, positive radio contact must be maintained at all

times. In all cases, the use of electronic devices, other than for UAS flight and mission required

usage, will be selected in accordance with FAR 91.21, unless specifically authorized under Special

Provisions of the COA governing the flight operations.

13


All flight termination points not included in normal recovery points will be determined based

upon direct visual inspection via manned aircraft/ground observation. This list will be

promulgated prior to commencement of each flight, including location (Lat/Long/Elevation),

surrounding terrain, access roads, fire risks/levels, and environmental impacts. Selection will be

based first and foremost upon prevention of loss of life or damage to persons or property in the air

or on the ground, along with such factors as weather (snow, heavy mud, ice, flooding, and fire

hazards), agricultural activity (fallow or seasonally vacant fields versus active farming),

unexpected human activity (e.g., unplanned campers), and access to the recommended flight

termination points (roads, etc.) for aircraft recovery/HAZMAT operations.

Prior to any flight (or repeated series of flights), WSU UAS users/staff will notify local public

safety officials (in writing) with pertinent information, including all planned UAS schedules and

emergency termination points. In addition, homes and businesses located in an area where an off-

normal event is occurring will be contacted via phone (or in person) and provided with

instructions on what to do if the UAS has impacted at their location.

14


Section 8: UAS Emergency Procedures

All WSU UAS will require an FTS. Specific Fail-Safe/FTS will vary based upon the UAS design

and implementation, varying from hold-mode (continued flight on current path) to full fail-safe

mode of operation. For WSU UAS operating areas, hold-mode will not be allowed, as it could

allow the UAS to depart the area in uncontrolled flight. When autonomous return (return home)

is available, it shall be used, followed by throttle down and orbit mode, and, as a last resort,

followed by controls being set to implement an immediate ground impact/crash to ensure that the

UAS stays within the assigned operational area. All WSU UAS users must be able to show a

graceful degradation to lesser modes of operation, in case of partial UAS control system failure.

This could range from climb and hold, to automatic navigation through a series of waypoints to

bring the UAS to a safe location for autonomous recovery. For fixed wing (or long range rotary

wing) engine to idle will occur first, in order to provide additional time to attempt to reestablish

command link interface. Note: Until further notice, fully autonomous flight by WSU UAS is not

authorized, nor will a COA application addressing autonomous flight receive approval by WSU

for forwarding to the FAA.

Ultimately, each UAS emergency contingency plan must be based on the specific UAS for the

specific operating area. The WSU UAS user will draft addendums to this SOP, for final

review/approval by WSU UAS Operations Advisor, that clearly meet the requirements of this

SOP and ensure maximum safety of flight and graceful degradation of the UAS system.

If lost-link occurs and the radio-control system does not employ its assigned fail-safe mode of

operation, the UAS control system will be required to place control surfaces of the UAS into a

continual turning position at reduced throttle level in order to maintain the UAS within the

assigned operating area, while the PIC attempts to reestablish the link.

If the UAS fails to respond to commands from the PIC, the following action will be immediately

taken:

1. WSU Controller/PIC will contact cognizant airspace ATC on the assigned frequency,

providing notification of fly-away/lost-link condition, and the UAS’s last known

position, heading, airspeed, and altitude.

2. UAS Controller/PIC will broadcast a warning on the local UNICOM frequency every 3

minutes, stating the type of UAS, and its estimated location/altitude of the UAS.

Additional broadcasts on other frequencies will be made when necessary, based upon

15


local airspace activity.

3. WSU UAS onsite users will contact the standby chase team (whether on the ground or in

the air), to initiate a search for the UAS, unless the UAS has remained within visual sight

of the UAS PIC. Chase team members cannot include the UAS PIC or VO.

4. If communications are reestablished, the UAS will be recovered and all future flight

operations will cease. A full written report will be provided to the WSU UAS Operations

Advisor within 24 hours of the incident, in order to determine the cause of the problem

and confirm whether operations can continue.

16


Section 9: Downed UAS Recovery Procedures/Environmental Impacts

Recovery of downed UAS assets will be performed in coordination with local county emergency

crews in order to ensure that all applicable HAZMAT requirements are met, in the same manner

as that of a downed manned aircraft. A prearranged plan of action (pre-accident plan) will be

established prior to each flight, so that responsibilities for all recovery responders are clearly

defined. This may be as simple as a declaration of minimal HAZMAT impacts (i.e., a single

NiCad battery for a quadrotor), or extensive (i.e., a fixed-wing UAS with NiCad batteries, aviation

fuel and lubricant oil carried onboard).

At all times, the appropriate firefighting and HAZMAT equipment for the UAS operation being

conducted shall be carried by the WSU UAS team; a checklist of this equipment shall be added to

the SOP addendum for the operation.

Private property shall not be accessed until permission of the owner and/or occupants has been

granted.

17


Section 10: Privacy Rules/Considerations

WSU’s privacy rules are – in part – derived from current draft legislation being considered by

Congress, including MRW 13745 (sponsored by Senator Ed Markey of Massachusetts), and

House Bill 2178, cosponsored by Congresspersons Morris and Morrell of Washington. These

rules are neither cumbersome nor hard to follow, but they MUST be followed.

WSU UAS users will document the following for each flight (or series of flights):

1. Type of data to be collected (video, still pictures, etc.).

2. Data storage medium (onboard processor, ground station thumb drive, etc.).

3. Specific kinds of information/data that the WSU UAS research team might inadvertently

collect on an individual (or a group of individuals) not involved with the WSU

research/UAS operations.

Based upon such information, the following must be documented by the WSU UAS user, within

the SOP addendum, prior to completing the draft COA:

1. How the collection or retention of information or data that is unrelated to the

specified research will be minimized.

2. Whether such information or data might be sold, leased, or otherwise provided to

third parties, and if so, under what circumstances it might be so sold or leased;

3. The period for which such information or data will be retained, as well as how it will

be destroyed.

4. The possible impact the operation of the WSU UAS may have upon the privacy of

individuals;

5. The specific steps that will be taken to mitigate any possible unauthorized disclosure of

information or data (e.g., encryption methods and/or other security features);

6. A telephone number and email address that an individual with complaints about

WSU UAS operations may use to report such complaints, as well as to request

confirmation that personally identifiable data relating to such individual has been

collected;

7. A reasonable process for the individual to request to obtain such data in a timely

and an intelligible manner.

18


In all cases, WSU UAS users and staff shall design operations to minimize collection of

information and data unrelated to ongoing operations.

In addition, WSU UAS users shall:

1. Clearly and conspicuously label the UAS as being from WSU (with contact information

on the UAS);

2. Ensure consent for operation above private property, including the landowner and any

tenants who have a right to occupy the property, after having received actual notice that

the UAS is equipped with an imagery or other sensory device from which personal data

could inadvertently be collected; and,

3. Ensure that the WSU UAS is flown above public lands in a manner that does not

unreasonably interfere with the rights of others/not otherwise prohibited.

The WSU Office of __________ shall provide oversight of privacy issues for all WSU UAS

operations.

19


Section 11: Public Awareness

Maximizing public awareness of WSU UAS operations is a key part of successful UAS operations

within the community. General best-practice communications include:

1. Identifying a WSU spokesperson for each approved COA;

2. Developing a dedicated WSU UAS website with information about upcoming flights,

research being conducted, contact information, and an opportunity for visitors to take a

virtual look at the UAS being used – and the impact it will have on ongoing research;

3. Maintaining a list of frequently asked questions (and answers) available on the website;

4. Staging a yearly open house to showcase the type of research WSU is conducting, the

type(s) of UAS being used, and a chance to dialog with WSU UAS research and

operations staff;

5. Sharing emergency planning steps (i.e., what to do if you see a UAS crash, or fly-away

UAS) with local law enforcement and first responders;

6. Posting informational videos on various research efforts, including the associated benefits

of research using UAS;

7. Broadcasting Public Service announcements on radio and television about WSU UAS

operations, including interviews on WZUU;

8. Publishing announcements in local or regional print media;

9. Establishing a toll-free public ‘hotline’ telephone number to report a downed UAS or to

register complaints regarding UAS operations, including privacy and noise complaints;

10. Ensuring local airports using AWOS are provided with information for broadcast to pilots

in the local systems at airports surrounding UAV operational areas. AWOS can provide

automated announcement of WSU UAS scheduled/ongoing UAS operations, as well as

emergency announcements of fly-away/downed UAS.

11. Adding WSU UAS information to ATIS updates, providing situation awareness to pilots

operating in the area of WSU UAS operations; and,

12. Announcing WSU UAS operations via NOTAM.

20


Section 12: FAA Reporting Requirements

Routine UAS FAA reporting requirements will be done in accordance with the approved FAA

COA. All FAA reporting will be presented to OGRD Director________________ for final

review, a minimum of five working days before the FAA reporting deadline.

Accident/incident reports will be done in accordance with standing FAA Federal Aviation

Regulations (FAR), as amplified upon by COA guidelines/instructions. Although some

requirements may be similar to FAA Notice N8020.11C, Aircraft Accident and Incident

Notification, Investigation, and Reporting (2 February 2010), the COA will provide specifics

focused on the accident/incidents reporting related directly to the approved UAS operations. NO

REPORTS are to be forwarded to the FAA prior to review by the WSU UAS Operations Advisor

and OGRD Director________________.

It is important to remember that the newness of UAS operations means a void in regulations

needed to operate efficiently. It is the role of all WSU UAS personnel to accurately document

concerns/deficiencies found in such regulations, in order for WSU to report same to local FAA

representatives.

21


Section 13: WSU Reporting Requirements

In addition to all reporting required by the FAA, WSU UAS users will:

22

Appendices


Appendix A: COA Checklist

The following must be completed prior to approval and release of any draft WSU UAS COA:

❑ Initial request for use of UAS in support of WSU funded research

❑ Valid airworthiness certificate

❑ Identification of currently certified WSU UAS PIC

❑ Identification of currently certified WSU UAS VO

❑ Identification of currently certified WSU UAS PI

❑ WSU UAS SOP Addendum, including:

• Flight Plan

• Communications Plan

• Property/Usage Approval Letter (if not WSU property)

• Local Landowner Notification Plan

• Public Affairs Plan

• Privacy Plan

• Emergency Action Plan

• Lost Link/Flyaway Procedures

• Standby Chase Team Procedures

• HAZMAT Plan

• Incident Reporting Plan

❑ Export control statement

❑ Insurance coverage

❑ Completed draft FAA UAS COA

❑ WSU UAS Operations Advisor Recommendation for COA Approval

❑ WSU Office of Grant and Research Development_____________ Approval

Letter

2


A-1

Appendix B: List of WSU Certified Pilots/Assigned UAS Group

NAMEUAS

GROUP

CURRENT

(Y/N)EMAIL TEL

3


B-1

Appendix C: Acronyms and Abbreviations

AFD Airport Facilities Directory

ATIS Automatic Terminal Information Service

AWOS Automated Weather Observation System

COA Certificate of Authorization

DOD Department of Defense

DUATS Direct User Access Terminal Service

FAA Federal Aviation Administration

FAR Federal Aviation Regulation

FBO Fixed Base Operator

FCC Federal Communications Commission

FTS Flight Termination System

GCS Ground Control Station

HAZMAT Hazardous Material

LOS Line of Sight

MOA Military Operations Area

NAS National Airspace System

NOTAM Notice to Airmen

PI Principal Investigator

PIC Pilot in Command

SAA See and Avoid

SOP Standard Operating Procedures

STA Special Temporary Authorization

UAS Unmanned Aircraft System – or – Unmanned Aerospace System

UNICOM Universal Communications

VO Visual Observer

WSU Washington State University

C-1

4


Appendix D: FAA References/Rules and Regulations

AC-91-57 – Model Aircraft Operating Standards (June 9, 1981)

Aeronautical Information Manual (AIM) (3 April 2014)

FAR Part 61 – Certification: Pilots, Flight Instructors, and Ground Instructors

FAR Part 91 – General Operating and Flight Rules

N8020.11C – Aircraft Accident and Incident Notification, Investigation, and Reporting

8900.1 CHG 351 – Unmanned Aircraft Systems

N8900.227 – Unmanned Aircraft Systems (UAS) Operational Approval (30 July 2013)

N8900.268 – Education, Compliance, and Enforcement of Unauthorized Unmanned

Aircraft Systems Operators

D-1

5


Appendix E: Points of Contact List

E-1

6

wsu research | washington state university€¦ · web view2015. 1. 6. · a prearranged plan of...

Documents