 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZMA center controller reported managing aircraft conflicts caused by difficulty coordinating with adjacent airspace.
| Attributes | |
| ACN | 1479140 |
| Time | |
| Date | 201709 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZMA.ARTCC |
| State Reference | FL |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Transport High Wing 2 Turboprop Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 129 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 9 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
Aircraft X checked in turning back with the number 2 engine out; blocked aircraft Y trying to check on from approach who was not radar identified climbing to 12000 feet. Aircraft Z was about 10 miles out in front of the aircraft Y not on my frequency climbing to 12000 feet inside of approach airspace. When aircraft Y called initial check on was that he was responding to a TA climb. So I radar identified him and then climbed him to his filed altitude. Immediately after aircraft Z checked on and advised that someone just flew past him. I told aircraft Y that I had no idea what nassau was doing since it was their airspace but told him to maintain 11000 feet so he would be separated from aircraft Y. Aircraft Y was on an incorrect code. During this time an aircraft a was 8 miles and parallel with aircraft Y so I could see approach was having difficulty separating their planes. Fix the radar feed so I can see aircraft departing nassau. As it is right now I cannot see aircraft below 9000 feet which would have prevented this error. We did have a radar feed in their old system but since they went to the new system we can't see anything and it is really dangerous. I can't believe this vital piece of equipment was overlooked.
Original NASA ASRS Text
Title: ZMA Center Controller reported managing aircraft conflicts caused by difficulty coordinating with adjacent airspace.
Narrative: Aircraft X checked in turning back with the number 2 engine out; blocked Aircraft Y trying to check on from approach who was not radar identified climbing to 12000 feet. Aircraft Z was about 10 miles out in front of the Aircraft Y not on my frequency climbing to 12000 feet inside of Approach airspace. When Aircraft Y called initial check on was that he was responding to a TA climb. So I radar identified him and then climbed him to his filed altitude. Immediately after Aircraft Z checked on and advised that someone just flew past him. I told Aircraft Y that I had no idea what Nassau was doing since it was their airspace but told him to maintain 11000 feet so he would be separated from Aircraft Y. Aircraft Y was on an incorrect code. During this time an aircraft A was 8 miles and parallel with Aircraft Y so I could see Approach was having difficulty separating their planes. Fix the RADAR feed so I can see aircraft departing Nassau. As it is right now I cannot see aircraft below 9000 feet which would have prevented this error. We did have a radar feed in their old system but since they went to the new system we can't see anything and it is really dangerous. I can't believe this vital piece of equipment was overlooked.
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.