ZUA controller describes a situation where he/she did not look at the complete time update of an air...

Narrative:

When aircraft X departed guam (pgum) I retrieved the flight strips to get a boundary time. Normally one strip prints out with a boundary fix/time. Occasionally multiple strips print out with the last one being the outer boundary time. Multiple strips printed out for aircraft X and I used the last one; which indicated a boundary time of XB42Z. A glitch in the ofdps [offshore flight data processing system] gave out an incorrect time and unusual routing; which I was not aware of. I transferred the aircraft as normal to ZOA. They reported not having the aircraft in their system yet; so I manually transferred aircraft X with the time on the strip. The glitch made the outer fix time off by 1 hour. Aircraft X's actual time at the boundary was XA42Z. After I checked the time I confirmed it was accurate and we transferred the aircraft to commercial radio. Because the last two numbers of the time were the same I did not realize the time was off by one hour (XB42 instead of XA42). After talking with others at ZUA; they advised me that this used to be a much more common problem. I had not personally ever seen this specific scenario; but was told after that the flight plans that file jobss..wrnnr always create this glitch. ZUA is informing everyone of the incident and to be sure all four digits of the boundary times are checked. My only recommendation is that the 'glitch' is found and fixed.

Original NASA ASRS Text

Title: ZUA Controller describes a situation where he/she did not look at the complete time update of an aircraft and missed the fact that it actually showed 1 hour later than he/she thought.

Narrative: When Aircraft X departed Guam (PGUM) I retrieved the flight strips to get a boundary time. Normally one strip prints out with a boundary fix/time. Occasionally multiple strips print out with the last one being the outer boundary time. Multiple strips printed out for Aircraft X and I used the last one; which indicated a boundary time of XB42Z. A glitch in the OFDPS [Offshore Flight Data Processing System] gave out an incorrect time and unusual routing; which I was not aware of. I transferred the aircraft as normal to ZOA. They reported not having the aircraft in their system yet; so I manually transferred Aircraft X with the time on the strip. The glitch made the outer fix time off by 1 hour. Aircraft X's actual time at the boundary was XA42Z. After I checked the time I confirmed it was accurate and we transferred the aircraft to Commercial Radio. Because the last two numbers of the time were the same I did not realize the time was off by one hour (XB42 instead of XA42). After talking with others at ZUA; they advised me that this used to be a much more common problem. I had not personally ever seen this specific scenario; but was told after that the flight plans that file JOBSS..WRNNR always create this glitch. ZUA is informing everyone of the incident and to be sure all four digits of the boundary times are checked. My only recommendation is that the 'glitch' is found and fixed.

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.

Attributes
ACN	1227088
Time
Date	201412
Local Time Of Day	0001-0600
Place
Locale Reference	ZUA.ARTCC
State Reference	GU
Aircraft 1
Make Model Name	Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Oceanic
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 1
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

ZUA controller describes a situation where he/she did not look at the complete time update of an aircraft and missed the fact that it actually showed 1 hour later than he/she thought.