The most common question in UAS procurement is “which platform should we get?” The correct answer to that question starts with a different question: what group classification does your mission requirement actually demand?
Group classification — the FAA and DoD framework for categorizing UAS by weight and operating altitude — is not a marketing distinction. It determines payload capacity, endurance, airspace and regulatory treatment, and the operational ceiling of the platform you are procuring. Mismatching platform class to mission requirement produces either a platform that cannot execute the mission or a platform that is larger, more complex, and more expensive than the mission requires.
Both errors are expensive. The second one is more common.
The Classification Framework
DoD UAS Group classification is defined by maximum gross takeoff weight and normal operating altitude.
Group 1 covers platforms under 20 pounds with operating altitudes below 1,200 feet AGL. These platforms are suited for close-range reconnaissance, short-duration surveillance, and training operations where endurance and payload capacity are secondary to portability and low cost of operation. Regulatory treatment is relatively straightforward. Operational complexity is low.
Group 2 covers platforms between 21 and 55 pounds with operating altitudes up to 3,500 feet AGL. This class represents the most operationally significant expansion over Group 1: meaningful payload capacity (typically 4–8kg depending on configuration), substantially increased endurance (2–5 hours depending on propulsion), and the ability to carry intelligence-grade sensor payloads, communications relay equipment, or AI inference hardware simultaneously. The regulatory and operational complexity increases proportionally.
Group 3 covers platforms between 55 and 1,320 pounds with operating altitudes up to 18,000 feet MSL. Within Group 3, the practical operational category for most non-enterprise programs is platforms in the 55–150 pound range: endurance of 6–12+ hours, payload capacity of 10–25kg, and the operational profile required for persistent ISR, multi-sensor simultaneous operation, and extended-duration autonomous missions. Regulatory requirements at Group 3 include airspace integration considerations that Group 2 operations typically do not face at the same scale.
The Procurement Mismatch Problem
The characteristic error in the current market is procuring a Group 1 or light Group 2 platform for a mission requirement that actually demands Group 2 or Group 3 capability, driven by a lower acquisition price that appears favorable until the platform cannot execute the mission it was procured for.
The mechanism is predictable. An agency writes a requirement around the missions they are currently conducting under BVLOS and payload constraints imposed by their existing platforms. The requirement, shaped by current operational limitations, appears to be satisfiable by a less capable platform. The less capable platform wins the procurement on price. The agency then encounters missions — extended perimeter surveillance, multi-sensor ISR, fire monitoring requiring thermal and EO simultaneous operation — that the procured platform cannot execute. A second procurement follows.
The two-procurement path consistently costs more than a single correctly scoped procurement would have, in addition to the operational gap during the period when the underspecified platform was in use.
How to Scope the Group Requirement
The correct way to determine required platform class is to work backward from operational requirements, not forward from available budget.
Payload capacity drives the minimum class. What sensors, communications equipment, or payloads does the mission require simultaneously? Each payload element has a weight. Sum the payload weight, add structural and battery reserves, and you have a minimum platform capacity. If simultaneous EO/IR, communications relay, and AI edge inference hardware totals 6kg, you need a platform with 6kg+ of usable payload margin — which eliminates most Group 1 platforms and many light Group 2 configurations.
Endurance drives the minimum group. How long does the mission require continuous on-station coverage? Short-duration reconnaissance (under 90 minutes) is achievable with Group 1 or light Group 2 platforms. Area surveillance requiring 3+ hours on station demands mid-to-heavy Group 2. Persistent ISR, extended maritime or border patrol, or wildfire perimeter monitoring requiring 6+ hours on station requires Group 3 endurance.
Range drives BVLOS requirements. How far from the launch point does the mission require the platform to operate? Visual line of sight operations max out at roughly 1–2km depending on conditions and observer capability. Operations beyond that range require BVLOS authority and platforms with reliable beyond-line-of-sight communications links and detect and avoid capability — elements that are present in purpose-built BVLOS platforms and absent in platforms designed for visual line of sight operation.
Autonomy requirements drive compute requirements. If the mission requires real-time AI inference at the edge — fire detection, target recognition, autonomous navigation — the platform’s compute architecture is a mission-critical specification element, not an optional upgrade. A platform without sufficient onboard compute to execute the required inference workload cannot perform the mission regardless of its group classification.
Group 2 Mission Profiles
Group 2 platforms are optimally suited for the following mission profiles.
Infrastructure inspection requiring coverage of defined corridors or facilities with a 2–5 hour endurance requirement, where the sensor payload is a single EO/IR system and real-time video downlink.
Short-duration ISR in support of ground operations where sortie duration is under 3 hours, the operational area is within 15–20km of the launch point, and payload requirements are manageable within a 4–6kg capacity.
AI detection deployment for area surveillance, wildfire monitoring, or search and rescue operations where mission duration is under 4 hours and a single detection module is sufficient for the operational requirement.
Training and development programs where the platform serves as a testbed for AI model development, sensor integration, or operator certification in an environment where endurance and payload capacity are secondary to cost of operation and ease of maintenance.
Group 3 Mission Profiles
Group 3 platforms are the correct choice for the following mission profiles.
Persistent ISR requiring 6+ hours of continuous on-station coverage, where the operational cost of launching multiple Group 2 sorties to maintain coverage exceeds the operational and acquisition cost differential of a Group 3 platform.
Multi-sensor simultaneous operation where payload requirements include EO/IR imaging, AI edge inference hardware, communications relay, and potentially additional sensors operating simultaneously. The payload capacity to run a full sensor suite simultaneously without compromise is characteristic of Group 3 platforms, not Group 2.
Extended-range BVLOS operations where the mission area is beyond the practical range of a Group 2 platform given endurance constraints, or where the operational tempo requires persistent coverage across a geographic area that demands extended range.
Payload delivery or specialized payload operations where the weight or volume of the required payload exceeds Group 2 capacity. Agricultural applications, aerial application, and heavy sensor package deployment are in this category.
The Upgrade Path Question
A well-structured UAS acquisition accounts for the upgrade path from current requirements to future requirements.
Programs that begin with Group 2 capability should be evaluating whether their mission requirements are likely to expand into Group 3 territory within the platform’s lifecycle. If they are, procurement decisions that create architectural compatibility between Group 2 and Group 3 platforms — shared operator training, compatible ground control systems, common sensor payload interfaces — reduce the total cost of the eventual expansion.
Platforms that share flight controller architecture and operational profiles allow operators trained on Group 2 to transition to Group 3 operations without retraining from scratch. Platforms on incompatible architectures create a training debt that is paid when the capability expansion occurs.
Forge & Flight Labs LLC manufactures platforms across Group 1, Group 2, and Group 3 classifications. All platforms share open autopilot architecture and common operational profiles, enabling training investments at any tier to transfer forward as mission requirements grow. Contact us to discuss your specific mission requirements and the platform configuration best matched to them.