37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 539150 |
Time | |
Date | 200202 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : ape.vortac |
State Reference | OH |
Altitude | msl single value : 10000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : cmh.tracon |
Operator | other |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Person 1 | |
Affiliation | government : faa |
Function | controller : flight data |
Qualification | controller : radar pilot : instrument |
Experience | controller radar : 2 controller time certified in position1 : 8 flight time total : 1000 |
ASRS Report | 539150 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | other anomaly other |
Independent Detector | aircraft equipment : tcas other controllera other controllerb |
Resolutory Action | none taken : unable |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | FAA Navigational Facility ATC Human Performance |
Primary Problem | ATC Human Performance |
Situations | |
ATC Facility | computer equipment : cmh.tracon procedure or policy : cmh.tracon |
Narrative:
I'm working data position, north radar (nr) says to south radar (sr) 'did you drop the tag of flight check?' south radar responds 'no.' when we compared south radar to north radar, the full data block (call sign, altitude, etc) were still displayed. The aircraft had been handed off to ZID. On the north radar display there was no full data block, not even a limited data block! (Ie, no '*' symbol, no altitude, no nothing...except a target). This is less data than we see on high altitude overflts (at least they have a '*' symbol wherein one can slew to it and bring up a limited data block). North radar could not even slew to it and bring up the limited data block. This was reported to the supervisor, but I didn't see the supervisor take any action beyond acknowledging that. Shortly thereafter, north radar selected a different range setting and the full data block appeared. Going back to the original range setting and the data block vanished again (only a target remained without a limited data block). I've seen this happen before. This is not good, as we depend on the 'quick look' function. (Yes, quick look was on and selected...it was just this 1 target.)
Original NASA ASRS Text
Title: CMH FLT DATA CTLR CONCERN WITH NON DISPLAYABLE FULL DATA TAG.
Narrative: I'M WORKING DATA POS, N RADAR (NR) SAYS TO S RADAR (SR) 'DID YOU DROP THE TAG OF FLT CHK?' S RADAR RESPONDS 'NO.' WHEN WE COMPARED S RADAR TO N RADAR, THE FULL DATA BLOCK (CALL SIGN, ALT, ETC) WERE STILL DISPLAYED. THE ACFT HAD BEEN HANDED OFF TO ZID. ON THE N RADAR DISPLAY THERE WAS NO FULL DATA BLOCK, NOT EVEN A LIMITED DATA BLOCK! (IE, NO '*' SYMBOL, NO ALT, NO NOTHING...EXCEPT A TARGET). THIS IS LESS DATA THAN WE SEE ON HIGH ALT OVERFLTS (AT LEAST THEY HAVE A '*' SYMBOL WHEREIN ONE CAN SLEW TO IT AND BRING UP A LIMITED DATA BLOCK). N RADAR COULD NOT EVEN SLEW TO IT AND BRING UP THE LIMITED DATA BLOCK. THIS WAS RPTED TO THE SUPVR, BUT I DIDN'T SEE THE SUPVR TAKE ANY ACTION BEYOND ACKNOWLEDGING THAT. SHORTLY THEREAFTER, N RADAR SELECTED A DIFFERENT RANGE SETTING AND THE FULL DATA BLOCK APPEARED. GOING BACK TO THE ORIGINAL RANGE SETTING AND THE DATA BLOCK VANISHED AGAIN (ONLY A TARGET REMAINED WITHOUT A LIMITED DATA BLOCK). I'VE SEEN THIS HAPPEN BEFORE. THIS IS NOT GOOD, AS WE DEPEND ON THE 'QUICK LOOK' FUNCTION. (YES, QUICK LOOK WAS ON AND SELECTED...IT WAS JUST THIS 1 TARGET.)
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.