37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1215910 |
Time | |
Date | 201411 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZTL.ARTCC |
State Reference | GA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
At the leonn sector 29; I took radar on aircraft X that was on a vector but then cleared back to mayos intersection; descending to FL240. Maybe two minutes later; I had radar on aircraft Y; which was direct mayos; also descending to FL240 out of about FL253. To be honest; I'm not quite sure I took the hand off on aircraft Y or if I auto acquired that aircraft. At this point; aircraft X was cleared direct mayos; descending to FL240; which would have been head on with aircraft Y; descending to the same altitude; cleared to the same fix; had I not cleared aircraft X direct to royos intersection. At this point; I may have auto acquired aircraft Y; which had a 100 knot overtake as both aircraft are on the same path of flight. I then turned aircraft Y; 20 degrees right and turned aircraft X; 20 degrees left and expedited the descent. During this time W32 violated sector 33's airspace with aircraft on vectors that were not pointed out and an aircraft descending to FL240 was in conflict with an aircraft in sector 33's airspace; level at FL240; which the controller had to climb to FL260 to maintain positive separation. After the aircraft were positively separated; I got the necessary spacing and in trail for clt arrivals and continued sequencing the rest of the clt arrivals.I recommend that ZDC maintain positive separation of aircraft; before initiating hand offs with sector 29.
Original NASA ASRS Text
Title: ZTL Controller reports while trying to separate two aircraft another Center violates airspace which distracts the ZTL Controller.
Narrative: At the Leonn sector 29; I took radar on Aircraft X that was on a vector but then cleared back to MAYOS intersection; descending to FL240. Maybe two minutes later; I had radar on Aircraft Y; which was direct MAYOS; also descending to FL240 out of about FL253. To be honest; I'm not quite sure I took the hand off on Aircraft Y or if I auto acquired that aircraft. At this point; Aircraft X was cleared direct MAYOS; descending to FL240; which would have been head on with Aircraft Y; descending to the same altitude; cleared to the same fix; had I not cleared Aircraft X direct to ROYOS intersection. At this point; I may have auto acquired Aircraft Y; which had a 100 knot overtake as both aircraft are on the same path of flight. I then turned Aircraft Y; 20 degrees right and turned Aircraft X; 20 degrees left and expedited the descent. During this time W32 violated sector 33's airspace with aircraft on vectors that were not pointed out and an aircraft descending to FL240 was in conflict with an aircraft in sector 33's airspace; level at FL240; which the controller had to climb to FL260 to maintain positive separation. After the aircraft were positively separated; I got the necessary spacing and in trail for CLT arrivals and continued sequencing the rest of the CLT arrivals.I recommend that ZDC maintain positive separation of aircraft; before initiating hand offs with sector 29.
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.