Small Transport; Low Wing; 2 Recip Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 8
Workload; Troubleshooting; Situational Awareness; Confusion; Communication Breakdown; Distraction
ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Air Traffic Control Provided Assistance
Procedure; Human Factors
Working R19 [and] 20 there was icing and weather at the time. Aircraft X was an overflight on V386. PSP landing TUS. On V386 this route is head on with the PSP departures from SoCal approach PSP/Desert sector. In the LOA we give these V386 aircraft to SoCal at 110. When this happens with a PSP departure head on we have to call SoCal and give a restriction to cross Yucca at or above 120. We can also tell SoCal to stop the departure at 100 but there is a MOCA there that they have to climb above it by a certain time and in case of radio failure the best option is to give a restriction. They were flashing an Aircraft Y out of 60 climbing to 130. I called SoCal Springs sector and they would not answer; finally after the third call Controller answers and yells and says 'Unable I'm busy' without letting me tell them the control instruction; so on the shout line I tell Controller 'Aircraft Y cross Yucca at or above 120 if not unable handoff;' and I give my initials. Not knowing if they were going to issue the restriction because I got no response from Controller. I turn my Aircraft X which was requesting direct BLH; but because of restricted airspace R2501 I couldn't give him direct BLH yet. So he wouldn't be head on with the departure I turn him the only way I can; 15 left. I cannot go right cause of the MVA's; and I can't go further left then 15 degrees because of R2501. If he did not make the restriction it would have still been close; but in my mind at least they weren't head on; and it could have been a crash. SoCal Controller then yelled over the land line handoff; and I replied 'I tried giving you a restriction; but you hung up on me.' I told them; 'Unable handoff'. Controller said; 'he was out of 120.' Looking at the tapes he was at YUCCA at 115. He missed the restriction; so I am not sure if they gave him the control instruction or not. Controller was very unprofessional. I said okay then point out Aircraft X at 110 will be direct BLH. I took the handoff on Aircraft Y; and they did not answer me again. So I had to punish the pilot and go back to PSP instead of BLH because Controller was not taking my call on the point out Aircraft X once he cleared R2501. SoCal Controller then was not taking the handoff on him either until finally the controller relieving me called and said 'Handoff Aircraft X'. Then Controller took the handoff. This was a very unprofessional situation. Controller should have had an assistant help or acted more professional. I needed for them to do the control instruction; and Controller was not answering. This kind of behavior should not be allowed and punishes pilots and it makes it a hostile work environment. It should definitely be addressed to Controller. Since Controller is famous for this kind of behavior; but from what I've heard no one addresses Controller because of fear. This is a safety hazard.For the situation to be brought to Controller's attention; and some kind of performance evaluation done.
ZLA Controller describes a situation with a SCT Controller who doesn't take a call from ZLA and then tries to handoff the aircraft. ZLA needed the aircraft to make a restriction and the SCT Controller yelled they were busy. ZLA Controller didn't know if the SCT Controller gave the aircraft the restriction.