37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1413977 |
Time | |
Date | 201701 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ATL.Tower |
State Reference | GA |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Miss Distance | Horizontal 2500 Vertical 200 |
Narrative:
Aircraft X departed rwy 8R RNAV to hrshl. IFR conditions once he got airborne; the radar showed him drifting south just like a lot of the previous departures. When the ca alert went off I asked him to confirm that he was in his left turn to hrshl since I couldn't see him out of the window. The pilot replied that we are correcting. At that time I turned him to 040 heading and stopped his climb at 2500 feet. The aircraft off his right side was climbing out of 2700 feet. I was told closest proximity was .4 miles and less than 200 ft.about 10 minutes earlier the same situation occurred but the aircraft was actually on the right track the radar was wrong and the target jumped back to the right track. So when the radar showed aircraft X drifting south I questioned the pilot instead of issuing an immediate turn; due to the fact that it has been known to show a target in one spot but the plane is actually in another spot. The radar has been doing this now for about 2 months and it has been a concern for controllers. 25 minutes or so later the radar showed an aircraft off runway 9L with a ca alert with himself while there was another departure of his left that also drifted south according to the radar. Our radar technicians have informed us that gwinnett's sensor is out and this causes all of the anomalies. Fix gwinnett's sensor or take us off fusion.
Original NASA ASRS Text
Title: ATL Tower Controller reported of target jumps due to the Fusion RADAR which contributed to a loss of separation.
Narrative: Aircraft X departed Rwy 8R RNAV to HRSHL. IFR conditions once he got airborne; the radar showed him drifting south just like a lot of the previous departures. When the CA alert went off I asked him to confirm that he was in his left turn to HRSHL since I couldn't see him out of the window. The pilot replied that we are correcting. At that time I turned him to 040 heading and stopped his climb at 2500 feet. The aircraft off his right side was climbing out of 2700 feet. I was told closest proximity was .4 miles and less than 200 ft.About 10 minutes earlier the same situation occurred but the aircraft was actually on the right track the radar was wrong and the target jumped back to the right track. So when the radar showed Aircraft X drifting south I questioned the pilot instead of issuing an immediate turn; due to the fact that it has been known to show a target in one spot but the plane is actually in another spot. The radar has been doing this now for about 2 months and it has been a concern for controllers. 25 minutes or so later the radar showed an aircraft off runway 9L with a CA alert with himself while there was another departure of his left that also drifted south according to the radar. Our radar technicians have informed us that Gwinnett's sensor is out and this causes all of the anomalies. Fix Gwinnett's sensor or take us off Fusion.
Data retrieved from NASA's ASRS site 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.