1. The benefit of combining the components is concentrated in NE, the basis for choosing the default configuration is inconsistent, and uncertainty estimates are missing
Table 3 reports the following:
| Method | SR ↑ | nDTW ↑ | NE ↓ |
|---|
| w/o Both | 14.3 | 10.4 | 116.3 |
| w/o Foresight (Backtracking only) | 16.3 | 9.4 | 111.4 |
| w/o Backtracking (Foresight only) | 15.0 | 10.5 | 111.3 |
| Full FaB-Fly | 15.1 | 9.1 | 97.6 |
These results support the positive effect of Foresight used alone, as well as the value of the combination in reducing the average navigation error. However, adding Foresight on top of Backtracking lowers SR from 16.3 to 15.1 and nDTW from 9.4 to 9.1, while NE improves from 111.4 to 97.6.
Table 4 shows that this pattern is not specific to one configuration. All four judge-input combinations have lower NE (89.8–102.6) than both single-component variants (111.3 and 111.4), but all of them have lower SR than w/o Foresight (16.3), and three of the four also fall below w/o Backtracking (15.0). When only one judge uses video, SR drops to 13.0 and 11.7, below not only the image-only configuration (14.4) but also w/o Both (14.3). The benefit of the combination therefore appears consistently in NE, but not in SR or trajectory quality.
Moreover, the default configuration is not the best on any single metric across the paper's ablations. The highest SR is achieved by w/o Foresight (16.3, Table 3) and the lowest NE by "video Foresight + image Backtracking" (89.8, Table 4); in Table 5, using Qwen 3.8 27B as the judge yields a higher SR (15.7), and using Gemma 4 26B A4B yields better NE (92.3) and nDTW (10.2). When discussing Table 3, the authors use NE to argue that the combination is better than w/o Foresight, but when discussing Table 4, they use SR to argue that using videos for both judges is better than using video for only one, so the metric underlying the argument switches between the two analyses. I suggest stating the primary metric and the criterion for selecting the default configuration explicitly.
The claims should be qualified accordingly. The introduction limits the complementarity of the two components to reducing navigation errors, but the contribution list and the conclusion describe them as complementary without qualification, and the discussion of Table 4 interprets the SR result of using videos for both judges as consistent with this complementarity.
Finally, the manuscript does not report the number of repeated runs, random seeds, confidence intervals, or the number of episodes in each evaluation split. Both video generation and MLLM inference are stochastic, while the SR gain of the full system is only 15.1−14.3=0.8 percentage points over w/o Both and 15.1−15.0=0.1 points over Foresight only.
NE is also sensitive to the configuration: changing only the judge model makes NE vary between 92.3 and 107.1, a range (107.1−92.3=14.8) comparable to the NE improvement of the combination over w/o Foresight (111.4−97.6=13.8). Without uncertainty estimates, it is difficult to judge whether these differences are stable.
2. The improvement over external baselines comes mainly from the base framework, and the comparison conditions on AerialVLN-Fine are asymmetric
All analyses in Section 4.3, including Table 3, are conducted on AerialVLN-Fine. The SR of w/o Both already reaches 14.3, i.e., 14.3−8.0=6.3 points above FineCog-Nav, whereas the full method adds only 15.1−14.3=0.8 points over w/o Both. Hence, the 15.1−8.0=7.1-point improvement over FineCog-Nav comes mainly from the base framework (landmark memory, instruction grounding, geometric candidate narrowing, and low-level control) rather than from Foresight and Backtracking.
This gap is also accompanied by asymmetric comparison conditions. Page 7 states that, among the zero-shot methods, CityNavAgent, LookasideVLN, and FaB-Fly use prior environmental data, yet neither of the former two appears in Table 2; moreover, FaB-Fly's landmark memory on AerialVLN-Fine is built from images captured across each entire scene. FaB-Fly is therefore the only method in Table 2 that uses a prior survey, and its improvement over FineCog-Nav conflates prior information with the contribution of the method itself.
There are no ablations on AerialVLN-S, yet page 7 attributes the improvement over LookasideVLN to evaluating flights before and after execution. I suggest adding w/o Both on AerialVLN-S and including at least one baseline on AerialVLN-Fine that also uses environmental priors, or at least marking the priors used by each method in the tables.
The sources of the baseline numbers should also be stated: which results are cited directly and which were re-run, and which base models, environment memories, and action budgets were actually used. Differences in base models likewise affect the attribution of performance differences.
3. Direct mechanistic validation is missing for whether the signal from predicted videos reflects actual execution outcomes
The authors recognize that predictions for distant or unobserved regions may be inaccurate and use Backtracking to handle prediction errors; by design, the generated videos serve only to compare candidates and need not precisely reproduce the actual flight path (p. 2, lines 83–103; p. 3, lines 150–155). These are reasonable design choices. The remaining question is whether the key semantic information that distinguishes candidates in the generated videos can reliably predict how well the actual flight satisfies the instruction.
According to Eq. (1), V^(g)∼Wθ(⋅∣o,u(g)), the video model is conditioned only on the current observation o and the candidate-specific movement prompt u(g), whereas the actual low-level controller additionally uses the current instruction segment si (p. 5, §3.2; p. 6, Eqs. (1)–(2)). The same target can be reached via different paths, so relations such as "crossing" or "detouring" depicted in the video may not match the path the controller actually takes. Imprecise predictions can still provide a useful ranking signal, but the current support comes mainly from downstream performance.
The "image Foresight" in Table 4 scores candidates from the current observation and the candidate's location information, and can serve as a control for testing whether videos provide additional information. However, the effect of video relative to images reverses depending on the Backtracking input: with image-based Backtracking, SR drops from 14.4 to 11.7; with video-based Backtracking, it rises from 13.0 to 15.1.
The explanation of Figure 3(a) also needs clarification. The movement prompt for the second candidate specifies a 10 m flight ("fly 10m toward the zebra crossing"), which, according to Section 3.3, is exactly that candidate's distance from the UAV; yet the predicted video shows the UAV not reaching the crosswalk, and the text explains this as a 10 m flight being unable to reach the second candidate.
If u(g) encodes the full distance, "not reaching" reflects how the generator renders the prompt rather than the true geometry; if u(g) encodes only the horizontal distance and ignores the height difference (the UAV starts on a rooftop), the prompt itself omits height information. In either case, the discriminative signal in this example does not necessarily reflect whether the candidate is actually reachable.
I suggest adding a direct candidate-level analysis. Visit-All already flies to every narrowed candidate and scores each observed flight with the Backtracking judge (p. 9), so without new flight experiments the authors can report the agreement between Foresight scores and actual-flight scores or outcomes (e.g., top-1 agreement or rank correlation), as well as the agreement between predicted and actual flights on key action events. This would clarify when the system benefits from video prediction and when it relies on Backtracking to recover.
4. There is a clear trade-off between endpoint success and trajectory fidelity, and direct evidence for the value of process verification is lacking
On AerialVLN-Fine, FaB-Fly improves SR from 8.0 (FineCog-Nav) to 15.1, but nDTW drops from 22.5 to 9.1 and NE increases from 91.4 to 97.6 (p. 7, Table 2). This trade-off is not limited to AerialVLN-Fine: on AerialVLN-S val-unseen, FaB-Fly's OSR (28.3) is clearly lower than that of LookasideVLN (36.0) and CityNavAgent (35.2), and its NE (79.7) is higher than CityNavAgent's (60.2).
The authors attribute the lower nDTW to the low-level controller flying directly toward landmarks rather than closely tracing the reference path, and to return flights reducing trajectory similarity, and they acknowledge this limitation in the conclusion (p. 8, lines 414–425; p. 9, lines 482–485). However, Table 3 shows that return flights explain only a small part of the gap: w/o Both, which involves no return flights, already has an nDTW of only 10.4, below FineCog-Nav (22.5) and even NavGPT (15.9), and adding Backtracking lowers it by only a further 1.0–1.4 (10.4→9.4 and 10.5→9.1). The main gap stems from the base framework itself.
A lower nDTW does not directly imply violating the language instruction, since the reference path may not be unique and return flights also increase trajectory differences. However, the core motivation of this paper concerns process requirements such as crossing a river, detouring, and turning, and endpoint SR and average NE alone cannot distinguish among the following cases:
- reaching the target while satisfying the action constraints in the instruction;
- reaching the target via a path that does not meet the instruction's requirements;
- satisfying the instruction with a trajectory whose shape differs from the reference route.
I suggest a segment-level analysis based on the existing trajectories that distinguishes semantic action violations from general path deviations. This would verify the problem the paper targets more directly than explaining the drop in nDTW.
5. The cost comparison is incomplete, and the source of the additional overhead is hard to interpret
The timing in Figure 4 already includes flight time: the full method takes about ×1.20 the time of w/o Both while improving SR by 0.8 points, and Visit-All takes about ×1.86 the time of the full method while achieving about 0.7 points higher SR (p. 9). These numbers support FaB-Fly's cost advantage over exhaustive visiting.
However, Figure 4 omits w/o Foresight. The SR of this variant is not only the highest in Table 3 but also higher than that of Visit-All (15.1+0.7=15.8 according to the text): a variant that generates no videos, first flies to the first location of the lowest-cost route, and retries at most once outperforms Visit-All, which physically flies to every candidate. This makes the omission of w/o Foresight all the more worth questioning, and suggests two possibilities: selecting among all candidates by Backtracking scores may not be reliable, or these differences lie within noise.
The w/o Foresight variant has worse NE, and its total time also depends on how often Backtracking is triggered, so it should be measured under the same timing protocol. If the main value of the full system lies in reducing NE, the cost discussion should present this benefit explicitly.
In addition, each segment may require generating a 5–10 s video and calling the judge for each of up to 8 candidates, yet the total time increases by only about 20% over w/o Both. Because Appendix A.3 deduplicates routes by their final endpoints rather than by the current candidates, the number of current candidates entering Foresight may be substantially smaller than 8, and the correct current candidate may also be excluded.
I suggest reporting the distribution of the number of candidates per segment, the fraction of single-candidate segments, the fraction of segments in which the correct candidate is retained, and the number of videos actually generated per episode, along with the hardware or service environment, whether calls run serially or in parallel, and how video generation, judge calls, and flight time are each timed. This would help reproduce the timing comparison and show in how many decisions Foresight actually participates in a multi-candidate choice.
6. Several key implementation details are missing, which affects reproducibility and the attribution of results
The paper specifies the models used, the prior-survey procedure, the main parameters of candidate narrowing, and the single-retry rule, but the main text and Appendix A still lack the following:
- the value of the backtracking threshold τ (a location is accepted when zobs≥τ) and how it was chosen;
- the weight λ in the route cost Γ(r) (Eq. (4)), and the mapping from motion phrases other than "turn left"/"turn right" to the reference turn angle ϕ(mj) (Appendix A.3; only ϕ(turn left)=+45∘ and ϕ(turn right)=−45∘ are given);
- the text-embedding model and similarity threshold used for retrieval (Appendix A.2), and the distance threshold for merging landmark detections (Appendix A.1);
- how the MLLM judges' outputs are mapped to the scores z^(g)∈[0,1] and zobs∈[0,1] (Eqs. (2)–(3)), the complete judge prompts, and the frame-sampling settings for the predicted and observed videos;
- whether videos are still generated when only one candidate is available;
- the control implementation and arrival criterion for returning to the departure pose qdep, and whether return flights count toward the action budget;
- how w/o Foresight selects the alternative candidate after Backtracking is triggered.
The last item particularly needs to be specified. Appendix A.3 states that, in the w/o Foresight variant, the UAV flies to the first location of the lowest-cost route, but the retry in the full method relies on the Foresight scores, g=argmaxg∈C~i∖{gF}z^(g) (Algorithm 1, line 8). It is unclear which ranking replaces z^(g) once Foresight is removed, and this variant happens to achieve the highest SR.
One minor clarification remains. The related-work section states that FineCog-Nav judges subgoal completion by combining observations, subgoal memory, and imagined scene descriptions, but the introduction characterizes it as a check based on the observation upon arrival. I suggest that the introduction distinguish more precisely between "verifying directly with the flight video" and "judging completion using historical memory," so that readers do not take the difference to be whether historical information is used at all.