RFI for Unmanned Aircraft System (February 17th 2026).pdf

REQUEST FOR INFORMATION

Bureau of Alcohol, Tobacco, Firearms and Explosives

Firearms Operations Division

Unmanned Aircraft System (UAS)

1. Reference Number: DJA–26-AHDQ-N-0001

2. Response Due Dates: Electronic Responses/Submissions shall be received no later than March 31st , 2026 at 3:00 PM EST to Mr. Jim Huff via email (james.huff@atf.gov ).

3. RFI Purpose:

This Request for Information (RFI) as identified in the Federal Acquisition Regulation (FAR)

15.201 (c) (7) is issued solely for market research and planning purposes. It does not constitute an Invitation for Bids, Request for Proposal, or Request for Quotes.

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) has a requirement to obtain Unmanned Aircraft System (UAS) information. ATF is looking to gather information on companies who provide similar commodities.

Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Those who respond to this RFI should not anticipate feedback concerning their submission. All submissions will become the property of the Government and will not be returned. Proprietary information, if any, must be clearly marked on all material(s) submitted. All information received marked Proprietary will be handled in accordance with 41 USC 2101-2107. Responding to the RFI is completely voluntary and will not enhance or adversely affect responses to any resulting solicitation if such solicitation is issued at a later date. There is no competitive advantage gained by any of the respondents to this RFI.

Additionally, the Government will not provide reimbursement for any information that may be submitted in response to this RFI. Respondents are solely responsible for all expenses associated with responding to this RFI. No promise of future business with the Government will result from responding to this RFI.

Questions if submitted MUST be received no later than March 6th , 2026 3:00PM EST, the answers will be posted to this same website after March 13th , 2026 3:00PM EST.

Industry is encouraged to advise the Government what other information it needs to better understand the Government’s requirements, to reduce the risk contingency built into pricing, and to reduce barriers to competition.

mailto:james.huff@atf.gov http://www.fbo.gov/

4. Background:

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) is a unique law-enforcement agency in the United States Department of Justice that focuses on protecting its communities from violent crime. ATF is responsible for bringing to justice those criminals, and criminal organizations who illegally use and traffic firearms, illegally use and store explosives, commit acts of arson and bombings, acts of terrorism, and divert alcohol and tobacco products.

5. Objectives:

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) has a requirement to obtain UAS information. ATF is looking to gather information on companies who work in the field of UAS.

6. Requirements Summary:

ATF is interested in receiving responses from vendors who can provide information on the below tentative commodity requirement similar to the below Unmanned Aircraft System

(UAS):

PERFORMANCE WORK STATEMENT

1. PURPOSE

The purpose of this contract is to establish, operate, and sustain a standardized, modular, and category‑based National Small Unmanned Aircraft System (sUAS) capability for use across the federal government. This contract is intended to provide federal departments and agencies access to commercially available, secure, and mission appropriate sUAS systems that meet defined technical, operational, and cybersecurity requirements, enabling agencies to select platforms aligned to their specific mission needs rather than procuring vendor‑specific solutions. The focus of this acquisition is establishing a common federal baseline for sUAS capabilities that supports law enforcement, emergency response, disaster response, reconnaissance, inspection, training, and other authorized governmental uses, while maximizing interoperability, competition, and long‑term sustainment.

The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) serves as the sponsoring organization for this acquisition and will utilize awarded systems in support of overt and covert law enforcement operations. In addition, this contract is structured to be available for use by all federal executive agencies, subject to each agency’s statutory authorities, mission requirements, funding availability, and applicable interagency agreements, without creating any obligation to procure.

2. BACKGROUND

ATF is a federal law enforcement agency within the United States Department of Justice responsible for enforcing federal criminal laws related to firearms, explosives, arson, bombing incidents, violent crime, and the regulation of alcohol and tobacco products. ATF conducts a wide range of investigative, regulatory, and response activities across diverse operational environments, including urban, rural, indoor, austere, and disaster impacted settings.

Unmanned aircraft systems have become an essential operational tool across the full spectrum of ATF mission sets. These missions extend beyond specialized tactical or response elements and include investigative support, planned enforcement operations, emergency response, post incident documentation, scene reconstruction, training, and routine operational support. As such, ATF’s sUAS requirements are not confined to a single component or use case, but span multiple operational contexts, risk profiles, and capability needs.

Historically, sUAS utilization within ATF has included, but has not been limited to, Special Response Teams (SRT), National Response Teams (NRT), field divisions, investigative groups, and training elements. Each of these users place different demands on aircraft performance, payloads, endurance, communications, maneuverability, data handling, and cybersecurity posture. No single sUAS platform can effectively satisfy all operational requirements.

Accordingly, ATF requires access to a structured portfolio of sUAS capabilities organized by clearly defined categories and performance characteristics. This approach enables components across the agency to select systems appropriate to their specific mission needs while maintaining common standards for safety, security, interoperability, training, and sustainment. This contract is intended to support agency wide adoption of sUAS capabilities in a consistent, scalable, and policy aligned manner, while avoiding vendor lock in and ad hoc, mission specific procurements.

