Narrative:

I received a late transfer at time XX21Z on air carrier X estimating the fir between tokyo center and oak oceanic at time XX29Z FL350, at the same time I received another transfer that was very confusing on an air carrier exactly one hour later. In my rush to activate the flight plan on air carrier X, I made a one hour error on the activation of air carrier X time. At XX34Z (approximately) air carrier Y requested climb from FL330 to FL350. I checked the strips and the odaps scope and determined that separation existed when in fact it did not. In actuality I only had 4 min separation between air carrier X and Y. I issued the clearance at XX37Z to air carrier Y to climb to FL350. It was discovered when air carrier X progressed 170E. I hour early, air carrier X did not report the fix, had he done so this error would not of happened. Contributing factors were: a late transfer from tokyo 9 min from the fix (LOA requires at least 30 min advance transfer from the fix). In the same transfer call, tokyo confused the issue with another air carrier transfer, it was a very confusing call. Air carrier X did not report the fix. This one issue would of stopped this error from occurring. It is not required to report the fix. It was at one time, but the FAA decided it was unnecessary. There is an ucr filed by the controllers on this issue, we think this should be a compulsory reporting point.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR Y CLB TO OCCUPIED ALT HAD LTSS FROM ACR X UNDER OCEANIC CTL. SYS ERROR.

Narrative: I RECEIVED A LATE TRANSFER AT TIME XX21Z ON ACR X ESTIMATING THE FIR BTWN TOKYO CTR AND OAK OCEANIC AT TIME XX29Z FL350, AT THE SAME TIME I RECEIVED ANOTHER TRANSFER THAT WAS VERY CONFUSING ON AN ACR EXACTLY ONE HR LATER. IN MY RUSH TO ACTIVATE THE FLT PLAN ON ACR X, I MADE A ONE HR ERROR ON THE ACTIVATION OF ACR X TIME. AT XX34Z (APPROX) ACR Y REQUESTED CLB FROM FL330 TO FL350. I CHKED THE STRIPS AND THE ODAPS SCOPE AND DETERMINED THAT SEPARATION EXISTED WHEN IN FACT IT DID NOT. IN ACTUALITY I ONLY HAD 4 MIN SEPARATION BTWN ACR X AND Y. I ISSUED THE CLRNC AT XX37Z TO ACR Y TO CLB TO FL350. IT WAS DISCOVERED WHEN ACR X PROGRESSED 170E. I HR EARLY, ACR X DID NOT RPT THE FIX, HAD HE DONE SO THIS ERROR WOULD NOT OF HAPPENED. CONTRIBUTING FACTORS WERE: A LATE TRANSFER FROM TOKYO 9 MIN FROM THE FIX (LOA REQUIRES AT LEAST 30 MIN ADVANCE TRANSFER FROM THE FIX). IN THE SAME TRANSFER CALL, TOKYO CONFUSED THE ISSUE WITH ANOTHER ACR TRANSFER, IT WAS A VERY CONFUSING CALL. ACR X DID NOT RPT THE FIX. THIS ONE ISSUE WOULD OF STOPPED THIS ERROR FROM OCCURRING. IT IS NOT REQUIRED TO RPT THE FIX. IT WAS AT ONE TIME, BUT THE FAA DECIDED IT WAS UNNECESSARY. THERE IS AN UCR FILED BY THE CTLRS ON THIS ISSUE, WE THINK THIS SHOULD BE A COMPULSORY RPTING POINT.

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.