Single-Pilot Resource Management (SRM)
Most Part 107 operations are flown by exactly one remote pilot, holding a controller, watching a live video feed, tracking airspace, and monitoring battery and telemetry all at once — with no co-pilot to hand off a task to when things get busy. Single-Pilot Resource Management, or SRM, is the discipline of managing every resource available to that one pilot — workload, automation, information, and equipment — so nothing important gets dropped when attention is limited. This lesson breaks SRM into its practical components and shows how each applies to a real sUAS mission.
What SRM means for a remote pilot
SRM is the art and science of managing every resource — human, hardware, and information — available to a single pilot, before and during a flight, to make sure the mission is completed safely. It was originally developed for single-pilot manned aircraft, where a lone pilot has to do everything a two-person crew would normally divide between them. The concept transfers directly to sUAS operations: a remote pilot flying without a visual observer or payload operator is functionally a single-pilot crew, juggling flight control, navigation, communication, and monitoring simultaneously.
Task management: doing the right thing at the right time
Task management is the skill of prioritizing what deserves attention at any given moment, rather than treating every task as equally urgent. During a mission, a remote pilot juggles maintaining visual line of sight, monitoring the live video feed, watching battery telemetry, scanning for other aircraft or people entering the area, and possibly operating a camera or sensor payload. Good task management means recognizing that maintaining VLOS and scanning for hazards always take priority over adjusting a camera angle or checking a text message, even when the less important task feels momentarily more interesting or urgent.
Automation management: knowing what the aircraft is doing for you
Modern sUAS include automation like GPS position hold, return-to-home, obstacle avoidance, and geofencing. Automation reduces a solo pilot's workload, but it also creates a specific risk: over-reliance on automation the pilot doesn't fully understand. A pilot who assumes obstacle avoidance will always catch every hazard, or who has never manually flown the aircraft without GPS assist, has a dangerous gap in skill exactly when automation might fail or behave unexpectedly. Good automation management means knowing precisely what each automated feature does, what its limits are, and being able to fly manually if it disengages or malfunctions.
Information management: filtering signal from noise
A single remote pilot has access to a large amount of information before and during a flight — weather briefings, NOTAMs, airspace data, manufacturer specifications, live telemetry, and visual observation. Information management is the skill of gathering what's actually needed, verifying its reliability, and not becoming overwhelmed or distracted by low-value information at the expense of high-value information, like a live battery warning buried under a stream of routine telemetry updates.
Single-Pilot Resource Management treats the lone remote pilot as the hub connecting task, automation, information, and workload management.
View LargerWorkload management and recognizing task saturation
Workload management is closely related to task management but focuses specifically on total mental capacity rather than prioritization — recognizing when the sheer number of things happening at once has exceeded what one person can safely track. Task saturation is the point where a pilot is so overloaded that something important, often the most important thing (like maintaining VLOS), gets silently dropped without the pilot even noticing it happened. The correct SRM response to recognizing task saturation is to shed lower-priority tasks immediately — pause the camera work, simplify the flight path, or land — rather than trying to push through and do everything at once.
Worked scenario: SRM during a solo inspection flight
You're flying a solo cell tower inspection, manually piloting close to the structure while simultaneously operating a zoom camera to capture detail shots. Partway through, you notice a gust of wind requiring more active control input than expected, at the same moment a text message notification lights up your phone in your pocket. Good SRM here means immediately recognizing this as a workload spike: the wind gust demands full attention on flight control, the camera work is lower priority and can pause, and the phone notification is irrelevant and should be ignored entirely until the aircraft is safely stabilized or landed.
SRM and the legal responsibility behind it
Just as with ADM broadly, SRM supports the remote pilot's responsibility under 14 CFR 107.19 to ensure the operation remains safe throughout the flight, not just at launch. A pilot who becomes so task-saturated that they lose track of the aircraft's position relative to people or obstacles has failed that ongoing responsibility, regardless of whether the specific cause was automation over-reliance, poor task prioritization, or simple information overload.
Why SRM matters more for solo remote pilots than it might for manned aviation
A manned aircraft pilot at least has the aircraft's own attitude and motion providing constant physical feedback about what's happening. A remote pilot working from a controller and screen is more insulated from that direct feedback and more dependent on correctly managing the information sources available to them — making deliberate SRM practice arguably even more important for sUAS operations than it is in some manned, single-pilot contexts.
| Component | What it manages | Common failure mode |
|---|---|---|
| Task management | Prioritizing what deserves attention right now | Treating a low-priority task (camera angle) as equally urgent as a high-priority one (maintaining VLOS) |
| Automation management | Understanding what automated features do and their limits | Over-relying on obstacle avoidance or GPS hold without a manual-flight fallback plan |
| Information management | Filtering high-value information from low-value noise | Missing a critical battery or link warning buried among routine telemetry updates |
| Workload management | Total mental capacity and recognizing task saturation | Continuing to add tasks after capacity is already exceeded, silently dropping something important |
Recognizing and Responding to Task Saturation Mid-Flight
Use this sequence any time you notice yourself falling behind on a solo mission.
Notice the warning signs
Losing track of elapsed flight time, forgetting to check battery percentage, or feeling like you're reacting instead of anticipating are all signs of task saturation building.
Identify the highest-priority task
In almost every case this is maintaining visual line of sight and flight control — everything else is secondary by comparison.
Shed lower-priority tasks immediately
Pause camera or payload operation, simplify the remaining flight path, and stop trying to multitask until workload is back under control.
Reassess before resuming
Confirm the aircraft's position, remaining battery, and surrounding hazards before resuming any paused task.
Land if workload does not recover
If shedding tasks doesn't restore a manageable workload, land the aircraft rather than continuing the mission task-saturated.
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| Believing SRM only applies when flying without a visual observer | "Single-pilot" sounds like it excludes any crewed operation | SRM specifically describes the solo remote pilot's own workload management, which still applies even alongside a crew — CRM (next lesson) adds the coordination layer on top. | FAA Risk Management Handbook |
| Assuming more automation always means less workload | Automated features are marketed as making flying easier | Automation reduces routine workload but adds the burden of understanding its limits and having a manual fallback plan. | FAA Risk Management Handbook |
| Trying to push through task saturation instead of shedding tasks | Stopping a paid task (camera work) feels like a failure or a cost | Shedding lower-priority tasks under high workload is the correct SRM response, not a failure. | 14 CFR 107.19 |
Is SRM only relevant to pilots who fly without any crew at all?
No. SRM describes how the individual remote pilot manages their own workload, information, and automation. It applies whether or not a visual observer or other crew member is present — when a crew is present, Crew Resource Management (the next lesson) adds coordination between people on top of each individual's own SRM.
Does using automation like return-to-home mean I don't need strong manual flying skills?
No. Good automation management specifically requires the ability to fly manually if the automated feature disengages, fails, or behaves unexpectedly. Relying on automation without that manual fallback is a recognized SRM failure mode, not sound practice.
How do I know if I'm task-saturated versus just busy?
A useful marker is whether you're anticipating problems or only reacting to them after they happen. Forgetting to check something routine (battery level, elapsed time) that you'd normally track without thinking is a strong sign that workload has exceeded your capacity.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.