37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1370095 |
Time | |
Date | 201607 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZSU.ARTCC |
State Reference | PR |
Aircraft 1 | |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 129 |
Flight Phase | Final Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6.5 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Local control called approach stating RWY10 was closed due to debris in the runway. Aircraft X was on a southeast bound heading for the ILS approach to RWY8 at 2500 feet. There was a stuck microphone on 119.4 frequency for approximately 3 or 4 minutes. Aircraft X went thru multiple higher minimum vectoring altitudes at 2500 feet during the stuck microphone. Approach attempted to contact aircraft X on guard frequency multiple times to turn and/or climb the aircraft. Aircraft X tried to contact the tower for instruction. Approach told local to climb the aircraft immediately to 5000 feet for the minimum vectoring altitudes in the area and turn northbound to exit the area. Communication was reestablished with aircraft X on R1 backup frequency aircraft X landed without incident. Extreme weather in the area during incident.the R5 controller continued to send more aircraft into R1's airspace; without R1 accepting the handoffs; during and after the incident. R5 should have held aircraft in their airspace instead of violating R1's airspace repeatedly with more inbound traffic until the stuck microphone and low aircraft situation was taken care of. This put more stress on the R1 controller. More than likely; the R1 controller missed required control instructions to the low aircraft because of the extra stress.
Original NASA ASRS Text
Title: ZSU Controller reported a NORDO aircraft entered their airspace below the minimum vectoring altitude. It was also reported that the adjacent sector also allowed aircraft to enter their sector without approving the handoffs.
Narrative: Local Control called approach stating RWY10 was closed due to debris in the runway. Aircraft X was on a southeast bound heading for the ILS approach to RWY8 at 2500 feet. There was a stuck microphone on 119.4 frequency for approximately 3 or 4 minutes. Aircraft X went thru multiple higher Minimum Vectoring Altitudes at 2500 feet during the stuck microphone. Approach attempted to contact Aircraft X on guard frequency multiple times to turn and/or climb the aircraft. Aircraft X tried to contact the tower for instruction. Approach told Local to climb the aircraft immediately to 5000 feet for the Minimum Vectoring Altitudes in the area and turn northbound to exit the area. Communication was reestablished with Aircraft X on R1 backup frequency Aircraft X landed without incident. Extreme weather in the area during incident.The R5 controller continued to send more aircraft into R1's airspace; without R1 accepting the handoffs; during and after the incident. R5 should have held aircraft in their airspace instead of violating R1's airspace repeatedly with more inbound traffic until the stuck microphone and low aircraft situation was taken care of. This put more stress on the R1 controller. More than likely; the R1 controller missed required control instructions to the low aircraft because of the extra stress.
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.