Narrative:

The previous controller I had relieved had two IFR aircraft in his sector but only one aircraft on his frequency. A BE40 was inbound to the tjig airport for the visual approach runway 9 and was already switched to the tjig tower. An A320 was approximately 8-10 miles behind inbound for the ILS 10 approach at tjsj. I had noticed that the BE40 had crossed the arrival corridor for tjig and had established himself on the final to runway 10 at tjsj. I promptly called tjig and asked what the BE40 was doing. Controller had no response and that is when I told him that his BE40 had missed his airport and was inbound to the wrong airport. Controller replied; 'I'll ask him'. Immediately thereafter I called tjsj and told them to stop all westbound departures because the BE40 had missed his airport and was not sure what he was going to do. Tjsj acknowledged and complied. The BE40 at five mile final to tjsj made a hard left hand turn northbound to tjig at 1;000 MSL and descending. At this point the A320 was approximately 10-12 final to runway 10. It appeared as if the BE40 was making an opposite direction arrival to runway 27 at tjig because of his proximity to the runway along with his altitude; now 700 MSL. The BE40 continued into a left downwind pattern for runway 9 at tjig. When the BE40 was parallel to the A320 separated vertically; I called tjig and asked the controller if the BE40 had my airbus insight and if the aircraft were maintaining visual separation to which the controller replied yes. I then cleared the A320 for the approach. Raptor playback showed a loss of separation when the BE40 was on left base/short final to runway 9 (tjig) and the A320 3 mile final to runway 10 (tjsj). Raptor shows 2.65 miles and 900 ft; however; not only are the aircraft landing different airports staggered 5 miles apart but also visual separation along with a 72 degree course divergence existed at the time. The BE40 172 heading and the A320 ahead on a 100 heading. This situation is particularly unsafe because unlike the tjsj airport we have no missed approach instruction for the tjig airport. This has happened multiple times as IFR aircraft go around at tjig and everyone is left at the mercy of the pilot and the tjig controller because there is no standard climb out instruction. While the aircraft goes around at tjig; tjsj continues to depart aircraft on a 330 heading which because of the close proximity to tjig put aircraft on a head on course. A few months ago a similar situation happened and two aircraft came in close enough proximity to view the event as a near mid-air. This is very unsafe and needs to be addressed immediately! I suggest the following: a) establish a missed approach procedure for the tjig airport and have it implemented in the LOA as soon as possible! B) terminate the 330 heading departures at tjsj immediately! Furthermore; I will address the departure and arrival corridors at ZSU and explain how they are a disaster waiting to happen. The departure corridor cross paths with the arrival gates. Previously numerous operator error's have occurred because of this built in conflict.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZSU Controller described conflict event when traffic on a visual approach to TJIJ initiated a missed approach and conflicted with an A320 inbound to TJSJ; the reporter noting the need for standard procedures covering these types of events.

Narrative: The previous controller I had relieved had two IFR aircraft in his sector but only one aircraft on his frequency. A BE40 was inbound to the TJIG airport for the visual approach Runway 9 and was already switched to the TJIG Tower. An A320 was approximately 8-10 miles behind inbound for the ILS 10 approach at TJSJ. I had noticed that the BE40 had crossed the arrival corridor for TJIG and had established himself on the final to Runway 10 at TJSJ. I promptly called TJIG and asked what the BE40 was doing. Controller had no response and that is when I told him that his BE40 had missed his airport and was inbound to the wrong airport. Controller replied; 'I'll ask him'. Immediately thereafter I called TJSJ and told them to stop all westbound departures because the BE40 had missed his airport and was not sure what he was going to do. TJSJ acknowledged and complied. The BE40 at five mile final to TJSJ made a hard left hand turn northbound to TJIG at 1;000 MSL and descending. At this point the A320 was approximately 10-12 final to Runway 10. It appeared as if the BE40 was making an opposite direction arrival to Runway 27 at TJIG because of his proximity to the runway along with his altitude; now 700 MSL. The BE40 continued into a left downwind pattern for Runway 9 at TJIG. When the BE40 was parallel to the A320 separated vertically; I called TJIG and asked the Controller if the BE40 had my Airbus insight and if the aircraft were maintaining visual separation to which the Controller replied yes. I then cleared the A320 for the approach. RAPTOR playback showed a loss of separation when the BE40 was on left base/short final to Runway 9 (TJIG) and the A320 3 mile final to Runway 10 (TJSJ). RAPTOR shows 2.65 miles and 900 FT; however; not only are the aircraft landing different airports staggered 5 miles apart but also visual separation along with a 72 degree course divergence existed at the time. The BE40 172 heading and the A320 ahead on a 100 heading. This situation is particularly unsafe because unlike the TJSJ airport we have no missed approach instruction for the TJIG airport. This has happened multiple times as IFR aircraft go around at TJIG and everyone is left at the mercy of the pilot and the TJIG Controller because there is no standard climb out instruction. While the aircraft goes around at TJIG; TJSJ continues to depart aircraft on a 330 heading which because of the close proximity to TJIG put aircraft on a head on course. A few months ago a similar situation happened and two aircraft came in close enough proximity to view the event as a near mid-air. This is very unsafe and needs to be addressed immediately! I suggest the following: A) Establish a missed approach procedure for the TJIG airport and have it implemented in the LOA ASAP! B) Terminate the 330 heading departures at TJSJ immediately! Furthermore; I will address the departure and arrival corridors at ZSU and explain how they are a disaster waiting to happen. The departure corridor cross paths with the arrival gates. Previously numerous Operator Error's have occurred because of this built in conflict.

Data retrieved from NASA's ASRS site as of April 2012 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.