A procurement-focused comparison of Class I and Class II UAS ground infrastructure — from maintenance bay dimensions through crew sizing — for operators planning mixed-fleet operations or transitioning between platform classes.
NATO divides unmanned aircraft systems into three classes based on maximum takeoff weight, operating altitude, and mission scope. This classification — outlined in STANAG 4670, STANAG 4703, and associated documents — is more than administrative. It drives fundamentally different ground infrastructure requirements that procurement officers frequently underestimate when moving from experimental UAS acquisition to operational capability.
This article focuses on the two classes most commonly procured by defence forces, border security agencies, and commercial operators: Class I (small UAS under 150 kg) and Class II (medium UAS 150–600 kg). Class III platforms (over 600 kg) operate from fixed airfield infrastructure that is a different procurement category.
The NATO classification thresholds establish baseline operating characteristics, though specific platforms within each class vary significantly in detailed requirements.
Under 150 kg maximum takeoff weight, Class I platforms operate typically below 5,000 feet above ground level and serve tactical reconnaissance missions. Endurance ranges from 2 hours (micro UAS) to 12 hours (larger Class I platforms). Common platforms include:
Between 150 and 600 kg, Class II platforms operate typically from 5,000 to 18,000 feet and serve operational-level ISR missions. Endurance reaches 24 hours. Common platforms include:
The infrastructure gap between Class I and Class II operations is significant — typically 3–5x larger facility, 4–8x higher power demand, and 2–3x larger crew. Understanding these scaling factors helps procurement plan realistic facility investments.
Maintenance bay dimensions are the dominant driver of facility sizing. Class I platforms fit in a compact bay — 6 × 4 m comfortably accommodates a ScanEagle (3.1 m wingspan) with surrounding workspace for maintenance access. Class II platforms require substantially more space. An Elbit Hermes 450 has 10.5 m wingspan; accommodating it with workspace access and surrounding parts and tool storage easily consumes 10 × 8 m.
Ceiling height follows the same pattern. Class I platforms with 3.0 m ceiling can be maintained at working height; Class II platforms with larger wings and taller tail sections need 4.5 m clear ceiling for access to upper surfaces and vertical stabilisers.
Class I operations are electrically modest. GCS workstations, battery charging for small UAS batteries, climate control for the modest facility footprint, and lighting add up to 30–50 kVA peak demand. A standard 63A three-phase supply handles this comfortably.
Class II operations require significantly more electrical capacity. Larger GCS workstation count, fuel-based platform support systems (typical Class II platforms are fuel-based rather than electric), HVAC for larger facility, and tactical data processing infrastructure push peak demand to 80–150 kVA. 200A three-phase supply or dedicated substation becomes necessary.
This is where the two classes diverge most dramatically. Class I operations offer options: catapult launch (works anywhere with level ground), hand-launch (works anywhere with an operator), short runway (200–400 m), or VTOL (rotary-wing or VTOL variants). Recovery is typically arresting net for catapult-launched systems or skid/belly landing for smaller platforms.
Class II operations require proper runway. Minimum take-off distance for typical Class II platforms ranges from 400 m (Shadow variants, short take-off configurations) to 1,200 m (Hermes 450 and similar). Paved surface is preferred; some platforms accept prepared dirt or gravel. Recovery requires conventional landing rollout, meaning runway length equivalent to take-off plus margin for rollout and stopping distance.
Many UAS operators — particularly border security forces and military ISR units — operate mixed fleets combining Class I and Class II platforms. This introduces design considerations that single-class operations do not face.
Modern GCS architecture increasingly supports multi-platform operation through NATO STANAG 4586 compliance. A single GCS workstation can control platforms from different manufacturers and different classes, as long as the platform's ground control interface conforms to STANAG 4586 data standards. This is operationally powerful: one crew qualification set works across multiple platforms; rotating crews between platforms becomes straightforward; reduced workstation count versus dedicated per-platform GCS.
The facility implication is that the GCS workspace can be unified across Class I and Class II operations, reducing total workspace needs compared to completely separate infrastructure.
Maintenance bays cannot be unified effectively. Class I platforms fit in spaces too small for Class II platforms. Running both through a single large bay is possible but wastes space when only Class I platforms are being worked on. Mixed-fleet operators typically specify adjacent dedicated bays — one Class I bay, one Class II bay — connected by shared workshop infrastructure (parts storage, common tools, administration).
Class I electric platforms and Class II fuel-based platforms run on different logistics streams. Battery charging infrastructure for Class I (typically LiPo or Li-ion battery banks with specialised chargers) has no overlap with Class II fuel supply. Mixed-fleet facilities typically include both: a battery bay meeting NFPA 855 fire safety standards for stationary battery storage, plus an aviation fuel storage area meeting ICAO Aerodrome Design Manual requirements for fuel handling.
The following decision questions help match facility specification to the planned UAS operations:
Specify facility capacity 20–30% above current operational requirement. UAS operations tempo and scope tend to grow after initial deployment — as crew proficiency rises, platform reliability improves, and operational value becomes evident. Under-sized facilities become bottlenecks within 18–24 months. Over-sized facilities provide growth capacity at marginal cost.
Class I and Class II UAS ground infrastructure requirements differ by roughly 3x in physical scale and power demand. Mixed-fleet operations are operationally common and benefit from unified GCS architecture while retaining separated maintenance and logistics infrastructure. Procurement specifications should reflect realistic growth trajectories and the specific regulatory compliance applicable to the deployment context.
For deeper technical content, see the related resources below. structmod engineering is available for requirements consultation under appropriate security clearance framework.