3. OBJECTIVE

The objective of this contract is to establish a flexible, scalable acquisition vehicle through which ATF and other federal agencies may obtain small unmanned aircraft systems organized into standardized capability categories, rather than single purpose or mission specific solutions. The intent is to enable agencies to select sUAS platforms and associated components that align with varying operational environments, mission complexity, risk tolerance, and data sensitivity requirements, while preserving competition, interoperability, and long term sustainment.

This objective emphasizes the use of a category based acquisition framework and common performance expectations, while allowing the Government to evaluate, award, and order systems appropriate to authorized missions and operational needs. Category definitions and system groupings are established in Section 4 (Scope of Work).

4. SCOPE OF WORK

The Contractor shall provide complete, turnkey sUAS solutions when ordered at the task order level, including aircraft, payloads, ground control stations, support equipment, training, warranty coverage, and sustainment services. The Government intends to evaluate and award systems across a standardized set of sUAS capability categories that reflect distinct operational environments, endurance profiles, airframe configurations, and payload capacity classes. These categories are intended to support agency wide and cross agency mission requirements while avoiding platform specific or vendor specific solutions.

The sUAS capability categories under this contract include:

• Training platforms

• Interior platforms

• Short–Medium range platforms

• Long Range platforms

• Fixed Wing platforms

• Tethered platforms

• Lift platforms (<50 pounds maximum takeoff weight)

• Heavy Lift platforms (≥50 pounds maximum takeoff weight)

5. TECHNICAL REQUIREMENTS

This section establishes standardized, vendor agnostic technical requirements for each sUAS capability category under this contract. Requirements are structured to support competitive procurement, enforceability, cybersecurity compliance, and audit survivability. Each category is presented as a discrete requirement set consisting of Mandatory Requirements (pass/fail) and Value Added Features (VAF) (evaluated, non mandatory).

Cybersecurity requirements apply uniformly across all sUAS categories and are defined once to avoid duplication within individual category requirement sets. categories Cybersecurity requirements apply uniformly across all sUAS categories and are defined once to avoid duplication within individual category requirement sets.

5.1 CYBERSECURITY CLASSIFICATION (APPLIES TO ALL CATEGORIES)

5.1.1 Objective

The Government will determine the required cybersecurity level for a given use case and/or ordering activity. Vendors shall indicate which cybersecurity level their proposed system is and whether it is capable of meeting and provide supporting evidence.

This framework aligns with:

• FIPS 199 (Security Categorization of Federal Information and Information Systems)

• FIPS 200 (Minimum Security Requirements for Federal Information and Information Systems)

• NIST SP 800 53 (Security and Privacy Controls for Information Systems and Organizations), current revision

• NIST SP 800 53B (Control Baselines for Information Systems and Organizations)

Baseline selection and tailoring will be performed by the Government in accordance with the Risk Management Framework (RMF). Vendors are not responsible for performing formal FIPS 199 categorization.

5.1.2 Cybersecurity Levels Used in This Contract

For purposes of this contract, systems shall be represented as capable of meeting one of the following baseline aligned cybersecurity levels:

• Low Security Level

• Moderate Security Level

• High Security Level

These levels describe capability alignment, not Government authorization decisions.

5.1.3 Vendor Submission Requirements

For each proposed system, the vendor shall submit:

1. The highest cybersecurity level the system is capable of meeting (Low / Moderate / High).

2. A system boundary and data flow description covering aircraft, controller, payloads, GCS software, backend services, update mechanisms, storage, and networking.

3. A control alignment crosswalk mapping system capabilities to applicable NIST SP 800 53 and SP 800 53B control families.

4. Supporting documentation and evidence proportionate to the claimed level.

5. Inaccurate, unsupported, or inconsistent cybersecurity capability representations may result in elimination from consideration or other remedies as permitted by law and regulation.

5.1.4 Government Responsibilities

The Government will evaluate submitted evidence and assign the cybersecurity level used for evaluation or award. The Government may assign a lower level if evidence is insufficient and may require additional evidence during evaluation or post award validation.

For systems evaluated at Moderate or High Security Level, any cloud computing service used to store, process, transmit, or facilitate access to Federal information shall maintain an active FedRAMP authorization at the appropriate impact level for the duration of the contract.

5.1.5 Supply Chain Risk Mitigation for Low Impact Systems

5.1.5.1 Applicability

Systems that present identified supply chain risk may be eligible for evaluation and award only when proposed for FIPS 199 Low Security Level use cases and only when the Offeror demonstrates Government acceptable supply chain risk mitigation measures.

This provision applies solely to systems evaluated and used at the Low Security Level and does not apply to systems evaluated at Moderate or High Security Levels.

5.1.5.2 Allowable Risk Posture

The presence of identified supply chain risk does not automatically disqualify a system from consideration for Low Security Level use cases, provided that such risk is:

• Explicitly identified,

• Appropriately mitigated through compensating controls, and

