 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ARTCC radar controller observes problem with automation handoff capabilities to adjoining control sector. When handoff is initiated, the associated data block does not immediately display to the xferring control sector.
| Attributes | |
| ACN | 397900 |
| Time | |
| Date | 199803 |
| Day | Mon |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : sln |
| State Reference | KS |
| Altitude | msl bound lower : 33000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | artcc : zkc |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller non radar : 8 controller radar : 14 |
| ASRS Report | 397900 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
| Situations | |
| ATC Facility | other physical facility |
Narrative:
R24 (sector) is positioned next to R26. I initiated handoff (automated) to R26. Track showed aircraft was in handoff mode to R26 (26 was flashing on data block). R26 did not have data block displayed. I would have thought that was impossible. Track on R24's scope was showing in a handoff status to R26. R26 did not show that at all. R26 showed only beacon target with history. After approximately 2 mins, the data block appeared in handoff status on R26's scope. After R26 accepted handoff, the data block on R24's scope would drop off, then reappear. This occurred 4-5 times with varying times between track dropping and reappearing. This phenomena was reported by other controllers in the center. Management blamed the problem on cdc or something.
Original NASA ASRS Text
Title: ARTCC RADAR CTLR OBSERVES PROB WITH AUTOMATION HDOF CAPABILITIES TO ADJOINING CTL SECTOR. WHEN HDOF IS INITIATED, THE ASSOCIATED DATA BLOCK DOES NOT IMMEDIATELY DISPLAY TO THE XFERRING CTL SECTOR.
Narrative: R24 (SECTOR) IS POSITIONED NEXT TO R26. I INITIATED HDOF (AUTOMATED) TO R26. TRACK SHOWED ACFT WAS IN HDOF MODE TO R26 (26 WAS FLASHING ON DATA BLOCK). R26 DID NOT HAVE DATA BLOCK DISPLAYED. I WOULD HAVE THOUGHT THAT WAS IMPOSSIBLE. TRACK ON R24'S SCOPE WAS SHOWING IN A HDOF STATUS TO R26. R26 DID NOT SHOW THAT AT ALL. R26 SHOWED ONLY BEACON TARGET WITH HISTORY. AFTER APPROX 2 MINS, THE DATA BLOCK APPEARED IN HDOF STATUS ON R26'S SCOPE. AFTER R26 ACCEPTED HDOF, THE DATA BLOCK ON R24'S SCOPE WOULD DROP OFF, THEN REAPPEAR. THIS OCCURRED 4-5 TIMES WITH VARYING TIMES BTWN TRACK DROPPING AND REAPPEARING. THIS PHENOMENA WAS RPTED BY OTHER CTLRS IN THE CTR. MGMNT BLAMED THE PROB ON CDC OR SOMETHING.
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.