FAA Part 107 Advanced Drone Operations Exam Prep

8.1 Visual Line of Sight Requirements and Common Misinterpretations

Visual Line of Sight (VLOS) under Part 107 is not a “camera view” requirement; it is a requirement that the remote pilot can see the aircraft with unaided vision (except for corrective lenses). In exam questions, the key is to separate what the rules require from what your screen happens to show.

What VLOS Means in Practice

Start with the simplest test: if you can’t see the aircraft directly, you are not meeting VLOS. “Directly” matters because a live video feed is not the same as unaided visual contact. If you rely on a zoomed display to identify the aircraft, you may still be able to describe its position, but you are not satisfying the VLOS standard.

Next, consider the environment. VLOS is affected by obstacles and terrain. A tree line, a building, or a ridge can block your view even if the aircraft is still within the allowed distance. In other words, distance alone does not guarantee VLOS.

Finally, remember that VLOS is about the aircraft’s position relative to your eyes, not about the aircraft’s ability to “stay visible” on a screen. If your view is blocked, the mission is not compliant even if the aircraft is flying normally.

Common Misinterpretations That Show Up on Exams

Misinterpretation 1: “If I can see it on the monitor, I’m good.” The monitor is not the required method of seeing. The exam expects you to choose the option that explicitly ties visibility to unaided visual observation.

Misinterpretation 2: “If the aircraft is within a certain distance, VLOS is automatic.” Distance helps, but it does not override line-of-sight obstructions. A short flight behind a wall can fail VLOS.

Misinterpretation 3: “Observers can replace VLOS.” Observers can help maintain situational awareness, but the remote pilot’s VLOS requirement is not satisfied by delegating the visual check entirely. If the remote pilot cannot see the aircraft, the operation is not compliant.

Misinterpretation 4: “If I can see it sometimes, that counts.” VLOS is a continuous condition during flight. If the aircraft becomes obscured for any portion of the flight, you must treat that as a failure of VLOS for that period.

A Systematic Decision Process

Use this step-by-step logic when answering exam scenarios:

1. Identify the visibility method in the answer choice: unaided vision vs. monitor.
2. Check for obstructions: buildings, trees, terrain, or anything that blocks your view.
3. Confirm who is seeing: remote pilot vs. observer vs. both.
4. Assess continuity: is the aircraft visible throughout the relevant segment?
5. Match the scenario to the rule language: if the choice only mentions a screen, it’s usually wrong.

Examples That Train Your Eye

Example 1: The screen fix You fly a small quadcopter over a field. The aircraft is visible to you at takeoff, but as it moves behind a parked trailer, you cannot see it directly. You still see it clearly on your controller screen. The correct exam-style conclusion is that VLOS is not met during the behind-trailer segment because direct unaided visibility is blocked.

Example 2: Distance without visibility You keep the aircraft close, well within typical operational comfort, but you fly it behind a low hill. The aircraft remains within a short horizontal distance, yet your view is blocked by terrain. The correct conclusion is that VLOS fails due to obstruction.

Example 3: Observer assistance limits An observer can see the aircraft when you cannot, and they call out headings and relative position. Even with good communication, the remote pilot’s VLOS requirement is not satisfied if you cannot see the aircraft directly. The best answer emphasizes that observer sighting does not replace the remote pilot’s required visibility.

Quick Self-Check Before You Commit to a Flight

If you can’t answer “Yes” to all three questions—Can I see the aircraft directly? Is my view blocked by anything? Will it stay visible for the whole flight segment?—then the scenario is likely designed to test a VLOS failure.

And yes, the controller screen can be useful for navigation and confirmation, but it is not the compliance substitute the exam is looking for.

8.2 Using a Visual Observer and Defining Roles and Communication

A Visual Observer (VO) helps you maintain situational awareness while you operate under Visual Line of Sight. The VO does not replace your responsibility to see and avoid; instead, the VO expands the “eyes on the scene” so you can make faster, cleaner decisions. Think of the VO as a structured second set of eyes with a defined job, not a helpful bystander who happens to watch.

Foundational Roles and Responsibilities

Remote Pilot In Command (RPIC) remains responsible for the flight path, control inputs, and final “go/no-go” decisions. The RPIC also decides when to pause, stop, or reposition based on what the VO reports.

Visual Observer watches for traffic, obstacles, and anything that could affect safe operation. The VO’s primary focus is outside the aircraft’s immediate viewpoint—where the RPIC might not be looking at every moment.

Optional Spotter or Safety Assistant may handle non-flight tasks like keeping the takeoff area clear or managing ground hazards. If you use one, keep the VO focused on visual scanning so the VO’s attention does not get split.

A practical best practice is to assign roles before you power up. For example, if you’re doing a roof inspection, you can brief: “I fly and control altitude and lateral movement. You watch for people, vehicles, and nearby aircraft. If you see anything, you call it out immediately and keep watching until I confirm the action.”

Communication That Works Under Stress

Good communication is short, consistent, and actionable. The goal is not to describe everything the VO sees; it’s to provide the information the RPIC needs to act.

Use a simple call-and-response style:

• VO calls: what it is, where it is relative to the aircraft, and whether it is moving toward your flight path.
• RPIC confirms: what action you will take (e.g., “Hold position,” “Climb 10 feet,” “Turn left,” “Stop and land”).

Keep calls standardized so you don’t waste time translating. For instance, if the VO sees a person walking into the area, the call should be specific: “Person entering from left, moving toward us.” Then the RPIC responds: “Stop and hold. I’m backing up.”

Defining Scan Patterns and Coverage

A VO should not stare at one spot. A scan pattern prevents “tunnel vision,” especially when the aircraft is moving or when the background is busy.

Common scan patterns include:

• Sector scan: VO divides the area into sectors (front, left, right, behind) and rotates attention.
• Altitude scan: VO checks for traffic at the aircraft’s altitude and also above/below, since aircraft can appear suddenly.
• Ground-to-air scan: VO alternates between near-field obstacles (trees, poles, vehicles) and distant traffic.

Example: During a linear inspection along a road, the VO can scan the direction of travel plus a buffer to the sides. If the aircraft is moving forward, the VO’s scan should lead slightly ahead of the aircraft’s path so hazards are noticed before they become urgent.

Clear Triggers for Immediate Calls

To avoid missed hazards, define triggers that require an immediate call. Examples include:

• Any unplanned person or vehicle entering the operating area.
• Any aircraft appearing in the vicinity, especially if it could intersect your path.
• Any obstacle that could conflict with your planned route, including wires, poles, and branches.
• Any loss of visual clarity (e.g., glare, smoke, heavy shadows) that reduces the VO’s ability to maintain awareness.

A useful rule: if the VO would want the RPIC to change something right now, the VO calls right now.

Example: Two-Person Team Briefing and Execution

Before takeoff, you and the VO agree on three things: role boundaries, call format, and what actions you will take.

Briefing example

• RPIC: “I control the aircraft. If you see traffic or an obstacle, call it immediately with left/right and whether it’s moving toward us.”
• VO: “I’ll scan in sectors and keep watching until you confirm the action.”
• Both: “If you call a hazard, we pause the maneuver until we’re clear.”

In-flight example The aircraft is moving laterally to frame a building sign. The VO sees a small aircraft appear behind and slightly above your path. The VO calls: “Aircraft behind, slightly above, moving toward our line.” The RPIC responds: “Hold position. I’m turning left to increase separation.” The VO continues scanning to ensure no additional traffic enters the area.

Example: Preventing Common Communication Failures

1. Vague calls: “Something’s there.” Fix it by requiring location and movement: “Vehicle on right, moving toward the flight path.”

2. Too much detail: “It’s a red car with a white trailer…” Fix it by focusing on action: “Vehicle entering from right.”

3. No confirmation: VO calls, RPIC doesn’t respond. Fix it by using a confirmation step: “Hold” or “Proceed with the next segment.”

When roles and communication are defined, the VO becomes a reliable safety layer rather than an extra voice. That reliability is what helps you stay compliant and calm—especially when the scene changes faster than your first plan.

8.3 Managing Situational Awareness for Complex Terrain and Crowds

Situational awareness is not a single skill; it’s a chain of small checks that keep you from being surprised. In complex terrain and near crowds, the chain has more links because your view can be blocked, your ground speed can change, and people create unpredictable movement.

Foundational Model for Awareness

Start with a simple loop: See → Understand → Decide → Act → Recheck. “See” means you confirm what’s in front of you and what’s behind you. “Understand” means you translate what you see into risk: obstacles, people, and airspace constraints. “Decide” means you choose the next control action and the next scan point. “Act” means you execute smoothly and within your aircraft limits. “Recheck” means you verify the result before you move on.

A practical rule: if you cannot describe the next 10 seconds of flight in plain language, you are not ready to commit to a maneuver.

Terrain Awareness: Occlusion and Closure Rates

Complex terrain creates two common problems: occlusion and closure rate.

• Occlusion happens when hills, buildings, trees, or even the aircraft’s own attitude hide parts of the scene. If you lose sight of a landing zone behind a ridge, you may also lose sight of people who move into that zone.
• Closure rate is how quickly two objects approach each other in your field of view. A crowd moving toward a fixed point can close faster than you expect, especially if you’re flying low and slow.

Best practice: plan your route so that your “primary view” stays clear. If you must fly behind an obstruction, do it briefly and with a preplanned recovery action, such as a turn to restore line of sight.

Crowd Awareness: Movement Patterns and Safe Margins

Crowds don’t move like a spreadsheet. People cluster, split, and surge. Treat the crowd as a dynamic boundary rather than a static target.

Use two layers of spacing in your head:

1. Operational spacing: the distance you need to keep from entering unsafe proximity.
2. Visual spacing: the distance that keeps you able to track people without losing them behind your own aircraft angle.

Easy example: if you’re filming a walkway and you notice people drifting toward your planned path, shift your flight line laterally rather than continuing forward and hoping they “stay put.” Lateral movement usually preserves your ability to see the crowd edge.

Scan Strategy That Works in Real Life

A scan plan prevents “tunnel vision.” Use a repeating pattern:

• Primary scan: aircraft attitude and flight path.
• Secondary scan: the nearest obstacle line and the crowd boundary.
• Tertiary scan: the far end of the route and any escape direction.

Keep the scan pattern consistent. Consistency reduces the chance that you forget to check one category when workload rises.

Mind Map: Situational Awareness for Complex Terrain and Crowds

Example: Ridge Line Survey with a Crowd Below

Scenario: You’re mapping a hillside with a ridge line in front of you, and a small crowd is gathered below near a trailhead.

1. Before takeoff, identify the ridge segments that will block your view of the crowd. Choose a flight line that keeps the crowd edge visible for the majority of the pass.
2. During the pass, use the scan loop. Primary scan stays on aircraft path; secondary scan checks the crowd edge; tertiary scan checks your escape direction if the crowd shifts.
3. When you see the crowd edge drift toward your projected path, don’t continue forward. Decide to shift laterally to re-establish visual spacing and operational spacing.
4. If the ridge blocks the crowd edge entirely, treat that as a decision trigger. Stabilize, turn to restore line of sight, and resume only when you can again describe the next 10 seconds clearly.

Example: Low Pass over Uneven Ground

Scenario: You’re flying low over uneven ground near people standing along a fence.

The risk isn’t just obstacles; it’s that uneven terrain can change your attitude and your camera angle, which changes what you can see. If you notice the fence line disappearing from your secondary scan, slow down and level out before continuing. A stable attitude is a visibility tool, not just a comfort feature.

Decision Triggers and Clean Responses

Use a short list of triggers so you don’t improvise under pressure:

• You cannot clearly identify the crowd edge.
• You lose the nearest obstacle line from your secondary scan.
• Your planned route would require you to fly through an occluded area longer than you intended.
• You feel uncertain about your aircraft orientation relative to the terrain.

Clean responses are usually the same: stabilize, reduce speed, restore line of sight, and then choose the next move. If you can’t restore line of sight quickly, abort and land. That’s not failure; it’s the most reliable way to keep the awareness chain intact.

8.4 Exam Style Questions for Maintaining Control and Compliance

Exam questions usually test whether you can apply the rules while staying in control of the aircraft. The trick is to treat each question like a mini checklist: identify the rule being tested, confirm the limiting condition, then choose the action that keeps the operation compliant and controllable.

Core Control Concepts You Must Apply Under Exam Pressure

Start with the idea that “maintaining control” is not just about flying smoothly. It means you can still maneuver to avoid hazards, stop or slow the aircraft’s movement relative to the environment, and comply with operational limits. In Part 107 terms, that shows up as correct use of visual line of sight, correct observer support, and correct responses to changing conditions.

Next, remember that compliance is conditional. Many answers hinge on whether a condition is present: controlled airspace, operations over people, night requirements, or whether the aircraft is still within the required operational boundaries. If the question implies a condition exists, you must assume it matters unless the question explicitly removes it.

How to Read Exam Questions Like a Pilot

