 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
D10 developmental approach controller reported receiving a handoff of an aircraft that was on a conflicting path with the adjacent sector's traffic.
| Attributes | |
| ACN | 1507535 |
| Time | |
| Date | 201712 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | DFW.Airport |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 170/175 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | A321 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was being vectored from the east downwind to runway 35R for an ILS approach descending 8;000 feet. Aircraft Y was being vectored from the west downwind for an ILS approach to runway 35R descending to 6;000 feet. Both aircraft are being worked by the same controller at this point. They turned aircraft X to the west and turned aircraft Y to the east; both at this point descending to 4;000 feet. They decided to change aircraft X's runway to runway 36L at the last minute and flashed the data block to my position. Aircraft X was then switched to my frequency without resolving the conflict with aircraft Y. Once aircraft X checked in on my frequency; I immediately issued a turn to 200 to avoid aircraft Y. Once separation was re-established; aircraft X was vectored back to runway 36L for the ILS approach.the only thing that I think I could have done to help this situation was ensure that the adjacent sector was turning either aircraft Y or aircraft X to avoid each other before I took the hand-off. The conflict should have been resolved before the frequency change occurred.
Original NASA ASRS Text
Title: D10 Developmental Approach Controller reported receiving a handoff of an aircraft that was on a conflicting path with the adjacent sector's traffic.
Narrative: Aircraft X was being vectored from the east downwind to Runway 35R for an ILS approach descending 8;000 feet. Aircraft Y was being vectored from the west downwind for an ILS approach to Runway 35R descending to 6;000 feet. Both aircraft are being worked by the same controller at this point. They turned Aircraft X to the west and turned Aircraft Y to the east; both at this point descending to 4;000 feet. They decided to change Aircraft X's runway to Runway 36L at the last minute and flashed the data block to my position. Aircraft X was then switched to my frequency without resolving the conflict with Aircraft Y. Once Aircraft X checked in on my frequency; I immediately issued a turn to 200 to avoid Aircraft Y. Once separation was re-established; Aircraft X was vectored back to Runway 36L for the ILS approach.The only thing that I think I could have done to help this situation was ensure that the adjacent sector was turning either Aircraft Y or Aircraft X to avoid each other before I took the hand-off. The conflict should have been resolved before the frequency change occurred.
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.