|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||atc facility : zoa.artcc|
|Altitude||msl bound lower : 35000|
msl bound upper : 37000
|Controlling Facilities||artcc : zoa.artcc|
|Operator||common carrier : air carrier|
|Make Model Name||Commercial Fixed Wing|
|Operating Under FAR Part||Part 121|
|Flight Phase||climbout : initial|
|Affiliation||government : faa|
|Function||controller : radar|
|Qualification||controller : radar|
controller : non radar
|Experience||controller non radar : 22|
controller radar : 20
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Anomaly||other anomaly other|
|Independent Detector||other controllera|
|Resolutory Action||none taken : anomaly accepted|
|ATC Facility||computer equipment : zoa.artcc|
radar equipment : zoa.artcc
Today; while working OC9; at XA52Z; air carrier X was given a cpdlc clearance to climb from FL360 to FL370. Between XA53-XA59Z; the controller received 3 erroneous nda and fn-cad messages. At XA59Z; the controller reissued a cpdlc clearance for air carrier X to climb from FL360 to FL370. At XB02Z; the controller received a no response from aircraft warning message and issued a HF clearance through sfo comrdo for air carrier X to climb from FL360 to FL370. At XB04Z; the controller received another erroneous fn-cad message. At XB08Z; the controller received a pilot readback (on his original comrdo clearance) from sfo comrdo through HF; stating the aircraft was already level at FL370. (It appears that the aircraft received a cpdlc clearance prior to getting this HF clearance. If so; why did the controller get the warning message that the clearance had not been delivered?) at XB09Z; the controller received a no response from aircraft warning message. At XB12Z; the controller requested that air carrier X confirm altitude. At XB14Z; the controller received a fail nda message. Sometime around XB15Z; the controller sent a message through sfo comrdo to confirm altitude on air carrier X and received a level report at FL370. Additionally at XB21Z; the controller received a contact tyo center message which contained the wrong contact frequencys. Several messages were subsequently sent to the controller pertaining to the wrong contact information being sent. This is a recurring problem; which may cause or contribute to an accident(south) or incident(south). This was a contributing factor in a recent 'non occurrence' which led to an oceanic ATC controller being put on an opportunity to demonstrate performance.
Original NASA ASRS Text
Title: ZOA CTLR EXPRESSED CONCERN REGARDING THE NEW OCEANIC EQUIP AND CLRNC CONFIRMATION PROCS UTILIZED.
Narrative: TODAY; WHILE WORKING OC9; AT XA52Z; ACR X WAS GIVEN A CPDLC CLRNC TO CLB FROM FL360 TO FL370. BTWN XA53-XA59Z; THE CTLR RECEIVED 3 ERRONEOUS NDA AND FN-CAD MESSAGES. AT XA59Z; THE CTLR REISSUED A CPDLC CLRNC FOR ACR X TO CLB FROM FL360 TO FL370. AT XB02Z; THE CTLR RECEIVED A NO RESPONSE FROM ACFT WARNING MESSAGE AND ISSUED A HF CLRNC THROUGH SFO COMRDO FOR ACR X TO CLB FROM FL360 TO FL370. AT XB04Z; THE CTLR RECEIVED ANOTHER ERRONEOUS FN-CAD MESSAGE. AT XB08Z; THE CTLR RECEIVED A PLT READBACK (ON HIS ORIGINAL COMRDO CLRNC) FROM SFO COMRDO THROUGH HF; STATING THE ACFT WAS ALREADY LEVEL AT FL370. (IT APPEARS THAT THE ACFT RECEIVED A CPDLC CLRNC PRIOR TO GETTING THIS HF CLRNC. IF SO; WHY DID THE CTLR GET THE WARNING MESSAGE THAT THE CLRNC HAD NOT BEEN DELIVERED?) AT XB09Z; THE CTLR RECEIVED A NO RESPONSE FROM ACFT WARNING MESSAGE. AT XB12Z; THE CTLR REQUESTED THAT ACR X CONFIRM ALT. AT XB14Z; THE CTLR RECEIVED A FAIL NDA MESSAGE. SOMETIME AROUND XB15Z; THE CTLR SENT A MESSAGE THROUGH SFO COMRDO TO CONFIRM ALT ON ACR X AND RECEIVED A LEVEL RPT AT FL370. ADDITIONALLY AT XB21Z; THE CTLR RECEIVED A CONTACT TYO CTR MESSAGE WHICH CONTAINED THE WRONG CONTACT FREQS. SEVERAL MESSAGES WERE SUBSEQUENTLY SENT TO THE CTLR PERTAINING TO THE WRONG CONTACT INFO BEING SENT. THIS IS A RECURRING PROB; WHICH MAY CAUSE OR CONTRIBUTE TO AN ACCIDENT(S) OR INCIDENT(S). THIS WAS A CONTRIBUTING FACTOR IN A RECENT 'NON OCCURRENCE' WHICH LED TO AN OCEANIC ATC CTLR BEING PUT ON AN OPPORTUNITY TO DEMONSTRATE PERFORMANCE.
Data retrieved from NASA's ASRS site as of January 2009 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.