• Determined by the Government to be acceptable for the intended Low impact use.

Risk acceptance under this provision constitutes limited, use specific acceptance and does not represent general approval of the system, vendor, or supply chain.

5.1.5.3 Acceptable Mitigation Measures

Supply chain risk mitigation measures may include, but are not limited to:

• Independent third party security assessments or testing;

• Architectural isolation of the system from Government enterprise networks;

• Restricted or controlled operating environments;

• Elimination or disablement of non essential communications paths, services, or update mechanisms;

• Local only data storage and processing;

• Compensating technical, operational, or procedural controls sufficient to reduce risk to an acceptable level for Low Security Level use.

Vendor self assertions or unsupported claims of mitigation are insufficient. Mitigation measures must be supported by evidence commensurate with the claimed risk reduction.

5.1.5.4 Government Determination

The Government will evaluate submitted mitigation evidence and determine whether:

• The proposed mitigations are credible and sufficient;

• The residual risk is acceptable for Low Security Level use; and

• The system may be considered for evaluation, award, or ordering under this provision.

The Government may assign a system a lower cybersecurity level, restrict its allowable use, or determine the system ineligible if mitigation evidence is insufficient or inconsistent.

5.1.5.5 Use Restrictions

Systems approved under this provision are restricted to:

• The evaluated configuration;

• The approved Low Security Level use case(s); and

• The specific operating conditions evaluated by the Government.

Any expansion of use, change in mission profile, modification of configuration, or change in data handling requires re evaluation by the Government.

5.1.5.6 Statutory and Regulatory Limitations

Nothing in this section shall be interpreted as:

• A waiver of statutory prohibitions;

• Authorization to use systems prohibited by law or regulation; or

• Limitation on the Government’s authority to exclude systems based on supply chain risk.

All systems remain subject to applicable statutory, regulatory, and policy restrictions, including but not limited to FAR Subpart 4.21 and Section 889 of the National Defense Authorization Act.

5.1.6 Authorization to Operate (ATO) Support and Cybersecurity Cooperation

5.1.6.1 General Requirement

For any system ordered under this contract, the Contractor shall make knowledgeable technical personnel available to support the ordering agency’s cybersecurity authorization process, including Authorization to Operate (ATO) or equivalent approval, as required by the Authorizing Official.

This requirement applies for the duration of the agency’s authorization activities related to the ordered system.

5.1.6.2 Scope of Support

Upon request by the ordering agency, the Contractor shall provide reasonable assistance, documentation, and technical information necessary to support cybersecurity authorization activities, which may include, but is not limited to:

• System architecture descriptions;

• System boundary and data flow documentation;

• Control implementation descriptions aligned to NIST SP 800 53 and applicable baselines;

• Configuration details, software and firmware inventories, and update mechanisms;

• Supply chain risk mitigation descriptions and supporting evidence;

• Responses to Authorizing Official, ISSO, or assessor questions related to system security posture.

5.1.6.3 Limits of Responsibility

The Contractor is not responsible for performing security categorization, risk acceptance, authorization decisions, or issuance of an ATO.

Authorization decisions remain solely within the authority of the Government Authorizing Official.

Contractor support under this section constitutes cooperation and information support only and does not guarantee authorization approval.

5.1.6.4 Timeliness and Availability

The Contractor shall respond to reasonable requests for authorization related information within timeframes appropriate to the authorization process, as coordinated with the ordering agency.

Failure to provide required information or reasonable cooperation may be considered a failure to support ordered systems and may impact future task order eligibility or past performance evaluations, as permitted by law and regulation.

5.1.6.5 Cost and Ordering Considerations

ATO support under this section is limited to information and cooperation necessary to support authorization and does not require the Contractor to perform independent security assessments unless explicitly ordered at the task order level.

If extensive or ongoing authorization support beyond reasonable cooperation is required, such services shall be defined and priced at the task order level.

5.2 CATEGORY SPECIFIC TECHNICAL REQUIREMENTS

Mandatory Requirements are evaluated on a pass/fail basis. Value Added Features are not required for award but may be used for technical differentiation. Final category assignment rests solely with the Government.

Category assignment determinations will be based on demonstrated performance against the mandatory requirements of each category.

5.2.1 TRAINING PLATFORMS

Role Definition:

Training platforms are intended to support entry level pilot qualification, recurrent proficiency, and skills sustainment across Federal sUAS programs. These systems are deliberately cost controlled, durable, and expendable, enabling agencies to train realistically without risking operational platforms or inflating lifecycle costs. Training platforms are expected to absorb routine training attrition and mishaps as part of normal use. While primarily training focused, these systems may be employed operationally in limited, low risk scenarios when appropriate.

Operational Employment Characteristics (Informational, Non Evaluated):

Training platforms are used in high repetition environments to develop foundational pilot skills, including aircraft orientation, precision hover, coordinated movement, payload control, and emergency response behaviors. These systems are expected to be flown frequently by novice and intermediate pilots, operate in close proximity to personnel during instruction, support multi aircraft training environments without unacceptable interference, and provide flight handling characteristics that translate meaningfully to operational sUAS platforms to enable muscle memory transfer rather than negative training. This subsection is provided for context only and does not establish additional mandatory requirements.

