37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 494839 |
Time | |
Date | 200012 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : cmh.tracon |
State Reference | OH |
Aircraft 1 | |
Controlling Facilities | tower : cyyz.tower |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | pilot : instrument |
Experience | controller radar : 18 controller time certified in position1 : 7 flight time total : 1000 |
ASRS Report | 494839 |
Person 2 | |
Affiliation | government : faa |
Function | maintenance : technician |
Qualification | technician : repairman |
Events | |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | ATC Facility Maintenance Human Performance |
Primary Problem | ATC Facility |
Narrative:
Yesterday and today, I had same occurrence. Yesterday, handoff to me at south radar from ZID. Full data block did not appear until aircraft on mutual boundary. Before that, there was not even a limited data block nor even a 'splat' symbol. There was only a primary and beacon target. No mode C altitude. Nothing! However, the target and full data block/limited data block appeared just fine on unused scope! Today, I was working north radar and final radar was not taking handoff. Same problem! In both instances, changing the range setting cleared up the problem. Airways facilities advised. This is extremely serious situation. Something is not right with the ARTS. Callback conversation with reporter revealed the following information: reporter advised incident took place in a common handoff area with ZID, nikls intersection, aircraft was descending to 11000 ft. Nikls is approximately 40 mi from the radar main bang. Maintenance apparently resolved the problem shortly after being notified of the incident, because the following day, and thereafter, the condition did not recur. Controller states that he never received a reason or the resolution to the occurrence.
Original NASA ASRS Text
Title: CMH ARTS RADAR AUTOMATION PROB.
Narrative: YESTERDAY AND TODAY, I HAD SAME OCCURRENCE. YESTERDAY, HDOF TO ME AT S RADAR FROM ZID. FULL DATA BLOCK DID NOT APPEAR UNTIL ACFT ON MUTUAL BOUNDARY. BEFORE THAT, THERE WAS NOT EVEN A LIMITED DATA BLOCK NOR EVEN A 'SPLAT' SYMBOL. THERE WAS ONLY A PRIMARY AND BEACON TARGET. NO MODE C ALT. NOTHING! HOWEVER, THE TARGET AND FULL DATA BLOCK/LIMITED DATA BLOCK APPEARED JUST FINE ON UNUSED SCOPE! TODAY, I WAS WORKING N RADAR AND FINAL RADAR WAS NOT TAKING HDOF. SAME PROB! IN BOTH INSTANCES, CHANGING THE RANGE SETTING CLRED UP THE PROB. AIRWAYS FACILITIES ADVISED. THIS IS EXTREMELY SERIOUS SIT. SOMETHING IS NOT RIGHT WITH THE ARTS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ADVISED INCIDENT TOOK PLACE IN A COMMON HDOF AREA WITH ZID, NIKLS INTXN, ACFT WAS DSNDING TO 11000 FT. NIKLS IS APPROX 40 MI FROM THE RADAR MAIN BANG. MAINT APPARENTLY RESOLVED THE PROB SHORTLY AFTER BEING NOTIFIED OF THE INCIDENT, BECAUSE THE FOLLOWING DAY, AND THEREAFTER, THE CONDITION DID NOT RECUR. CTLR STATES THAT HE NEVER RECEIVED A REASON OR THE RESOLUTION TO THE OCCURRENCE.
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.