Week 01 · lesson
Mission-System Decision Review
Now you have enough structure to make a first UAS engineering decision.
Not a shopping decision. Not a "which one looks cool" decision. A mission-system decision.
The question is:
Which aircraft category best fits the mission, and what evidence supports that choice?
This lesson gives you a method for answering that without pretending the answer is universal.
Three starting categories
We will use three broad categories this week.
| Category | Useful strengths | Common limits |
|---|---|---|
| Multi-rotor | Hovering, vertical takeoff, precise position changes, close inspection | Shorter endurance, less efficient forward flight, battery-sensitive |
| Fixed-wing | Efficient forward flight, longer range, broad area coverage | Needs forward motion, more launch/landing planning, less useful for stationary close inspection |
| Hybrid VTOL | Vertical takeoff plus wing-borne cruise | More complex, more failure modes, often higher cost and training demand |
These are not brand recommendations. They are engineering patterns.
A mission can point toward one category because of what it needs the aircraft to do.
Criteria before choice
A decision matrix compares options against criteria. The criteria come from the mission.
For Week 1, use these criteria:
| Criterion | What you are asking |
|---|---|
| Payload fit | Can the category carry the sensor or camera needed for the product? |
| Movement pattern | Does the category move the way the mission needs? |
| Endurance need | Does the mission need long efficient coverage or short controlled inspection? |
| Operating area | Does the site support the category’s launch, landing, and movement needs? |
| Boundary control | Can the team keep the operation inside the planned boundary? |
| Evidence quality | Can the category help produce the required data product? |
Notice what is missing: "my favorite." Personal preference is allowed to exist. It just does not get to pretend it is evidence.
Worked example: three mission profiles
Mission A: roof edge inspection
Product: images of roof edges, gutters, and possible storm damage.
Key needs: slow movement, stable hover, angled images, short distance, careful positioning.
Likely category: multi-rotor.
Why: hovering and precise movement matter more than long-distance efficiency. The mission product depends on controlled image angles around one structure.
What could still make it no-go: people entering the area, poor wind, missing authority, battery concern, unclear image-quality requirement.
Mission B: large farm field survey
Product: broad coverage images of crop condition across a large field.
Key needs: efficient coverage, planned path, long endurance, repeated passes.
Likely category: fixed-wing or hybrid VTOL.
Why: the mission is about covering area. A fixed-wing aircraft is efficient in forward flight. Hybrid VTOL may help if launch and landing space is constrained, but it adds complexity.
What could still make it no-go: airspace issues, property permission, insufficient landing plan, weather, unclear data handling.
Mission C: trail erosion check
Product: images of specific erosion points along a trail.
Key needs: multiple target locations, controlled views, obstacles, possibly limited clear space.
Likely category: multi-rotor or hybrid VTOL depending on distance and launch area.
Why: if targets are close and need careful inspection, multi-rotor fits. If targets are spread far apart and launch/landing constraints are difficult, hybrid VTOL may be considered. This is not a one-sentence decision.
What could still make it no-go: people on the trail, trees, wind, permission, poor communication link, or unclear exclusion zones.
The matrix
Use a simple rating scale.
- 3 = strong fit
- 2 = possible fit with tradeoffs
- 1 = weak fit or high constraint
- 0 = not appropriate for this mission
Example matrix for roof edge inspection:
| Criterion | Multi-rotor | Fixed-wing | Hybrid VTOL |
|---|---|---|---|
| Payload fit | 3 | 2 | 2 |
| Movement pattern | 3 | 1 | 2 |
| Endurance need | 2 | 3 | 3 |
| Operating area | 2 | 1 | 2 |
| Boundary control | 3 | 1 | 2 |
| Evidence quality | 3 | 1 | 2 |
| Total | 16 | 9 | 13 |
The total helps, but it is not magic. If one criterion is critical, the team should say so.
For roof edge inspection, movement pattern and evidence quality matter heavily. A fixed-wing aircraft scoring well on endurance does not solve the main problem.
Decision paragraph
A decision matrix is useful, but the final recommendation needs words.
Weak recommendation:
Use a quadcopter because it got the most points.
Better recommendation:
For roof edge inspection, a multi-rotor is the best starting category because the mission needs short-range, controlled positioning and angled image capture more than long-distance endurance. Fixed-wing endurance is useful in other missions, but it does not fit this close inspection as well. The recommendation is still conditional on authority, weather, people-free operating area, battery condition, and a clear image-quality target.
That paragraph does three things:
- names the mission;
- connects the category to mission criteria;
- keeps the safety and authority boundary alive.
That is the difference between a score and an engineering argument.
Misconception: highest total always wins
A matrix can hide bad thinking if the criteria are weak.
Suppose a team gives "cool factor" the same weight as safety boundary control. The matrix may produce a number, but the reasoning is not defensible.
A decision tool does not make the decision for you. It organizes evidence so humans can inspect the reasoning.
If the result seems strange, do not worship the spreadsheet. Check the criteria.
Build your mission-platform matching matrix
Choose one mission:
- roof inspection;
- trail erosion check;
- field water mapping;
- construction progress imagery;
- wildlife habitat observation using supplied evidence only.
Create a matrix with the three categories and six criteria from this lesson.
Then write a recommendation paragraph with this structure:
For [mission], [category] is the best starting choice because [criteria]. [Another category] has [strength], but [reason it is less suitable]. This recommendation depends on [authority/safety/data boundary].
Add one limitation
Every good recommendation includes a limitation.
Examples:
- This analysis does not authorize flight.
- This analysis assumes the mission product is still images, not thermal data.
- This analysis uses broad categories, not a specific aircraft model.
- This analysis does not verify current airspace, weather, or site permission.
- This analysis does not prove the aircraft can carry a particular camera.
Limitations do not weaken your work. They show that you understand what your evidence can and cannot prove.
Check your understanding
Why use criteria before choosing a category?
Because the mission should determine the aircraft category. Criteria prevent the team from choosing based only on preference or habit.
Why might fixed-wing be a poor choice for a roof edge inspection?
It is efficient in forward flight, but close, slow, angled inspection favors hovering and precise position changes.
What does a limitation statement do?
It tells the reader what your evidence does not prove, so the recommendation is not overstated.
Success criteria
Your decision review is ready when it includes:
- one specific mission product;
- a completed matrix with three aircraft categories;
- ratings that are explained by mission needs;
- one recommendation paragraph;
- at least one no-go or authority condition;
- one limitation statement.
If another person cannot see why you chose the category, you have a preference, not a decision review.