33  UAV Trajectory Control

Network-Aware Paths, Feedback Loops, and Traceable Adjustment Decisions

33.1 Start Simple

Start with a mission that moves, loses energy, and changes its radio path while it works. In UAV Trajectory Control, the practical question is what the aircraft must sense, relay, decide, and prove before the flight or network role is safe enough to trust.

In 60 Seconds

UAV trajectory control decides how an aircraft should move after the mission has started. A network-aware controller adjusts waypoints, orbit center, route spacing, altitude, speed, or station-keeping behavior from current records: link freshness, gateway reachability, payload backlog, energy reserve, route constraints, and safety state. A good trajectory decision records the observed problem, selected adjustment, rejected adjustment, safety gate, energy gate, expected effect, and fallback action.

33.2 Learning Objectives

By the end of this chapter, you will be able to:

• Explain how UAV trajectory control connects mission objectives, network records, safety constraints, and energy reserve.
• Compare waypoint shift, orbit center shift, radius change, dwell-time control, altitude adjustment, and station-keeping.
• Distinguish a network problem from an energy, payload, gateway, or safety problem before moving the aircraft.
• Build a trajectory adjustment record with selected and rejected actions.
• Define fallback behavior when a path update cannot be executed safely.

33.3 Overview: Make One Bounded Path Change

If you only need the operating rule, this layer is enough: trajectory control should classify the problem, change one bounded part of the path, and preserve the records that keep the aircraft useful and safe.

Trajectory control changes a path only after records, classification, safety, energy, execution, verification, and fallback are traceable.

Mobile summary: Make one bounded path change, verify the same records again, and use the fallback before energy or safety margin is spent.

Classify

Name the pressure first: stale status, weak gateway, payload backlog, low reserve, route conflict, coverage gap, or safety constraint.

Adjust

Choose a waypoint shift, dwell change, orbit shift, altitude band, route spacing change, or station-keeping behavior that targets that pressure.

Verify

Compare the same records after the move, then keep, reverse, reduce, hand off, buffer, or recall the mission according to the fallback rule.

33.4 Corridor Relay Record

For the utility corridor example, the useful record is a small decision trace. It explains why the aircraft moved, what it refused to change, and how the team will know whether the adjustment worked.

Observed pressureUrgent status from the far segment is stale; bulk imagery can wait; the crew-facing gateway leg still works.

Selected adjustmentShift one waypoint and add a short dwell near the weak segment while leaving the gateway-facing leg unchanged.

Rejected adjustmentReject expanding the whole racetrack because it spends reserve and may damage the working gateway exit.

Fallback ruleIf urgent status remains stale, hand relay duty to a standby aircraft, mark the segment delayed, or reduce the mission scope before reserve is spent.

33.5 Why Trajectory Control Oscillates

A trajectory controller becomes unstable when it reacts to every noisy record as if it were a mission fact. The safe design separates fast flight stabilization from slower mission-level path changes.

• Measurement noise: one stale link sample should not trigger a large route change without confirming gateway, payload, energy, and safety context.
• Coupled effects: a dwell that helps urgent status can drain reserve, delay later tasks, and grow the payload queue.
• Exit-path risk: moving toward a weak segment can break the gateway-facing leg unless the record keeps that path explicit.
• Fallback timing: if the controller waits too long to reduce, hand off, or recall, the aircraft may spend the reserve that made fallback possible.

Trajectory Control Boundaries

Minimum Viable Understanding

• A trajectory is not just a path; it is a time-ordered motion plan tied to mission records.
• Trajectory changes should not be triggered by one weak metric alone. Link, gateway, payload, energy, safety, and mission context must be checked together.
• Slowing, hovering, widening a route, or shifting an orbit can improve one area while harming energy reserve, coverage elsewhere, or gateway reachability.
• A safe controller separates fast flight stabilization from slower mission-level path adjustment.
• Every trajectory update should leave a decision record that explains why the move was made and what will cause the next check.

33.6 Prerequisites

Revisit these chapters if the terms are unfamiliar:

• UAV Network Topologies: topology choices, gateway exits, and physical link records.
• UAV Swarm Coordination: task ownership, formation behavior, and state freshness.
• FANET Fundamentals: aerial ad hoc links and routing choices.
• UAV Energy-Aware Mission Planning: battery reserve, return planning, and energy constraints.

