37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1081035 |
Time | |
Date | 201304 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZNY.ARTCC |
State Reference | NY |
Aircraft 1 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
There is a major issue with the way the bermuda sector; a radar sector unless the radar fails is operated. We are using atop to control the traffic in an out of bermuda as well as overflights. As far as overflights go the system works. As far as the transition to the airport; this system is inadequate. It was a fairly moderate traffic flow into the bermuda sector. There was a core track exiting the sector. Most aircraft were on the track. Some fix to fix direct; and others from the entry fix to bda then to the exit fix; which added to the complexity. The sector was split out hi and low. There was a departure climbing to FL290. There were 2 inbounds to bda at FL300 and FL310. There were multiple aircraft on the track above FL310. Air carrier X a frequent arrival into bda was entering at FL370 which is in violation of our agreement unless apreqed. I was unable to descend this flight due to the fact that we cannot use radial DME separation until 130 miles from the VOR. When I probed the flight down to FL310 atop showed conflicts with more than 5 aircraft. I had to hold the flight for almost 20 minutes at FL370 at a fix and then send the flight over 100 miles off their route of flight to descend the aircraft. This is a major issue due to the limitations of the system.
Original NASA ASRS Text
Title: ZNY Controller voiced concern regarding the Bermuda Sector operations when RADAR is not available.
Narrative: There is a major issue with the way the Bermuda Sector; a RADAR sector unless the RADAR fails is operated. We are using ATOP to control the traffic in an out of Bermuda as well as overflights. As far as overflights go the system works. As far as the transition to the airport; this system is inadequate. It was a fairly moderate traffic flow into the Bermuda Sector. There was a core track exiting the sector. Most aircraft were on the track. Some fix to fix direct; and others from the entry fix to BDA then to the exit fix; which added to the complexity. The sector was split out HI and LOW. There was a departure climbing to FL290. There were 2 inbounds to BDA at FL300 and FL310. There were multiple aircraft on the track above FL310. Air Carrier X a frequent arrival into BDA was entering at FL370 which is in violation of our agreement unless APREQed. I was unable to descend this flight due to the fact that we cannot use radial DME separation until 130 miles from the VOR. When I probed the flight down to FL310 ATOP showed conflicts with more than 5 aircraft. I had to hold the flight for almost 20 minutes at FL370 at a fix and then send the flight over 100 miles off their route of flight to descend the aircraft. This is a major issue due to the limitations of the system.
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.