1. Introduction
Unmanned aerial vehicles (UAVs) support repeated visual, thermal, and LiDAR-based inspections of overhead transmission assets while reducing personnel exposure to energized lines and difficult terrain [
1,
2,
3]. Reliable inspection, however, requires more than a short, collision-free route. The vehicle must maintain asset-specific clearance from conductors, towers, and insulators, remain sufficiently close to the inspection corridor to preserve task utility, and account for vegetation, buildings, terrain, and moving obstacles.
Path planning in this setting is difficult for three related reasons. First, although every fixed object is kinematically static, its geometry and operational meaning may differ: a conductor is checked by its distance to a line, a tower by horizontal stand-off from its axis, and ordinary clutter by surface clearance. Treating these objects as a single undifferentiated class obscures their distinct constraints. Second, a path that is geometrically clear at one instant can still conflict with a moving object when the UAV and the object reach the same location at similar times. Third, postprocessing can introduce an unsafe shortcut unless the feasibility conditions applied during search are also enforced during smoothing. These considerations motivate a planner that represents safety as an explicit feasible set rather than solely as a weighted penalty.
Recent studies have advanced both power-line-specific and general UAV planning. Li et al. developed an improved A* method for power-line inspection [
4], and Xing et al. coupled perception with model-predictive control for autonomous line inspection [
5]. In broader environments, global–local planners have combined optimized A* search with the dynamic window approach (DWA) [
6], while risk-aware formulations have addressed flight in unknown environments [
7]. These studies provide useful components, but differences in maps, vehicle models, safety margins, and validation protocols preclude a direct comparison of their reported numerical results.
The gap addressed here is therefore not the absence of A*, dynamic-obstacle prediction, or line-of-sight smoothing as individual components. Instead, it concerns their constraint-consistent integration with power-line semantics in a reproducible planner and matched simulator. In PL-RiskPlanner, the soft field ranks a candidate edge only after a hard point-and-segment verifier has accepted it. Consequently, changing a risk weight can alter the preferred feasible path, but it cannot make an edge that violates a specified clearance admissible. Reusing the verifier during shortcutting yields the sampled-feasibility-preservation property stated formally in
Section 3.6. The method is therefore positioned as a planner for power-line corridors rather than as a new general-purpose or computationally accelerated A* variant.
Figure 1 illustrates the physical elements represented in the planning model. The side elevation is schematic because tower clearance is evaluated in the horizontal plane, with the simulated route laterally offset from the tower axis. The conductor and its caution band affect both feasibility and risk, while trees, buildings, and predicted moving-obstacle positions influence waypoint selection.
The contributions are consolidated as follows:
We formulate a power-line-specific feasible set that distinguishes conductor-line distance, tower-axis stand-off, tagged-insulator clearance, general-clutter surface clearance, and predicted moving-object clearance. A soft risk objective ranks only admitted edges, and the same sampled segment predicate is applied during graph search, line-of-sight smoothing, and final evaluation. Proposition 1 establishes sampled-feasibility preservation, within the stated sampling resolution, for any finite set of soft-risk weights.
We provide an implementation-level description that includes a worked candidate calculation, pseudocode, explicit failure handling, an uncertainty margin for noisy velocity estimates, and a machine-readable parameter manifest. The formulation explicitly states the limitations of the sampled verifier and does not claim a continuous-time safety guarantee.
We construct a paired simulation benchmark with six scenario families, three difficulty levels, five seeds, executable classical and hybrid baselines, controlled obstacle-count and occupied-volume-density factors, component ablations, one-at-a-time weight perturbations, and targeted tests of route crossings and prediction noise. An additional comparison imposes the same cap on hard-verifier point checks for every planner, thereby avoiding the assumption that an A* expansion, an RRT sample, and a DWA rollout are equivalent computational units. The configurations, seeds, trial-level records, analysis scripts, and publication figures are included as reproducibility artifacts.
The remainder of this paper is organized as follows.
Section 2 positions the method relative to recent power-line, hybrid, dynamic, and risk-aware planners.
Section 3 defines the simulator, risk and feasibility models, search procedure, baselines, metrics, and reproducibility protocol.
Section 4 and
Section 5 present the matched benchmark, density and ablation results, and dynamic-risk and sensitivity analyses.
Section 6 summarizes the conclusions supported by these results and outlines the remaining steps from simulation to practical validation.
3. Materials and Methods
3.1. Study Scope and Planning Problem
This study evaluates path planning in synthetic corridor geometry with obstacle states supplied to the planner. It does not model onboard perception, low-level flight control, wind, communication delay, or vehicle dynamics beyond a maximum-speed approximation of arrival time. The term “online” in
Figure 2 denotes computation performed for a single planning query from a supplied obstacle-state snapshot; it does not imply a deployed real-time replanning system. Accordingly, PL-RiskPlanner is evaluated as a planner for power-line corridors, not as a universal obstacle-avoidance algorithm or a faster implementation of A*.
The workspace is
m. A planning state is the UAV-center position
and a candidate path is an ordered sequence
where
m and
m in the default corridor. The planning task is to connect these endpoints with segments that remain in
and satisfy all five sampled clearance inequalities in Equation (
8), while minimizing the accumulated objective in Equation (
10). The nominal inspection route is laterally displaced from a straight conductor located at
m and
m. Tower axes are located at
m and
m. In the simulator, conductor distance is the perpendicular distance to the straight line, whereas tower distance is the horizontal distance to the nearest tower axis. The conceptual catenary in
Figure 1 is not used in the numerical evaluation.
Conductors, towers, insulators, trees, buildings, and terrain are all kinematically static in the simulator. They are nevertheless represented as distinct semantic classes because their safety functions are not interchangeable. A conductor uses distance to a line and a conductor-specific stand-off; a tower uses horizontal distance to an axis; an insulator uses net clearance to a tagged sphere and its own threshold; and general static clutter denotes the remaining non-asset spherical proxies. Thus, “static obstacle” refers to general clutter unless a power asset is named explicitly; this distinction does not imply that conductors or towers move. In the implementation, every fixed spherical proxy, including each tagged insulator, also undergoes a generic non-contact check, with the stricter insulator threshold imposed in addition. Dynamic objects are represented as spheres with constant velocity vectors. Static and dynamic net clearances subtract both the obstacle radius and the UAV radius m, whereas conductor and tower thresholds are specified directly for the UAV center.
Figure 2 summarizes a complete planning query and includes a worked edge evaluation. In panel A,
denotes the predecessor grid state,
a candidate admitted by the hard verifier, and
a candidate rejected by that verifier. A
waypoint is a retained three-dimensional vertex in an ordered path. In panel C, the raw grid path connects adjacent search waypoints. A
verified shortcut connects non-consecutive raw waypoints only after SafeSeg accepts the segment. A
rejected candidate edge fails the same predicate and is therefore excluded from both the search graph and the smoothed path.
Section 3.4,
Section 3.5 and
Section 3.6 define the numerical entries and module interactions.
3.2. Scenario Families and Test Conditions
The generator deterministically constructs six scenario families from a family name, difficulty level, map index, and random seed.
Table 2 summarizes these factors. The three difficulty levels use base static-object counts of 8, 16, and 28, to which family-specific bonuses of 0–12 objects are added. Object classes are assigned cyclically in the order shown in
Table 2. The tree-intrusion family follows the cycle tree–tree–wire-risk, whereas each other family cycles through its listed classes. Static centers are sampled as
m and
m. Heights follow
m for tower-adjacent, insulator, and wire-risk objects,
m for terrain, and
m for trees and buildings. The base radii for trees, buildings, terrain, tower-adjacent objects, insulators, and wire-risk objects are 1.8, 3.0, 2.5, 2.0, 1.1, and 1.0 m, respectively. Each base radius is multiplied by the difficulty factor 1.00, 1.25, or 1.55 and by an independent draw from
.
Only the dynamic-obstacle family contains randomly generated moving objects in the general benchmark: 1, 3, or 5 objects at easy, medium, or hard difficulty, respectively. Their initial centers follow m, m, and m, while their radii follow m. Initial velocity components are sampled from m/s in the x and y directions and m/s in the z direction. The targeted route-crossing tests replace these random motions with controlled crossings near estimated UAV arrival times. For each generated map, the local pseudorandom generator is initialized by interpreting the first 16 hexadecimal digits of SHA-256(seed:family:difficulty:map-index) as an integer. Generated coordinates and radii are stored to three decimal places. This rule, the canonical family identifiers, and every ordered object list are retained in the released manifest and trial archive.
Figure 3 shows plan-view projections generated directly by the released scenario code for one matched, medium-difficulty condition. Each colored circle represents the horizontal footprint of a spherical obstacle proxy after addition of the UAV radius, and its color identifies the object class. The circular symbols in the legend denote the same classes but are not drawn to scale. In contrast, the pale annotated rectangle represents only the plan-view projection of the continuous conductor safety band; it is not another obstacle symbol. The tower–insulator and tree-intrusion families concentrate objects near power assets, the building–terrain family combines larger clutter classes, and the dynamic family adds moving objects marked with velocity vectors. Each object’s
z coordinate remains active in the three-dimensional safety calculations and is not discarded by the planner.
The default safety distances are m from the conductor, m from a tower axis, and m of net clearance from tagged insulator spheres. The environment configuration also retains a 0.2 s integration step and an 800-step episode limit for compatibility with future control-policy studies; these values do not determine graph-search execution time.
3.3. Research Difficulties and Design Responses
The method addresses four specific difficulties in this planning problem.
D1: Heterogeneous asset geometry. Conductors, tower axes, tagged insulators, and general clutter require distinct distance functions and thresholds. Equation (
8) addresses this issue through an explicit five-part feasibility predicate.
D2: Temporal coexistence. Spatial clearance alone does not reveal a route-crossing conflict. Equations (
3) and (
4) therefore introduce candidate-specific arrival-time prediction, with a bounded uncertainty margin when velocity estimates are noisy.
D3: Constraint consistency. Unconstrained shortcutting can invalidate an edge that was accepted during search. The method therefore applies one sampled segment predicate during search, smoothing, and final evaluation, leading to Proposition 1.
D4: Computational accountability. Repeated geometric checks increase query time, while algorithm-specific iteration counters are not directly comparable. We therefore report wall-clock time and expanded or sampled states and conduct an additional experiment with the same cap on hard-verifier point checks for every planner.
These design responses delimit the methodological contribution. PL-RiskPlanner does not alter the asymptotic A* search rule, nor do we claim that arrival-time prediction is novel in isolation. The contribution examined here is a testable, power-line-specific composition in which semantic constraints define admissibility, soft risk affects preference only within the feasible set, and postprocessing cannot bypass the sampled checker. The route-crossing tests address D2, the component ablation addresses D3, and the density, weight, and equal-budget analyses examine D1 and D4.
3.4. PL-RiskPlanner Workflow
PL-RiskPlanner combines five modules: approximate arrival-time prediction, a power-line risk field, a hard point-and-segment verifier, six-connected risk-aware A* search, and verifier-gated line-of-sight smoothing. The method is hybrid in composition because it couples discrete global search, time-indexed obstacle prediction, hard geometric screening, and geometric postprocessing; “hybrid” does not denote a new A* expansion rule.
Figure 2 provides a worked example from the medium-difficulty dynamic-obstacle scenario with map index 1 and seed 0. Starting from the predecessor
m, the candidate
m has an estimated arrival time of 10.3 s and a risk value of 1.5556, which gives an edge cost of 9.4446. The alternative
m is rejected before cost comparison because its conductor and tower distances are 2.83 m and 4.47 m, respectively, both below their hard thresholds. Panel C further shows that non-consecutive raw waypoints are connected only when the proposed shortcut passes SafeSeg. The dashed orange edge represents a rejected proposal and is not part of either returned path.
3.5. Dynamic Prediction, Risk Field, and Hard Feasibility
For a candidate state
, the approximate arrival time is computed from the straight-line distance to the start and the configured maximum speed
m/s:
This low-cost estimate does not integrate distance along the partially constructed path and can therefore differ from the arrival time during dynamic execution. For a moving object
j with center
, velocity
, and radius
, the predicted center is
When the relative standard deviation of a velocity estimate is
, the optional radial uncertainty margin is
where
and
m by default in the uncertainty-aware tests. The margin is set to zero in the nominal matched benchmark. Dynamic net clearance is obtained by subtracting
,
, and
from the distance between the candidate state and the predicted center.
Let
,
,
,
,
, and
denote conductor distance, tower-axis distance, net tagged-insulator clearance, minimum net clearance to any fixed spherical proxy (including tagged insulators), predicted dynamic-object clearance, and deviation from the nominal inspection route. A normalized caution function is
where
s is the hard boundary and
c is the caution distance. Conductor and tower caution distances are
and
; static and dynamic caution clearances are 3 m. The soft field is
The default weights are
,
,
,
, and
. These values are prespecified engineering scaling coefficients rather than fitted probabilities. Each proximity term is dimensionless and bounded in
, so coefficients between 4 and 6 place the four asset and obstacle terms on a comparable scale. Route deviation is measured in meters and therefore receives the smaller coefficient of 0.08, preventing a meter-scale offset from dominating the bounded proximity terms. The defaults were fixed before the formal benchmark and were not optimized for individual scenarios or adjusted after inspection of the test outcomes. Because tagged insulators belong to the fixed-sphere pool used to compute
, they contribute to the generic static-risk term through
; the separate
check imposes their asset-specific hard stand-off.
Soft risk never replaces feasibility. The five explicit clearance constraints have different meanings:
enforces conductor-line stand-off,
enforces horizontal tower-axis stand-off,
enforces tagged-insulator surface clearance,
prevents contact with every fixed spherical proxy, and
prevents contact with a moving-object sphere at the predicted arrival time. The
check therefore includes a zero-clearance contact test for insulators, while
imposes the stricter tagged-insulator threshold. Together with the workspace bound, a point is admitted only when
A segment is accepted only if every sampled point passes Equation (
8):
where
S includes both endpoints and at least one interior point, with a sample spacing no greater than 0.5 m. The search, final metric computation, and smoothing stages all call the same function. This sampled test provides a reproducible numerical verifier, but it does not prove continuous-time collision avoidance between samples.
3.6. Risk-Aware Search and Safety-Verified Smoothing
The global search uses a 4 m, six-connected Cartesian grid with a Euclidean heuristic. For adjacent states, the edge cost is
subject to
. The search stops when it reaches the goal or expands 20,000 nodes. If no goal path is found, the run is recorded as a planning failure, not automatically as a safety violation.
After the search, greedy line-of-sight smoothing tests the farthest remaining waypoint first. A shortcut is accepted only when it satisfies Equation (
9); otherwise, the candidate endpoint is moved backward until a safe shortcut is found. During final whole-path verification, the planner falls back to the raw grid path if the smoothed result fails. Algorithm 1 summarizes this procedure.
| Algorithm 1: PL-RiskPlanner for one obstacle-state snapshot. |
Require: Scenario , start , goal , grid spacing h, weights, Ensure: A verified path or a planning-failure record
1:
Construct the risk field and hard verifier from
2:
Initialize the A* frontier with
3:
while frontier is not empty and expanded nodes do
4:
Pop the state with minimum accumulated cost plus Euclidean heuristic
5:
for each of its six grid neighbors do
6:
Estimate and predicted moving-object centers
7:
if or then
8:
continue
9:
end if
10:
Relax the edge using Equation (10)
11:
end for
12:
end while
13:
if the goal was not reached then
14:
return failure
15:
end if
16:
Reconstruct the raw grid path
17:
Greedily accept only shortcuts that pass SafeSeg
18:
Verify the complete smoothed path; otherwise use
19:
return the verified path and sampled-clearance metrics
|
Proposition 1 (sampled-feasibility preservation). Assume that PL-RiskPlanner returns a path after its final verification. Every point in the segment sample set satisfies Equation (
8)
, irrespective of the finite values assigned to λ and the five soft-risk weights. Proof. Search inserts an edge only after SafeSeg returns 1. Smoothing replaces a subsequence only with an edge for which the same predicate also returns 1, and final verification checks every retained edge again. The risk terms are evaluated only after this admissibility test and therefore cannot authorize an infeasible edge. This property is limited to the stated 0.5 m sampling resolution and should not be interpreted as a continuous-time safety certificate. □
For V expanded grid vertices and neighbor edges, priority-queue search has the usual graph overhead. If M objects and at most K segment samples are checked per edge, geometry evaluation contributes . Greedy smoothing is in the worst case for an N-waypoint raw path. Expanded nodes, wall-clock query time, and raw/final waypoint counts are therefore reported alongside path metrics.
3.7. Executable Baselines, Ablations, and Parameters
The matched benchmark contains only algorithms that are executed for every listed trial: standard A* [
11], RRT* [
12], RRT-Connect [
15], APF [
13], DWA [
14], risk-aware A*, an A*–DWA global–local hybrid [
6], and PL-RiskPlanner. All baseline implementations receive the same scenario geometry and use the same hard point-and-segment verifier. They are shared-simulator implementations of algorithmic families, not claims of exact reproduction of every cited paper.
Table 3 gives the complete primary settings; secondary score coefficients and all defaults are archived in
configs/planner_parameters.toml. No planner was retuned separately for a test family. The A*–DWA implementation follows the global-guide/local-rollout pattern summarized in
Section 2, and RRT-Connect provides a bidirectional sampling comparison. The native stopping counters in the final column are mechanism-specific safeguards, not a common compute unit: one A* node expansion, one RRT sample, and one DWA command rollout invoke different numbers of geometric checks. They are retained for exact reproduction, while the equal-verifier-budget experiment described below provides the resource-matched comparison requested for computational fairness.
The component ablation either sets the global multiplier to zero (thereby disabling all soft-risk guidance), removes the tower soft term, removes the dynamic soft term, or disables smoothing while retaining the hard verifier. The archived identifier for the first condition is without_powerline_risk_field, but the figures and tables label it “w/o soft-risk guidance” to describe the implemented intervention precisely. Arrival-time prediction is examined separately in the controlled route-crossing experiment because randomly moving objects do not necessarily create a temporal conflict. In particular, “without tower cost” does not remove the hard tower-clearance constraint, and “without dynamic risk” removes only the soft dynamic term while retaining the predicted dynamic-obstacle admissibility checks. This distinction allows the ablation to test soft guidance without changing the feasible set implicitly.
3.8. Experimental Design
The main matched benchmark contains 6 families × 3 difficulty levels × 20 map indices × 5 seeds paired scenario instances. Executing 8 planners produces 14,400 trial records. Instances are paired by family, difficulty, map index, and seed. For a given key, every planner receives the same workspace, start and goal, conductor and tower geometry, ordered static-object list, moving-object states, radii, and safety thresholds. The component ablation applies five planner configurations to the same 1800 instances, producing 9000 additional records.
The resource-matched audit uses the same six families and three difficulty levels, map indices 0–4, seeds 0–4, and all eight planners, giving additional trials. Each query is capped at 60,000 calls to the common point-level hard verifier, and every sampled point in a segment check consumes one unit of this budget. A query that reaches the cap before returning a verified path is recorded as a planning-only budget exhaustion rather than as a collision or safety violation. An algorithm may terminate earlier after reaching the goal, and the audit does not imply an equal number of floating-point operations outside the verifier. Instead, it imposes the same upper bound on calls to the shared, obstacle-dependent safety primitive and reports both the number of checks consumed and the wall-clock time.
The controlled static-density experiment isolates obstacle burden at medium difficulty. It uses three clutter-focused families, five map indices, five target counts
, four radius multipliers
, five planners, and five seeds, producing 7500 rows. Within each family–map–seed tuple, all conditions share one canonical ordered list of obstacle centers: count selects a prefix and radius multiplier changes radii only. The reported nominal occupied-volume fraction is
Because overlapping spheres are not unioned,
is a controlled density index rather than an exact free-space fraction.
The component-weight experiment uses one default condition and one-at-a-time perturbations of for . Six families, three difficulty levels, five map indices, eleven conditions, and five seeds yield 4950 records. This range was selected to examine reasonable calibration variation around the fixed defaults rather than to search for a post hoc optimum.
The targeted route-crossing test uses the dynamic-obstacle family at all 3 difficulty levels, 20 map indices, and 5 seeds. It places 2, 4, or 6 moving objects near the nominal route at estimated UAV arrival times, samples their speeds from m/s, and evaluates PL-RiskPlanner, the no-prediction variant, and the no-dynamic-risk variant. This design produces 900 records. The prediction-noise test uses the same 60 maps and 5 seeds, 4 planner variants, and relative velocity-noise standard deviations , producing 6000 records. Independent Gaussian noise with a component-wise standard deviation of is added only to the velocity supplied to the planner. Clearance is then recomputed using the unperturbed moving-object velocities and the same approximate-arrival-time convention; this quantity is termed the simulator-reference dynamic clearance.
The uncertainty-margin sweep uses ten map indices per difficulty level, five seeds, noise levels , multipliers , and caps m, producing 4050 records. The setting , m is the prespecified reference. These dynamic experiments are reported separately from the nominal benchmark to avoid generalizing results from controlled crossings or noisy velocity estimates to untested conditions.
3.9. Metrics and Statistical Analysis
The metric definitions separate four events:
Planner-reported success: the planner returns a goal-reaching path according to its own termination and internal checks.
Collision: sampled static or dynamic net clearance is non-positive.
Safety violation: any sampled conductor, tower, insulator, static, or dynamic clearance violates Equation (
8). A collision is therefore also a safety violation, but a search-budget failure is not.
Verified completion: planner-reported success with neither collision nor safety violation under the independent final evaluator. A planning-only failure is a non-completion without a recorded safety violation.
Path length is
To avoid rewarding a short path that does not pass final verification, the primary composite cost is
with
m. Smoothness matches the released implementation:
where zero-length segments are skipped. The reported energy value
is a geometric proxy, not measured electrical energy.
For a returned path, the minimum safety margin is the smallest value, over all sampled path points, among the conductor distance minus , tower distance minus , tagged-insulator net clearance minus , minimum net clearance to fixed spherical proxies, and dynamic-object net clearance. This common margin is positive only when every asset-specific sampled threshold is satisfied.
Path geometry, the energy proxy, clearance, smoothness, and search-size summaries are calculated only for verified completions. Wall-clock query time and are calculated over all trials. The timer starts immediately before deterministic scenario construction and stops when the planner returns. It therefore includes shared scenario preparation and planner-specific search and postprocessing but excludes the independent post hoc metric calculation. Algorithms are interleaved within each scenario key under the same guarded worker schedule. The resulting end-to-end times are descriptive matched measurements rather than isolated search-kernel benchmarks. In the route-crossing and velocity-noise analyses, simulator-reference dynamic clearance is also summarized over planner-returned paths before independent safety filtering, so unsafe returned paths are not hidden by complete-case selection. Outcome proportions receive Wilson 95% intervals, while mean paired differences relative to PL-RiskPlanner receive percentile-bootstrap 95% intervals from 2000 resamples using analysis seed 20260731. The complete analysis policy is stored in configs/major_revision_analysis.toml. Raw proportions are retained in the archive but are displayed in the manuscript as counts, percentages, or concise decimal values without unnecessary trailing zeros.
3.10. Implementation and Reproducibility
Experiments run on Windows 11 (build 10.0.26200; Microsoft Corporation, Redmond, WA, USA) with an Intel Core Ultra 7 270K Plus CPU (Intel Corporation, Santa Clara, CA, USA) (24 physical cores and 24 logical processors), 63.4 GB usable RAM, and an NVIDIA GeForce RTX 5090 D v2 (NVIDIA Corporation, Santa Clara, CA, USA) with 24,455 MiB memory. The planners execute on the CPU; the GPU is reported for workstation completeness and is not used to accelerate the graph or sampling planners. The software environment is Python 3.12.10, NumPy 2.4.6, pandas 3.0.3, SciPy 1.17.1, and Matplotlib 3.11.0.
Formal experiments use five seeds (0–4), process pools of at most four workers, periodic CSV checkpoints, and a resource guard that terminates a run if CPU utilization, system-memory use, GPU utilization, or GPU-memory use exceeds 90%. The run manifest records commands, package versions, workstation information, and SHA-256 hashes of the evaluated source and configuration files. The accompanying reproducibility archive contains configs/, src/, scripts/, trial-level CSV files, summary tables, figure-generation code, and the exact random seeds.
OpenAI Codex (GPT-5, OpenAI, San Francisco, CA, USA; accessed June–July 2026) assisted with experimental-protocol structuring, code editing, analysis-script organization, figure-layout refinement, and manuscript language. All formal numerical records reported here were computed by the archived local Python scripts from the stated configurations and seeds rather than accepted from model-generated text. The authors reviewed the code, numerical outputs, figures, and interpretations and remain responsible for this study.
6. Conclusions
We presented PL-RiskPlanner as a safety-constrained, risk-aware planning framework for synthetic power-line corridors. Hard conductor, tower, insulator, static-object, and predicted dynamic-object checks define the sampled feasible set; the power-line risk field ranks only admissible edges; and smoothing reuses the same segment verifier. The methodological claim is therefore constraint consistency across search and postprocessing, not a new or faster A* expansion rule. Across the 1800 nominal matched trials, no safety flag was recorded under the independent sampled evaluation, and the mean verified-path length was 110.64 m. Among matched cases completed by both methods, the mean paired path-length difference (DWA minus PL-RiskPlanner) was 0.16 m (95% bootstrap CI [0.12, 0.2] m); their aggregate verified-path means were 110.8 and 110.64 m, respectively. In addition, disabling verifier-gated smoothing increased mean path length by 13.64 m (95% paired-bootstrap CI [13.37, 13.91] m).
The direct comparison with DWA places this result in context. PL-RiskPlanner’s mean verified path was only 0.160 m shorter in paired trials, while DWA’s mean sampled minimum margin was 0.043 m larger and its mean query time was 2.268 s shorter. In contrast, PL-RiskPlanner returned 25.91 fewer waypoints on average and reduced the lower-is-better smoothness measure by 0.180. It is therefore better positioned here as a compact, globally searched and verifier-gated premission route generator, whereas the tested DWA baseline is a faster local rollout method; neither is claimed to dominate the other on every criterion. The equal-verifier-budget audit further exposed the computational trade-off. Within this cap, PL-RiskPlanner completed 292/450 queries and exhausted the budget in 158, whereas DWA completed 450/450 queries without exhausting the budget. The two planners consumed a mean of 45,577 and 18,696 point checks per query, respectively.
The targeted tests clarify where the dynamic components matter. In 300 route-crossing trials per variant, the no-prediction configuration produced 222 safety flags. For the complete planner, no safety flag was recorded. At the largest tested relative velocity-noise level, the bounded uncertainty margin changed the flag count from 203 to 47 and the mean simulator-reference dynamic clearance on returned paths from −0.27 to 2.23 m. These are condition-specific simulation results rather than a claim of universal or continuous-time safety.
A further contribution is the evaluation record itself: 50,400 trial records, fixed seeds, complete planner parameters, source hashes, controlled clutter factors, ablations, weight perturbations, noise tests, a common hard-verifier-budget audit, and scripts that regenerate the statistics and figures after checking data completeness. The current model does not represent perception, full vehicle dynamics, acceleration of moving objects, or physical flight. Validation with surveyed geometry, realistic timing and sensor streams, hardware-in-the-loop tests, and a staged program of supervised flight trials would therefore be required before drawing conclusions about field operation. The separation between asset-specific distance functions, hard admissibility, and soft guidance also provides an interface for related constrained-planning studies, but transfer beyond power-line corridors remains to be tested.