37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1555234 |
Time | |
Date | 201806 |
Place | |
Locale Reference | SJU.Airport |
State Reference | PR |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors SID ACONY4 |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Israel Aircraft Undifferentiated or Other Model |
Flight Phase | Climb |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Ground Supervisor / CIC Flight Data / Clearance Delivery |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Local controller departed aircraft X from runway 08. My positions: FD/clearance delivery (flight data/clearance delivery) combined with ground control and controller in charge (controller-in-charge). Seconds after; aircraft Y called sju tower and transmitted 'aircraft Y is squawk [code] runway heading'. I attempted to multifunction display squawk code; and did not find any fp (flight plan) in the ASR-8 system; and relayed to local. It was obvious aircraft Y had departed from runway 09 at isla grande airport -sig; (adjacent airport about 6 miles west of sju tower); due to a visible primary target squawking [their code] in the departure end of sig runway 09 climbing out of 1;000. After xa:00L sig tower class D reverts to class east; CTAF. Local controller responded 'aircraft Y do not fly runway heading; say intentions; I have a departure.' aircraft Y responded 'we request radar vectors please.' by this time aircraft X has already started takeoff roll. Local controller asked aircraft Y if he had sju tower in sight; and he replied yes. Local control (local controller) then instructed aircraft Y to fly direct sju tower and continue eastbound between the runways on a heading of 095. Local control then asked aircraft Y to verify call sign. Aircraft Y responded with his squawk code. Aircraft Y did not comply with any instruction and continued to fly eastbound still climbing. Local control directed aircraft Y 'proceed over head the control tower now.' aircraft Y continued flying eastbound climbing out of 3;500 feet. Aircraft X was then instructed to maintain 3;000; and local control coordinated an altitude of VFR at or above 5;000 for aircraft Y. Aircraft Y was given a brasher warning/possible pilot deviation and switched to san juan approach 119.4 frequency. Aircraft Y is clearly unfamiliar with sju class C airspace; and additionally does not fully comprehend the english language to the extent necessary to responsibly fulfill his duties as a pilot in command. Additionally; aircraft Y departed VFR; but checked in with a squawk code which also caused confusion on whether or not he was an IFR or VFR aircraft.my recommendation would be to validate the qualifications of aircraft Y and assure the pilot is aware of airspace and regulations. In my opinion; any control instruction given to aircraft Y would have been unsuccessful due to his lack of the english language and situational awareness. In this case local control reached out to aircraft X to achieve separation and was effective.
Original NASA ASRS Text
Title: SJU Controllers reported WW4 pilot with language barrier failed to comply with clearances resulting in a traffic conflict.
Narrative: Local Controller departed Aircraft X from Runway 08. My positions: FD/CD (Flight Data/Clearance Delivery) combined with Ground Control and CIC (Controller-in-Charge). Seconds after; Aircraft Y called SJU Tower and transmitted 'Aircraft Y is SQUAWK [code] runway heading'. I attempted to Multifunction display squawk code; and did not find any FP (flight plan) in the ASR-8 system; and relayed to Local. It was obvious Aircraft Y had departed from Runway 09 at Isla Grande Airport -SIG; (adjacent airport about 6 miles west of SJU Tower); due to a visible primary target squawking [their code] in the departure end of SIG Runway 09 climbing out of 1;000. After XA:00L SIG Tower class D reverts to Class E; CTAF. Local Controller responded 'Aircraft Y do not fly runway heading; say intentions; I have a departure.' Aircraft Y responded 'we request radar vectors please.' By this time Aircraft X has already started takeoff roll. Local Controller asked Aircraft Y if he had SJU Tower in sight; and he replied yes. LC (Local Controller) then instructed Aircraft Y to fly direct SJU Tower and continue eastbound between the runways on a heading of 095. LC then asked Aircraft Y to verify call sign. Aircraft Y responded with his squawk code. Aircraft Y did not comply with any instruction and continued to fly eastbound still climbing. LC directed Aircraft Y 'proceed over head the control tower now.' Aircraft Y continued flying eastbound climbing out of 3;500 feet. Aircraft X was then instructed to maintain 3;000; and LC coordinated an altitude of VFR at or above 5;000 for Aircraft Y. Aircraft Y was given a brasher warning/possible pilot deviation and switched to San Juan Approach 119.4 frequency. Aircraft Y is clearly unfamiliar with SJU class C airspace; and additionally does not fully comprehend the English language to the extent necessary to responsibly fulfill his duties as a pilot in command. Additionally; Aircraft Y departed VFR; but checked in with a squawk code which also caused confusion on whether or not he was an IFR or VFR aircraft.My recommendation would be to validate the qualifications of Aircraft Y and assure the pilot is aware of airspace and regulations. In my opinion; any control instruction given to Aircraft Y would have been unsuccessful due to his lack of the English language and situational awareness. In this case LC reached out to Aircraft X to achieve separation and was effective.
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.