{"id":"7de96a0f-950f-4315-8b47-961df353f5f7","arxiv_id":"1908.08651","paper_version":1,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":4.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":10,"one_line_summary":"The paper presents a Python-based discrete event simulator (TUS) that flags conflicts in preplanned eVTOL flight trajectories and reports flight duration, demonstrated on two small synthetic scenarios.","lead":"This paper introduces TUS, a discrete event simulator that checks whether preplanned eVTOL flight trajectories in an urban airspace maintain minimum separation and records how long the flights take. It is a first-step tool for testing UAM trajectory safety, but it is not validated against real operations or existing simulators.","discovery_kind":"extension","skeptic_critique":{"model":"deepseek-v4-flash","headline":"The safety predicate is internally contradictory: §4.5.2 applies longitudinal separation regardless of altitude, while §4.2/§4.3.3 allow vertical separation to substitute; until this is resolved the central safety output is not well-defined.","rationale":"The reader and I converge on the same load-bearing concern: the separation logic is stated two ways, and the safety output is central. I would keep the reader's CONDITIONAL verdict; the issue is a fixable specification ambiguity, not a reason to reject the simulation idea. I do not fully follow the reader's use of Experiment II as the demonstration, because the proposed alternative waypoint [4,2,1200] changes the horizontal route in addition to altitude, so even a horizontal-only separation rule could clear that scenario. The cleaner disambiguation is the co-located same-track test described above. A secondary gap is that no code or validation is provided, so the test cannot currently be run independently by a reader; that reinforces the conditional verdict but is not itself a separate technical flaw in the argument.","tokens_in":30653,"tokens_out":9698,"duration_ms":89622,"concrete_test":"Run a minimal two-vehicle scenario in TUS: vehicle A at (0,0,1000 ft) and vehicle B at (0,0,1200 ft), both piloted, with the same horizontal trajectory (0,0)->(10,0), same speed, and same departure time, so they are always horizontally co-located with 200 ft vertical separation. Call `check_conflict`; if it flags a conflict, the §4.5.2 rule (longitudinal separation regardless of altitude) is implemented; if it does not, vertical separation substitutes and §4.2/§4.3.3 is implemented. This directly fixes which conflict predicate the paper's safety output uses.","verdict_should_be":"UNCHANGED","load_bearing_attack":"Section 4.2, Principle 3 states that 'two eVTOL vehicles are allowed to fly into the horizontal position if a proper vertical separation (z) is applied,' and §4.3.3 applies the longitudinal requirement only 'when the minimum vertical separation is not followed.' Section 4.5.2 states the opposite: the longitudinal separation requirement 'is applied regardless of the altitude.' The described conflict computation (`check_conflict`, `euclidian_distance_sep`) uses only horizontal positions and `hsep`; no `vsep` or `z` enters the Euclidean-distance calculation. Under the §4.5.2 reading, vertical separation and the four flight levels have no effect on safety; under the §4.2 reading they do. Since the headline output is a binary safe/unsafe verdict, the same input can receive different verdicts depending on which sentence is implemented. This is an internal inconsistency in the central safety predicate, not a disagreement with external separation standards.","agreement_with_reader":"partial"},"referee_report":{"model":"deepseek-v4-flash","summary":"The paper introduces TUS, a discrete-event simulator for Trajectory-Based Urban Air Mobility (UAM) operations. The simulator takes as input a set of eVTOL vehicles with predefined trajectories and outputs a binary safety verdict (conflict-free or not) and the total flight duration. The authors describe the assumptions on airspace, mission, and vehicle performance, present a class-level implementation (UAM_manager, eVTOL, VideoMaker), and illustrate the tool with two experiments: a five-vehicle scenario with direct flights (Experiment I) and a two-vehicle crossing scenario where an altitude-based waypoint is proposed as a conflict-resolution measure (Experiment II). The stated main contribution is to provide a simulated environment for testing and measuring the effectiveness (e.g., flight duration) of trajectories planned for eVTOL vehicles.","tokens_in":30886,"tokens_out":3527,"duration_ms":33981,"significance":"If the separation semantics are made consistent and the simulator is validated against known conflict geometries, TUS could serve as a useful lightweight testbed for early UAM trajectory-planning research. The paper is explicit about its assumptions, the movement model is simple and transparent, and the two experiments demonstrate that the code executes as described. However, the central safety predicate is currently ill-defined because of a direct contradiction between the horizontal/vertical separation rule stated in Section 4.2 and the rule stated in Section 4.5.2, and this contradiction affects the interpretation of Experiment II. No validation against analytic results, real data, or a reference simulator is provided, which limits confidence in the safety outputs even after the contradiction is resolved.","major_comments":[{"comment":"The conflict-detection rule is internally contradictory. Section 4.2, Principle 3, states that two eVTOL vehicles are allowed to fly into the same horizontal position if a proper vertical separation (z) is applied, and Section 4.3.3 states that the longitudinal separation requirement applies 'when the minimum vertical separation is not followed.' In contrast, Section 4.5.2 states that the longitudinal separation requirement 'is applied regardless of the altitude.' The described implementation of `euclidian_distance_sep` and `check_conflict` uses only horizontal positions and `hsep`, with no `vsep` or `z` entering the Euclidean-distance calculation. Under the Section 4.5.2 reading, vertical separation and the four flight levels have no effect on safety; under the Section 4.2 reading, they do. Because the safety verdict is the central output, this contradiction must be resolved and the implemented rule stated unambiguously.","section":"§4.2 vs §4.5.2"},{"comment":"The reported conflict-resolution result depends directly on the unresolved separation rule. The alternative trajectory assigns eVTOL vehicle 1 an additional waypoint at [4, 2, 1200], and the paper states that 'TUS did not detect any conflict once the vertical and horizontal separation standards were respected.' If the implementation actually follows Section 4.5.2 (longitudinal separation regardless of altitude), then the altitude component of the waypoint cannot affect the horizontal separation check, and the original conflict would persist. The experiment therefore does not demonstrate a valid conflict-resolution solution until the separation semantics are fixed and the implementation is shown to be consistent with them.","section":"§7 (Experiment II)"},{"comment":"The speed used for stepping the simulation is inconsistent with the stated cruise speed. Section 4.3.3 gives a speed interval of 130–170 kts, while Section 4.5.2 first states a constant en-route airspeed of 170 mph and then computes the per-second step as 0.0417 NM, which corresponds to 150 kts (170 mph is approximately 147.7 kts, not 150 kts). Since the flight-duration output is presented as a measure of trajectory effectiveness, the actual speed used to convert ticks into distance must be stated consistently and used in the `step` method; otherwise reported durations such as 1084 s in Experiment I are not reproducible.","section":"§4.3.3 and §4.5.2"},{"comment":"The paper does not validate the simulator's outputs against any reference, such as real traffic data, analytically known conflict geometries, or an established simulator. The two experiments are demonstrations of the code paths rather than correctness tests. Because the tool is intended to decide whether trajectories are safe and to measure their efficiency, at least one experiment with a conflict geometry whose outcome is known analytically (e.g., two aircraft with exactly the minimum separation) is needed to support the claim that the output actually describes the safety of the supplied trajectories.","section":"§5–§7"}],"minor_comments":[{"comment":"Listing 2 contains `u a m.add_ev_list` (with spaces) instead of `uam.add_ev_list`, and Listing 3 has a missing closing parenthesis in `uam.add_ev_list([ev1, ev2)`. These typos should be corrected.","section":"Listings 2 and 3"},{"comment":"The abstract states 'One import outcome' instead of 'One important outcome.'","section":"Abstract"},{"comment":"The sentence 'The main contribution of this simulation tool is to provide a simulated environment for testing and measuring the effectiveness (e.g., flight duration) of trajectories planned for eVTOL vehicles' appears twice in Section 4.1.","section":"§4.1"},{"comment":"Figure 4 is referenced as a 'Table of Cruising Levels'; the caption should say 'Figure' rather than 'Table.'","section":"Figure 4"},{"comment":"The sentence 'Finally, the eVTOL vehicles that reach the final point of its trajectory' has a subject–verb agreement error ('vehicles ... its').","section":"§4.5.2"},{"comment":"The description of `euclidian_distance_sep` says the returned distance is 4.5 NM for a Euclidean distance of 5 NM and minimum separations 0.25 and 0.5; however, the text subtracts the maximum separation, which is consistent with the rule, but this should be clarified as a deliberate conservative choice rather than a formula for the physical distance.","section":"§4.5.1"}],"recommendation":"major_revision","confidential_remarks":"The paper is more of a technical report than a mature research contribution: there is no code repository link, no validation, and the central safety predicate is contradictory. The contradiction is fixable, but the authors must also decide whether the contribution is the simulator itself or the simulation results; if the former, the paper needs reproducible code and a precise specification of the separation rule. I would not recommend reject, as the simulator concept is reasonable and the issues are addressable within the manuscript's scope."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Quick take: this is a straightforward Python DES for checking whether given UAM trajectories keep minimum separation and measuring flight duration. The architecture—manager object, eVTOL vehicles, video renderer—is conventional, and the numbers are sensibly sourced from Uber, NASA, and Bosson and Lauderdale. The paper is clearly written about its assumptions, and the code snippets suggest a working toy. But the central safety rule is self-contradictory across sections, and there is zero validation against real data, analytic results, or a reference simulator. As written, the safe/unsafe output is not well-defined.\n\nWhat is actually new: not much scientifically. The contribution is a parameterized implementation that combines known DES movement, Euclidean separation checks, and UAM-specific separation values. If the code were released, it could serve as a didactic baseline for students. The paper does a decent job of laying out assumptions: flight levels at 1000–1600 ft, 0.25/0.5 NM horizontal separation, 200 ft vertical separation, turn rates, and climb rates all traced to Uber or [67]. The two experiments are simple demonstrations, not validation: they run the simulator, show a conflict, and then show a waypoint fix.\n\nThe soft spot is not a detail. Section 4.2 Principle 3 and §4.3.3 say vertical separation can substitute for horizontal separation—two aircraft can occupy the same x,y if z is respected. Section 4.5.2 says the longitudinal (horizontal) separation applies regardless of altitude, and the described check_conflict uses Euclidean distance in x,y with hsep only, never vsep. Under the second reading, flight levels and vertical separation have no effect on safety, and Experiment II's altitude-based waypoint would not resolve the conflict as claimed. The authors never reconcile this, and since the headline output is a binary safe/unsafe, the same scenario can yield opposite verdicts depending on which sentence is implemented. That is a load-bearing flaw.\n\nAlso missing: no public code, no comparison to BlueSky, TAAM, or Bosson and Lauderdale, and no sensitivity analysis. The paper claims to be a foundation for trajectory planning research, but without validation or a released artifact that claim is unbacked.\n\nWho is this for? Someone looking for a minimal, understandable UAM trajectory-checking toy to build on, and who is willing to read past the contradiction. As a scientific contribution it is thin; as a software tool paper it could be made useful if fixed.\n\nMy recommendation: send it to review only if the venue handles tools/simulation papers and the authors can be held to fixing the separation rule, adding validation, and releasing code. As is, I would not rely on its safety output.","headline":"A clear but unvalidated UAM simulator whose central safety rule contradicts itself, making the safe/unsafe output ill-defined.","tokens_in":31443,"tokens_out":3825,"would_cite":false,"duration_ms":36683,"reading_group":"maybe","serious_thinker":"no","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"The Trajectory-Based UAM Operations Simulator (TUS) is a discrete-event environment that tests whether planned eVTOL trajectories respect minimum separation and measures how long they take.","keywords":["Urban Air Mobility","eVTOL","Trajectory-Based Operations","Discrete Event Simulation","Conflict detection","Separation standards","Unmanned Aircraft System","Safety"],"falsifier":"Build a scenario with two eVTOL vehicles crossing the same $(x,y)$ point at the same tick on different flight levels, say $1000$ ft and $1200$ ft. Principle 3 of Section 4.2 says no conflict should be reported because vertical separation holds; the rule stated in Section 4.5.2 says the horizontal separation applies regardless of altitude and a conflict should be reported. Running this scenario in TUS, or reading the conflict-check code directly, settles which rule the safety output actually implements.","tokens_in":30475,"feed_emoji":"✈️","tokens_out":6414,"duration_ms":59735,"temperature":0.7,"pith_summary":"This paper presents TUS, a discrete-event simulation tool for Urban Air Mobility operations in which electric vertical take-off and landing (eVTOL) vehicles follow pre-planned trajectories. The simulator takes as input a set of vehicles, their origins and destinations, and their trajectories, and returns whether those trajectories are conflict-free under minimum-separation rules and how long the whole operation takes. The authors' stated goal is to give trajectory planners a testbed for measuring safety and effectiveness, especially flight duration, before a trajectory plan is used in flight. Early UAM operations are expected to be dense and to use reduced separation standards, so a tool that can compare candidate trajectories on both safety and duration is a step toward practical trajectory planning.","feed_headline":"TUS simulator tells planners if eVTOL routes are safe","feed_subtitle":"A discrete-event model flags conflicts and reports flight duration, letting planners test routes before takeoff.","key_machinery":"The load-bearing mechanism is the pair of classes UAM_manager and eVTOL. UAM_manager holds the set of vehicles, advances the simulation in one-second ticks, and decides safety with a conflict check that computes Euclidean distance between pairs of vehicles and subtracts the largest applicable minimum separation. The trajectory of each vehicle is a tuple $t = [(x_1,y_1,z_1,s_1),\\ldots,(x_n,y_n,z_n,s_n)]$ of longitudinal coordinates, altitude, and speed. The separation design is a cylinder: horizontal separation of $0.25$ NM for piloted and $0.5$ NM for autonomous aircraft, vertical separation of $200$ ft, and four flight levels tied to heading. TUS also includes a VideoMaker class that renders each second of movement as scatter-plot frames, giving a visual check of the trajectories.","core_discovery":"On its own terms, the paper's contribution is the Trajectory-Based UAM Operations Simulator (TUS): a Discrete Event Simulation environment that models multiple eVTOL vehicles, piloted, remotely piloted, and self-piloted, moving one second at a time along fixed trajectories through a $30\\ \\mathrm{NM} \\times 30\\ \\mathrm{NM}$ urban airspace with cruise flight levels at $1000$, $1200$, $1400$, and $1600$ ft. Each simulation tick moves a vehicle by $0.0417$ NM and logs its position; a conflict check compares pairwise distances against each vehicle's minimum horizontal separation ($0.25$ NM for piloted, $0.5$ NM otherwise) and vertical separation ($200$ ft). When a conflict is found the simulation halts and reports the conflicting vehicles; otherwise it returns the total time needed to deliver all flights. The main claimed value is an environment for testing and measuring the effectiveness, e.g., flight duration, of trajectories planned for eVTOL vehicles, in a way complementary to existing air traffic simulation tools.","pith_inferences":["If the implementation follows the statement in Section 4.5.2 that longitudinal separation applies regardless of altitude, then altitude and flight levels never influence conflict detection, which would make Experiment II's altitude-based fix (an extra point at 1200 ft) ineffective as described; a corrected model would compare vertical separation before applying horizontal separation.","A natural extension the paper does not pursue is to report the severity or duration of separation violations rather than a binary conflict flag, which would help rank unsafe trajectories.","The one-second tick with a fixed step length implies position updates without an explicit acceleration or climb model inside a tick, so the simulator's fidelity is kinematic; testing trajectories near the maximum turn rate of $7.2$ degrees per second could expose whether that simplification matters."],"forward_implications":["TUS gives a trajectory planner a go/no-go verdict: if any pair of vehicles violates separation, the simulation stops and names the conflicting vehicles.","Because the output includes the elapsed time to deliver all flights, planners can compare candidate trajectories on duration, not just safety.","The tool is scoped to early UAM maturity levels (UML 1-4) and a single urban area, with hundreds or thousands of simultaneous vehicles out of scope.","The same simulator can be used to test the impact of different separation standards, which the authors list as a future direction."],"supporting_citations":[{"why":"Supplies the eVTOL vehicle requirements and mission segments, including speed, climb/descent rates, and flight levels, that define the simulation's vehicle model.","marker":"[39]"},{"why":"Prior simulations of reduced separations in UAM environments that ground the $0.25$ NM minimum horizontal separation.","marker":"[67]"},{"why":"Air traffic control assessment for UAM and unmanned systems that justifies assuming reduced IFR separation is reasonable.","marker":"[54]"},{"why":"Analysis of scaling constraints for UAM operations, used as the basis for reduced-separation 4D trajectory operations.","marker":"[55]"},{"why":"The eVTOL service concept that supplies cruise speeds and altitudes as well as mission assumptions.","marker":"[9]"},{"why":"Airspace integration concepts and principles for UAM that define the operational constraints and hazard scope.","marker":"[24]"},{"why":"Rules of the air with cruise level conventions, adapted into the heading-based flight levels used by TUS.","marker":"[75]"},{"why":"An open air traffic simulator whose open-data approach inspires the TUS implementation structure.","marker":"[30]"}],"fun_headline_variants":["Simulator flags eVTOL route conflicts","TUS simulation predicts eVTOL safety","Conflict-checker for eVTOL flight plans","Desktop testbed for eVTOL trajectory safety","Pre-flight safety check for eVTOL paths"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The safety verdict rests entirely on a single, consistently implemented separation rule, but the paper gives two conflicting statements of that rule: one says vertical separation alone can let two eVTOL vehicles share the same horizontal position, while another says the horizontal separation requirement applies regardless of altitude.","fun_headline_variants_meta":{"raw":{"variants":["Simulator flags eVTOL route conflicts","TUS simulation predicts eVTOL safety","Conflict-checker for eVTOL flight plans","Desktop testbed for eVTOL trajectory safety","Pre-flight safety check for eVTOL paths"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000707,"raw_usage":{"total_tokens":3242,"prompt_tokens":1061,"completion_tokens":2181,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":677,"completion_tokens_details":{"reasoning_tokens":2112}},"tokens_in":677,"tokens_out":2181,"duration_ms":16000,"temperature":1.0,"reasoning_tokens":2112,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-14T11:33:41.461809+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"Build a scenario with two eVTOL vehicles crossing the same $(x,y)$ point at the same tick on different flight levels, say $1000$ ft and $1200$ ft. Principle 3 of Section 4.2 says no conflict should be reported because vertical separation holds; the rule stated in Section 4.5.2 says the horizontal separation applies regardless of altitude and a conflict should be reported. Running this scenario in TUS, or reading the conflict-check code directly, settles which rule the safety output actually implements.","supporting_citations":[{"cited_title":"eVTOL Vehicle Requirements and Missions","cited_arxiv_id":null,"evidence_quote":"Supplies the eVTOL vehicle requirements and mission segments, including speed, climb/descent rates, and flight levels, that define the simulation's vehicle model."},{"cited_title":"Simulation evaluations of an autonomous urban air mobility network management and separation service","cited_arxiv_id":null,"evidence_quote":"Prior simulations of reduced separations in UAM environments that ground the $0.25$ NM minimum horizontal separation."},{"cited_title":"Assessment of air traffic control for urban air mobility and unmanned systems","cited_arxiv_id":null,"evidence_quote":"Air traffic control assessment for UAM and unmanned systems that justifies assuming reduced IFR separation is reasonable."},{"cited_title":"Scaling constraints for urban air mobility operations: Air traffic control, ground infrastructure, and noise","cited_arxiv_id":null,"evidence_quote":"Analysis of scaling constraints for UAM operations, used as the basis for reduced-separation 4D trajectory operations."},{"cited_title":"Fast-Forwarding to a Future of On-Demand Urban Air Transportation","cited_arxiv_id":null,"evidence_quote":"The eVTOL service concept that supplies cruise speeds and altitudes as well as mission assumptions."},{"cited_title":"Urban air mobility airspace integration concepts and considerations","cited_arxiv_id":null,"evidence_quote":"Airspace integration concepts and principles for UAM that define the operational constraints and hazard scope."},{"cited_title":"Rules of air - annex 2, 2005","cited_arxiv_id":null,"evidence_quote":"Rules of the air with cruise level conventions, adapted into the heading-based flight levels used by TUS."},{"cited_title":"Bluesky ATC simulator project: an open data and open source approach","cited_arxiv_id":null,"evidence_quote":"An open air traffic simulator whose open-data approach inspires the TUS implementation structure."}],"review_version":1}