1. Underline the constraint. Look for phrases like “in controlled airspace,” “over people,” “night,” “lost link,” or “cannot maintain visual line of sight.”
2. Identify the required action. The exam often asks what you must do next, not what you could do.
3. Check the “control first” logic. If two choices both sound legal, pick the one that preserves the ability to maneuver and avoid hazards.
4. Avoid “paper compliance.” An answer that satisfies a rule on paper but ignores immediate control (for example, continuing toward a hazard) is usually wrong.

Exam Style Example 1: Visual Line of Sight with an Observer

Scenario: You are flying a small UAS and you lose the ability to maintain visual line of sight with the aircraft. You have a visual observer who can see the aircraft.

Best answer logic: The correct choice is the one that restores the ability to maintain the required visual reference through proper observer use, not one that continues as-is. If the question implies you cannot maintain VLOS, you should not “hope” the aircraft stays safe. Instead, you should take the action that reestablishes control and compliance—typically by using the observer to support maintaining the required visual reference and adjusting flight to remain within the operational concept.

Common wrong answer pattern: Continuing the flight while claiming the observer “will tell you where it is,” without addressing that you still must be able to maintain the required visual reference for safe operation.

Exam Style Example 2: Controlled Airspace and Authorization Timing

Scenario: You plan to operate near an airport in controlled airspace. The question states that authorization has not been received yet.

Best answer logic: The compliant action is to not conduct the operation as planned until authorization requirements are satisfied. If the question asks what you should do before takeoff, the answer is about waiting or revising the plan to avoid the controlled airspace requirement.

Common wrong answer pattern: Proceeding because the flight is short, low altitude, or “away from runways.” The exam treats controlled airspace compliance as a gating requirement.

Exam Style Example 3: Lost Link Priorities

Scenario: During a mission, the aircraft loses command and control link.

Best answer logic: The correct response prioritizes immediate safety and risk reduction. You should follow the aircraft’s lost link procedure and take actions within your control to manage the situation, such as ensuring you are not creating additional hazards. The exam expects you to avoid actions that increase risk while the aircraft is not under reliable control.

Common wrong answer pattern: Attempting to “override” the situation with unsafe maneuvers or ignoring the lost link state.

A Practical Mini Drill for Multiple-Choice

For each practice question, write a one-line decision rule before choosing:

• “If VLOS is not maintained, the next step must restore compliant visual reference and control.”
• “If authorization is missing for controlled airspace, the next step must prevent the operation.”
• “If link is lost, the next step must reduce risk using the lost link procedure and safe pilot actions.”

This keeps you from getting trapped by tempting but incorrect answers that sound reasonable while violating the condition the question is testing.

8.5 Practical Observer Based Mission Walkthroughs With Checklists

This section turns observer rules into repeatable actions. The goal is simple: when the aircraft is moving, the observer’s job is to keep the remote pilot’s attention on control and compliance, while the observer manages what the pilot cannot reliably see.

Observer Roles That Actually Matter

Start with a clean division of labor. The remote pilot maintains control inputs, monitors flight telemetry, and ensures the aircraft stays within operational limits. The observer watches for traffic, obstacles, and anything that could break the mission’s visual requirements.

A common mistake is treating the observer as a “spotter who also flies.” Instead, the observer should provide short, specific calls that help the pilot decide. If the observer cannot see the aircraft clearly, they should say so immediately—because “I think it’s fine” is not a safety status.

Preflight Walkthrough with Checklist

Use this walkthrough every time, even for familiar locations.

Preflight Checklist

• Confirm observer assignment: One observer is designated, or multiple observers are assigned with clear handoffs.
• Brief communication method: Decide on call signs and phrase structure (for example, “Traffic left,” “Obstacle ahead,” “Aircraft lost”).
• Verify line of sight plan: Identify where the observer will stand so they can see the aircraft without being blocked by terrain, vehicles, or structures.
• Set scan pattern: Agree on a scan sequence (near field to far field, then back) so the observer is not randomly looking.
• Review mission boundaries: Know the planned altitude, lateral limits, and any “no-go” zones like people or restricted areas.
• Practice a quick lost-link response: The observer should know what to do if the aircraft disappears from view or the pilot calls for immediate action.

Easy Example

You plan a mapping flight near a warehouse. Before takeoff, the observer stands on the side with the clearest view of the flight path. During briefing, you agree that the observer will call “Obstacle ahead” if a crane boom enters the aircraft’s projected path, not after the aircraft has already passed it.

In-Flight Walkthrough with Checklist

During flight, the observer’s job is continuous. The pilot’s job is also continuous. The checklist keeps both jobs from drifting.

In-Flight Checklist

• Before takeoff: Observer confirms aircraft is visible and can be tracked.
• During climb and maneuvering: Observer scans for traffic and obstacles, especially during turns.
• During steady segments: Observer maintains aircraft tracking while scanning the surrounding area.
• When conditions change: If wind pushes the aircraft toward obstacles, the observer calls the direction and urgency.
• If the aircraft is lost from view: Observer immediately reports “Aircraft lost,” and the pilot initiates the appropriate recovery behavior.
• If people enter the area: Observer calls “People entering,” including approximate direction and distance.

Easy Example

Midway through a survey, a small bird or a glinting object appears near the flight path. The observer does not guess. They state what they see: “Possible bird near left of path, distance about 30 meters.” The pilot can then slow, adjust altitude if permitted, or pause the mission.

Post-Flight Walkthrough with Checklist

After landing, the observer and pilot should close the loop. This is where small errors become repeatable improvements.

Post-Flight Checklist

• Confirm mission completion status: Did the aircraft remain within the planned area and altitude?
• Log key calls: Note any traffic, obstacles, or visibility issues and whether the response was timely.
• Debrief communication: Were calls short and actionable? If not, adjust phrase structure for next time.
• Assess observer positioning: If the observer had to move to keep the aircraft in view, revise the stand location or flight path.

Easy Example

After a flight, you realize the observer’s view was blocked during a turn because a parked truck shifted into the line of sight. Next time, you reposition the observer or adjust the turn timing so the aircraft stays visible.

Mind Map: Observer Based Mission Workflow

Mind Map: Callouts That Lead to Decisions

Quick Integrated Scenario Walkthrough

On 2026-02-13, you run a short inspection flight over a parking lot with an observer. Preflight: you brief scan pattern and agree that the observer will call “People entering” if anyone approaches the edge of the work area. In flight: during a left turn, the observer spots a pedestrian stepping into the projected path and calls direction and distance. The pilot pauses the maneuver and repositions the aircraft to keep the mission within the planned boundaries. Postflight: you note that the observer’s scan was strongest when standing slightly forward of the pilot’s position, so you adjust stance for the next run.

This walkthrough style keeps the observer’s actions measurable: visibility, scanning, and callouts that support immediate pilot decisions.

9.1 Interpreting METAR and TAF for Drone Mission Planning

METAR and TAF are the weather’s “current status” and “near-term plan.” For Part 107 planning, you use them to decide whether the mission can be conducted safely within your operational limits, especially visibility, wind, and precipitation.

METAR Basics for Drone Pilots

A METAR is a snapshot issued regularly (often hourly). It includes wind, visibility, clouds, temperature/dew point, and weather phenomena. When you read it, treat it like a checklist: if any item would break your plan, you either adjust the plan or postpone.

Key fields to focus on:

• Wind: direction and speed, plus gusts if present. For drones, wind affects control margins and battery endurance.
• Visibility: the horizontal distance you can see. Low visibility can reduce your ability to maintain situational awareness.
• Ceiling: derived from the lowest cloud layer reported as broken/overcast (or vertical visibility in some cases). Ceiling matters because it often correlates with how “low” the sky is.
• Weather: rain, drizzle, fog, mist, snow, thunderstorms. These can reduce visibility and complicate operations.
• Temperature and Dew Point: used to infer fog/frost risk and icing risk. Even if icing isn’t your main concern, a small spread between temperature and dew point can signal moisture problems.

Example METAR Interpretation

METAR: KXYZ 1512Z 21012G20KT 5SM -RA BR BKN008 OVC015 10/9 A2992

• Wind: 210° at 12 kt, gusting 20 kt. Expect control challenges during takeoff/landing and higher battery drain.
• Visibility: 5 statute miles. That’s not “zero,” but it’s limited for maintaining clear visual reference.
• Weather: -RA (light rain) and BR (mist). Mist can make the air look “hazy” even when visibility seems borderline.
• Clouds: BKN008 (broken at 800 ft AGL) and OVC015 (overcast at 1,500 ft AGL). The ceiling is 800 ft.
• Temp/dew point: 10°C/9°C. The small spread suggests moisture is close to saturation.

A practical planning response: if your mission requires clear visual tracking and you have limited margin for wind and haze, you might reduce altitude, change the route, or delay.

TAF Basics for Drone Pilots

A TAF is a forecast for a longer window (commonly 24–30 hours). It’s structured in periods with expected changes. The trick is to read it as a timeline, not a single forecast.

Key fields to focus on:

• Wind changes: direction shifts and gust expectations.
• Visibility and ceiling trends: whether conditions improve or deteriorate.
• Cloud layer changes: especially when a ceiling is expected to drop below your comfort threshold.
• Weather onset and duration: when rain/fog/mist is expected to start and stop.

Example TAF Interpretation

TAF: KXYZ 1511/1611 21010KT 6SM BKN010 FM1518 23015G22KT 4SM -RA BR OVC008 TEMPO 1520/1524 2SM +TSRA FM1600 20012KT 5SM SCT012

Read it like this:

• 1511–1518Z: BKN010 at 1,000 ft AGL, visibility 6SM, wind 210/10.
• From 1518Z: wind increases and shifts, visibility drops to 4SM, rain/mist begins, and ceiling lowers to OVC008.
• Tempo 1520–1524Z: visibility can drop to 2SM with thunderstorms. Even if your drone is not flying in the storm core, the visibility reduction and turbulence risk can be disqualifying.
• From 1600Z: conditions improve to 5SM and SCT012.

For planning, you’d align your mission window with the best period and build a go/no-go trigger for the transition at 1518Z.

Practical Planning Workflow

1. Start with the METAR: confirm what’s happening right now. If visibility is already below your operational comfort level or the ceiling is too low, don’t rely on a “maybe it improves” forecast.
2. Scan the TAF for changes: find the time blocks where visibility drops, ceiling lowers, or weather begins.
3. Pick your mission window: schedule the operation during the most favorable period, not the average one.
4. Define go/no-go triggers: for example, if wind gusts exceed your control margin or if visibility drops below your minimum, you stop.
5. Re-check close to launch: conditions can shift faster than forecasts, especially around precipitation and fog.

Example: Choosing Between Two Launch Times

You have two potential launch times separated by 2 hours.

• METAR at 1400Z: wind 18010KT, 7SM, BKN020, no precipitation.
• TAF indicates: from 1500Z, visibility drops to 4SM with mist and ceiling lowers to OVC010.

Best choice: launch at 1400Z if your mission can be completed before 1500Z. If you wait for 1500Z, you’re planning around degraded visibility and a lower ceiling, which increases the chance you’ll need to terminate mid-mission.

Common Exam Traps

• Treating TAF like a single value: exam questions often expect you to use the forecast period that overlaps the operation time.
• Ignoring gusts: wind speed alone can look acceptable while gusts make control margins unsafe.
• Confusing visibility with ceiling: low ceiling can still exist with decent visibility, and vice versa; both matter.
• Overlooking TEMPO groups: “temporary” conditions can still occur during your flight window.

9.2 Wind, Gusts, and Density Altitude Effects on Small UAS Performance

Wind and gusts change how your aircraft moves through the air, while density altitude changes how well it can generate lift and thrust. Together, they determine whether you can hold altitude, maintain control authority, and climb when you need it. The exam questions usually test whether you can connect the scenario to the correct performance consequence.

Foundational Concepts You Need First

Wind vs. Gusts

Wind is the steady component of airflow. Gusts are short, rapid increases or decreases in wind speed, often with shifting direction. For small UAS, gusts matter because they can momentarily exceed the control authority you planned for.

Example: If the forecast wind is 15 kt and your aircraft’s control system is trimmed for that, you might still be fine—until a gust spikes to 25 kt for a few seconds. During that spike, the aircraft may drift, require more control input, or temporarily lose the ability to hold a precise track.

Density Altitude

Density altitude is a way to express how “thick” the air effectively is for performance. Higher density altitude means lower air density, which reduces propeller thrust efficiency and reduces lift for a given airspeed. Even if the weather report lists a temperature and pressure, the performance impact is tied to density altitude.

Example: A 90°F day with lower pressure can produce a density altitude that behaves like a much higher elevation. The aircraft may feel “lazy”: it needs more distance to climb and may struggle to maintain altitude at the same throttle setting.

Wind Effects on Control and Track

Groundspeed vs. Airspeed

Most performance rules in Part 107 contexts assume you care about airspeed for lift and control. Wind changes groundspeed, so you can see a slow or fast ground track without changing the aircraft’s lift-producing airspeed.

