Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 12
Time Pressure; Workload; Situational Awareness; Human-Machine Interface; Confusion; Communication Breakdown
ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Software and Automation; Procedure; Human Factors; Company Policy; Airspace Structure; Manuals
Aircraft X is the lead aircraft in a flight of three conducting midair refueling at FL260.  Aircraft X flight is non-RVSM (Reduced Vertical Separation Minima) due to two of the aircraft being non-RVSM compliant. The Controller at ZLC17 initiated a radar handoff of Aircraft X flight.  ZLC17 did not request approval for the block altitude or non-RVSM compliance. In addition; ZLC17 made no effort to coordinated the type of formation; or the distance in trail of the aircraft in the flight. Aircraft Y is enroute at FL290.  ZLC17 initiates a radar handoff for Aircraft Y. The flight path of Aircraft Y is in direct conflict with Aircraft X flight. I did not take the handoffs on either of aircraft because they merged shortly after entering my airspace.  ZLC17 transfers communication of Aircraft X flight without the acceptance of a radar handoff or coordination.I call ZLC17 on the landline and ask how we are going to separate the aircraft they are handing me.  At this point Aircraft X flight and Aircraft Y have violated my airspace without a radar handoff being accomplished.  I direct ZLC17 to climb Aircraft Y to FL330 immediately.  ZLC17 indicates they are not in communication with Aircraft Y; as they were performing a 'flash through' even though the targets were going to merge. After ending the landline communication; I ask Aircraft X flight if they can accept FL300 for traffic.  Aircraft X indicated they could accept the new block but it would take them some time to climb as they were in the process of refueling.  I assigned Aircraft X FL300. This still would not have provided me positive separation due to Aircraft X flight being non-RVSM; but I wanted to get at least 1000 feet of vertical separation because I was not in communication with Aircraft Y.  I also assigned Aircraft X a vector away from traffic as soon as they were able to maneuver.  Shortly after these control instructions Aircraft Y checks on frequency; without a radar handoff; climbing to FL330 and on a vector for traffic. These control instructions were issued by ZDV32; who was still in communication with the Aircraft Y.  After assessing the altitude and heading will ensure positive separation; I clear Aircraft X flight back on course in the Aerial Refueling route with their previously assigned altitude of FL260. Once vertical separation is achieved; I cleared Aircraft Y on course.Separation was never lost. Aircraft X flight and Aircraft Y were nearly 30 miles inside my airspace with no radar handoff and no coordination. This is blatantly reckless behavior from ZLC17. This is not a simple mistake. This is willfully ignoring requirements of the 7110.65. These targets were going to merge and they took zero action until I prompted them. There is a clear error chain in place and thankfully were we able to act in time to avoid a loss of separation or worse. ZLC acts in a careless and reckless manner every single day.  They will not answer the shout line and they do not request approval for block altitudes or IAFDOF (Wrong altitude for Direction of Flight) aircraft.  They knowingly and willfully violate the FAAH 7110.65 every single day.  We report these omissions and nothing gets done.  No one is ever held accountable. Today; the recklessness and complacency of ZLC nearly caused an accident. This will continue to happen until someone at the FAA has the courage to punish controllers that are either unqualified; careless and/or purposefully reckless.
A Minneapolis Center Controller reported Salt Lake Center allowed aircraft on converging courses to enter their sector even though they did not take the handoffs. The Minneapolis Controller also reported Salt Lake controllers routinely disregard published procedures and rules in the FAAH 7110.65.