Week 01 · lesson
Mission, Authority, and Boundaries
A drone mission begins before anything powers on.
That is not dramatic safety language. It is how responsible UAS work actually functions. The first engineering decision is not "which drone looks best?" The first decision is whether the mission is defined, bounded, and allowed.
This course does not certify you to fly. It does not give you permission to operate an aircraft. It does not replace current FAA rules, local law, school policy, parent permission, site permission, or the judgment of a qualified adult supervisor.
What it can teach you is how to reason like someone who respects those boundaries.
Mission purpose comes first
A mission purpose explains why the UAS exists for this task.
Weak purpose:
Fly over the baseball field.
Better purpose:
Capture overhead images of standing water on the baseball field so grounds staff can decide which areas need drainage review.
The second version is more useful because it names the product and the person who will use it.
A mission purpose should answer four questions.
| Question | Example answer |
|---|---|
| What decision or product is needed? | Identify water accumulation areas |
| Who needs it? | Grounds staff |
| What evidence will the UAS collect? | Overhead images with location notes |
| What is outside the mission? | Flying over nearby homes, people, or roads |
The last row is important. A boundary is not a failure of imagination. It is how the mission stays controlled.
Authority is not the same as capability
A drone may be physically able to fly somewhere. That does not mean it is appropriate or allowed.
Capability asks:
Can the system do this?
Authority asks:
Are we allowed to do this under the relevant rules and supervision?
Safety asks:
Should we do this under today’s conditions?
Evidence asks:
What will prove that the mission worked?
A responsible UAS decision needs all four.
The aircraft does not care whether you have authority. The propellers will spin if the system allows it. That is exactly why humans must do the slower thinking before the fast machine moves.
Study versus operation
In this course, you may study mission planning, analyze examples, compare aircraft categories, inspect supplied evidence, and build simulation-first decision records.
That is not the same as operating a real aircraft.
Use this distinction:
| Course activity | What it can prove | What it cannot prove |
|---|---|---|
| Reading a rule summary | You can identify a concept | You are authorized to fly |
| Completing a mission plan | You can reason through constraints | The site is approved for flight |
| Using a simulator | You can practice choices safely | Real weather and hardware will behave the same way |
| Inspecting supplied images | You can evaluate evidence quality | You personally collected lawful flight data |
| Handling hardware under supervision | You can identify parts and risks | You may operate independently |
This is not meant to scare you away from drones. It is meant to keep the difference clear.
The operating boundary
An operating boundary defines where the mission is allowed to happen and where it is not.
A useful boundary includes:
- physical space: buildings, fields, trees, roads, sidewalks;
- vertical limits: how high the aircraft may be planned to operate;
- people: where bystanders may appear and how the team prevents unsafe exposure;
- time: start, stop, light, weather, and school schedule constraints;
- data: what may be captured, stored, shared, or deleted;
- authority: who can approve, pause, or cancel.
A vague boundary sounds like:
Around the school.
A better boundary sounds like:
The planned observation area is the east practice field only. The aircraft must remain within the field boundary and away from the parking lot, building entrances, and people. The mission stops if people enter the planned area or wind exceeds the supervisor's limit.
That is much less exciting. Good. Excitement is not a safety plan.
No-go conditions
A no-go condition is a reason to stop or refuse the mission.
No-go decisions are not signs that the team failed. They are signs that the team understands the system.
Examples:
| No-go condition | Why it matters |
|---|---|
| People are inside the planned operating area | The mission boundary is broken |
| Weather exceeds the planned limit | The aircraft may not behave as expected |
| Battery condition is unknown or damaged | Power risk is not controlled |
| The needed permission is missing | Authority is not established |
| The mission product is unclear | The flight may create risk without useful evidence |
| The communication link is unreliable | Control and telemetry may be compromised |
A no-go decision should be recorded. Future teams learn from recorded decisions. "We just felt weird about it" is less useful than "Wind gusts exceeded the planned limit by 5 mph."
Worked example: boundary note for a field-mapping idea
Mission idea:
Map the school practice field after heavy rain.
Draft boundary note:
The mission product is a set of overhead images showing standing water locations on the practice field. The planned area is the practice field only. The mission excludes nearby roads, parking lots, building entrances, and any area with people present. A qualified supervisor must verify current rules, site approval, weather limits, and battery condition before any real operation. For this course task, students will create the plan and evaluate supplied or simulated evidence only.
Now inspect the note.
It names the product. It names the space. It names excluded areas. It separates course planning from real operation. It puts authority with a qualified supervisor instead of pretending a worksheet authorizes flight.
That is a responsible boundary note.
Misconception: "It is just a small drone"
Small does not mean harmless. A small aircraft can still injure someone, damage property, capture inappropriate data, or create a situation that the team cannot control.
The risk is not only mass. Risk also includes speed, propellers, battery energy, altitude, people nearby, operator skill, weather, permissions, and what the mission asks the team to do.
If you hear "It is just a small drone," translate it into an engineering question:
Which risks are lower because it is small, and which risks are still present?
That question is useful. The shortcut is not.
Build your responsible-use boundary note
Choose one mission idea from Lesson 1. Write a boundary note with these labels:
- Mission product
- Intended user
- Planned area
- Excluded area
- Data boundary
- Authority needed
- No-go conditions
- Course-only limitation
The course-only limitation should be explicit. Example:
This course task is a planning and evidence-analysis exercise. It does not authorize real flight.
Check your understanding
Why does authority matter if the aircraft is physically capable?
Because a system can be physically able to do something that it is not allowed or safe to do. Engineering decisions must include permission, supervision, rules, and risk.
What is a no-go condition?
A specific condition that requires the team to stop, delay, or refuse the mission.
Why should boundaries include data?
Because UAS missions can collect images and location information. Responsible use includes what data is captured, stored, shared, and excluded.
Success criteria
Your boundary note is ready when it:
- names a specific mission product;
- identifies who would use that product;
- defines the planned and excluded areas;
- names at least three no-go conditions;
- separates course planning from real operation;
- avoids claiming that this course authorizes flight.
If your note could be used to justify flying anywhere because "we have a drone," it is not done yet.