Example: With a headwind, your groundspeed drops but your airspeed can remain stable. With a tailwind, groundspeed increases, which can trick you into thinking the aircraft is performing better than it is.

Drift and Heading Control

Crosswinds create drift. If you fly a straight line over the ground without correcting, the aircraft will slide sideways. The correct response is to maintain the required heading or track using the control system and any guidance mode you’re using.

Example: You plan a survey line parallel to a road. A crosswind pushes the aircraft off-line. If you keep the same heading, you’ll drift; if you adjust heading to counter drift, you can hold the intended track.

Gust Effects on Stability and Margin

Why Gusts Are More Than “Extra Wind”

Gusts can cause rapid changes in the forces acting on the aircraft. That can lead to altitude excursions, speed changes, or control saturation. The key exam idea is that gusts reduce your margin because they can force larger control inputs than steady wind.

Example: You plan a hover at a location with steady wind 10 kt. If gusts reach 20 kt, the aircraft may require more thrust to counter the gust-induced tilt or lateral force. If your throttle margin is thin, altitude hold can degrade.

Practical Planning Response

Use gusts to set conservative expectations for track-keeping and climb performance. If the mission requires precise positioning, treat gusts as a reason to increase buffer distance from obstacles and people, and to avoid tight maneuvers.

Example: For an inspection requiring consistent framing, you might choose a wider approach path and slower lateral transitions when gusts are forecast, so the aircraft doesn’t overshoot the target during gust-induced drift.

Density Altitude Effects on Climb and Hover

Reduced Climb Capability

Lower air density reduces available lift and thrust. The aircraft may still fly, but it will climb more slowly and may not reach the planned altitude if you start too high or if you demand a rapid climb.

Example: You launch at a field at 2,000 ft MSL on a hot day. The aircraft’s climb rate is reduced. If you attempt to reach a target altitude immediately, you may not get there before you reach the operational area.

Hover Power Margin

If your aircraft must hover or maintain a low-speed profile, density altitude can push it closer to maximum power. That reduces the ability to recover from disturbances like gusts.

Example: In warm, high-density-altitude conditions, a gust that would normally be corrected with small control inputs may require near-maximum thrust. The result can be a noticeable altitude drop or a slower recovery.

Integrated Scenario Reasoning for Exam Questions

When a question mentions wind and gusts, think “control authority and track stability.” When it mentions high temperature, high elevation, or low pressure, think “reduced performance margin.” When both appear, treat the mission as having compounded risk: gusts demand control effort, while density altitude limits the aircraft’s ability to supply that effort.

Example Scenario: Wind 18 kt with gusts to 28 kt, temperature 95°F, and launch at a higher-elevation site. The correct reasoning is that gusts can cause drift and altitude excursions, while density altitude reduces climb and hover margin. A safe answer typically involves conservative positioning, avoiding tight timing, and ensuring you can maintain altitude and control authority.

Quick Check Examples You Can Use While Studying

1. Steady headwind 12 kt, no gusts: Expect slower groundspeed but stable airspeed if you maintain the same control inputs.
2. Crosswind with gusts: Expect drift and possible lateral overshoot; plan wider margins for positioning.
3. Hot day at higher elevation: Expect reduced climb and hover margin; avoid assuming the aircraft will reach altitude on the same timeline as on cooler days.
4. Hot day plus gusts: Treat as compounded risk; prioritize altitude and control authority over tight maneuvering.

9.3 Visibility, Ceiling, and Precipitation Considerations for VFR Operations

VFR planning for Part 107 starts with a simple idea: if you can’t see what you need to see, you can’t safely maintain control. “Visibility” and “ceiling” are the two numbers that most directly affect whether you can keep the aircraft in sight and avoid hazards like wires, vehicles, and terrain features.

Visibility Fundamentals for Keeping the Aircraft in Sight

Visibility is how far you can see in the atmosphere. In practice, you use it to judge whether the drone will remain visually identifiable against the background. Light haze can reduce contrast even when the aircraft is technically “there,” and that matters for judging distance and speed.

A useful exam mindset is to connect visibility to tasks:

• Tracking the aircraft: Can you keep it in sight without straining?
• Detecting hazards: Can you spot obstacles along the route?
• Maintaining orientation: Can you tell which direction the aircraft is moving?

Example: Visibility reported as 5 miles with scattered clouds at mid-level. You plan a short inspection along a straight corridor. The drone stays over open ground, and you can track it easily. That’s consistent with safe visual operations because the background is not cluttered and contrast remains adequate.

Example: Visibility reported as 1 mile in fog. Even if the drone is flying at a modest altitude, you may lose the aircraft quickly and misjudge its position. For VFR operations, that’s a strong indicator that the mission should not proceed.

Ceiling Basics and Why It Changes Your Risk

Ceiling is the height of the lowest layer of clouds or obscuring phenomena reported as broken or overcast. For VFR planning, ceiling affects how much of the sky is “available” for visual tracking and how likely you are to fly into obscured air.

A lower ceiling can force you to fly closer to the ground to stay clear of cloud layers, but that increases obstacle density and makes wire avoidance harder. It also reduces the time you have to react if the aircraft drifts toward the edge of the visible area.

Example: Ceiling 800 feet AGL with broken clouds. If your planned route crosses near trees, poles, or rooftops, flying low to remain below the cloud layer compresses your margin for error. The exam logic is to treat low ceiling as a constraint that can increase workload and hazard exposure.

Precipitation Types and Their Operational Effects

Precipitation affects visibility, aircraft performance, and control quality. For exam purposes, focus on how precipitation changes what you can see and how stable the flight feels.

• Rain: Often reduces visibility and can create glare on the ground and on the aircraft body.
• Snow: Can reduce visibility and may accumulate on surfaces, affecting control response.
• Drizzle and mist: Can be deceptively bad because visibility can drop while cloud layers still look “not too low.”
• Thunderstorms: Not just weather; they imply rapidly changing conditions and strong turbulence risk.

Example: Light rain with visibility 3 miles and ceiling 1,500 feet. If the route is open and you can maintain clear sightlines, the mission may still be feasible. The key is that the reported visibility supports visual tracking.

Example: Mist with visibility 1 mile and ceiling 400 feet. Even if the drone is small and slow, the combination of low ceiling and reduced visibility makes it easy to lose the aircraft or fail to detect obstacles in time.

Turning Reports into Decisions

VFR planning is not about memorizing numbers; it’s about matching conditions to what you must do visually. Use a decision checklist that ties each weather element to a specific operational requirement.

• Visibility supports continuous visual contact along the entire route.
• Ceiling does not force you into cluttered airspace where obstacles are harder to see.
• Precipitation does not degrade contrast or create obscuring layers.
• You can maintain a safe buffer for unexpected drift, especially near obstacles.

Example: Visibility 2 miles, ceiling 900 feet, light drizzle. If your route is over a busy industrial area with many vertical obstacles, the drizzle’s effect on contrast plus the low ceiling’s effect on where you must fly can make the mission unsafe even though the drone is within typical altitude limits.

Practical Scenario Walkthrough

Scenario: You receive a report showing visibility 4 miles, ceiling 2,000 feet, and light rain. Your route is a straight line over open fields with a single crossing near a utility corridor.

1. Visibility check: 4 miles supports tracking the aircraft against a relatively uniform background.
2. Ceiling check: 2,000 feet gives room to avoid cloud layers without flying extremely low near clutter.
3. Precipitation check: Light rain may reduce contrast, but the route’s openness limits how often you must identify small obstacles.
4. Risk buffer: You plan extra lateral spacing from the utility corridor and keep the flight path simple.

This is the integrated logic the exam expects: weather elements are not separate facts; they combine into whether you can see, avoid, and control for the entire mission.

9.4 Building a Go No Go Decision Framework Using Measurable Criteria

A good Go/No-Go framework turns “I think it’ll be fine” into a checklist of measurable conditions. For Part 107, your goal is not to predict the future; it’s to confirm that the mission you planned still fits the rules and the aircraft can safely do the job.

Step 1: Define the Mission Envelope in Numbers

Start with the limits that matter for your specific operation.

• Airspace permission: authorization status and altitude ceiling.
• Weather: wind speed and gust tolerance, visibility, and precipitation.
• Aircraft performance: max takeoff weight, battery endurance, and climb margin.
• Operational geometry: planned distance to obstacles and people, and whether you can maintain control.

Example: You plan a 20-minute mapping flight at 300 ft AGL near a controlled airport. Your envelope might include “wind ≤ 18 mph sustained, gusts ≤ 25 mph” and “ceiling ≥ 1,500 ft AGL with no rain.” Those thresholds become your decision inputs.

Step 2: Convert Rules into Decision Gates

Many exam questions boil down to whether a condition violates an operational requirement. Turn those into gates you can check quickly.

• Gate A: Airspace permission
  • If you do not have the required authorization for the planned altitude/area, it’s No-Go.
• Gate B: Visual operation requirements
  • If you cannot maintain required visual reference and control, it’s No-Go.
• Gate C: People and risk category
  • If your planned operation over people does not match the allowed category, it’s No-Go.
• Gate D: Night or lighting
  • If it’s night and you cannot meet the lighting/visibility requirements, it’s No-Go.

A practical trick: write each gate as a yes/no statement that you can answer in under 30 seconds.

Step 3: Use a Measurable Weather Model

Weather decisions should be based on what you can observe and what you can measure.

• Wind: use sustained wind and gusts from the source you trust, then compare to your aircraft’s tested tolerance.
• Precipitation: treat rain or active precipitation as a hard stop unless your aircraft and mission plan explicitly allow it.
• Visibility and ceiling: if you can’t maintain the required visual reference, the exact ceiling number matters less than the operational effect.

Example: METAR shows wind 16G24 kt. Your threshold is gusts ≤ 25 mph (about 22 kt). Even if sustained wind is acceptable, the gusts exceed your limit, so you choose No-Go before launch.

Step 4: Build a Scoring System for “Borderline” Conditions

Not every mission fails because of one obvious violation. For borderline cases, use a simple scoring approach that forces consistency.

• Assign Green (Pass), Yellow (Caution), Red (Stop) for each category: airspace, weather, aircraft readiness, and operational geometry.
• Go only if you have no Red items.
• If you have Yellow items, require at least one mitigation that keeps you within limits.

Mitigation examples:

• Reduce altitude to stay under an authorization ceiling.
• Shorten route to maintain obstacle clearance.
• Delay launch to wait for gusts to drop.
• Swap to a different takeoff point to improve line-of-sight.

Step 5: Lock in Aircraft Readiness with Objective Checks

Your framework should include aircraft-specific gates that don’t depend on feelings.

• Battery health and charge level sufficient for reserve margin.
• Propellers intact, no visible damage.
• Compass/GNSS status appropriate for the mission.
• Firmware and controller settings consistent with your planned operation.

Example: You planned a 12-minute outbound leg plus 8-minute return. Battery estimate shows 18 minutes with a 20% reserve. If preflight shows battery voltage sag or unusually high current draw, you reduce the mission length or cancel. If you can’t restore the reserve margin, it’s No-Go.

Step 6: Decide and Document with a Single Pass

Before takeoff, run the framework once, then again after any major change (new wind reading, updated authorization, or a change in route).

Integrated Example: One Mission, Three Outcomes

You’re flying a 25-minute inspection at 250 ft AGL.

• Airspace: authorization granted up to 300 ft AGL for the exact area. Gate A = Pass.
• Weather: wind 14 mph sustained, gusts 28 mph. Your gust limit is 25 mph. Gate B = Red via weather model.
• Aircraft: battery reserve margin is fine.

Result: No-Go because the weather gate fails, even though airspace and aircraft readiness pass.

Now change only one variable: gusts drop to 22 mph while everything else stays the same. Gate B becomes Pass, and you can Go—assuming your visual reference remains stable during takeoff and the route stays within your obstacle clearance plan.

Finally, keep the weather acceptable but change the route to pass closer to a tall structure than planned. Operational geometry becomes Red, so you either re-plan to restore clearance or cancel.

A framework like this keeps your decisions consistent under pressure. It also makes exam-style questions easier, because you’re already trained to ask: which gate fails, and what measurable condition caused it?

9.5 Practical Weather Scenario Exercises With Correct Rule Based Actions

These exercises train you to translate weather reports into Part 107 decisions. The goal is simple: if the weather makes the mission unsafe or noncompliant, you stop. If it stays compliant, you proceed with a plan that matches the conditions.

Foundational Weather Inputs You Must Convert into Decisions

Start by identifying the three things weather affects most for drones: (1) visibility for maintaining visual reference, (2) wind for control and safe ground handling, and (3) precipitation and cloud base for VFR conditions and operational risk. Then convert raw reports into operational limits.

Quick conversion mindset:

• Visibility: Can you reliably see the aircraft and any required visual references?
• Wind: Can you maintain control margins, especially during takeoff, landing, and any hover or low-speed segments?
• Ceiling and precipitation: Are you staying within VFR expectations and avoiding conditions that degrade control or visibility?

Exercise 1: Visibility Drop Near the Target