Mandatory Requirements (Pass/Fail):

Cost Control and Attrition Tolerance:

• The system shall be purpose built or configured for training use, emphasizing low unit cost and ease of replacement.

• The fully configured system (aircraft, controller, required batteries, and charging equipment) shall have a unit price not exceeding $2,000 USD at time of proposal. This price cap reflects the Government’s requirement for expendable, attrition tolerant training systems.

• The system shall be designed such that damage during training operations is anticipated and does not render the training program financially unsustainable.

Flight Characteristics and Training Fidelity:

• The system shall support stable position hold flight modes suitable for basic orientation, hover, and precision control training.

• Flight handling characteristics shall reasonably approximate those of common operational sUAS platforms to support skill transfer.

• The system shall support controlled lateral, vertical, and yaw movements suitable for structured training exercises.

Training Environment and Safety:

• The system shall be safe to operate in close proximity to unprotected personnel.

• The system shall support operation in multi drone training environments, allowing simultaneous flight of multiple aircraft without unacceptable control, interference, or safety issues.

Payload and Emergency Procedures Training:

• The system shall support basic payload operation sufficient to train camera orientation, framing, and basic payload control concepts.

• The system shall support training for emergency procedures, including loss of link behavior, controlled recovery, and pilot initiated failsafe actions.

Control Interface:

• The system shall use a handheld controller suitable for entry level pilot training.

• Controller input logic (pitch, roll, yaw, throttle) shall align with common UAS control conventions to enable transfer of skills to operational controllers.

Durability and Sustainment:

• The system shall be sufficiently durable to withstand routine training mishaps without catastrophic failure.

• High wear components shall be replaceable rapidly without specialized tools.

• Batteries shall be rechargeable, swappable, and suitable for repeated training cycles with high expected cycle life.

• Replacement parts shall be readily available and low cost.

Cybersecurity and Data Handling:

• Training platforms shall be capable of meeting Low Security Level requirements under the cybersecurity framework defined in Section 5.1.

• Cloud connectivity, if present, shall be capable of being disabled.

• The system shall not require external network connectivity for basic flight operations.

Value Added Features (Evaluated, Non Mandatory):

• Enhanced resistance to environmental conditions (e.g., wind, light precipitation, dust) beyond baseline safety requirements, supporting realistic outdoor training.

• Extended endurance or range approaching the upper bounds of the Training category.

• Advanced EO payloads (e.g., improved low light performance) to introduce sensor concepts prior to operational training.

• Operator assist features that enhance safety or usability without reducing pilot authority or masking poor technique.

• Integration with vehicle based or local display systems that do not rely on cloud services.

• Training oriented telemetry or playback features supporting after action review.

5.2.2 INTERIOR PLATFORMS

Interior platforms are intended to provide real time situational awareness inside structures by operating ahead of personnel during interior movement. These systems are optimized for confined, GPS denied, RF challenged, and low light environments, including residential, commercial, and industrial structures. Interior platforms prioritize precise low speed control, survivability, rapid deployment, and operator safety. Exterior flight capability, when present, is secondary to interior performance.

Operational Employment Characteristics (Informational, Non Evaluated):

Interior platforms are employed as flow in front reconnaissance assets, moving through rooms, hallways, stairwells, and vertical spaces before personnel entry or as personnel advance. These systems are expected to operate in close proximity to walls, ceilings, doorways, and obstacles;

maintain stable flight at very low speeds and tight clearances; function in environments with concrete, rebar, metal framing, and signal attenuation; prioritize information gathering and survivability over endurance or range; and accept routine physical contact as part of normal operation. This subsection is provided for context only and does not establish additional mandatory requirements.

Mandatory Requirements (Pass/Fail):

Operational Environment:

• The system shall be optimized for flight in confined, GPS denied indoor environments.

• The system shall support stable position hold flight suitable for cluttered rooms, hallways, stairwells, vertical shafts, and crawl spaces.

• The system shall be capable of operating in low light or no light interior conditions.

Size, Maneuverability, and Deployment:

• The system shall not exceed 10.5 inches by 10.5 inches in its operational configuration.

This dimensional limit is intended to reflect common interior access constraints and is not based on anthropometric precision.

• The system shall be capable of accessing spaces an average sized human can crawl into or conceal themselves within.

• The system shall support rapid deployment from stored state to airborne in under 60 seconds.

• The system shall support hand launch and recovery.

Flight Control and Handling:

• The system shall support stabilized flight modes suitable for precision interior maneuvering.

• The system shall allow controlled forward, lateral, vertical, and yaw movement at low speeds appropriate for interior operations.

• Any autonomous obstacle avoidance, if present, shall be capable of being enabled or disabled by the operator.

Video, Sensors, and Situational Awareness:

• The system shall provide a real time video feed suitable for navigation and tactical situational awareness.

