Narrative:

The challenger had a filed IFR flight plan, but was not transferred from pkacc (in russia) to zan. The challenger contacted ATC approximately 130 NM west of enm on his filed route of flight at FL370. I had 2 KC135 aircraft on a mission that were due to recover IFR to eilson airport. The KC135's usually request FL370-FL410 on their recovery. The rtes of flight would have been a confliction if the KC135's had called before the challenger contacted me on his own. There was not a loss of separation purely because of the timing of the events. There is a serious need for better communications and transfer procedures between the cis (russia) and the united states. This is not the first time transfer has not been made.

Related reports:

Google
 

Original NASA ASRS Text

Title: CTLR AT ZAN CLAIMS THAT THEIR RUSSIAN FACILITY BOUNDARY CTLRS DO NOT ALWAYS FORWARD FLT PLAN DATA FOR INCOMING FLTS TO ZAN AIRSPACE. RPTR CONTENDS THAT THIS IS AN ONGOING PROB.

Narrative: THE CHALLENGER HAD A FILED IFR FLT PLAN, BUT WAS NOT TRANSFERRED FROM PKACC (IN RUSSIA) TO ZAN. THE CHALLENGER CONTACTED ATC APPROX 130 NM W OF ENM ON HIS FILED RTE OF FLT AT FL370. I HAD 2 KC135 ACFT ON A MISSION THAT WERE DUE TO RECOVER IFR TO EILSON ARPT. THE KC135'S USUALLY REQUEST FL370-FL410 ON THEIR RECOVERY. THE RTES OF FLT WOULD HAVE BEEN A CONFLICTION IF THE KC135'S HAD CALLED BEFORE THE CHALLENGER CONTACTED ME ON HIS OWN. THERE WAS NOT A LOSS OF SEPARATION PURELY BECAUSE OF THE TIMING OF THE EVENTS. THERE IS A SERIOUS NEED FOR BETTER COMS AND TRANSFER PROCS BTWN THE CIS (RUSSIA) AND THE UNITED STATES. THIS IS NOT THE FIRST TIME TRANSFER HAS NOT BEEN MADE.

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.