You plan a daytime inspection 1 mile from the launch point. METAR shows: visibility 6 miles, wind calm, scattered clouds at 3,500 feet AGL. Ten minutes later, local observation reports haze and the target area looks washed out.

Correct rule based action: Modify or no-go based on your ability to maintain visual reference. If you cannot reliably see the aircraft and the required references, you do not continue. A common mistake is assuming “6 miles” means “good everywhere.” Weather can vary across short distances.

Best practice example: If you still have clear sight of the aircraft but the target is hard to distinguish, you can reduce exposure by shortening the mission segment and returning to a point where visual reference is stable.

Exercise 2: Wind with Gusts During Takeoff and Landing

METAR reports wind 18 knots from the west with gusts to 28 knots. Your aircraft manual lists a maximum steady wind limit of 25 knots, but gusts are the real problem because control margins shrink during transitions.

Correct rule based action: No-go unless your safe operating plan explicitly accounts for gusts and you can maintain control during takeoff, hover, and landing. If your plan depends on “it’ll probably calm down,” you’re making an assumption, not a decision.

Best practice example: If you must proceed for operational reasons, you can modify the plan by launching and landing into the wind only if your aircraft can handle gusts safely at those phases. If you cannot verify that, you stop.

Exercise 3: Ceiling and Cloud Layers Affecting VFR Expectations

Suppose METAR shows broken clouds at 1,200 feet AGL and visibility 5 miles in light rain. Your mission is planned at 300 feet AGL with a route that would place you near the cloud layer edge.

Correct rule based action: No-go if precipitation and cloud conditions reduce your ability to maintain visual reference or if the operational environment makes control unreliable. Even when your planned altitude is below a cloud layer, the edge effects and rain can reduce contrast and visibility.

Best practice example: If the rain is light and visibility remains stable, you may modify by staying farther from the cloud edge and reducing time in the affected area. If visibility degrades, you return early.

Exercise 4: Timing from TAF Trend

TAF indicates a deterioration window starting at 14:30 local time, with reduced visibility and increasing wind. Your mission window is 13:45 to 15:00.

Correct rule based action: Modify the schedule so the mission completes before the deterioration begins, or no-go if you cannot finish early enough. This is where planning beats hope: you’re not just reading weather, you’re using it to set a decision deadline.

Best practice example: Set a “turn-back time” before the forecast change. If you’re behind schedule, you return rather than pushing into the forecast deterioration.

Exercise 5: Integrated Decision Drill with a Simple Checklist

Use this sequence every time:

1. Confirm visibility supports reliable visual reference for the entire mission segment.
2. Confirm wind and gusts are within your safe control margins for takeoff, route, and landing.
3. Confirm precipitation and cloud conditions do not degrade visibility or control.
4. Decide: Go, Modify, or No-go.

Example decision: If visibility is marginal and gusts are high, you choose No-go. If visibility is solid but wind is near your limit, you choose Modify by shortening the route and tightening the return deadline.

Common Exam Traps and How to Avoid Them

• Treating a single METAR value as uniform across the entire mission area.
• Ignoring gusts because the steady wind looks acceptable.
• Continuing when you can’t maintain reliable visual reference, even if the aircraft is still “technically” within planned altitude.

Final Practice Set with Answers in Mind

For each scenario, state your action (Go, Modify, No-go) and the single weather factor that drives it. If you can’t name that factor in one sentence, you’re not ready to commit to the mission.

10.1 Building a Mission Plan From Objectives to Airspace and Weather Checks

A mission plan is not a formality; it is a chain of decisions that keeps you inside the rules while still accomplishing the job. Start with the objective, then translate it into a flight profile, then verify airspace permission and weather feasibility. If any link breaks, you adjust the plan before you launch.

Define Mission Objectives into Measurable Requirements

Write the objective as a task you can verify after the flight. For example, “inspect a roof” becomes “capture 0.5-inch ground sample distance imagery of the north roof plane, with at least 70% overlap.” From there, derive operational requirements:

• Area and geometry: boundaries, target altitude above ground level, and required camera angles.
• Time and duration: how long you need to cover the area and how that fits within battery limits.
• Data quality constraints: wind limits that affect image blur, and lighting needs for consistent exposure.

Best practice: convert vague goals into numbers early. If you cannot state a number, you cannot test whether the plan still works when conditions change.

Translate Requirements into a Flight Profile

Now turn requirements into a practical route and operating parameters.

• Altitude selection: choose an altitude that meets image resolution while respecting any airspace limits and obstacle clearance.
• Route structure: decide between grid, line, or perimeter patterns based on the shape of the area.
• Speed and spacing: set speeds and camera trigger intervals so overlap targets are met.
• Failsafe behavior: confirm what the aircraft will do if control is lost, and ensure the behavior still avoids hazards.

Example: If the roof is narrow, a grid may waste battery on empty space. A perimeter plus a short interior pass can achieve coverage with less time in wind.

Perform Airspace Checks Before You Commit

Airspace verification happens before you finalize the route. The goal is to determine whether you need authorization and what constraints apply.

• Identify the operating area: use your planned takeoff point and the furthest point of flight.
• Determine controlled airspace involvement: if your area intersects controlled airspace, you must check the relevant authorization process.
• Record constraints: altitude ceilings, time limits, and any conditions tied to the authorization.

Best practice: treat airspace checks as a gate. If you cannot confirm permission and constraints, you do not “plan around it” in the air; you revise the mission on the ground.

Build the Weather Checks into the Same Decision Loop

Weather is not just “VFR or not.” It affects control, visibility, and the ability to maintain safe margins.

• Wind: check sustained wind and gusts, then compare them to your aircraft’s handling and your mission’s stability needs.
• Visibility and precipitation: ensure you can maintain the required visual references and avoid reduced control.
• Ceiling and cloud base: confirm you can operate without inadvertently entering conditions that conflict with your planned flight profile.

Example: If you need steady hover for close inspection, a gusty forecast can force a lower speed, a different route, or a postponed mission. The plan should reflect the decision you will make when gusts exceed your threshold.

Use a Go/No Go Framework That Matches Your Plan

A good plan includes explicit thresholds so you do not improvise under time pressure.

• Preflight thresholds: wind/gust limits, visibility minimums, and acceptable battery reserve.
• In-flight triggers: what you do if conditions drift, such as slowing down, shortening the route, or landing early.

Final Verification Before Launch

Before takeoff, verify that the route you intend to fly still matches the constraints you confirmed.

• Airspace vs route: confirm the planned altitude and lateral boundaries fit the authorization constraints.
• Weather vs flight profile: confirm wind and visibility still support the chosen speed, pattern, and camera settings.
• Aircraft readiness vs plan: confirm battery state, firmware status, and sensor readiness align with your expected duration.

Example: If your authorization limits altitude to a ceiling lower than your original plan, adjust the route or camera trigger settings on the ground. Do not “hope” the imagery will still meet the resolution requirement.

Integrated Example from Start to Finish

Objective: capture inspection imagery of a rectangular warehouse roof with 80% overlap and consistent angles.

1. Requirements: target GSD, altitude above ground, and coverage boundaries.
2. Flight profile: choose a grid pattern sized to the roof dimensions, set speed and trigger interval to meet overlap.
3. Airspace: check whether the roof area intersects controlled airspace; if authorization is required, record the altitude ceiling and any time limits.
4. Weather: verify wind and gusts are within your stability threshold for the camera setup; confirm visibility supports maintaining required visual reference.
5. Go/No Go: if gusts exceed the threshold or visibility drops below your minimum, abort or shorten the route.
6. Final verification: confirm the adjusted route stays within authorized altitude and the battery reserve supports the shortened plan.

A mission plan built this way turns “rules and conditions” into concrete decisions. You are not just preparing to fly; you are preparing to make the right call when the real world refuses to cooperate exactly as forecast.

10.2 Route Planning for Obstacles, Terrain, and Controlled Airspace Constraints

Route planning for Part 107 missions is where “it should fit” becomes “it fits, and you can explain why.” The goal is to build a route that stays within operational limits while avoiding obstacles, accounting for terrain effects, and respecting controlled airspace permissions.

Start with the Mission Geometry

Begin by translating the job into geometry: takeoff point, target area, required coverage pattern, and landing point. If you need a straight-line inspection, your route is mostly a corridor. If you need mapping, your route becomes a set of parallel passes with planned turns.

A practical habit: write down three distances before you touch airspace. First, the maximum planned horizontal distance from the takeoff point. Second, the farthest point from the aircraft during the mission. Third, the maximum altitude above ground level you intend to use. These numbers later help you sanity-check whether your route accidentally pushes into a boundary you didn’t mean to cross.

Build an Obstacle and Terrain Buffer

Obstacles aren’t just towers and trees; they include wires, rooftops, and even terrain rises that reduce your clearance margin. Use a layered buffer approach:

1. Baseline clearance: choose a conservative vertical margin above the highest relevant obstacle or terrain feature along the route.
2. Horizontal tolerance: assume you may drift laterally during turns, wind gusts, or GPS inaccuracies.
3. Operational margin: keep extra room for contingency actions like slowing down, changing altitude, or reversing course.

Example: You plan a corridor route along a river valley. The valley floor is low, but the far bank rises into a ridge. Even if the route stays “level” relative to your starting point, the ridge can shrink your effective clearance. The fix is to either adjust altitude relative to terrain or shift the route to avoid the steep rise.

Map Controlled Airspace Constraints into the Route

Controlled airspace constraints are not abstract; they are route-shaping rules. Treat them like gates your route must pass through.

• If the route crosses controlled airspace, you need to ensure authorization covers the specific operation area and time window.
• If the route stays outside controlled airspace, you still must verify that your planned path and contingency paths do not drift into it.

A useful method is to mark three zones on your plan: the planned route, the likely drift zone (based on wind and maneuvering), and the contingency zone (where you might go if you need to land early or avoid an unexpected obstacle). If any of those zones intersect controlled airspace without permission, you adjust the route or the mission plan.

Use a Constraint-First Route Construction Workflow

Build the route in this order to avoid rework:

1. Airspace first: outline the operation area and identify where controlled airspace boundaries intersect your intended path.
2. Terrain and obstacles next: for each segment, identify the highest relevant obstacle/terrain feature and set an altitude that preserves clearance.
3. Pattern and turns last: turns are where you can accidentally violate both obstacle clearance and airspace boundaries. Plan turn radii and ensure the aircraft remains within the clearance buffer during the maneuver.

Example: Your mapping pattern requires tight turns near a building. If you simply draw the straight passes, you may discover during the turn that the aircraft would pass closer to the building than the straight-line clearance assumed. Re-draw the pattern with wider turn arcs or shift the pattern footprint.

Segment-Level Verification with Simple Rules

Do a quick “segment audit” for every leg of the route:

• Leg altitude: confirm the altitude you plan is still safe over the highest obstacle/terrain point within that leg.
• Leg lateral position: confirm the leg stays far enough from obstacles that could intrude into your drift zone.
• Turn behavior: confirm the aircraft remains within the clearance buffer and does not cross into unauthorized airspace during the turn.

Example: You plan a leg that is clear at your chosen altitude, but the next leg passes near a treeline. During the turn, the aircraft may swing toward the treeline. The fix is to either increase the clearance buffer for the turn segment or redesign the pattern so the turn occurs over a safer area.

Integrated Example: Corridor Inspection Near Controlled Airspace

You are inspecting a utility corridor that runs near a controlled airspace boundary. Your route plan includes:

• A corridor route with planned altitude set to clear the tallest nearby structure and terrain rise.
• A drift zone that accounts for wind during cross-corridor segments.
• A contingency zone that covers a safe landing path if you need to stop early.

If the planned route crosses controlled airspace, you ensure authorization covers the operation area and the time window that includes the entire corridor segment and any contingency landing path. If authorization does not cover the contingency zone, you adjust the route footprint so the contingency zone remains outside controlled airspace or you modify the mission so the contingency action stays within authorized limits.

That’s the whole trick: route planning is not just drawing a line. It’s drawing a line plus the space around it, then proving the aircraft can stay inside that space while meeting obstacle clearance and airspace permission requirements.

10.3 Preflight, Launch, and Recovery Procedures for Operational Consistency

Operational consistency is what turns “it worked last time” into “it will work today.” The goal is not to memorize a ritual; it’s to run the same decision path every flight so you catch the same kinds of errors before they become problems.

Preflight Procedures That Prevent Repeat Mistakes

Start with a preflight checklist that mirrors how the exam questions think: verify, confirm, and then commit.

1. Mission brief in plain language: State the objective, the takeoff point, the intended flight area, and the landing point. If you can’t describe the plan in one minute, you probably can’t execute it under time pressure.

2. Airspace and authorization confirmation: Verify your operating location against the authorization or waiver conditions you plan to follow. A common exam-style trap is assuming “near the boundary” means “close enough.” Treat boundaries as hard limits.

3. Aircraft condition and configuration: Confirm battery condition, prop integrity, firmware status, and that the aircraft is configured for the intended operation (for example, correct flight mode and return-to-home settings). If your return-to-home altitude is set too low for nearby obstacles, the aircraft may “return” into trouble.