• The system shall support low light enhancement, infrared, or equivalent capability.

• The camera system shall provide sufficient angular coverage to observe obstacles above, below, and ahead of the aircraft.

Control and Communications:

• The system shall operate in RF challenged environments including reinforced concrete and dense interior construction.

• Command and control links shall be digital and low latency.

• The system shall not require cellular connectivity for command, control, or video.

• Cloud dependent functionality, if present, shall be capable of being disabled.

• Third party analytics or automated processing services, if present, shall be capable of being disabled.

Safety and Survivability:

• The system shall be safe to operate in close proximity to unprotected personnel.

• The system shall withstand routine wall, door, and obstacle contact without catastrophic failure.

• High wear components shall be replaceable rapidly in the field.

Perching and Observation:

• The system shall be capable of perching or otherwise maintaining a stationary observation position while continuing to stream live video.

Failsafes and Recovery:

• The system shall include failsafe behaviors appropriate for indoor environments.

• Automatic behaviors shall prioritize controlled landing or hover over uncontrolled flight.

Cybersecurity and Data Handling:

• The system shall be capable of meeting Low or Moderate Security Level requirements under Section 5.1.

• The system shall not automatically upload mission data to external servers.

• Mission data shall be retained locally and exportable under Government control.

Logistics and Sustainment:

• Batteries shall be swappable and suitable for rapid operational turnaround.

• Vendors shall provide sustainment support suitable for frequent operational use.

Value Added Features (Evaluated, Non Mandatory):

• Exterior to interior transition capability (e.g., window ingress).

• Full manual FPV flight modes for advanced operators.

• Extended perching or stationary observation duration.

• Dual video feeds for operator and command.

• Thermal imaging or advanced infrared payloads.

• Compatibility with tactical displays, goggles, or external monitors. • Integration with situational awareness tools (e.g., ATAK).

• Modular mounts for mission specific payloads (e.g., speakers, sensors).

• Two way audio or relay communication capability.

• Enhanced crash survivability features beyond baseline.

• Enhanced ability to operate in adverse interior environmental conditions, including dust, smoke, debris, and airflow, without compromising safety or control.

5.2.3 SHORT–MEDIUM RANGE PLATFORMS

Short–Medium Range platforms are team owned, operator centric exterior systems intended to provide real time situational awareness forward of maneuvering personnel or vehicle elements.

These platforms are actively flown by a single operator and are closely coupled to the tempo, movement, and decision making of the supported team. They are not designed for long duration persistence, unattended loiter, or enterprise level ISR missions.

Operational Employment Characteristics (Informational, Non Evaluated):

Short–Medium Range platforms are employed as dynamic reconnaissance and overwatch assets, typically launched, maneuvered, repositioned, and recovered multiple times during a single operational evolution. These systems are expected to move with the supported element rather than operate independently; provide rapid look ahead, flank, and overwatch capability; be repositioned frequently as terrain, threat, or mission context changes; operate in proximity to tactical radios, vehicles, and personnel; and prioritize responsiveness and operator control over endurance or automation. This subsection is provided for context only and does not establish additional mandatory requirements.

Mandatory Requirements (Pass/Fail):

Operational Role and Tempo:

• The system shall be designed for continuous hands on control by a single operator throughout the mission.

• The system shall be capable of launch, employment, and recovery within a single tactical evolution.

• The system shall be suitable for use as a team level asset rather than a command or enterprise level ISR platform.

Range and Endurance Envelope:

• The system shall support a minimum effective operational radius of 5 miles from the operator in a typical operational configuration.

• The system shall support a minimum flight endurance of 30 minutes in a typical operational configuration.

• Systems exceeding an effective operational radius of 5 miles or flight endurance of 60 minutes may be reclassified under the Long Range / Endurance category at the Government’s discretion.

• Final category assignment rests solely with the Government.

Flight and Control Characteristics:

• The system shall provide stable, responsive flight suitable for active maneuvers in exterior environments.

• The system shall support real time piloting with minimal reliance on autonomous behaviors.

• Loss of command or control shall be treated as mission failure, with safe recovery prioritized over mission continuation.

Video and Sensor Performance:

• The system shall provide a real time video feed of sufficient quality to support forward reconnaissance and threat detection.

• Camera performance shall support meaningful ISR; systems with insufficient video quality to inform tactical decision making are not acceptable.

• The operator shall be able to actively control the camera during flight.

Control and Communications:

• The system shall maintain reliable command, control, and video links within the defined Short–Medium Range envelope.

• The system shall not require cellular connectivity for command, control, or video transmission.

• The system shall operate in proximity to tactical radios without unacceptable interference.

Operational Environment:

• The system shall be suitable for exterior operations in varied terrain and weather conditions typical of field operations.

• The system shall support rapid repositioning and recovery as the supported element moves.

Cybersecurity and Data Handling:

• The system shall be capable of meeting Low or Moderate Security Level requirements under Section 5.1.

• The system shall not automatically upload mission data to external servers.

• Cloud dependent functionality, if present, shall be capable of being disabled.

