Narrative:

I instructed the handoff assist to amend the flight plan for air carrier X. Seeing aluri as the next fix; and never hearing of that fix; I assumed that it was well in ZNY's airspace. Apparently aleri is before lucti in ZMA's airspace; causing the flight plan to back track; resulting in an error within oceanic procedures (atops). I should have gone to the end of the airway to tie in the route of flight at the correct fix instead of assuming or called ZMA to confirm. Fdio; eram; erid; and/or atops (fligh plan processing softwares) should provide notification alerting the controller that the route entered was in error is back tracking on itself.

Google
 

Original NASA ASRS Text

Title: ZSU ARTCC Controller reported entering an improper routing in the ERAM for an aircraft.

Narrative: I instructed the handoff assist to amend the flight plan for Air Carrier X. Seeing ALURI as the next fix; and never hearing of that fix; I assumed that it was well in ZNY's airspace. Apparently ALERI is before LUCTI in ZMA's airspace; causing the flight plan to back track; resulting in an error within Oceanic Procedures (ATOPS). I should have gone to the end of the airway to tie in the route of flight at the correct fix instead of assuming or called ZMA to confirm. FDIO; ERAM; ERID; AND/OR ATOPS (FLIGH PLAN PROCESSING SOFTWARES) should provide notification alerting the controller that the route entered was in error is back tracking on itself.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.