37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1528252 |
Time | |
Date | 201803 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | D10.TRACON |
State Reference | TX |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | B777 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
I was working feeder west 1 and 2 combined. At about XA38Z the first issue started. Aircraft Y checked in going too fast for the published speed at the boundary fix. Ukw sector was running almost all of the aircraft faster than the published STAR speeds. The aircraft would check in with speed assignment of 310 KTS or greater than complying at the boundary fix. Most were given the comply restriction from ukw way too late; so they were not going to be able to comply. This is a daily occurrence and for us. The aircraft compress to less than 5 NM separation as soon as they enter our airspace. They were shipping aircraft late; so I had hardly any time to fix the situation. The first time it became a separation issue was at XA43Z. Aircraft X; H/B77W; was in front of aircraft Z; large weight aircraft. Aircraft Z was run too fast to the boundary; so they compressed with aircraft X. I did what I could to save the wake turbulence separation loss with speed assignments and headings. Aircraft a was the next aircraft inbound left too fast. Aircraft B was following that aircraft a and aircraft B was kept too fast and was less than 5 NM separation before I took the hand-off. I called ukw and told them I fixed the first separation issue; and they needed to fix the rest. The controller argued that they did have 5 mn radar separation. It was almost 4 NM separation. I didn't take the hand-off on aircraft B hoping they would turn them out or spin them and provide proper separation. Instead; the ukw controller kept aircraft B coming into my airspace and shipped them to me without me taking a hand-off; violating my airspace. Aircraft C was following aircraft B; and they were less 5 NM separation too. They also kept aircraft C coming into my airspace without a hand-off; violating my airspace. He starting turning the next couple of aircraft out to provide proper separation. He kept aircraft D coming inside my airspace without a hand-off; violating my airspace. Aircraft D was also issued direct zmman (a fix inside my airspace) without coordination; violating the LOA (letter of agreement). Aircraft east and aircraft F were handed off too fast; and aircraft G was handed off too high.again; this situation is a daily (if not multiple times a day) occurrence with this ZFW sector. When our os (operations supervisor) or controller in charge (controller in charge) call their os or controller in charge; they usually aren't aware of the situation and say they'll talk to the controller. First; all ZFW arrival sectors need to have the aircraft sequenced prior to our airspace boundary. They need to stop sequencing at our boundary or inside our boundary.second; they need to have the aircraft established at the STAR speeds prior to STAR fixes at our boundary.
Original NASA ASRS Text
Title: D10 TRACON Controller reported ZFW sector was not complying with LOA; STAR restrictions; national or facility policy. This caused loss of standard and wake turbulence separation.
Narrative: I was working Feeder West 1 and 2 combined. At about XA38Z the first issue started. Aircraft Y checked in going too fast for the published speed at the boundary fix. UKW sector was running almost all of the aircraft faster than the published STAR speeds. The aircraft would check in with speed assignment of 310 KTS or greater than complying at the boundary fix. Most were given the comply restriction from UKW way too late; so they were not going to be able to comply. This is a daily occurrence and for us. The aircraft compress to less than 5 NM separation as soon as they enter our airspace. They were shipping aircraft late; so I had hardly any time to fix the situation. The first time it became a separation issue was at XA43Z. Aircraft X; H/B77W; was in front of Aircraft Z; Large Weight aircraft. Aircraft Z was run too fast to the boundary; so they compressed with Aircraft X. I did what I could to save the wake turbulence separation loss with speed assignments and headings. Aircraft A was the next aircraft inbound left too fast. Aircraft B was following that Aircraft A and Aircraft B was kept too fast and was less than 5 NM separation before I took the hand-off. I called UKW and told them I fixed the first separation issue; and they needed to fix the rest. The controller argued that they did have 5 MN radar separation. It was almost 4 NM separation. I didn't take the hand-off on Aircraft B hoping they would turn them out or spin them and provide proper separation. Instead; the UKW controller kept Aircraft B coming into my airspace and shipped them to me without me taking a hand-off; violating my airspace. Aircraft C was following Aircraft B; and they were less 5 NM separation too. They also kept Aircraft C coming into my airspace without a hand-off; violating my airspace. He starting turning the next couple of aircraft out to provide proper separation. He kept Aircraft D coming inside my airspace without a hand-off; violating my airspace. Aircraft D was also issued direct ZMMAN (a fix inside my airspace) without coordination; violating the LOA (Letter of Agreement). Aircraft E and Aircraft F were handed off too fast; and Aircraft G was handed off too high.Again; this situation is a daily (if not multiple times a day) occurrence with this ZFW sector. When our OS (Operations Supervisor) or CIC (Controller in Charge) call their OS or CIC; they usually aren't aware of the situation and say they'll talk to the controller. First; all ZFW arrival sectors need to have the aircraft sequenced PRIOR to our airspace boundary. They need to stop sequencing at our boundary or inside our boundary.Second; they need to have the aircraft established at the STAR speeds prior to STAR fixes at our boundary.
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.