UAV - Unpiloted Aerial Vehicle
Air Traffic Control Fully Certified
Communication Breakdown; Situational Awareness
ATC Issue All Types
General None Reported / Taken
Human Factors; Procedure
I was working ZLA33/32 and had just also combined with ZLA34. One of the pieces of traffic that the Controller working ZLA34 gave me was a UAV operating 510B600. I asked the Supervisor for the mission paperwork and noticed that the pre-coordinated flight plan paperwork showed that the aircraft should have been operating 510B590. As part of the briefing from Sector 34; I was also told about a balloon operating above FL600. I looked at that map and noticed the flight plan was proposed to be in approximately the same location as the UAV flight. I asked the Supervisor to call the provided number to have the balloon flight begin a squawk so we could see the balloon location. We observed the balloon code pop up less than 8 miles from the UAV. Although this did not result in a loss of separation; the potential was definitely present. The UAV flight should not have been allowed to operate in an altitude not previously coordinated. In addition it is unclear if operating at 510B600 gives a UAV permission to operate above FL600. The balloon flights should be required to continually squawk a code with an altitude readout for improved ATC planning.
ZLA Controller voiced concern regarding a potential conflict between a balloon operation conducted an operating transponder and a UAV with less than clear altitude parameters.