 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Controller claims that odaps in oceanic control cannot process ATC generated messages in a timely manner.
| Attributes | |
| ACN | 253455 |
| Time | |
| Date | 199310 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : zoa |
| State Reference | CA |
| Aircraft 1 | |
| Controlling Facilities | artcc : zoa |
| Operator | common carrier : air carrier |
| Make Model Name | Widebody, Low Wing, 4 Turbojet Eng |
| Navigation In Use | Other |
| Flight Phase | cruise other |
| Route In Use | enroute : other oceanic |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : non radar |
| Qualification | controller : radar |
| Experience | controller radar : 6 |
| ASRS Report | 253455 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : unable |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Navigational Facility |
| Air Traffic Incident | other |
| Situations | |
| Navigational Aid | Unspecified |
Narrative:
This morning, while working heavy traffic on oceanic sector OC1, I encountered 2 substantial delays on the odaps system. At XA08.23 UTC, I activated strips on air carrier X, a transfer from tokyo center. I received a message waiting light until XA09.13 UTC. During this 50 second period, I was unable to process messages or make any other computer amendments. At XA09.13, I received a 'message cleared, time ranked' message. About 5 seconds later I received 'accept air carrier X.' I had to check the computer to insure air carrier X was activated correctly. At XB42.58, I pressed the 'ack' key to receive the next arinc message. Nothing came up on the CRT until XB44.2. Again, I was 'locked out' of the computer. During a busy traffic period, the above is unsatisfactory and may lead to an incident/accident. This is a reported recurring problem!
Original NASA ASRS Text
Title: CTLR CLAIMS THAT ODAPS IN OCEANIC CTL CANNOT PROCESS ATC GENERATED MESSAGES IN A TIMELY MANNER.
Narrative: THIS MORNING, WHILE WORKING HVY TFC ON OCEANIC SECTOR OC1, I ENCOUNTERED 2 SUBSTANTIAL DELAYS ON THE ODAPS SYS. AT XA08.23 UTC, I ACTIVATED STRIPS ON ACR X, A TRANSFER FROM TOKYO CTR. I RECEIVED A MESSAGE WAITING LIGHT UNTIL XA09.13 UTC. DURING THIS 50 SECOND PERIOD, I WAS UNABLE TO PROCESS MESSAGES OR MAKE ANY OTHER COMPUTER AMENDMENTS. AT XA09.13, I RECEIVED A 'MESSAGE CLRED, TIME RANKED' MESSAGE. ABOUT 5 SECONDS LATER I RECEIVED 'ACCEPT ACR X.' I HAD TO CHK THE COMPUTER TO INSURE ACR X WAS ACTIVATED CORRECTLY. AT XB42.58, I PRESSED THE 'ACK' KEY TO RECEIVE THE NEXT ARINC MESSAGE. NOTHING CAME UP ON THE CRT UNTIL XB44.2. AGAIN, I WAS 'LOCKED OUT' OF THE COMPUTER. DURING A BUSY TFC PERIOD, THE ABOVE IS UNSATISFACTORY AND MAY LEAD TO AN INCIDENT/ACCIDENT. THIS IS A RPTED RECURRING PROB!
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.