INSERT, DELETE AND COLLAPSE WAYPOINTS WITHOUT LOSING INTENT
A local route change needs two unambiguous boundaries: where the new path starts and where it continues. First identify the intended position in the leg sequence. Then decide whether the task inserts a new point, replaces the current TO point, removes one fix or collapses a whole intervening segment. These operations can produce similar names in different orders, with very different paths between them. [66, PDF pp. 319-327,334]
1. Insert through a known revise point. Use the selected waypoint's LAT REV and NEXT WPT when adding the next intended point. Read the revised sequence to confirm that the new identifier occupies the intended position. If using direct F-PLN insertion, inspect how the receiving row shifts. Do not assume that selecting the row beside a name always means adding after that name. [66, PDF pp. 319-327,334]
2. Check the new connection. A newly inserted point can be followed by a discontinuity because no onward connection has yet been defined. Establish the intended continuation and create only that connection. Inserting a geographically plausible fix between two others does not establish that both connecting legs match the clearance or the procedure's intended course geometry. [66, PDF pp. 319-327,334]
3. Delete a single fix deliberately. Put CLR into the intended waypoint field and inspect the resulting temporary plan. Read the neighbour fixes and any gap or new direct leg. Include the deleted fix's altitude, speed and time restrictions in the review: removing its row can remove those associated requirements from the coded plan, even when a corresponding operational restriction still needs separate management. [66, PDF pp. 319-327,334]
4. Collapse a segment using its intended rejoin. For several unwanted intermediate fixes, the source offers NEXT WPT/re-entry methods that can string to a later existing fix. Identify the correct occurrence if the same name appears more than once. Inspect which intermediate rows disappeared and what remained after the rejoin. A repeated identifier can represent a later return to the same place, not necessarily a duplicate to eliminate. [66, PDF pp. 319-327,334]
5. Distinguish a future change from a present-position shortcut. Editing the route after a named fix does not necessarily command the immediate direct leg from the aircraft's current position. Use DIR TO for that particular cleared task and inspect its consequences separately. Complete a normal route edit with INSERT, active-sequence inspection and a review of any changed downstream predictions. [66, PDF pp. 319-327,334]