UAV - Unpiloted Aerial Vehicle
Air Traffic Control Fully Certified
Situational Awareness; Communication Breakdown
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Procedure
A UAV was in the block FL500B650 on a flight. The affected sectors had no prior knowledge of this UAV flying through the airspace and did not receive any specific information on potential lost-link; lost-comm; or route of flight information. I asked the MOS desk if they were aware the flight was transiting our airspace and they informed me that they did not know the flight was occurring and did not have easy access to the control information including pilot phone numbers. In addition; the aircraft type showed a 'ZZZZ.' If we don't know the specific aircraft is a UAV; then it is impossible to know that a lost-link may occur and specifically what routes may be flown should a lost-link occur. After I was off position; I was able to find the information for the flight and I discovered that the route the aircraft flew was also not an approved route. This potentially could put future flights in conflict with other UAV missions in the same vicinity. This event did not cause an OE/OD/etc; but the potential for mishap is great if the needed information is not given to the controllers working the positions. The proponents/users need to ensure coordination with the affected facilities prior to UAV flights. Controllers need to have ready access to lost-link and lost-comm procedures and phone numbers of the remote pilots. ERAM needs to be adapted ideally to show the correct aircraft type but at a minimum ERAM needs to indicate whether an aircraft is a UAV or not.
ZLA Controller voiced concern regarding an UAV operation that was lacking specific operator contact information; ERAM aircraft type designation/s and sector briefings.