4. Control link and failsafe readiness: Perform a range or link check per manufacturer guidance. Then verify what happens on link loss: does it hover, land, or return? Your plan should match the behavior you will actually see.

5. Weather and performance sanity check: Confirm wind direction and speed relative to your takeoff and landing. If gusts are near your comfort limit, plan for a slightly longer landing approach and a more conservative first leg.

6. Crew roles and communication: If you have a visual observer, define who calls traffic, who calls airspace issues, and what phrase means “stop.” Consistency matters more than clever wording.

Launch Procedures That Keep the First Minute Predictable

The first minute is where small errors compound. Use a repeatable sequence.

1. Site setup: Clear the takeoff and landing zones of loose debris. Confirm you have a safe, unobstructed path for the initial climb.

2. Final pre-launch scan: Look for people, vehicles, and obstacles that could enter the flight path during spool-up. Then check that the aircraft orientation matches your control inputs.

3. Arming and takeoff: Arm only when you are ready to lift. If you need to pause, disarm or hold according to your aircraft’s procedure rather than improvising.

4. Stabilize before moving: After takeoff, hover or climb to your planned altitude and only then start the mission route. This prevents “route planning while still correcting” behavior.

5. First-leg verification: Confirm heading, altitude, and speed match expectations. If they don’t, fix it immediately while you still have room to maneuver.

Recovery Procedures That Avoid Last-Second Surprises

Recovery is not “landing when you feel like it.” It’s a controlled end to the mission.

1. Define the landing trigger: Use a measurable trigger such as remaining battery percentage or time-on-task. Don’t wait for the aircraft to warn you.

2. Return-to-home alignment with reality: If you rely on return-to-home, ensure the route won’t cross obstacles or people. If the aircraft will return at a fixed altitude, that altitude must be safe for the site.

3. Approach planning: Choose a landing direction that accounts for wind and rotor wash. A crosswind landing is where many “it was fine until the end” incidents happen.

4. Landing and post-landing actions: After touchdown, disarm and secure the aircraft. Then document any anomalies (unusual vibrations, unexpected behavior, or control issues) while details are fresh.

Example: Consistent Workflow for a Controlled Airspace Mission

You plan a mapping flight near a controlled airspace boundary with an authorization that limits altitude and requires staying within a defined area.

• Preflight: You confirm the authorization limits, set return-to-home altitude above the nearest obstacle, and verify wind is within your operational comfort range. You also confirm your observer knows the stop phrase.
• Launch: You take off, climb to the planned operating altitude, hover briefly to confirm heading and altitude, then begin the route inside the authorized area.
• Recovery: You set a battery trigger before the first leg ends, then return using the same route logic you used for departure. On approach, you land into the wind and disarm only after touchdown.

Example: When the Plan Meets Reality

During launch, you notice the aircraft’s climb is slower than expected due to a heavier-than-usual battery or slightly higher wind.

• You do not start the mission route early.
• You re-check altitude and speed against your expected profile.
• If you can’t reach the planned operating altitude safely within your site constraints, you abort and recover using your landing trigger logic.

Consistency means you respond to deviations with the same structured steps every time: verify, stabilize, and then decide.

10.4 In Flight Monitoring Requirements and How to Respond to Deviations

In-flight monitoring is where rules become real. Part 107 expects the remote pilot to keep the aircraft under control, maintain required visual conditions, and respond promptly when conditions change. The exam questions usually test whether you notice the change early enough and choose the action that restores compliance without creating a new hazard.

Core Monitoring Responsibilities

Start with the basics you must continuously satisfy: maintain control of the aircraft, keep the aircraft within the required operational limits, and ensure the flight remains safe for the environment around you. Practically, that means you are not “hands off” after takeoff. You actively scan for traffic, obstacles, and changes in weather or visibility.

A good monitoring rhythm is: (1) confirm aircraft state, (2) confirm environment, (3) confirm mission constraints. Aircraft state includes altitude, speed, battery level, link quality, and flight mode. Environment includes nearby people, vehicles, structures, and airspace cues you planned for. Mission constraints include the planned route, maximum distance, and any authorization or waiver limitations.

What to Monitor During the Flight

Altitude and vertical profile. Small UAS drift is common in wind. If your planned altitude is 200 ft AGL and you notice you’re creeping upward, correct early rather than waiting until you’re clearly out of tolerance.

Position relative to planned route. If you planned a straight line survey and you start deviating laterally, you may still be within altitude limits but you could be drifting toward obstacles or restricted areas.

Battery and power margin. Battery monitoring is not just about landing before empty. It’s about having enough margin to execute a safe landing or contingency if conditions worsen.

Control link and control responsiveness. If you see intermittent latency, delayed control response, or frequent failsafe triggers, treat it as a compliance and safety issue. The correct response is to reduce complexity: slow down, increase separation from hazards, and prepare to land.

Visual line of sight and situational awareness. If you lose the aircraft in clutter, glare, or terrain, you must regain the ability to see it. “I can still fly by GPS” is not a substitute for required visual conditions.

Deviation Triggers and Immediate Response Logic

A deviation is any change that threatens compliance or safety. The exam-friendly way to answer is to identify the deviation type, then choose the action that restores compliance with the least additional risk.

Deviation types you should recognize:

• Airspace or authorization mismatch: you are entering an area you were not authorized to operate in.
• Altitude or distance mismatch: you exceed planned limits.
• Weather or visibility deterioration: you can no longer maintain required visual conditions.
• Loss of control link quality: control responsiveness degrades.
• Obstacle or people proximity: you are closer than planned or than safe.

Response priorities:

1. Maintain separation from hazards (people, obstacles, terrain).
2. Restore compliance (altitude, route, visibility, authorization conditions).
3. Stabilize the aircraft before making fine adjustments.
4. Land or terminate the mission when restoration is not achievable safely.

Mind Map: Monitoring and Deviations

Example: Altitude Drift and Route Correction

You launch for a mapping pass planned at 150 ft AGL. After two minutes, wind increases and the aircraft slowly climbs. You notice the climb while still maintaining visual contact.

Correct response: reduce throttle or adjust pitch to bring the aircraft back to the planned altitude, then re-center on the planned route. You should not continue the mission pattern while out of the intended altitude profile, because that increases the chance of obstacle conflict and violates the operational intent.

Example: Visibility Drop During a Survey

You begin a line scan in good visibility. Midway, haze thickens and the aircraft becomes harder to track against the background.

Correct response: stop complex maneuvers, move to a position where you can clearly see the aircraft, and consider terminating the mission if you cannot maintain required visual conditions. Continuing because the GPS track still looks fine is not the right approach.

Example: Control Link Degradation Near Obstacles

While approaching a building edge, you see intermittent latency and the aircraft responds more slowly to commands.

Correct response: increase separation from obstacles immediately, stabilize the aircraft, and prepare to land or return using the safest available option. If the link quality continues to worsen, mission continuation becomes the wrong choice.

Practical Checklist for In-Flight Monitoring

Before you fly the next segment, do a quick mental check: “Where am I, how high am I, what’s my battery margin, can I clearly see the aircraft, and am I still within the planned constraints?” If any answer is “no” or “not sure,” treat it as a deviation and act early.

10.5 Practical End to End Mission Plans for Commercial Drone Tasks

A strong mission plan is not a document you admire; it is a sequence of decisions you can defend. For Part 107, the goal is to connect your objective to airspace permissioning, aircraft limits, weather, and the exact way you will fly. Below is a systematic workflow you can reuse for common commercial tasks.

Step 1: Define the Task and the Operating Envelope

Start with three facts: what you will capture, where you will fly, and what “done” means. Then translate those facts into operational limits.

Example: Roof inspection for a 2-story building.

• Objective: capture high-resolution imagery of shingles and gutters.
• Area: a rectangle roughly 120 m by 60 m.
• Done: complete a set of overlapping passes covering both roof planes.

Best practice: write the envelope in measurable terms—maximum altitude, maximum distance from the takeoff point, and the planned flight path shape. If your plan says “stay close,” the exam will treat that as a problem.

Step 2: Build the Airspace Permission Plan

Treat airspace as a gate you must pass before you start thinking about camera settings. Verify whether you need LAANC authorization or a waiver.

Example: The site is near a controlled airport.

• Action: check the airspace class and the nearest controlled facility.
• If controlled airspace: request authorization for the specific altitude and time window.
• If authorization is limited: adjust the mission altitude or route to match the approved conditions.

Best practice: align your planned altitude with the authorization ceiling. If you plan 400 ft but authorization allows 300 ft, you do not have a “minor mismatch.” You have a noncompliant plan.

Step 3: Confirm Aircraft Readiness and Performance Limits

Your aircraft is part of the compliance chain. Verify that the aircraft can safely do the mission within the planned wind, weight, and battery constraints.

Example: Same roof inspection, but with a gusty afternoon.

• Action: check wind forecast and compare to your aircraft’s controllability margins.
• Confirm battery capacity supports the full route plus a buffer.
• Ensure the takeoff weight is within limits for stable hover and climb.

Best practice: plan a conservative battery reserve. If your route is 18 minutes and you have 20 minutes of usable time, you are not planning—you are hoping.

Step 4: Translate Weather into Go No Go Criteria

Weather decisions should be rule-based and measurable. Use visibility, cloud clearance, wind, and precipitation as explicit thresholds.

Example: Overcast with low ceiling.

• Action: confirm you can maintain required visibility and remain clear of clouds as applicable.
• If conditions reduce controllability or visibility: delay or modify the plan.

Best practice: write down your decision triggers before you launch. During the mission, you should be executing the plan, not inventing it.

Step 5: Plan the Flight Path and Control Strategy

Now connect the objective to how you will fly. For most commercial tasks, you need repeatable coverage and predictable turns.

Example: Roof inspection flight path.

• Use parallel passes over each roof plane.
• Keep a consistent standoff distance for image overlap.
• Plan turn points so you do not drift toward obstacles during yaw and bank.

Best practice: decide where you will be when you lose situational awareness. If you cannot describe your “safe recovery posture,” you are missing a key part of the plan.

Step 6: Preflight Briefing and Roles

If you use a visual observer, define communication and responsibilities. If you do not, your plan still needs a clear scan pattern and a defined method for obstacle awareness.

Example: One remote pilot, one visual observer.

• Pilot: maintains control and navigates the route.
• Observer: watches for traffic and obstacles, calls out deviations early.
• Communication: short, standardized calls like “traffic left,” “obstacle ahead,” “altitude stable.”

Best practice: rehearse the briefing in under five minutes. If it takes longer, it will fail under field conditions.

Step 7: Execute, Monitor, and Adjust Without Breaking Compliance

Execution is where plans either hold or collapse. Monitor altitude, speed, battery state, and authorization constraints.

Example: Mid-mission battery drops faster due to headwind.

• Action: shorten the remaining passes.
• Maintain compliance: do not exceed authorized altitude or enter restricted areas.
• End state: land with the aircraft in a controlled manner, not a last-second scramble.

Best practice: define an “abort point” tied to battery percentage or time remaining.

Step 8: Closeout and Documentation

After landing, document what matters: mission time, any deviations, and any safety-related notes. Keep records consistent with your operational requirements.

Example: You had to skip one roof plane due to wind.

• Record the reason and the exact portion not completed.
• Note any corrective action for the next attempt.

Best practice: deviations should be traceable. If you cannot explain it in one sentence, it is not documented.

Example: One Mission, Two Common Variations

Variation A: Same roof inspection, but authorization allows only 250 ft.

• Adjust the standoff distance and camera settings so image quality remains acceptable at the lower altitude.
• Keep the same coverage plan shape, but recalculate pass spacing to preserve overlap.

Variation B: Same site, but you must operate closer to obstacles due to access constraints.

• Re-plan turn points to avoid swinging toward trees or power lines.
• Increase your obstacle scan frequency during turns and reduce speed to maintain control margins.

The exam often tests whether you can keep compliance while adapting the plan. Your best defense is a plan that already separates “what must not change” (authorization, limits, safety) from “what can change” (route geometry, pass spacing, timing).

11.1 Emergency Categories and What Triggers Immediate Action

Emergency handling under Part 107 is less about memorizing dramatic labels and more about recognizing the moment when “normal control” stops being reliable. The FAA frames emergencies around conditions that require immediate action to reduce risk to people, property, and the aircraft.

Start with a simple mental model: an emergency is any situation where you cannot reasonably maintain safe flight using your planned procedures. That includes loss of control, loss of required link, or a condition that makes collision avoidance or safe landing unlikely. Your first job is to stabilize the situation, then decide what action best reduces harm.

Emergency Categories You Should Expect on the Exam

1. Aircraft Control Problems These include situations where the aircraft is not responding as expected, is drifting uncontrollably, or is behaving in a way that suggests a control system issue. A key trigger is “control is not what it should be,” not “I feel nervous.”