33.7 How This Chapter Fits

Topology decides who can talk to whom. Swarm coordination decides who owns each task. Trajectory control decides how the aircraft should move when current records show the plan is no longer good enough. This chapter focuses on the mission-level trajectory decisions that sit above low-level flight stabilization and below production readiness checks.

The overview depth layer shows the trajectory control loop that anchors record intake, problem classification, bounded trajectory update, safety gate, energy gate, execution, verification, and fallback record.

33.8 Control Loop

A trajectory controller should make one bounded adjustment at a time, then verify whether the records improved. This keeps trajectory control from becoming an uncontrolled chase after noisy metrics.

1. Collect records: link freshness, route state, gateway exit, payload queue, energy reserve, safety state, and mission progress.
2. Classify the problem: coverage gap, stale link, gateway weakness, payload backlog, route conflict, low reserve, or safety risk.
3. Generate candidate adjustments: shift waypoint, shift orbit center, change route spacing, adjust speed or dwell time, change altitude band, or station-keep.
4. Apply safety and energy gates: reject any adjustment that violates separation, geofence, return reserve, role handoff, or payload constraints.
5. Execute the bounded change: send the new trajectory intent and keep the previous safe behavior available.
6. Verify the effect: compare the same signals after the aircraft has had time to follow the new path.
7. Record fallback: if the records do not improve, choose a different adjustment, reduce the mission, buffer data, hand off role, or recall.

33.9 Adjustment Strategies

Trajectory control is not one algorithm. It is a family of adjustments, each with a different failure mode.

Figure 33.1: UAV trajectory strategy map comparing waypoint shift, orbit center shift, route spacing, speed or dwell change, altitude band, and station-keeping with their record triggers and check risks.

33.9.1 Waypoint shift

Move the next waypoint or small route segment toward a mission area that needs attention.

Use when the path is close to correct but one local area is under-served.

Check risk: a small shift may break the next gateway, safety, or task handoff assumption.

33.9.2 Orbit center shift

Move the center of a circular or racetrack path toward a persistent demand area.

Use when a repeated path should spend more useful time near one part of the mission area.

Check risk: improving one side of the orbit can weaken coverage or gateway reachability elsewhere.

33.9.3 Route spacing change

Widen or tighten path spacing for coverage, sensing, or relay quality.

Use when the issue is area coverage, repeated gaps, or too much duplicate path overlap.

Check risk: tighter spacing costs time and energy; wider spacing can hide missed areas.

33.9.4 Speed or dwell change

Slow down, speed up, or pause briefly over a section of interest.

Use when payload collection, link quality, or inspection confidence depends on time over an area.

Check risk: dwell time can consume energy and delay later tasks.

33.9.5 Altitude band change

Change altitude within the allowed mission envelope to improve visibility, link geometry, or separation.

Use when the route shape is acceptable but vertical position is part of the problem.

Check risk: altitude can affect coverage, payload quality, wind exposure, and separation rules.

33.9.6 Station-keeping

Hold a position or small patrol pattern to preserve relay, gateway, or observation service.

Use when current traffic needs a stable point more than broad movement.

Check risk: holding position can drain reserve and leave other tasks uncovered.

33.10 Trajectory Decision Record

The trajectory decision record is the artifact that prevents path changes from becoming untraceable behavior. It should be compact enough to update during testing and precise enough to audit after a mission.

Figure 33.2: UAV trajectory decision record showing observed problem, selected adjustment, rejected adjustment, link state, gateway state, energy reserve, safety gate, payload state, fallback action, and recheck trigger.

Observed problem What records show the current path is not good enough?

Selected adjustment What bounded path change will be tried first?

Rejected adjustment Which plausible adjustment was rejected, and why?

Link and gateway state Does the new path preserve the required peer, relay, or gateway exit?

Energy reserve Can the aircraft execute the change and still preserve return or role-handoff reserve?

Safety gate Does the change respect separation, geofence, altitude, obstacle, and operator constraints?

Payload state Does the path support live, summarized, buffered, or delayed payload behavior?

Recheck trigger What records force the next trajectory check?