Logistics and Sustainment:

• Batteries shall be swappable and suitable for rapid operational turnaround.

• The system shall be supportable at the team level without reliance on enterprise infrastructure.

Value Added Features (Evaluated, Non Mandatory):

• Extended range or endurance approaching the upper bounds of this category.

• Advanced EO/IR payloads, including enhanced zoom or low light performance.

• Improved resistance to environmental conditions (e.g., wind, precipitation, dust) beyond baseline requirements.

• Ability to carry and operate communications relay payloads (e.g., mesh radio nodes) to extend ground communications.

• Integration with situational awareness and command and control tools (e.g., ATAK).

• Operator assist features that enhance safety or usability without reducing operator authority.

• Enhanced navigation aids that remain operator driven.

5.2.4 LONG RANGE / ENDURANCE PLATFORMS

Long Range / Endurance platforms are mission centric sUAS systems intended to provide persistent situational awareness, wide area coverage, or sustained observation over extended durations. These platforms are typically owned, managed, and tasked at a higher echelon due to increased cost, complexity, and mission impact. Unlike team owned platforms, Long Range systems are not required to remain tightly coupled to a single tactical evolution and may support multiple phases, elements, or operational objectives concurrently.

Operational Employment Characteristics (Informational, Non Evaluated):

Long Range / Endurance platforms are employed to maintain continuity of observation across extended timelines, distances, or areas where frequent launch and recovery would be impractical.

These systems are expected to operate independently of maneuver element tempo; provide persistent ISR or wide area coverage across phases of an operation; employ supervised autonomy to reduce operator workload; accept longer setup, recovery, and sustainment timelines; and support handoff between operators or control elements when appropriate. This subsection is provided for context only and does not establish additional mandatory requirements.

Mandatory Requirements (Pass/Fail):

Mission Scope and Persistence:

• The system shall be designed to support extended duration missions that outlast a single tactical evolution.

• The system shall be capable of sustained loiter or wide area observation without continuous hands on piloting.

• The system shall be suitable for employment as a shared or higher echelon asset.

Range and Endurance Envelope:

• The system shall support a minimum flight endurance of 90 minutes in a typical operational configuration.

• The system shall support an effective operational radius greater than 5 miles from the operator or control element.

• Systems meeting or exceeding these thresholds may be categorized as Long Range / Endurance even if they also meet Short–Medium minimums.

Flight, Control, and Autonomy:

• The system shall support operator supervised flight, monitoring, or mission management rather than continuous manual piloting.

• Autonomous or semi autonomous features (e.g., loiter, route following, orbit) may be employed, provided the operator retains authority and override capability.

• On loss of command or control, the system shall support configurable behaviors appropriate to mission needs, including autonomous recovery or safe termination.

Video and Sensor Performance:

• The system shall provide high quality real time ISR suitable for extended observation and decision support.

• Sensor performance shall justify persistent employment; systems with limited ISR utility are not acceptable.

• The operator shall be able to actively manage sensors during flight.

Control and Communications:

• The system shall maintain reliable command, control, and data links across the defined long range envelope.

• The system shall not require cellular connectivity for basic flight operations.

• Any cloud enabled functionality shall comply with the cybersecurity framework defined in Section 5.1.

Operational Environment and Logistics:

• The system may require vehicle supported launch, recovery, or sustainment.

• Extended setup, recovery, and sustainment timelines are acceptable.

Cybersecurity and Data Handling:

• The system shall be capable of meeting Moderate or High Security Level requirements under Section 5.1.

• Systems evaluated at Moderate or High Security Level that rely on cloud services shall meet applicable FedRAMP requirements.

• Mission data shall not be automatically uploaded to external servers unless explicitly approved by the Government.

Value Added Features (Evaluated, Non Mandatory):

• Endurance significantly exceeding minimum requirements.

• Advanced EO/IR payloads with enhanced zoom, stabilization, or multi sensor fusion.

• Autonomous mission management features that further reduce operator workload.

• Ability to carry and operate communications relay payloads (e.g., mesh radio nodes).

• Integration with situational awareness and command and control tools (e.g., ATAK).

• Environmental hardening enabling sustained operation in adverse weather conditions.

• Modular payload bays to support mission specific sensors or relay equipment.

5.2.5 FIXED WING PLATFORMS

Fixed Wing platforms are mission centric sUAS systems optimized for long duration flight, wide area coverage, and efficient transit over extended distances. Classification as a Fixed Wing platform is determined primarily by airframe configuration and launch/recovery method, not endurance or range performance alone. These systems emphasize aerodynamic efficiency, endurance, and coverage area over vertical maneuverability or confined space access. Fixed Wing platforms are typically owned and managed at a higher echelon due to cost, sustainment demands, and mission impact.

Operational Employment Characteristics (Informational, Non Evaluated):

Fixed Wing platforms are employed for broad area reconnaissance, route surveillance, mapping, and persistent exterior ISR where multirotor systems would be inefficient or impractical. These systems are expected to cover large geographic areas efficiently, support long transits to and from mission areas, operate primarily in exterior, open environments, accept reduced maneuver precision in exchange for endurance and range, and require deliberate launch and recovery planning. This subsection provides operational context only and does not establish additional mandatory requirements.

