 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZSU controller described a failed attempt to issue a descent clearance noting the frequency utilized has had problems for an extended amount of time.
| Attributes | |
| ACN | 995523 |
| Time | |
| Date | 201202 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZSU.ARTCC |
| State Reference | PR |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Hercules (C-130) |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Shortly after I assumed the position I noticed that the previous controller's instruction for a B737 to expedite descent was not working as planned. I issued a turn to the descending B737 aircraft and called traffic with no reply from the B737. We have bad radios in the area; so I watch a second to see if he took the turn. I called a total of three times to the B737 before he took the turn. I had also called traffic to the C130 and the pilot reported traffic in sight. The projected path initially looked close but appeared separation would not be lost. I wanted the turn for extra comfort but as it played out it ended to be right at the minimums for separation as they passed. We have had frequency problems on 135.7 for an extended amount of time; but I'm not sure if I was blocked; pilot was not listening; or it was a blind spot. I believe if the B737 had taken the turn when I initialized it I would have had plenty of space. Proper frequencies would be great. We have been reporting those down for years. Maintenance seems to reset it; someone does a brief frequency check and it's called back up. The expedite descent clearance was not necessary in the first place. I should have just stopped descent vertically as soon as I sat down.
Original NASA ASRS Text
Title: ZSU Controller described a failed attempt to issue a descent clearance noting the frequency utilized has had problems for an extended amount of time.
Narrative: Shortly after I assumed the position I noticed that the previous controller's instruction for a B737 to expedite descent was not working as planned. I issued a turn to the descending B737 aircraft and called traffic with no reply from the B737. We have bad radios in the area; so I watch a second to see if he took the turn. I called a total of three times to the B737 before he took the turn. I had also called traffic to the C130 and the pilot reported traffic in sight. The projected path initially looked close but appeared separation would not be lost. I wanted the turn for extra comfort but as it played out it ended to be right at the minimums for separation as they passed. We have had frequency problems on 135.7 for an extended amount of time; but I'm not sure if I was blocked; pilot was not listening; or it was a blind spot. I believe if the B737 had taken the turn when I initialized it I would have had plenty of space. Proper frequencies would be great. We have been reporting those down for years. Maintenance seems to reset it; someone does a brief frequency check and it's called back up. The expedite descent clearance was not necessary in the first place. I should have just stopped descent vertically as soon as I sat down.
Data retrieved from NASA's ASRS site as of July 2013 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.