37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1602878 |
Time | |
Date | 201812 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown Ground Event / Encounter Other / Unknown |
Narrative:
While working the local control position during the night time session; I noticed a call sign of an aircraft; moving along the center taxiway in between runways. I looked and observed that it wasn't an aircraft that matched up with the target. It was a vehicle. A discussion ensued between myself and a supervisor regarding the previous events concerning false targets popping up on the asdex [airport surface detection equipment; model X] matching up with a previous departure. The target would end up being a city ops vehicle patrolling and carrying out their regular duties. We've also noted that when it has occurred on other occasions; the educated guess was that the city ops vehicle was holding somewhere west of taxiway hotel in the dirt when the false target began to float across the asdex. On this particular occasion; the target didn't just float across the screen; it actually tagged up with the city ops vehicle and continued to keep the tag of aircraft X. The supervisor directed me to ask the city ops vehicle to turn off their squitter for 1 minute and to then turn it back on. The city ops vehicle complied and the aircraft X tag remained attached to the vehicle. The only time the tag disappeared from the vehicle was when the city ops veered off into the safety area to avoid exiting aircraft who just landed. While the vehicle drove east along taxiway hotel; the aircraft X tag remained connected to the vehicle. The obvious safety issue is when the weather is not VFR and we aren't able to confirm the immediate identity of the false target. I recommend the active investigation on the matter to determine whether it's a software; hardware; or any other type of issue that is causing these false targets. Maybe it's a city ops squitter issue and not an asdex issue.
Original NASA ASRS Text
Title: A Tower Local Controller reported an airport operations vehicle tagged up on their ground radar with as an with an aircraft call sign.
Narrative: While working the Local Control position during the night time session; I noticed a call sign of an aircraft; moving along the center taxiway in between runways. I looked and observed that it wasn't an aircraft that matched up with the target. It was a vehicle. A discussion ensued between myself and a supervisor regarding the previous events concerning false targets popping up on the ASDEX [Airport Surface Detection Equipment; Model X] matching up with a previous departure. The target would end up being a city ops vehicle patrolling and carrying out their regular duties. We've also noted that when it has occurred on other occasions; the educated guess was that the city ops vehicle was holding somewhere west of taxiway hotel in the dirt when the false target began to float across the ASDEX. On this particular occasion; the target didn't just float across the screen; it actually tagged up with the city ops vehicle and continued to keep the tag of Aircraft X. The Supervisor directed me to ask the city ops vehicle to turn off their squitter for 1 minute and to then turn it back on. The city ops vehicle complied and the Aircraft X tag remained attached to the vehicle. The only time the tag disappeared from the vehicle was when the city ops veered off into the safety area to avoid exiting aircraft who just landed. While the vehicle drove east along Taxiway Hotel; the Aircraft X tag remained connected to the vehicle. The obvious safety issue is when the weather is not VFR and we aren't able to confirm the immediate identity of the false target. I recommend the active investigation on the matter to determine whether it's a software; hardware; or any other type of issue that is causing these false targets. Maybe it's a city ops squitter issue and not an ASDEX issue.
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.