Mandatory Requirements (Pass/Fail):

Mission Scope and Employment:

• The system shall be designed for sustained exterior operations over large geographic areas.

• The system shall be suitable for missions prioritizing endurance, coverage area, and transit efficiency over confined space maneuverability.

• The system shall be employable as a shared or higher echelon asset.

Range and Endurance Envelope:

• The system shall support a minimum flight endurance of 90 minutes in a typical operational configuration.

• The system shall support an effective operational radius greater than 5 miles from the launch or control element.

• Systems meeting these thresholds may also meet Long Range / Endurance requirements depending on mission use.

Launch and Recovery:

• The system shall support non runway launch and recovery methods suitable for field deployment (e.g., hand launch, rail launch, bungee launch, net recovery, belly landing).

• The system shall not require prepared runways or permanent infrastructure for launch or recovery.

Flight Control and Autonomy:

• The system shall support stabilized fixed wing flight and navigation.

• Operator supervised autonomous flight modes (e.g., waypoint navigation, loiter patterns) shall be supported.

• The operator shall retain the ability to intervene or override autonomous behaviors at all times.

Video, Sensors, and Data Collection:

• The system shall support ISR, mapping, or surveillance payloads appropriate for wide area or long duration missions.

• Sensor performance shall be sufficient to provide actionable intelligence consistent with fixed wing mission profiles.

• The system shall support real time data downlink and/or post mission data retrieval as appropriate to the mission.

Control and Communications:

• The system shall maintain reliable command and control links across the defined operational envelope.

• The system shall not require cellular connectivity for basic flight operations.

• Any cloud enabled functionality shall comply with the cybersecurity framework defined in Section 5.1.

Cybersecurity and Data Handling:

• The system shall be capable of meeting Moderate or High Security Level requirements under Section 5.1.

• Systems relying on cloud services at Moderate or High levels shall meet applicable FedRAMP requirements.

• Mission data shall not be automatically uploaded to external servers unless explicitly approved by the Government.

Logistics and Sustainment:

• The system shall be supportable in austere or field environments.

• Batteries, propulsion components, and critical spares shall be replaceable without depot level maintenance.

Value Added Features (Evaluated, Non Mandatory):

• Endurance or range significantly exceeding minimum requirements.

• Hybrid propulsion or energy efficient designs extending flight duration.

• Advanced mapping, photogrammetry, or surveying payloads.

• High end EO/IR sensors with wide area coverage or enhanced zoom.

• Ability to carry and operate communications relay payloads (e.g., mesh radio nodes).

• Integration with situational awareness and command and control tools (e.g., ATAK).

• Rapid field assembly or breakdown for transport.

• Environmental hardening enabling operation in adverse weather conditions, including winds aloft and precipitation.

5.2.6 TETHERED PLATFORMS

Tethered platforms are mission centric sUAS systems designed to provide persistent, elevated overwatch, communications support, or localized situational awareness by leveraging a physical tether for continuous power delivery and/or data transmission. These systems prioritize endurance, reliability, and continuous presence over mobility and range. Tethered platforms are typically employed from fixed or semi fixed positions such as command posts, vehicles, staging areas, or secured sites.

Operational Employment Characteristics (Informational, Non Evaluated):

Tethered platforms are employed to maintain continuous aerial presence over a defined area for extended durations where battery limited aircraft would be impractical. These systems are expected to remain airborne for extended periods without cycling batteries; operate from stationary or semi stationary ground elements; provide persistent visual overwatch, communications relay, or sensor coverage; support command, coordination, or safety functions rather than maneuver centric ISR; and be integrated into command post or vehicle based operations. This subsection provides operational context only and does not establish additional mandatory requirements.

Mandatory Requirements (Pass/Fail):

Operational Role and Persistence:

• The system shall be designed to provide continuous or near continuous aerial presence for extended durations.

• The system shall support persistent overwatch, observation, or communications support without reliance on onboard battery endurance.

• The system shall be suitable for employment as a stationary or semi stationary asset.

Tether and Power Architecture:

• The system shall utilize a physical tether to provide continuous power delivery between the aircraft and ground element.

• The tether shall support data transmission, either integrated within the same tether or via a dedicated parallel conductor, sufficient to sustain command, control, and payload data flows during continuous operation.

• The system shall include an integrated or companion tether management system to control deployment, retraction, and tension.

• The system shall support safe and controlled ascent, descent, and tether handling during operation.

Flight and Control Characteristics:

• The system shall support stable hover and precise positional control appropriate for persistent observation.

• The system shall be capable of maintaining a fixed or operator defined altitude for extended periods.

• The system shall support controlled recovery in the event of power interruption, tether fault, or system malfunction.

Video, Sensors, and Payloads:

• The system shall provide a continuous real time video feed suitable for sustained situational awareness.

