M1-T1: Introduction to UAVs and their classifications

Learning objectives

After this lesson, you should be able to:

• Classify a UAV by mass, airframe and operation category.
• Relate class to payload, endurance, onboard compute and failure consequences.
• Explain why regulation is by operation and risk, not only by mass, and where to find the rules that apply.
• Choose a class for a GNSS-denied inspection mission and justify it.

Conceptual explanation

UAVs are classified along several independent axes: mass (micro, small, medium, large), airframe (multirotor, fixed-wing, VTOL; lesson M1-T2), endurance and range, autonomy level (remotely piloted, automated, autonomous) and regulatory category. No single global scheme exists: regulators and militaries each define their own groups, and the numerical limits differ.

Engineering intuition

Mass is the master variable because everything scales with it: required thrust, battery size, impact energy and so the harm a failure can do. A 250 $g$ drone and a 25 kg drone fail in very different worlds, so the safety case, the redundancy and the acceptable risk differ by orders of magnitude. For autonomy design this has a direct meaning: a heavy vehicle can carry redundant sensors and a powerful computer but must justify safety far more rigorously; a light one must make do with less and is operated under lighter rules.

Regulation follows risk of the operation: where, how close to people, beyond visual line of sight or not. Mass is one input. The numeric limits and category names are jurisdiction-specific and change; always read the current rule for the place you fly.

Mathematical formulation

Kinetic energy at impact is a useful common measure of consequence, and shows why mass and speed both matter:

Wing loading and disc loading characterise airframe class: disc loading (thrust per rotor disc area) for rotorcraft and wing loading (weight per wing area) for aeroplanes; both feed the power estimates of the next lesson. Endurance is the usable energy divided by average power:

$m$, $v$

vehicle mass (kg) and speed (m/s).

$E_{\text{battery}}$

pack energy (Wh).

$P_{\text{avg}}$

mean electrical power (W); see lessons M1-T2 and M1-T7.

Architecture and data flow

For system design, class selection is the first row of the requirements table: mission radius, payload mass, endurance, environment and autonomy level lead to a class; the class then constrains the mass budget, which constrains compute and sensors (lessons M1-T10, M7-T12 and M7-T13), and sets the regulatory process that the verification plan must serve (lessons M8-T3 and M8-T5).

Real-world UAV applications

• Choosing a platform for indoor GNSS-denied inspection (small multirotor).
• Long-range mapping where hover is unnecessary (fixed-wing or VTOL).
• Deciding which regulatory process applies before any flight testing.
• Estimating whether a candidate payload (a LiDAR and a Jetson) fits a vehicle class at all.

Implementation example

This runs as shown: a small helper that screens a mission against vehicle classes by payload and endurance, and computes impact energy. The class boundaries are illustrative, not regulatory.

def impact_energy_j(mass_kg, speed_ms): return 0.5 * mass_kg * speed_ms ** 2

CLASSES = [  # name, max take-off mass (kg), typical max payload fraction, typical endurance (min). Illustrative, not regulatory.
    ("micro", 0.25, 0.10, 10), ("small multirotor", 25.0, 0.25, 35), ("small fixed-wing/VTOL", 25.0, 0.20, 90),
]

def screen(payload_kg, endurance_min):
    ok = []
    for name, mtom, frac, endu in CLASSES:
        if endu >= endurance_min and payload_kg <= mtom * frac: ok.append(name)
    return ok

# A GNSS-denied inspection mission: stereo camera + LiDAR + companion computer + gimbal-free = about 1.2 kg payload, 20 minutes
print("candidates:", screen(1.2, 20))
assert screen(1.2, 20) == ["small multirotor", "small fixed-wing/VTOL"] and screen(1.2, 60) == ["small fixed-wing/VTOL"] and screen(0.02, 5) == ["micro", "small multirotor", "small fixed-wing/VTOL"]
assert impact_energy_j(1, 10) == 50 and abs(impact_energy_j(25, 15) - 2812.5) < 1e-9

Common engineering mistakes

Failure modes

Debugging approach

1. Write the mission as numbers (radius, payload, endurance, environment) before comparing classes.
2. Check each number against a measured or published figure for a real vehicle in the class.
3. Read the operating rules for the jurisdiction and write the operating limits as requirements (lesson M8-T1).
4. Recompute endurance with the payload’s power included.

Practical exercises

1. Pick a class for a 30-minute tunnel inspection with a 1.5 kg payload and justify the mass and endurance.
2. Compute the impact energy of a 2 kg vehicle falling from 30 m (ignoring drag) and compare it with 1 kg at 10 m/s.
3. Find the rule for small UAS in your country and list its mass limit and its main operating conditions.
4. List three requirements that change when the same vehicle flies beyond visual line of sight.

Interview questions

Write an answer in your own words, then reveal the model answer. Nothing is sent anywhere.

References and further reading

Primary papers, official documentation and standards. Each claim above that is specific to a tool or version points here.

• EASA: operating a drone (open, specific and certified categories)
• FAA: commercial small UAS operations (Part 107)
• EASA: specific category civil drones (operational risk assessment, SORA)
• $K$. $P$. Valavanis, $G$. $J$. Vachtsevanos (eds.), Handbook of Unmanned Aerial Vehicles, Springer, 2015.

What’s next