2. Lost Link and Communication Failures Lost link is a classic trigger because it removes your ability to command the aircraft. If you lose control link and cannot re-establish it quickly, you must treat the situation as an emergency even if the aircraft appears stable.

3. Flyaway or Uncommanded Movement A flyaway is when the aircraft continues away from your intended area without your ability to correct it. The trigger is the combination of uncommanded movement and inability to regain effective control.

4. Collision Risk and Immediate Avoidance Needs If another aircraft, vehicle, or person enters a path where a collision is likely, the emergency is the risk itself. The trigger is not the moment of impact; it is the moment you determine that continued flight as planned is unsafe.

5. In-Flight Malfunctions That Affect Safety Examples include unexpected power loss, abnormal flight characteristics, or indications that the aircraft cannot maintain safe altitude or attitude. The trigger is a safety-relevant malfunction that prevents you from continuing the mission safely.

What Triggers Immediate Action

Immediate action means you stop debating and start reducing risk. Use three triggers that show up repeatedly in exam questions:

• Loss of ability to control the aircraft: commands do not produce expected response.
• Loss of ability to maintain separation: you cannot keep the aircraft away from hazards.
• Loss of ability to safely continue or land: the aircraft cannot be managed to a controlled outcome.

A practical way to apply this is to ask: “If I keep doing what I was doing for the next 10 seconds, does risk increase?” If yes, you act now.

Immediate Actions in a Safe Order

When an emergency triggers, your actions should follow a consistent priority order:

1. Acknowledge the emergency and stop mission tasks If you are recording data, stop focusing on the camera and focus on control and separation.

2. Reduce risk through control and positioning If you have control, maneuver to increase distance from hazards and move toward a safer landing area.

3. Use your aircraft’s emergency behavior if applicable Many aircraft have predefined behaviors for lost link. The exam expects you to follow the aircraft’s programmed response while still monitoring for opportunities to regain control.

4. Prepare for recovery or termination Recovery means returning to a safe landing zone. Termination means landing as soon as it is safe to do so, even if it ends the mission.

5. After the immediate risk is reduced, handle reporting and documentation The emergency response doesn’t end when the aircraft lands. You must be ready to document what happened and comply with reporting requirements when applicable.

Example: Lost Link That Looks “Okay”

You are flying a small inspection route at a steady altitude. At 300 feet AGL, the control link drops. The aircraft continues straight for a few seconds and appears stable. The exam logic still treats this as an emergency trigger because you cannot command it. Immediate action is to treat the situation as lost link, monitor for re-linking, and be ready to respond according to the aircraft’s lost-link behavior and your available options.

Example: Collision Risk from a Ground Vehicle

A ground vehicle suddenly drives into your planned flight path near a construction site. You estimate that continuing the route will bring the aircraft into a collision course. The emergency trigger is collision risk, so immediate action is to maneuver to increase separation and move toward a safer area for continued flight or landing.

Example: Control Issue During a Low Pass

You notice the aircraft responds sluggishly to control inputs during a low pass near a structure. You cannot confidently maintain clearance. The trigger is loss of ability to control safely, so immediate action is to stop the mission plan, maneuver to reduce risk, and prioritize a safe landing rather than completing the intended shot.

Emergency categories are the labels; triggers are the moment you act. If you can identify the trigger quickly and follow a consistent priority order, you’ll answer the exam questions correctly and, more importantly, reduce real-world risk.

11.2 Lost Link, Fly Away, and Return to Home Behavior Considerations

A “lost link” is not just an inconvenience; it’s a control problem. Under Part 107, your job is to ensure the aircraft remains controllable and that your procedures reduce the chance of harm when communications degrade. Many exam questions test whether you can identify the correct priority: regain safe control, prevent uncontrolled flight, and follow the aircraft’s programmed failsafe behavior.

Foundational Concepts and What “Lost Link” Means

Lost link typically occurs when the remote controller can no longer exchange commands or telemetry with the aircraft. That can happen due to range limits, interference, antenna orientation, or obstructions. The key exam idea is that “lost link” triggers the aircraft’s failsafe logic, which may include actions like hover, land, or return-to-home.

Fly away is closely related but not identical. A fly away is when the aircraft continues moving away from the intended area due to loss of control inputs, navigation errors, or failsafe behavior that does not match the environment. In practice, fly away risk rises when GPS is weak, obstacles block sensors, or the aircraft’s return path crosses hazards.

Return to Home behavior is the aircraft’s attempt to navigate back to a predefined point, usually the takeoff location. The exam focus is not on memorizing brand-specific features; it’s on understanding what return-to-home generally does and what you must verify before flight.

Preflight Checks That Prevent Bad Failsafe Outcomes

Before takeoff, confirm the aircraft’s failsafe settings match the mission environment. If return-to-home is enabled, verify the home point is correct and that the return altitude will clear nearby obstacles. A common mistake is assuming “return to home” automatically avoids everything. Many systems do not guarantee obstacle avoidance during failsafe; they may simply follow a route at a set altitude.

Also consider wind. If you expect strong gusts, a return-to-home climb or descent can drift enough to change the landing or pass over location. The exam-friendly reasoning is simple: failsafe behavior is deterministic, but the environment is not.

In-Flight Behavior When Link Is Lost

When you notice lost link indications, your first step is to attempt to regain control within safe limits. That means moving the controller position to improve antenna orientation and line of sight, if doing so does not increase risk to people or property. If the aircraft is already executing failsafe, you should monitor its path rather than chase it blindly.

If return-to-home is active, watch for two things: whether the aircraft is climbing to the programmed altitude and whether that altitude is sufficient for the area around the home point. If the return path would cross controlled airspace boundaries or obstacles, your preflight planning should have addressed it. The exam expects you to recognize that you cannot “fix” a poor return-to-home plan after the aircraft is already committed.

Example: Lost Link over a Parking Lot

You launch from a small lot near a warehouse. The aircraft is set to return-to-home at 120 feet AGL. During the mission, telemetry drops and the aircraft enters return-to-home. You see it climb and then head back toward the takeoff point. The warehouse roof is 90 feet high, so the return altitude provides clearance. You reposition the controller to improve link quality, and the aircraft continues its return. The correct operational takeaway is that the failsafe action was predictable and the return altitude matched the obstacle environment.

Example: Fly Away Toward a Restricted Area

You fly near a boundary and the aircraft loses link. Instead of returning, it drifts due to weak navigation inputs and wind, effectively moving away from the intended area. This is a fly-away scenario: the aircraft’s behavior is not keeping it within your planned safety envelope. The exam logic is that your preflight verification of home point quality, failsafe mode, and expected wind effects would reduce this risk.

Practical Decision Checklist

• Know your aircraft’s failsafe action for lost link.
• Confirm home point accuracy before takeoff.
• Ensure return-to-home altitude clears nearby obstacles.
• Account for wind that can shift the aircraft during failsafe.
• During the event, attempt link recovery safely and monitor the aircraft’s path.

Post-Event Considerations Without Guessing

After the aircraft lands or the link is restored, document what you observed: when the link degraded, what the aircraft did, and what conditions were present (wind, obstructions, controller position). This is not about assigning blame; it’s about identifying which part of the chain—planning, settings, or environment—failed so the next flight’s risk is lower.

11.3 Collision Avoidance Priorities and Immediate Risk Reduction Steps

Collision avoidance in Part 107 is less about memorizing a single “magic rule” and more about using a clear priority order when something feels off. The exam expects you to recognize the correct first action, then the next action, while staying within the operational limits you already planned for.

Foundational Priorities for Immediate Action

Start with the idea that collision risk is time-critical and information-limited. You may not know the other aircraft’s altitude, speed, or intent, so your job is to reduce the chance of contact using the most reliable cues you have.

Priority 1: Prevent immediate contact. If you detect a potential conflict, your first goal is to create separation. Separation can be horizontal, vertical, or both, but the practical choice depends on what you can do safely while maintaining control.

Priority 2: Maintain control and aircraft stability. A sudden maneuver that causes loss of control is not “risk reduction.” The correct action is the one that both reduces collision risk and keeps the drone controllable.

Priority 3: Avoid making the situation worse. Some actions increase uncertainty. For example, climbing into a layer of traffic you didn’t scan, or turning in a way that removes your visual reference to the conflict.

Priority 4: Resume safe operation only after the conflict is resolved. Once separation is established, you can return to the planned route or a safer loiter point.

Immediate Risk Reduction Steps You Can Apply Under Pressure

Use a short sequence so you don’t freeze when the question gets specific.

1. Confirm the cue, then commit. If you see a moving aircraft, don’t spend time re-checking settings. Confirm it’s a real contact (not a glare, not a reflection), then act.

2. Increase separation using the most available control input. If you have clear lateral space, a controlled lateral move is often the fastest way to create distance. If vertical separation is clearly available and you can maintain stable control, a climb or descent may be appropriate.

3. Prioritize smooth, predictable control. Sudden oscillations make it harder for you to track the other object and harder for anyone else to anticipate your path.

4. Re-scan the airspace around the new position. After the maneuver, look again. The conflict may have been one of multiple contacts.

5. If you cannot maintain safe separation, treat it as an emergency. The exam logic is simple: if you can’t reduce risk through normal maneuvering, you must switch to the safest available outcome, including returning to a safer location or initiating an emergency procedure consistent with your system.

Example: Two Aircraft Cross Paths Near Your Route

You’re flying a mapping line at 200 feet AGL. While tracking a waypoint, you notice a small aircraft crossing your path from left to right at a higher altitude. Your first instinct might be to “hold course and hope.” The exam expects you to reduce risk immediately.

Correct approach:

• Create separation first by moving laterally away from the crossing path while maintaining stable control.
• After the lateral move, re-scan to ensure there isn’t another contact forming a new conflict.
• Only then decide whether to continue the mission line or reposition.

Why this matches the priorities: you prevent immediate contact, you keep control, and you avoid a maneuver that removes your ability to track the aircraft.

Example: Observer Calls a Conflict You Can’t See Yet

An observer reports an aircraft approaching from behind your right shoulder, but you can’t visually confirm it immediately due to sun angle and your current camera orientation.

Correct approach:

• Reduce risk by adjusting your flight path in a controlled way that increases separation from the reported direction.
• Once you can confirm the cue, refine the separation maneuver.
• Avoid abrupt control inputs that could cause loss of control or make the observer’s job harder.

Key exam idea: you don’t wait for perfect information if the observer’s cue indicates a real risk.

Example: You Realize Your Planned Route Creates a Conflict

Halfway through a corridor flight, you notice that your route will pass close to a known approach path you previously checked. The conflict is not immediate contact yet, but the spacing is shrinking.

Correct approach:

• Don’t “stick to the plan” if the plan is now unsafe.
• Adjust early to restore safe separation, then re-scan.
• If you can’t restore safe spacing without unsafe maneuvering, terminate or reposition.

Quick Self-Check for Exam Questions

When a question asks what you should do “first,” choose the action that:

• reduces collision risk immediately,
• keeps the drone controllable,
• and doesn’t increase uncertainty.

If the answer choice requires you to ignore the conflict until later, it’s usually wrong. If it requires you to maintain control while creating separation, it’s usually right. And yes, the drone can be grounded without being dramatic.

11.4 Post Incident Actions Including Reporting and Documentation Requirements

When something goes wrong, the goal is not to guess what happened. It’s to stabilize the situation, preserve evidence, and produce a clear record that matches what you actually observed. Think of post-incident actions as three tracks running in parallel: safety, documentation, and required reporting.

Foundational Priorities After an Incident

Start with immediate safety steps. If the aircraft is still in a hazardous position, keep people clear and avoid creating new risks while you assess. If there is any chance of injury, treat it as a first-order concern and follow your local emergency response procedures.

Next, secure the scene. Move only what you must to prevent further harm. If you can do so safely, note the aircraft’s position, visible damage, and any environmental factors like wind direction, lighting conditions, or obstacles near the flight path.

Finally, preserve information. Capture screenshots from the flight controller app or remote ID interface if available, record GPS time stamps shown in logs, and save any relevant telemetry files. This is the part that often gets skipped because people want to “fix it later.” Later is where details evaporate.

What to Document Systematically

A good incident record is structured enough that someone else could reconstruct the sequence without guessing. Use a consistent format and include the following categories.

• Who: Remote pilot name, any visual observers, and other involved personnel.
• What: Aircraft make/model, serial number if available, and payload details.
• Where: Exact location description, nearest landmark, and any relevant airspace context you used during planning.
• When: Date and local time, plus the time stamps from flight logs.
• How: A timeline of events from takeoff to the incident, including control inputs and system alerts.
• Conditions: Wind, visibility, precipitation, and lighting; include what you observed rather than what you assume.
• Damage or Injury: Describe what you see, not what you think caused it.
• Actions Taken: What you did immediately after the incident and why.

If you need a date, use one like 2026-02-15 for your example record below.

Reporting Triggers and Practical Threshold Thinking

Reporting requirements depend on what happened, not on how dramatic it felt. The exam logic typically points you toward the idea that certain outcomes require prompt reporting and that “no one was hurt” does not automatically mean “no report.”

