 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
D10 controller described a 'ghost target' event while using the stars system; the reporter noting continued events involving the stars equipment.
| Attributes | |
| ACN | 1088681 |
| Time | |
| Date | 201305 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | D10.TRACON |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Final Approach |
| Route In Use | Other Instrument Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Dfw was shooting triple ILS approaches with monitors due to the weather. I was working the arrival 3 position when I noticed an aircraft track with no data block at 6000 feet (a splat * with an altitude) southbound right in between the final for 18R and 17C (17C's aircraft were at 6000 [feet] and 7000 [feet] for their turn on to the ILS (turn on altitude is 6000 [feet] for 17C)). I alerted other controllers of the traffic. It was approximately 18 miles north of dfw southbound. I slewed to the target and the identified the beacon code. I had the supervisor full route the beacon code and he said it showed 'flight not stored.' the target was southbound at 540 knots. It traveled approximately 5-8 miles then disappeared. Another of what I call 'ghost targets.' there are too many of these and eventually one of the 'ghost targets' is going to cause an incident. By the time I alerted other controllers; the aircraft were already below the 'ghost target' (as it was now south of the trip fixes where the aircraft begin their descent to dfw). Had someone seen it sooner and issued a safety alert and had the aircraft descend or turn it could have caused a very serious incident as there were aircraft side by side near this target. The FAA is supposed to be safety first and above all else. Someone needs to immediately address these 'ghost targets' and this system should be shut down and this facility returned to the ARTS IIIE before someone gets hurt. This system should not be brought back online for live traffic until they ensure that this problem is fixed. I have heard some of the stars people say this is a 'radar problem;' not a stars problem. Each time the beacon codes come up 'not stored' and I do not know if that will help them track down the problem. The ARTS IIIE did not have this problem. Either way; we should go back to a system that we know worked until we can determine the problem.
Original NASA ASRS Text
Title: D10 Controller described a 'Ghost Target' event while using the STARS system; the reporter noting continued events involving the STARS equipment.
Narrative: DFW was shooting triple ILS approaches with monitors due to the weather. I was working the Arrival 3 position when I noticed an aircraft track with no data block at 6000 feet (a splat * with an altitude) southbound right in between the final for 18R and 17C (17C's aircraft were at 6000 [feet] and 7000 [feet] for their turn on to the ILS (turn on altitude is 6000 [feet] for 17C)). I alerted other controllers of the traffic. It was approximately 18 miles north of DFW Southbound. I slewed to the target and the identified the beacon code. I had the Supervisor full route the beacon code and he said it showed 'flight not stored.' The target was southbound at 540 knots. It traveled approximately 5-8 miles then disappeared. Another of what I call 'Ghost Targets.' There are too many of these and eventually one of the 'Ghost Targets' is going to cause an incident. By the time I alerted other controllers; the aircraft were already below the 'Ghost Target' (as it was now south of the trip fixes where the aircraft begin their descent to DFW). Had someone seen it sooner and issued a safety alert and had the aircraft descend or turn it could have caused a very serious incident as there were aircraft side by side near this target. The FAA is supposed to be safety first and above all else. Someone needs to immediately address these 'Ghost Targets' and this system should be shut down and this facility returned to the ARTS IIIE before someone gets hurt. This system should not be brought back online for live traffic until they ensure that this problem is fixed. I have heard some of the STARS people say this is a 'RADAR problem;' not a STARS problem. Each time the beacon codes come up 'not stored' and I do not know if that will help them track down the problem. The ARTS IIIE did not have this problem. Either way; we should go back to a system that we know worked until we can determine the problem.
Data retrieved from NASA's ASRS site as of July 2013 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.