• Sensor performance shall justify persistent employment; systems with limited utility for overwatch or monitoring are not acceptable.

• The system shall support payload operation consistent with tethered employment (e.g., cameras, sensors, relay payloads).

Control and Communications:

• Command, control, and data transmission shall be supported via the tether and/or dedicated local links.

• The system shall not require cellular connectivity for basic flight operations.

• Any cloud enabled functionality shall comply with the cybersecurity framework defined in Section 5.1.

Safety and Site Integration:

• The system shall incorporate safety features appropriate for continuous operation over personnel, vehicles, or civilian areas.

• The tether shall be designed to minimize entanglement risk and withstand environmental stress consistent with sustained deployment.

Cybersecurity and Data Handling:

• The system shall be capable of meeting Moderate or High Security Level requirements under Section 5.1.

• Systems evaluated at Moderate or High Security Level that rely on cloud services shall meet applicable FedRAMP requirements.

• Mission data shall not be automatically uploaded to external servers unless explicitly approved by the Government.

Logistics and Sustainment:

• The system shall be supportable for extended duration deployment at fixed or semi fixed locations.

• Ground based components shall be transportable and deployable without specialized infrastructure.

Value Added Features (Evaluated, Non Mandatory):

• Extended operational altitude beyond minimum tethered requirements.

• Integrated communications relay payloads (e.g., mesh radio nodes) to extend or reinforce ground communications.

• Integration with situational awareness and command and control tools (e.g., ATAK).

• Redundant power sources or failover mechanisms for ground systems.

• Environmental hardening enabling sustained operation in adverse weather conditions (e.g., wind, precipitation).

• Rapid setup and teardown capabilities for mobile command post or vehicle based use.

5.2.7 LIFT PLATFORMS (<50 POUNDS)

Lift Platforms (<50 pounds) are mission support sUAS systems intended to transport, position, and optionally release payloads weighing less than 50 pounds in support of logistics, emergency response, disaster relief, firefighting support, and time sensitive resupply operations. These platforms prioritize lift capability, stability under load, and controlled payload handling over endurance, speed, or maneuver precision. The primary purpose of this category is payload movement, not ISR.

Operational Employment Characteristics (Informational, Non Evaluated):

Lift Platforms (<50 lb) are employed to move physical payloads where ground access is delayed, dangerous, or impractical. These systems are expected to operate at short to moderate ranges while carrying variable payload weights; maintain stability and controllability under load;

support deliberate, safety conscious flight profiles; be employed in cluttered, austere, or degraded environments; and prioritize safe payload retention and recovery over mission completion. This subsection provides operational context only and does not establish additional mandatory requirements.

Mandatory Requirements (Pass/Fail):

Lift Capability and Payload Handling:

• The system shall be capable of lifting and sustaining controlled flight with a payload weighing less than 50 pounds.

• The system shall demonstrate stable flight and controllability across a representative payload range within the category (e.g., 10–49 pounds).

• The system shall support secure attachment of user configurable payloads using mechanisms appropriate for aerial transport.

Endurance Under Load:

• The system shall support a minimum flight endurance of 20 minutes while carrying its maximum rated payload.

Mission Scope and Employment:

• The system shall be suitable for lift, transport, and delivery missions in support of emergency response, disaster relief, firefighting support, or logistics operations.

• The system shall not rely on external network connectivity, cloud services, or third party infrastructure to perform basic lift, flight, payload retention, or recovery functions.

Flight Control and Safety:

• The system shall support either active piloting or operator supervised flight, depending on system design.

• On loss of command and control, the system shall support configurable fail safe behaviors appropriate to payload carriage, including controlled landing or recovery.

• Fail safe behaviors shall prioritize public safety and payload containment over mission continuation.

Control and Communications:

• The system shall maintain reliable command and control links appropriate to lift and delivery operations.

• The system shall not require cellular connectivity for basic flight operations.

Cybersecurity and Data Handling:

• The system shall be capable of meeting Low or Moderate Security Level requirements under Section 5.1.

• The system shall not automatically upload mission data to external servers.

• Cloud dependent functionality, if present, shall be capable of being disabled.

Value Added Features (Evaluated, Non Mandatory):

• Operator controlled or automated payload release mechanisms.

• Enhanced payload stabilization or damping systems.

• Extended endurance beyond minimum requirements while carrying payload.

• Increased operational range under load.

• Modular or quick change payload attachment interfaces.

• Integration with situational awareness or command and control tools (e.g., ATAK) where mission appropriate.

• Environmental hardening enabling operation in adverse weather conditions (e.g., wind, precipitation) while carrying payloads.

• Precision placement or winch based delivery mechanisms.

5.2.8 HEAVY LIFT PLATFORMS (≥50 POUNDS)

Heavy Lift Platforms (≥50 pounds) are high consequence mission support sUAS systems designed to lift, transport, position, and optionally release payloads weighing 50 pounds or greater in support of disaster response, firefighting, emergency logistics, infrastructure support, and similar operations where payload mass, not ISR, is the dominant requirement.