In practice, your decision process should ask two questions:

1. Was there injury or significant property damage? If yes, treat reporting as urgent and prioritize accurate facts.
2. Was the aircraft involved in an event that indicates a safety risk beyond a minor malfunction? If yes, document thoroughly and follow the applicable reporting path.

Even when you’re not sure, your documentation should be detailed enough to support the determination.

Example Incident Record

Incident Summary: On 2026-02-15, during a Part 107 mapping flight, the aircraft experienced a sudden loss of control indications and descended rapidly before recovering partial control. No injuries were observed.

Timeline:

• 14:02:10 Takeoff completed; aircraft climbed to planned altitude.
• 14:05:33 Control link warning appeared; pilot initiated standard recovery actions.
• 14:05:41 Aircraft deviated from planned route; pilot attempted corrective inputs.
• 14:05:55 Aircraft impacted a grassy area off the intended flight line.

Location: Field near a named road intersection; coordinates recorded from flight log.

Conditions: Wind observed at takeoff; visibility clear; no precipitation.

Damage: Propeller blades bent; landing gear scuffed; payload mount intact.

Actions Taken: Maintained distance from the aircraft, ensured no bystanders approached, powered down after confirming safe conditions.

Evidence Preserved: Flight log file saved, app screenshots captured, and photographs taken from multiple angles.

This format helps you avoid the common mistake of writing a narrative that’s hard to verify.

Documentation Quality Checks

Before you submit anything, do a quick consistency pass. Confirm that your timeline matches the log time stamps, that your location description aligns with recorded coordinates, and that your “what you observed” statements are not replaced by “what you think happened.” If you used a visual observer, include their observations as separate entries so the record doesn’t blur into one blended story.

The best post-incident documentation reads like a set of verified observations with a clear sequence. It’s not meant to be persuasive; it’s meant to be accurate.

11.5 Practical Emergency Scenario Drills With Correct Compliance Responses

Emergency drills work best when they are boringly repeatable: identify the trigger, stop the bleeding, keep control, and only then sort out paperwork. The goal is not to “win” the scenario; it’s to choose the correct action sequence that matches Part 107 expectations and keeps people and property safer.

Drill 1: Lost Link with Controlled Descent Plan

Start with the foundational question: what does your aircraft do when the link drops? Before any scenario, confirm your failsafe settings (lost link behavior, return-to-home altitude, and geofence behavior if used). Then run the drill.

Scenario: You are 300 feet AGL over a field. At 2 miles out, the video freezes and telemetry degrades.

Correct compliance response:

1. Maintain aircraft control if possible. If control link remains partially available, adjust to reduce risk and prepare for recovery.
2. If control is not reliable, prioritize safe termination of the hazard. Use the aircraft’s programmed lost-link behavior, but ensure it does not create a new risk (for example, returning over a road full of vehicles).
3. Keep the aircraft within the intended operating area when feasible. If your return path would violate airspace permissions or altitude limits, the safer move is to avoid forcing a risky manual override.
4. After stabilization, land and secure. Do not keep flying “to see what happens.”

Easy example: If your RTH altitude would pass through a nearby controlled airspace boundary, you should have planned an RTH altitude that clears obstacles while staying within your permitted operating constraints.

Drill 2: Fly-Away Near Obstacles with Immediate Risk Reduction

Fly-aways are often caused by wind, GPS issues, or control input errors. The compliance-minded response is to reduce risk first, not to chase the aircraft.

Scenario: During a mapping run near a warehouse, the aircraft drifts laterally and begins climbing toward a crane.

Correct compliance response:

1. Stop the mission. Treat the situation as an emergency, not a “minor deviation.”
2. Use the safest available control inputs. If you can regain stable control, command a descent or lateral move that increases separation from obstacles.
3. Avoid overcorrecting. Oscillation can increase collision risk, especially in gusty wind.
4. If you cannot regain control quickly, prioritize separation. Let the aircraft follow its safest programmed behavior and prepare for a safe landing area.

Easy example: If the wind gusts are pushing the aircraft toward the crane, a controlled retreat to a pre-identified open area is safer than continuing the planned route.

Drill 3: Collision Avoidance with Traffic-Like Intrusion

Part 107 expects you to see and avoid. In drills, you simulate “traffic” using a spotter or a known moving object on the ground.

Scenario: A person on a nearby access road walks into your planned flight path.

Correct compliance response:

1. Immediate action to increase separation. Adjust altitude or lateral position to create distance.
2. Do not rely on recording. Video review is not an avoidance strategy.
3. Resume only after the risk is cleared. If separation cannot be maintained, land.

Easy example: If the person keeps moving toward the aircraft’s projected path, you should change the flight path right away rather than waiting for the “next waypoint.”

Drill 4: Emergency Landing with People Nearby

This drill focuses on operational restraint. If people are near the landing zone, your job is to keep the aircraft from becoming the problem.

Scenario: You must land quickly due to a power anomaly, but the landing area has a small group within the approach path.

Correct compliance response:

1. Choose the safest landing option available. If you can land without passing over people, do so.
2. Use a controlled approach. Avoid steep descents that can cause drift or unstable touchdown.
3. Secure the area before shutdown. Keep the aircraft stable until it is safe to approach.

Easy example: If you have a clear alternate landing spot 50 feet away, landing there is usually safer than trying to “thread the needle” over people.

Drill 5: Post-Incident Documentation Without Guesswork

Documentation should be factual and consistent with what you observed and what the aircraft recorded.

Scenario: After a lost-link event, the aircraft lands safely in an open area. You must prepare your incident notes.

Correct compliance response:

1. Record the timeline. Note when the trigger occurred, when control was lost, and when the aircraft stabilized.
2. Record conditions. Wind, visibility, and any unusual factors you observed matter because they explain why the event happened.
3. Record system behavior. Include what the aircraft did in failsafe mode and whether it matched your preflight expectations.
4. Record outcomes. Confirm no damage to people or property and note the landing location.

Easy example: If you wrote “video froze” at 10:14 and “telemetry recovered” at 10:16, keep those times consistent with your logs.

Drill Practice Template for Repetition

Use the same structure every time so your brain doesn’t improvise under stress.

A good drill ends with a clean landing and a clean record. If you can’t explain your actions in plain language afterward, the drill didn’t teach you the right sequence.

12.1 Remote Pilot Documentation Requirements and Record Keeping Practices

Remote pilot documentation is less about collecting paper and more about proving you followed the rules when someone asks. For Part 107, the core idea is simple: you must be able to show your identity, your authorization status, and the basic facts of the operation—especially if something goes wrong.

What You Must Carry and Show

Start with the minimum “show it on request” items. During operations, you should be prepared to present:

• Your FAA remote pilot certificate (or student certificate if applicable).
• Your FAA registration for the aircraft, if required for that aircraft.
• Any required authorizations for the airspace you’re using, such as LAANC permissions or other approvals.

A practical habit: keep these items in a single, consistent location on your phone and in a backup form. If your phone dies mid-mission, you still want a quick way to verify what you can.

What You Must Keep as Records

Part 107 record keeping is often misunderstood as “save everything forever.” In reality, you’re building a defensible trail for the operations you conducted. Typical record categories include:

1. Operational logs: date, location, time, aircraft ID, and a short description of the mission.
2. Preflight and condition notes: what you checked and any anomalies you observed.
3. Maintenance and inspection records: evidence that the aircraft was maintained and inspected according to your procedures.
4. Training and currency evidence: proof you meet the requirements to act as a remote pilot.
5. Incident and safety reporting documentation: notes and reports created after any required event.

A good rule of thumb is to record what you would need to answer: “What did you do, where did you do it, and what condition was the aircraft in?”

Building a Record Keeping System That Actually Works

Your system should match how you operate. If you fly one-off missions, a lightweight log is enough. If you run repeat jobs, you want templates.

Use a consistent structure for each flight entry:

• Mission header: date, location (or nearest intersection), and purpose.
• Aircraft and remote ID details: aircraft identifier and registration reference.
• Operational parameters: takeoff/landing times, maximum altitude, and whether you used an observer.
• Airspace authorization reference: the authorization ID or a note that it was not required.
• Preflight summary: battery status, airframe condition, and any deviations.
• Outcome: normal completion, any issues, and corrective actions.

This structure prevents the common failure mode: you remember the mission details, but the paperwork doesn’t.

Examples of Integrated Documentation

Example: One Day, Multiple Flights

You run three short flights for the same client. Instead of separate scattered notes, create one mission folder for the day and three flight entries inside it. Each entry includes the authorization reference and the preflight summary. If a question arises about one flight, you don’t have to reconstruct the day from memory.

Example: Preflight Anomaly and Corrective Action

During preflight, you notice a battery cell voltage imbalance. You do not launch. You record the observation, the corrective action (battery removed from service), and the replacement used. This turns a “near miss” into a clear, factual record of responsible decision-making.

Example: Observer Involvement

If you use a visual observer, document the observer’s role and the communication method you used. Your flight log should reflect that the observer was actively supporting situational awareness, not just standing nearby.

Record Retention and Organization Practices

Keep records organized so you can retrieve them quickly. Use consistent file naming such as YYYY-MM-DD_Location_AircraftID_MissionType. Store digital records in at least two places. For paper, keep a single binder or folder per month or per project.

If you ever need to reconstruct a mission, you want the answer in minutes, not hours. Documentation is not a chore; it’s your operational memory.

Quick Checklist for Each Flight Entry

• Certificate and authorization references available
• Flight date, location, and purpose recorded
• Aircraft identifier recorded
• Operational parameters recorded
• Preflight condition summary recorded
• Outcome and any issues recorded
• Any required incident notes recorded

12.2 Aircraft Maintenance, Inspection, and Preflight Documentation Standards

Aircraft maintenance and documentation are not separate from safe operations; they are the evidence trail that your aircraft is airworthy and your decisions are traceable. For Part 107, the exam focus is practical: what you must check, what you must record, and how documentation supports operational compliance.

Foundational Concepts for Airworthiness Evidence

Start with three ideas that show up repeatedly in questions and real missions:

1. Airworthiness is a condition, not a feeling. If the aircraft is damaged, modified, or operating outside limits, it is not “good enough” because it flies.
2. Inspection is a process with scope. You inspect what the manufacturer and your operating procedures require, not whatever looks interesting.
3. Documentation is the proof. Records show that inspections happened, maintenance occurred when required, and recurring issues were addressed.

A simple way to remember the flow is: maintain → inspect → document → operate. If any link is missing, the chain is weaker.

Preflight Documentation Standards That Matter

Preflight documentation typically includes the aircraft’s current status and the checks you performed before takeoff. A strong standard has four parts:

• Aircraft identity and status. Record the aircraft ID or serial reference used in your program, plus the current condition (e.g., “no known defects” or “defect corrected”).
• Maintenance and inspection references. Note the date of the most recent required inspection or maintenance action and what it covered.
• Preflight inspection results. Capture the outcome of your preflight checklist items, including any anomalies.
• Operational readiness decision. Document that you determined the aircraft was safe to operate based on the inspection results.

Example: If your checklist includes propeller condition, you don’t just “look.” You record whether props are cracked, chipped, or loose, and you note the action taken if you found a problem.

Inspection Scope and What to Record

Inspections should be aligned with your manufacturer’s instructions and your internal procedures. For exam-style thinking, categorize inspection items into four buckets:

1. Structure and airframe integrity

   • Look for cracks, loose fasteners, damaged landing gear, or bent arms.
   • Record the specific issue and whether it was corrected.

2. Propulsion and control components

   • Check prop condition, motor mounts, and control linkages.
   • Record any abnormal vibration, unusual motor behavior, or calibration needs.

3. Power system and energy management

   • Verify battery condition indicators, secure mounting, and connector integrity.
   • Record battery serial reference and any out-of-tolerance findings.

4. Navigation, sensors, and safety systems

   • Confirm firmware status per your procedure, sensor health, and failsafe behavior checks.
   • Record pass/fail outcomes for required preflight checks.

A useful rule for documentation quality: write down what would change your decision. If an item is normal and routine, a brief “OK” is enough. If it affects airworthiness, it must be specific.

Maintenance Records That Support Operational Decisions

Maintenance records should show what was done, when it was done, and why it was done. Keep them consistent with your maintenance plan. Common record elements include:

• Work performed (e.g., prop replacement, firmware update per procedure, motor mount inspection)
• Date and time frame (use the date format your program standardizes)
• Parts used (at least part identifier or reference)
• Inspection follow-up (what you checked after maintenance)
• Sign-off (who performed or verified the work)

Example: On 2026-02-13, a motor was replaced due to intermittent startup. Your record should note the replacement, the post-maintenance checks completed, and the outcome. If the post-checks were skipped, the record is incomplete even if the replacement was correct.

Integrated Example: From Finding a Defect to Documenting the Fix

Imagine you notice a propeller chip during preflight. A compliant workflow looks like this:

