Prepare for AUVSI Trusted Operator Program Level 2 by rehearsing complete mission decisions rather than isolated facts. Take a fictional flight task each week, produce an airspace classification call, a weather judgment with named products, three risks with measurable mitigations, and a crew briefing. Score your own output against a fixed rubric so weak links in the chain become visible before exam day. AUVSI's own site (auvsi.org) remains the authority for current eligibility, format, and administrative requirements; this plan covers the reasoning skills you can build on paper.
Study decisions, not flashcards: the mission-planning lens
Structure every study session around one end-to-end mission decision instead of a topic list. This forces airspace, weather, and risk knowledge to connect the way a professional operator's workflow demands.
Pick a single fictional mission — for example, a roof-inspection flight at the edge of a suburban industrial park — and require yourself to produce four artifacts before the session ends: an airspace call with the chart evidence you relied on, a weather judgment naming the products you used, three written risks each paired with a measurable mitigation, and a one-line crew briefing. This converts passive review into an operator's deliverable.
The contrast with topic-by-topic study shows up in retention of relationships, not just items. When you memorize airspace rules separately from weather rules, you can answer a fact question but stall when one scenario requires both. When every session ends in a chained decision, you learn which knowledge gates which step of a flight — authorization before launch, trend check before the go/no-go, mitigation written before the battery is ever installed.
Making an airspace call for a mission site, not a chart quiz
Practice identifying the airspace class at a specific point, near a boundary, under a specific operational condition — because authorization and communication duties follow from that combination.
Worked scenario: you plan photogrammetry at a point 4.2 nm from the center of a Class D airport, and your planning app shows the facility layer but you skim past the dotted boundary and the tower's operating status. The plausible mistake is assuming a Class D surface area applies identically at all hours, or that the app's color patch equals the legal boundary. The better decision is to confirm the boundary on a sectional or the app's airspace layer, then treat controlled airspace as conditional on the facility being active — and document in your mission file what the boundary was, what the class was, and what authorization you obtained.
Why it matters: the authorization you need, and the communication duty you carry, change entirely between the active and inactive states of that facility, and between inside and outside the boundary. Build the habit of writing the call as a full sentence — 'site X is under the Class D surface area of Airport Y, facility expected active at the planned time, authorization obtained via Z' — rather than a checkbox. A sentence exposes gaps; a checkbox hides them.
- Self-check: your airspace call names the chart or app layer you used, the class, the boundary distance, and the authorization path.
- Self-check: you can state what changes if the tower is not operating at your planned launch time.
- Self-check: you rehearsed at least one site on a boundary, not only deep inside a class.
Reconciling weather products in time order instead of picking a favorite
Practice reading current observations, scheduled forecasts, and any flight-specific tools as one timeline, because each product answers a different question about a different time window.
Worked scenario: the night before a morning survey flight, you study a terminal-area forecast that shows light wind, and you plan confidently. The plausible mistake is stopping there — a forecast is a prediction for a window, not an observation, and it cannot show a gust front that has already arrived by your launch time. The better decision is to sequence the products the next morning: read the current observation for actual conditions at the nearest station, compare it against what the forecast predicted, and treat any divergence as a signal to widen your safety margin or re-plan.
A short exercise makes the difference stick: write down, in order, what each product you use can and cannot tell you — an observation reports what already happened at one station; a forecast predicts a window ahead; a flight-level wind estimate refines both for your actual altitude. Then run one morning where you deliberately check the observation first. Notice how often the observed wind direction differs from the forecast, and how that changes your departure heading, your escape route, and your abort trigger.
Turning vague risks into mitigations you could actually execute
Separate the three planning concepts — hazard, risk, mitigation — and force every mitigation to include a trigger, an action, and a responsible role. Vague mitigations fail precisely when conditions deteriorate.
Worked scenario: your mission plan lists 'high winds' as a risk and the mitigation 'pilot will exercise caution.' The plausible mistake is treating that sentence as a completed plan. It names no threshold, so in the moment the pilot must invent a limit under stress; it names no action, so there is nothing to execute; and it names no role, so on a two-person crew nobody owns the decision. The better version reads: 'Risk: gusting wind exceeds capability for the aircraft. Mitigation: if sustained wind at 100 ft AGL exceeds 20 kt, or the gust spread exceeds 10 kt, the crew chief calls abort and the pilot lands at the pre-briefed alternate field.'
Why it matters: a mitigation with a trigger is testable — you can check the observation against the number and get a clean go/no-go — while 'exercising caution' cannot be audited and cannot be briefed. Write every mitigation in the cause-threshold-action-role form and read it aloud; if you cannot say it in one breath, it is too vague to execute under pressure. This single rewrite habit upgrades an entire risk section of a mission plan.
| Concept | What it answers | Drone example | Weak form | Strong form |
|---|---|---|---|---|
| Hazard | What could cause harm? | Gusting wind at the site | 'Weather' listed generically | 'Wind gusts at 100 ft AGL above aircraft capability' |
| Risk | How likely and how severe? | Loss of control near people | 'It might be dangerous' | 'Moderate likelihood, high severity, people downwind' |
| Mitigation | What specific control reduces it? | Abort and alternate landing | 'Pilot will be careful' | 'If gust spread exceeds 10 kt, crew chief calls abort; pilot lands at alternate field' |
Crew roles: rehearsing the brief and the call-out on paper
Practice defining who says what and when — a launch brief, in-flight call-outs, and an abort authority — because role ambiguity, not technical failure, is what a written scenario most efficiently exposes.
Operator-level UAS work is frequently a crew activity: a remote pilot in command, a visual observer, and sometimes a mission lead. On paper, rehearse the communication loop for one mission: before launch, each role states its responsibilities in one sentence; in flight, the visual observer uses fixed phraseology for traffic and obstacles ('traffic, two o'clock, high'); and the plan names who holds abort authority and how it is voiced. The rehearsal point is that a role is a set of expected statements, not a job title.
Exercise: take your scenario mission and script the two lines most likely to be improvised badly — the abort call and the lost-link or lost-sight event. Write the exact words. Then have a study partner play the visual observer while you fly a tabletop version of the mission, moving a model aircraft across a sketch of the site. Watch where the communication breaks down: usually at the moment both people assume the other has the picture. Debrief that moment specifically, and rewrite the brief so the hand-off of information, not just the hand-off of task, is explicit.
Abnormal events: deciding in priority order, not by reflex
Rehearse abnormal and emergency sequences as ordered decisions — maintain control, keep people clear, then resolve the event — so your first written response is never an equipment fix while the aircraft drifts.
For paper practice, build three abnormal-event cards: lost link, degraded battery indication, and an intruding aircraft near the flight path. For each, write your response as a numbered sequence and then interrogate the ordering. The disciplined order runs: first, what keeps the aircraft controllable; second, what keeps people and other airspace users clear; third, what resolves the underlying problem. A common weak answer jumps straight to re-establishing the link while the aircraft continues toward a people area — the sequence matters more than the technical step.
Link this back to the mitigation writing from the risk section: an abnormal card is only useful if it inherits the triggers and roles already defined in your plan. The pre-briefed alternate field, the abort authority, and the call-out phraseology you scripted for crew roles are exactly what makes an emergency response executable rather than improvised. When you self-score, check that every emergency card references something that already exists in the mission plan — if it introduces a brand-new location or role, the plan itself has a gap.
An adaptable four-week sequence and readiness checks
Run a four-week cycle — charts, weather, risk and crew, then full integration — with one written scenario per session and a fixed self-scoring rubric as your milestone tracker.
Week 1: airspace and charts — one boundary site per session, full airspace calls, and a re-check of what changes when a facility is inactive. Week 2: weather — sequence observations and forecasts for the same mission, note divergences, and set wind triggers in measurable numbers. Week 3: risk and crew — rewrite one old risk list into cause-threshold-action-role form and script the abort and lost-sight lines. Week 4: integration — two complete mission plans end to end, each timed, each scored. Adjust the weighting if your rubric shows one lane lagging; the sequence adapts to your scores, not a calendar.
Use this rubric per scenario, scoring each of five items 0 to 2 (absent, partial, complete): airspace call names source, class, and authorization path; weather judgment names products and reconciles observation with forecast; three risks each carry a measurable mitigation; crew brief assigns abort authority in exact words; emergency cards reference existing plan elements. Ten points maximum. Treat 8 or higher as a learning milestone that tells you the chain holds together — it is a study signal, not a prediction of any exam outcome, and it still leaves room to identify one weak lane. Readiness checks before exam day: you can produce a complete mission plan in one sitting, explain any single decision in under sixty seconds, and re-derive an abort trigger from the aircraft's stated limits rather than from memory of a random number. For current eligibility, format, and administrative requirements for TOP Level 2, confirm directly with AUVSI at auvsi.org, as credential details are maintained by the issuer.
- Readiness check 1: one sitting produces all four mission artifacts without reopening study notes.
- Readiness check 2: any decision in your plan can be justified in sixty seconds with its evidence named.
- Readiness check 3: your rubric score of 8 or higher is reached on two consecutive integrated scenarios.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.