33.11 Worked Example: Inspection Relay Path

Scenario: A utility crew is using a UAV as an inspection relay along a damaged corridor. The UAV follows a racetrack path near the crew while collecting status notes and buffering high-resolution images for later upload.

Observed problem:

• Urgent status notes from the far segment are delayed.
• The gateway path near the crew remains fresh.
• The image queue is growing but can wait.
• Energy reserve is acceptable only if the UAV does not extend the full route.

Rejected adjustment:

• Expanding the entire racetrack was rejected because it would increase route length and reduce return margin while helping only one segment.

Selected adjustment:

• Shift the near-side waypoint toward the far segment.
• Add a short dwell at the relay-friendly point.
• Keep the gateway-facing leg unchanged so urgent status still has an exit.
• Continue buffering high-resolution images until the gateway path is stronger.

Fallback behavior:

• If urgent status still does not improve, the UAV hands the relay role to a standby aircraft or marks the far segment as delayed.
• If reserve drops below the mission rule, the UAV stops accepting new relay tasks and returns.
• If the payload queue becomes too large, the mission records pending upload instead of marking delivery complete.

This worked example is useful because the trajectory change is bounded and record-based. It does not assume that a larger route, slower speed, or extra aircraft is automatically better.

33.12 Selection Checklist

Use this checklist before accepting a trajectory update.

Start with the mission State whether the path is serving sensing, relay, access, gateway, inspection, search, or handoff.

Classify traffic Separate control, telemetry, urgent status, summaries, and bulk payload data.

Check topology Confirm that the new path still supports the selected topology or intentionally changes it.

Check coordination Confirm that the path change does not create task overlap, formation conflict, or uncovered work.

Check energy Confirm return, handoff, or reduced-service behavior before extending a path or adding dwell time.

Check safety Reject changes that need unapproved altitude, unsafe spacing, obstacle shortcuts, or operator ambiguity.

Check payload State whether payload data is live, summarized, buffered, or delayed after the trajectory change.

Record fallback Define what happens if the records do not improve after the adjustment.

33.13 Common Pitfalls

1. Chasing a Single Metric

Moving the aircraft because one metric worsened can damage gateway reachability, safety, payload delivery, or energy reserve. Classify the problem before adjusting the path.

Flight Control vs Mission Control

Low-level stabilization keeps the aircraft flying. Mission-level trajectory control changes where the aircraft goes and why. Do not mix fast safety loops with slower mission decisions.

Coverage Must Preserve Exit Paths

A path can cover more area while weakening the gateway. Every trajectory update should state how traffic exits the aerial network.

4. Adding Dwell Without Energy Check

Slowing or holding position can improve a local task while draining reserve. Dwell time needs an energy gate and a fallback.

5. Leaving No Rejected Option

If the record does not say why a plausible adjustment was rejected, the next teammate cannot tell whether it was checked or missed.

33.14 Interactive Checks

Match Trajectory Control Concepts

Order a Trajectory Check

Label the Trajectory Decision Record

Knowledge Check

33.15 Summary

This chapter treated UAV trajectory control as a record-driven mission decision:

• Control loop: collect records, classify the problem, select a bounded adjustment, gate it for safety and energy, execute, verify, and record fallback.
• Strategies: waypoint shift, orbit center shift, route spacing change, speed or dwell change, altitude band change, and station-keeping.
• Decision record: observed problem, selected adjustment, rejected adjustment, link and gateway state, energy reserve, safety gate, payload state, fallback action, and recheck trigger.
• Worked example: a corridor relay adjustment that preserved urgent status delivery while allowing bulk imagery to buffer.
• Check habit: trajectory control should improve the mission without hiding gateway, safety, energy, payload, or coordination risk.

33.16 What’s Next

• To examine energy feasibility in more detail, read UAV Energy-Aware Mission Planning.
• To coordinate several aircraft trajectories, read UAV Trajectory Swarm Coordination.
• To study mission patterns and avoidance, read UAV Missions and Avoidance.
• To connect trajectory control to production readiness, read UAV Networks: Production Checks.

33.17 Key Takeaway

Trajectory control affects network quality as much as flight path. Route planning should consider link availability, gateway reachability, energy reserve, sensing windows, and safe fallback positions.