Center Controller working Flight Data position issued a clearance to an aircraft departing a non towered airport and assigned the aircraft an altitude below the Minimum Enroute Altitude. The reporter misidentified the departure airport due to improper use of automation software.

Date: 2024-05 · Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear · Phase: initial_climb

Anomalies: atc-issue-all-types|airspace-violation-all-types|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-cftt-cfit

Synopsis

Center Controller working Flight Data position issued a clearance to an aircraft departing a non towered airport and assigned the aircraft an altitude below the Minimum Enroute Altitude. The reporter misidentified the departure airport due to improper use of automation software.

Narrative

I was working the flight data/clearance delivery position at I90. Aircraft X called on the clearance delivery landline to pick up his IFR flight plan from ZZZ to ZZZ1. I was unsure exactly where the departure airport was but it sounded familiar so I used the STARS automation ' * T ' function for ZZZ which did not work because it was a four character identifier. However; in the past we have just dropped the last character and just used the first 3 characters. So I used the ' T' function for ZZZ; which displayed the airport approximately 10-15 miles east/southeast of ZZZ2. And since he called on our clearance delivery landline; was landing at an airport in our airspace and the ' * t' function showed his departure airport to be in our airspace that checked all the boxes in my mind to confirm he was at that airport. I then coordinated with the satellite sector in which that airport was located to get a release for that aircraft. I issued the instructions to the pilot that the satellite controller gave me which was 'released runway heading (160 degrees) and maintain 3000 ft'. The pilot was issued a 10-minute void time and then we both hung up the line.The pilot departed ZZZ as instructed however; that airport was actually very far west; near San Antonio in ZHU airspace. I was told later by my OM that the MEA in that area was 3900 and that a significant terrain event had occurred. Eventually the ZHU controller was able to reach the aircraft; resolve the issue and the rest of the flight was uneventful. Upon further investigation and adding to the reason why this happened; the '* T' function displayed the airport ZZZ3 that is in our airspace (but not depicted on our video map); not ZZZ.Update our '* T' functionality to be able to depict 4 character airports that are outside our airspace or inhibit any function that would depict any 4 character airport; therefore forcing us to confirm with the pilot where their airport is so we do not make any false assumptions and get lead down the path of 'expectation bias'.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.