Skip to Content
ID
2-508-1246
Name
Small Unmanned Aircraft System (sUAS) Team
Status
Published
Version
2.0
Updated
10/17/2023 12:35:37 PM
Original Release
06/19/2018
Last Major Release
10/17/2023
Description
A small Unmanned Aircraft System (sUAS) Team is comprised of a Remote Pilot in Command (Remote PIC) and a Technical Specialist – sUAS, an aircraft operations team without a human pilot onboard, also known as a drone. The Remote PIC holds a Remote Pilot Certificate for operating an sUAS and collecting data for improved situational awareness through remote sensing.
Resource Category
Incident Management
Primary Core Capability
Situational Assessment
Secondary Core Capability
 
Resource Kind
Team
Overall Function
The sUAS Team: 1. Provides situational awareness by transmitting real-time or near real-time imagery, data, or verbal assessment, using multiple technologies, such as photogrammetry, live video, thermal imaging, and lidar, to enhance the Common Operating Picture (COP), planning functions, and Incident Action Plan (IAP) development 2. Uses various platforms based on mission need in accordance with Federal Aviation Administration (FAA) Code of Federal Regulations (CFR) Part 107, specifying sUAS
Composition and Ordering Specifications
1. Discuss logistics for deploying this team, such as security, communications, lodging, transportation, power, recharging, fuel, and meals, prior to deployment 2. Remote PIC determines the duty cycle of aircraft based on assignment, environment, terrain, battery life, and other factors affecting performance 3. Requestor should consider the following needs when ordering: a. Collection: A measurable description of each information or image collection task, including image resolution, and distribution instructions b. Processing: Ability to link platform to satellite, platform-required ground reception and range limitations, if any, data collection media used, delivery points of data on media, media compatibility with end users, and the turnaround time for analysis c. Distribution: Parameters for when, where, and how to disseminate images, information, and data d. Storage: Image, data, and information storage locations and servers and time frames for storage and maintenance 4. Requestor orders data analysis capabilities separately 5. Requestor and provider should discuss the capability requirements of the mission: a. Fixed wing sUAS that have short- to medium-range capabilities and are more agile b. Rotary wing sUAS that are very agile and can provide near-stationary monitoring but have limited flight times and altitudes c. Lighter-than-air sUAS that have extended flight times and can achieve significant altitudes but lack maneuverability and are more susceptible to weather than other UAS types 6. Requestor provides management and oversight of this team by: a. Providing Air Operations Branch staff, including the Air Tactical Group Supervisor and the Air Support Group Supervisor b. Ensuring Air Operations Branch staff understand UAS operations, FAA regulations, and requirements of other state, local, tribal, territorial, and federal agencies having jurisdiction 7. Requestor and provider should discuss availability of equipment and supplies needed to establish an adequate Ground Control Station, such as a portable system for data management, wireless or networking equipment, batteries, and a specialized communications cache. 8. Based on mission requirements, requestor and provider should discuss data collection payload options such as: a. Aerial photography b. Full motion video c. Specialized sensors, such as photogrammetry, sonar, radar, infrared, lidar, and hyperspectral d. Infrared thermography (IRT) 9. Discuss mission planning factors, including: a. Time-on-scene and flight duration requirements b. Topography, climate, land and maritime factors, and population density c. Launch and retrieve capabilities; takeoff and line of sight capabilities; first-person view (FPV), beyond line-of-sight view, and video piloting; use of multiple controllers; and follow-me capability (electronic or tether) d. Operational time (day/night), takeoff and landing terrain, and operational area terrain e. Weather factors (maximum wind speeds, temperature, humidity, and inclement conditions) f. Airports and restricted airspace nearby 10. This team follows all applicable state, local, tribal, and territorial privacy laws and regulations 11. Requestor and provider should discuss the need for FAA waivers and authorizations, such as permission to fly beyond the visual line of sight, fly at night, fly directly over a person or people, fly multiple aircraft with only one pilot, fly above 400 feet, fly near airports, and fly in other restricted or special-use airspace 12. This team adheres to FAA restrictions on crew duty according to Title 14 CFR Part 117: Flight and Duty Limitations and Rest Requirements
Supporting Core Capabilities
None
Components
Component Notes  
Minimum Personnel Per TeamNot Specified
Component Types
Type Attribute
Type 1Same as Type 2
Type 23
SUPPORT PERSONNEL PER TEAM1. Requestor provides Air Operations Branch staff for management and oversight of this team 2. Requestor ensures Air Operations Branch staff understand UAS operations and meet requirements of FAA, Federal Communications Commission (FCC), Department of Transportation (DOT), and other state, local, tribal, territorial, and federal agencies having jurisdiction 3. One PIC serves as a safety flight observer for the UAS Team during flight operations and is not in direct control of an operational UAS platform. The PIC provides field oversight and situational awareness, and ensures the safety of the PIC operating the UAS 4. Teams can add additional UAS aircraft and a corresponding number of additional PIC personnel within a manageable span of control 5. For Type 1 teams using UAS aircraft over 55 pounds, requestor should add pilots and personnel based on manufacturer recommendations for safe operation and handling.
Component Types
Type Attribute
Type 1Same as Type 2
Type 22 – National Incident Management System (NIMS) Type 1 Remote Pilot in Command 1 – NIMS Type 1 Technical Specialist–sUAS
Aircraft Systems Per Team1. Requestor determines image resolution required using the National Imagery Interpretability Rating Scale (NIIRS) 2. sUAS platforms needed, such as fixed wing, rotary wing, or lighter-than-air, may vary based on mission assignment 3. For Type 1 and Type 2 teams, each sUAS should meet requirements under FAA Part 107
Component Types
Type Attribute
Type 1Same as Type 2
Type 2Combination of fixed wing, lighter-than-air, and rotary wing sUAS aircraft that meet requirements under FAA Part 107
Information Collection Equipment Per TeamRequestor provides image resolution requirements based on mission needs.
Component Types
Type Attribute
Type 1Same as Type 2, PLUS: Specialized information collection equipment, such as: 1. Specialized sensors, such as photogrammetry, sonar, radar, infrared, lidar, and hyperspectral 2. Infrared thermography (IRT)
Type 21. Photography 2. Full motion video
Communications Equipment Per Team MemberConsider alternate forms of communications, such as satellite phones, based on the mission assignment and team needs.
Component Types
Type Attribute
Type 1Same as Type 2
Type 21. Two-way portable radio 2. Cell phone
959
Notes
References
Reference
FEMA, NIMS 509: Air Operations Branch Director
FEMA, NIMS 509: Air Tactical Group Supervisor
FEMA, NIMS 509: Air Support Group Supervisor
FEMA, NIMS 509: Remote Pilot-in-Command
FEMA, NIMS 509: Technical Specialist – Small Unmanned Aircraft System
FEMA, National Incident Management System (NIMS), October 2017
Federal Aviation Administration (FAA) Joint Order (JO) 7200.23: Air Traffic Organization Policy, October 2016
Title 14 Code of Federal Regulations (CFR) Part 107: Small Unmanned Aircraft Systems, latest edition adopted
Title 14 CFR Part 117: Flight and Duty Limitations and Rest Requirements, latest edition adopted
Department of Homeland Security Best Practices for Protecting Privacy, Civil Rights, and Civil Liberties in Unmanned Aircraft Systems Programs, December 2015
Published Versions
Version Publish Date Document Type
2.0 10/17/2023 12:35:37 PM PDF
1.4 11/22/2019 4:49:22 PM PDF
1.3 9/28/2018 5:08:58 PM PDF
1.2 6/19/2018 11:38:38 AM PDF
1.1 6/19/2018 10:04:11 AM PDF
1.0 6/18/2018 11:30:59 PM PDF