1. Stop and assess. You do not launch “to see what happens.”
2. Determine impact on airworthiness. A chipped prop can affect balance and thrust, so it is a defect that changes the decision.
3. Correct before flight. Replace the prop per your procedure.
4. Update records. In your preflight documentation, note the defect, the corrective action, and that the aircraft is now ready.
5. Confirm follow-up checks. If your procedure requires a post-replacement check, record that outcome.

This pattern is exactly what exam questions test: the right action is the one that prevents operating with an unresolved condition and leaves a clear record of what changed.

Common Exam Pitfalls

• Recording only that you “checked.” The record must reflect results, especially for items that affect readiness.
• Mixing maintenance and inspection dates. Maintenance records and preflight records serve different purposes; keep them distinct.
• Ignoring unresolved defects. If a defect is found and not corrected, the aircraft is not ready, and the documentation should reflect that.

A good documentation standard is boring in the best way: it makes your decision defensible, your aircraft status clear, and your operations consistent.

12.3 Managing Operations With Contractors And Ground Teams Without Violations

When you hire contractors or coordinate a ground team, the goal is simple: everyone helps you run a Part 107-compliant operation, and nobody accidentally creates a violation. The exam tests your ability to connect roles, procedures, and communication to the rules.

Foundational Roles and Responsibility Boundaries

Under Part 107, the remote pilot in command remains responsible for the operation. Contractors can perform tasks like staging equipment, setting up a landing zone, or managing a perimeter, but they do not replace the remote pilot’s duties.

A practical way to think about it: the remote pilot owns the “flight and compliance decisions,” while the ground team owns “physical support tasks.” If a contractor starts giving flight instructions, you have a mismatch in responsibility.

Example: You hire a survey crew. The crew leader asks to “send it lower over the crowd to get better detail.” You must refuse that request unless the operation is authorized and compliant for the specific scenario. The ground crew can suggest, but you decide.

Pre-Task Planning That Prevents Rule Confusion

Before anyone touches equipment, define three things in plain language: the mission boundaries, the communication method, and the stop conditions.

1. Mission boundaries: where the aircraft will operate (altitude, lateral limits, and any airspace constraints you already verified).
2. Communication method: who talks to whom, and how you confirm critical calls.
3. Stop conditions: what triggers an immediate pause or abort, such as unexpected people entering the area, loss of visual reference, or a change in weather.

Example: Your ground team is told, “If you see people walking into the takeoff/landing area, call ‘HOLD’ immediately.” During the mission, someone steps into the approach path. You pause, re-establish safety, and only resume when the area is clear.

Ground Team Procedures That Support Visual Line of Sight

Part 107 requires you to maintain control and comply with visual line of sight requirements. A ground team can help you keep track of the aircraft by acting as your eyes and ears, but they cannot replace your responsibility to see and manage the flight.

Best practice: assign a single observer role if you need one, and specify what they report. Use short, unambiguous calls: “Aircraft left,” “Aircraft descending,” “Obstruction ahead,” or “Visual lost.”

Example: In a wooded area, the aircraft briefly disappears behind trees. The observer calls “VISUAL LOST.” You stop maneuvering that depends on visual reference, adjust to regain sight, and avoid continuing a planned route that assumes uninterrupted visibility.

Controlled Airspace and Authorization Handling with Contractors

If your operation requires authorization (such as controlled airspace permission), contractors must not treat authorization as “their job.” Your team should understand that authorization is tied to the operation you planned.

Best practice: brief the ground team on what they can and cannot change. They may move equipment within the designated area, but they should not change the flight path, altitude, or timing without your approval.

Example: A contractor wants to “start earlier” because the client is ready. Earlier start means different airspace conditions or a different time window. You either confirm the authorization still covers the revised plan or you delay until it does.

Operations over People and Perimeter Control

If your mission involves people near the aircraft, you must ensure the operation category and safety measures match the rules. Ground teams often manage the perimeter, but they must do it in a way that supports compliance.

Best practice: define the perimeter as a physical boundary with clear entry rules. If people must be kept out, the ground team enforces it. If people are allowed under a specific operational category, the ground team still prevents unexpected changes that would move you into a different category.

Example: You plan a route that keeps the aircraft away from bystanders. Mid-mission, a contractor opens a gate “just for a minute.” That minute can turn into an unplanned people exposure. The correct response is to stop the flight, secure the boundary, and resume only when the situation matches the plan.

Communication Protocols That Reduce Human Error

Use a simple call-and-response structure for critical events. The remote pilot confirms actions; the ground team reports observations.

• “READY” confirms the area is set.
• “HOLD” pauses operations due to a safety or compliance issue.
• “RESUME” confirms the condition is corrected.

Example: The observer reports “OBSTRUCTION ENTERING.” You call “HOLD.” The ground team moves the obstruction away and calls “RESUME.” You then re-check the aircraft’s position and continue.

Case-Style Example: The “Small Change” That Becomes a Violation

You authorized a mission at a specified altitude and route. The ground team learns the client wants a different angle and asks to adjust the flight path while you’re still on site.

Correct approach: stop and re-evaluate. If the change affects airspace permission, altitude, or people exposure, you cannot treat it as a minor tweak. You either revise the plan to match the authorization and safety boundaries or you end the operation.

The exam-friendly takeaway is consistent: contractors can help you execute the plan, but only you can ensure the executed plan still matches the compliance requirements.

12.4 Privacy, Data Handling, and Operational Conduct Requirements for Missions

Privacy and data handling aren’t separate from “how you fly.” They’re part of the same operational discipline: decide what you will collect, why you will collect it, how you will protect it, and how you will behave around people and property. Part 107 expects you to operate safely and responsibly; privacy and conduct requirements help you do that in the real world where cameras and microphones turn “incidental” into “evidence.”

Privacy Fundamentals for Drone Missions

Start with the simplest question: what does your mission capture? If your aircraft can record identifiable people, license plates, private property, or interior spaces through windows, treat the mission as privacy-sensitive. A practical best practice is to define “privacy boundaries” during planning: the areas you will avoid, the angles you will not use, and the times you will not fly when people are likely to be in view.

Example: You’re inspecting a warehouse roof. If the route passes over a parking lot, plan an approach that keeps the camera pointed downward and away from faces. If you must pass near vehicles, use zoom and framing to focus on the roofline rather than the people.

Data Handling Principles from Capture to Storage

Data handling is a chain. If any link is weak, you end up with accidental disclosure, lost evidence, or compliance headaches.

1. Minimize collection. Only record what you need for the deliverable. If still images are sufficient, avoid continuous video.
2. Control access. Limit who can view raw footage and who can export final products.
3. Protect storage. Use encrypted storage where possible, and avoid leaving files on shared devices.
4. Track retention. Decide how long you keep raw data and when you delete it. Keep final deliverables longer if your contract requires it.
5. Document handling steps. Keep a simple internal log: when data was captured, where it was stored, and who accessed it.

Example: After a bridge inspection, you store raw footage in a folder labeled with the mission ID, then export only the annotated stills needed for the report. You delete the raw video after the retention window unless the client requests it.

Operational Conduct Around People, Property, and Information

Operational conduct covers how you behave while flying and while handling what you collected.

• Maintain respectful distance from people and avoid hovering over individuals when you can reposition safely.
• Use observers when your mission requires it, and ensure they can help manage both safety and privacy boundaries.
• Do not use the aircraft to intrude into areas where people have a reasonable expectation of privacy.
• Treat any audio or video as sensitive. Even if you did not “intend” to capture someone, your system may.

Example: A homeowner asks you to “just get one more shot” of their backyard. If the shot would include identifiable faces or private activities, you can offer an alternative framing that captures the target feature without filming people.

Integrated Example Workflow for a Privacy-Sensitive Mission

Assume you’re filming a small construction site for progress documentation.

1. Planning: You confirm the camera can capture workers’ faces from your planned altitude and angle. You adjust the route to keep faces out of frame and set the camera to capture short clips only when key progress milestones occur.
2. Preflight: You assign an observer to watch for both safety and privacy boundaries, including when people move into the camera’s field of view.
3. During Flight: If workers step into view, you pause recording and reposition rather than continuing to film.
4. After Flight: You store raw clips under the mission ID, restrict access to the project lead, and export only the time-stamped clips needed for the client.
5. Retention: You delete raw clips after the agreed retention period, keeping only the exported deliverables.

This workflow keeps your mission compliant with operational expectations while also reducing the chance that you collect more personal information than necessary. It’s not about being paranoid; it’s about being precise.

Quick Checklist for Mission Execution

• Privacy boundaries defined before takeoff
• Recording type chosen based on deliverable needs
• Observer role includes privacy awareness
• Raw data stored with restricted access
• Exports limited to what the client requires
• Retention and deletion performed on schedule
• Internal log maintained for traceability

12.5 Practical Exam Review Sets With Integrated Mission Compliance Questions

This section uses short, realistic review sets that mix Part 107 compliance with the kind of decision-making the exam tests. Each set starts with a simple scenario, then forces you to apply the correct rule language to the mission details.

Review Set 1: Documentation and Operational Boundaries

Scenario: You’re hired to inspect a warehouse roof. The remote pilot will fly at 250 feet AGL, over a parking lot, and record video for the client.

Questions:

1. What documentation must be available for the remote pilot during the operation?
2. Which operational limit is most directly tied to the aircraft’s altitude?
3. If the mission includes recording people in the parking lot, what compliance focus should guide your planning?

Integrated best-practice reasoning:

• Keep your remote pilot certificate and any required operational documentation ready before you move the aircraft. The exam often frames “available” as “you can produce it when asked,” not “you wrote it somewhere.”
• Altitude limits are tied to the operation itself, so your planning should explicitly state the planned AGL and how you will verify it.
• For privacy and data handling, the exam expects you to treat recording as part of mission conduct: plan where the camera points, minimize unnecessary capture, and ensure your workflow doesn’t create avoidable misuse.

Example: If your plan says “about 300 feet,” you’re not giving yourself a compliance target. Rewrite it as “250 feet AGL maximum,” and confirm your aircraft’s altitude display and any geofencing behavior before takeoff.

Review Set 2: Preflight, Maintenance Mindset, and Launch Readiness

Scenario: Your aircraft has a new battery installed. The last preflight inspection was completed two days ago. You’re ready to launch for a short mapping flight.

Questions:

1. What must you do before flight that is not satisfied by “it flew fine last time”?
2. How should you treat aircraft condition checks when a component was changed?
3. What is the exam’s typical trap around “inspection” versus “preflight”?

Integrated best-practice reasoning:

• Preflight is about current condition, not historical luck. The exam likes answers that separate “maintenance records” from “before you fly, verify the aircraft is safe to operate.”
• A battery change means you should verify secure installation, correct connection, and expected behavior during startup.
• The trap is choosing an answer that only references paperwork. The correct approach includes both: confirm documentation where required and perform the operational checks that ensure safe flight.

Example: If you see a loose battery latch during preflight, you don’t “send it for a quick test.” You fix the issue first, because the exam assumes you will not launch with known unsafe conditions.

Review Set 3: Operations over People and Risk Controls

Scenario: You plan to film a small event. The flight path will pass near spectators, but you intend to keep the aircraft away from them.

Questions:

1. What determines whether the operation is considered over people?
2. If people are present under the flight path, what compliance category logic should you apply?
3. What should you do if your plan changes and people end up closer than expected?

Integrated best-practice reasoning:

• “Over people” is about the aircraft’s position relative to people during the operation, not your intent. The exam often rewards answers that focus on the actual flight geometry.
• If people are under the flight path, you must treat the mission as over people and apply the correct compliance requirements.
• If the environment changes, you adjust the operation to remain compliant. That can mean rerouting, delaying, or canceling.

Example: If you planned a route that clears the crowd but wind pushes you laterally, you must treat that as a compliance risk. The correct move is to stop and re-evaluate rather than hope the next minute stays the same.

Review Set 4: Integrated Scenario: One Mission, Multiple Compliance Checks

Scenario: A contractor requests a night inspection of a billboard. The flight will be in controlled airspace. You will use a visual observer.

Questions:

1. What two compliance areas must be verified before you even consider takeoff?
2. What does the observer role require for effective compliance?
3. How do you handle authorization constraints if the airspace permission is limited?

Integrated best-practice reasoning:

• Before takeoff, verify authorization/airspace permission and confirm night operational readiness. The exam expects you to treat these as gating items.
• An observer supports situational awareness, but compliance depends on clear communication and defined responsibilities.
• If authorization limits your altitude, time, or location, your mission plan must match those limits exactly. “Close enough” is not a compliance strategy.

Example: If authorization allows a specific time window, you schedule your launch so the flight occurs within that window. If you’re late, you don’t “stretch” the operation.

Mind Map: Exam Question Strategy for Compliance

Case-Style Wrap-Up Questions

1. Which compliance item is most likely to be tested as a “before flight” requirement: authorization, preflight checks, or post-flight reporting?
2. If your plan says “no people under the path” but spectators drift into the area, what is the most exam-consistent response?
3. When authorization includes constraints, what should your mission plan do with those constraints: ignore them, approximate them, or align exactly?