Narrative:

Oakland flight service call via ringline to request clearance for aircraft X from 'rawlings' airport to [a denver area airport] and would need three minutes on the ground. I found no flight plan in the system; flight service said he'd call back. A few minutes later he called; just as the flight plan populated in edst; from rwl; rawlins airport via direct tomsn.TOMSN6.ZZZ. I issued clearance from rawlins to ZZZ; with 'climb and maintain 170; expect FL250 five minutes after departure' and a clearance void time; if not off by XX00 to advise not later that xx+05 of intentions. I don't remember the beacon code offhand.not long afterward I noticed a xxyy code pop up in salt lake center's airspace; climbing and appearing to come towards my sector from worland airport; wrl. Nothing in edst matched an airplane coming from there; but the code matched the present assignment to [last three of previous discussed aircraft]; whose track I had created over rwl to wait for the departure. At this point it occurred to me that somebody might have confused rwl and wrl; just as salt lake initiated handoff and the track over rwl auto-acquired onto the handoff aircraft. At this point I called salt lake to inquire if the aircraft really were aircraft X; and; if so; how he had checked on with the sector. I was told it was [same last three numbers]; he couldn't get denver center on the assigned frequency (132.1; the departure frequency I had assigned for the clearance out of rwl); so he had gone to the salt lake frequency and checked on looking for clearance. The salt lake controller had issued clearance; believing the aircraft to be the usual VFR departure picking up an IFR clearance; and was not aware of any other issues in regard to the aircraft.when the [last three as the previous filed aircraft] checked on I was able to determine that he had received clearance through oakland flight service; but had not been able to reach denver center and so went over to the salt lake center frequency. This pilot is experienced and familiar with the area.the most serious immediate problem is that this aircraft departed believing he was operating IFR out of an airport where the responsible controller had no knowledge of the operation; with all the potential risk that entails. It is clear something in the communication between the pilot and flight service did not meet standards; and that the oakland flight service station had no familiarity with the airports or airspace for which he was requesting authorization for IFR operations.it is difficult to know how address readback errors; to which category these events clearly belong; other than with education. There appears to be a certain deficiency in the flight service station's operation; particularly with respect to familiarity with the area of responsibility.

Related reports:

Google
 

Original NASA ASRS Text

Title: A ZDV Controller and pilot report confusion after the aircraft departs IFR at one airport while the Controller was waiting for the aircraft to depart off of a different airport. The identifiers for the airports are close and caused the confusion.

Narrative: Oakland Flight Service call via ringline to request clearance for Aircraft X from 'Rawlings' airport to [a Denver area airport] and would need three minutes on the ground. I found no flight plan in the system; Flight Service said he'd call back. A few minutes later he called; just as the flight plan populated in EDST; from RWL; Rawlins Airport via direct TOMSN.TOMSN6.ZZZ. I issued clearance from Rawlins to ZZZ; with 'climb and maintain 170; expect FL250 five minutes after departure' and a clearance void time; if not off by XX00 to advise not later that XX+05 of intentions. I don't remember the beacon code offhand.Not long afterward I noticed a XXYY code pop up in Salt Lake Center's airspace; climbing and appearing to come towards my sector from Worland Airport; WRL. Nothing in EDST matched an airplane coming from there; but the code matched the present assignment to [last three of previous discussed aircraft]; whose track I had created over RWL to wait for the departure. At this point it occurred to me that somebody might have confused RWL and WRL; just as Salt Lake initiated handoff and the track over RWL auto-acquired onto the handoff aircraft. At this point I called Salt Lake to inquire if the aircraft really were Aircraft X; and; if so; how he had checked on with the sector. I was told it was [same last three numbers]; he couldn't get Denver Center on the assigned frequency (132.1; the departure frequency I had assigned for the clearance out of RWL); so he had gone to the Salt Lake frequency and checked on looking for clearance. The Salt Lake controller had issued clearance; believing the aircraft to be the usual VFR departure picking up an IFR clearance; and was not aware of any other issues in regard to the aircraft.When the [last three as the previous filed aircraft] checked on I was able to determine that he had received clearance through Oakland Flight Service; but had not been able to reach Denver Center and so went over to the Salt Lake Center frequency. This pilot is experienced and familiar with the area.The most serious immediate problem is that this aircraft departed believing he was operating IFR out of an airport where the responsible controller had no knowledge of the operation; with all the potential risk that entails. It is clear something in the communication between the pilot and Flight Service did not meet standards; and that the Oakland Flight Service Station had no familiarity with the airports or airspace for which he was requesting authorization for IFR operations.It is difficult to know how address readback errors; to which category these events clearly belong; other than with education. There appears to be a certain deficiency in the Flight Service Station's operation; particularly with respect to familiarity with the area of responsibility.

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.