Narrative:

I was working the in-flight position at grand forks AFSS. I received a call from air carrier X at minot, nd, requesting clearance to minneapolis. I intended to call minot approach to request the clearance but inadvertently dialed grand forks approach. In our communication we both missed clues and procedures that would have prevented the error. The communication was hampered by a handset or line that made it harder to understand what was said. I was working a midnight shift and that may have contributed. On the initial contact the controller identify the facility as grand forks approach. I assumed I was in contact with minot approach and only heard approach. I failed to identify the departure airport as required but identify the departure runway as 13. The controller at grand forks approach failed to recognize that runway 13 is not one of the runways at grand forks. I idented the aircraft as air carrier X. Approach advised that they had a flight plan on air carrier Y but not on air carrier X. I verified the aircraft callsign as air carrier X and approach assumed they changed the callsign and issued the clearance to air carrier X from the flight plan for air carrier Y. In issuing the clearance the controller failed to clear from the departure airport as required which would have identify the error. I failed to recognize the approach control frequency, issued as grand forks, and the tower hours stated by approach were also grand forks. I issued the clearance to air carrier X assuming it was from minot approach. The clearance was to climb and maintain 3000' which was below the minimum vectoring altitude. The error was identify when air carrier X called minot approach after departure. Minot approach called me to ask who I got the clearance from. I told them I got it from them. They told me it wasn't issued by them. That is when I realized what happened. If the proper procedures were followed by identify the departure airport in the request for clearance and in issuing the clearance the error would have been prevented. Also more attention to the clues in the communications would have also prevented the error.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR WAS INADVERTENTLY RELEASED FROM THE WRONG ARPT AND ISSUED AN ALT BELOW THE MOCA. ACFT CAME IN CLOSE PROX TO AN ANTENNA.

Narrative: I WAS WORKING THE INFLT POS AT GRAND FORKS AFSS. I RECEIVED A CALL FROM ACR X AT MINOT, ND, REQUESTING CLRNC TO MINNEAPOLIS. I INTENDED TO CALL MINOT APCH TO REQUEST THE CLRNC BUT INADVERTENTLY DIALED GRAND FORKS APCH. IN OUR COM WE BOTH MISSED CLUES AND PROCS THAT WOULD HAVE PREVENTED THE ERROR. THE COM WAS HAMPERED BY A HANDSET OR LINE THAT MADE IT HARDER TO UNDERSTAND WHAT WAS SAID. I WAS WORKING A MIDNIGHT SHIFT AND THAT MAY HAVE CONTRIBUTED. ON THE INITIAL CONTACT THE CTLR IDENT THE FAC AS GRAND FORKS APCH. I ASSUMED I WAS IN CONTACT WITH MINOT APCH AND ONLY HEARD APCH. I FAILED TO IDENT THE DEP ARPT AS REQUIRED BUT IDENT THE DEP RWY AS 13. THE CTLR AT GRAND FORKS APCH FAILED TO RECOGNIZE THAT RWY 13 IS NOT ONE OF THE RWYS AT GRAND FORKS. I IDENTED THE ACFT AS ACR X. APCH ADVISED THAT THEY HAD A FLT PLAN ON ACR Y BUT NOT ON ACR X. I VERIFIED THE ACFT CALLSIGN AS ACR X AND APCH ASSUMED THEY CHANGED THE CALLSIGN AND ISSUED THE CLRNC TO ACR X FROM THE FLT PLAN FOR ACR Y. IN ISSUING THE CLRNC THE CTLR FAILED TO CLR FROM THE DEP ARPT AS REQUIRED WHICH WOULD HAVE IDENT THE ERROR. I FAILED TO RECOGNIZE THE APCH CTL FREQ, ISSUED AS GRAND FORKS, AND THE TWR HRS STATED BY APCH WERE ALSO GRAND FORKS. I ISSUED THE CLRNC TO ACR X ASSUMING IT WAS FROM MINOT APCH. THE CLRNC WAS TO CLB AND MAINTAIN 3000' WHICH WAS BELOW THE MINIMUM VECTORING ALT. THE ERROR WAS IDENT WHEN ACR X CALLED MINOT APCH AFTER DEP. MINOT APCH CALLED ME TO ASK WHO I GOT THE CLRNC FROM. I TOLD THEM I GOT IT FROM THEM. THEY TOLD ME IT WASN'T ISSUED BY THEM. THAT IS WHEN I REALIZED WHAT HAPPENED. IF THE PROPER PROCS WERE FOLLOWED BY IDENT THE DEP ARPT IN THE REQUEST FOR CLRNC AND IN ISSUING THE CLRNC THE ERROR WOULD HAVE BEEN PREVENTED. ALSO MORE ATTN TO THE CLUES IN THE COMS WOULD HAVE ALSO PREVENTED THE ERROR.

Data retrieved from NASA's ASRS site as of July 2007 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.