Narrative:

I was training in the offshore central and east positions D side. Traffic was moderate with very little weather in the area with minimal impact. Aircraft X called requesting departure clearance off [an oil rig] to ZZZ. Trainee cleared aircraft via 'as filed' climbing to 3000. The trainee started track of the aircraft at the lat/long filed. Shortly after aircraft Y called looking for a clearance to ZZZ. The trainee ran a route line on aircraft Y to see his departure position on the scope. This is a common practice to run a route line to see the departure point fast. The trainee cleared the aircraft via 'as filed' climbing to 3000. After the clearance was issued and read back correctly; the trainee got off the line and started a track for the aircraft at the coordinates filed. The track started 115 miles south of what the route line showed where the aircraft should depart and approximately 11 miles near the track of the previously cleared aircraft. I noticed this right away and made sure he checked the cid's (computer identification) of the aircraft as they were similar xyx and xyz; maybe he mistyped. So he ran a route line on xyx which showed him 115 miles north; he retyped the track at the appropriate coordinates and again it tagged up 115 miles south. So; I had him run a route line on xyzand it showed him 115 miles north and again restarted the track at the appropriate coordinates and it tracked up 115 miles south. Immediately the computer error is recognized and I; the trainer; immediately made a call to [company] operations to cancel the clearance. The speed dial line listed at both offshore and ocean positions did not work and we were unable to reach [company] operations timely enough as the aircraft immediately departed both within 11 miles of each other. Both aircraft were radar identified and proceeded on course without further incident. This appears to be computer/systematic issue as I have never seen a route entry not correlate with the appropriate filed coordinates as they did. These [aircraft] depart every day; all day long without ever seeing a repeat of this prior; I am unsure if there is a recommended change needed other than fixing the issue in our system that caused the difference in route displayed and what was filed. The [company] operations line needs to be checked to ensure it is updated with the appropriate dial number or it needs to be fixed so we can immediately reach [company] operations when needed.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZHU Center controllers reported a computer error related to aircraft routings.

Narrative: I was training in the offshore Central and East positions D side. Traffic was moderate with very little weather in the area with minimal impact. Aircraft X called requesting departure clearance off [an oil rig] to ZZZ. Trainee cleared aircraft via 'as filed' climbing to 3000. The trainee started track of the aircraft at the lat/long filed. Shortly after Aircraft Y called looking for a clearance to ZZZ. The trainee ran a route line on Aircraft Y to see his departure position on the scope. This is a common practice to run a route line to see the departure point fast. The trainee cleared the aircraft via 'as filed' climbing to 3000. After the clearance was issued and read back correctly; the trainee got off the line and started a track for the aircraft at the coordinates filed. The track started 115 miles south of what the route line showed where the aircraft should depart and approximately 11 miles near the track of the previously cleared aircraft. I noticed this right away and made sure he checked the CID's (Computer Identification) of the aircraft as they were similar XYX and XYZ; maybe he mistyped. So he ran a route line on XYX which showed him 115 miles north; he retyped the track at the appropriate coordinates and again it tagged up 115 miles south. So; I had him run a route line on XYZand it showed him 115 miles north and again restarted the track at the appropriate coordinates and it tracked up 115 miles south. Immediately the computer error is recognized and I; the trainer; immediately made a call to [Company] operations to cancel the clearance. The speed dial line listed at both offshore and ocean positions did not work and we were unable to reach [Company] operations timely enough as the aircraft immediately departed both within 11 miles of each other. Both aircraft were radar identified and proceeded on course without further incident. This appears to be computer/systematic issue as I have never seen a route entry not correlate with the appropriate filed coordinates as they did. These [aircraft] depart every day; all day long without ever seeing a repeat of this prior; I am unsure if there is a recommended change needed other than fixing the issue in our system that caused the difference in route displayed and what was filed. The [Company] operations line needs to be checked to ensure it is updated with the appropriate dial number or it needs to be fixed so we can immediately reach [Company] operations when needed.

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.