Narrative:

Equipment outages and abnormal situations:-sju radar out of service (primary and secondary).-using backup radar (resulting in higher MVA; false targets; and radar clutter).-software malfunction (double targets; one with data block info; and a second one next to the other showing transponder number). -Conflict alert constantly going off due to the software problem; creating a lot of distraction.-fdio (flight data input/output system) out of service (obligating me to be requesting flight plans for most arrivals and departure traffic.-west (R1); east (R5); and final (R9) were combined despite the complexity; distractions; and volume of traffic due to all of the above mentioned.I approved a release out of runway 9 at tjig for aircraft X; I was unable to radar identify him when he first call because of all the clutter and radar problems going on. Then I requested the pilot to reset the transponder and to say his position and altitude in order to try to locate him. When I finally was able to confirm his position the aircraft was already inside sjut right in the middle of the departure corridor with aircraft Y departing out of runway 8 at tjsj. The tower controller noticed the situation and was able to stop aircraft Y below aircraft X keeping the situation under control.the pilot of aircraft X was supposed to turn heading 300 on departure and to climb and maintain 1;800. Obviously the pilot didn't followed the ATC initial departure clearance and kept flying runway heading; resulting in the sju tower airspace violation and possible loss of separation. The sigt controller also failed scanning and making sure the aircraft was turning on the assigned heading before switching it to approach frequency.recommendations:-if the radar is out of service sjut should not have automated releases. They should call for release all departure until radar is return back in service.-supervisor scanning the operation in order to help with coordination and make decisions like splitting sectors; opening radar assist position; etc. Especially during equipment outages days like today.-report the equipment outage and follow up to get it fix as soon as possible.-no reason why having the sectors combined under this situation; specially having the personal to keep the positions split and run a safe and better operation.-better scanning from the sigt controller to catch the error and correcting.-ask for help sooner.

Google
 

Original NASA ASRS Text

Title: ZSU Center Controller reported of an airborne conflict when a TJIG departure did not follow departure procedures and entered TJSJ airspace without permission.

Narrative: Equipment outages and abnormal situations:-SJU Radar out of service (Primary and Secondary).-Using backup radar (resulting in higher MVA; false targets; and radar clutter).-Software malfunction (double targets; one with data block info; and a second one next to the other showing transponder number). -Conflict Alert constantly going off due to the software problem; creating a lot of distraction.-FDIO (Flight Data Input/Output System) out of service (obligating me to be requesting flight plans for most arrivals and departure traffic.-West (R1); East (R5); and Final (R9) were combined despite the complexity; distractions; and volume of traffic due to all of the above mentioned.I approved a release out of Runway 9 at TJIG for Aircraft X; I was unable to radar identify him when he first call because of all the clutter and radar problems going on. Then I requested the pilot to reset the transponder and to say his position and altitude in order to try to locate him. When I finally was able to confirm his position the aircraft was already inside SJUT right in the middle of the departure corridor with Aircraft Y departing out of Runway 8 at TJSJ. The tower controller noticed the situation and was able to stop Aircraft Y below Aircraft X keeping the situation under control.The pilot of Aircraft X was supposed to turn heading 300 on departure and to climb and maintain 1;800. Obviously the pilot didn't followed the ATC initial departure clearance and kept flying runway heading; resulting in the SJU tower airspace violation and possible loss of separation. The SIGT controller also failed scanning and making sure the aircraft was turning on the assigned heading before switching it to approach frequency.Recommendations:-If the radar is out of service SJUT should not have automated releases. They should call for release all departure until radar is return back in service.-Supervisor scanning the operation in order to help with coordination and make decisions like splitting sectors; opening radar assist position; etc. especially during equipment outages days like today.-Report the equipment outage and follow up to get it fix ASAP.-No reason why having the sectors combined under this situation; specially having the personal to keep the positions split and run a safe and better operation.-Better scanning from the SIGT controller to catch the error and correcting.-Ask for help sooner.

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.