Narrative:

Aircraft 1 was a uav and was cleared to delay in the A4 airspace from FL500-590. I observed aircraft 1 maneuvering close to the edge of the boundary for some time. I continued my scan and clearances for other aircraft. When I scanned back to aircraft 1; it was still close to the boundary. As I watched; it got close enough to the edge of the airspace that I alerted the controller in the adjacent sector; the A4 boundary is the same as the sector boundary. I told the controller I didn't think aircraft 1 would be able to turn fast enough to stay in the airspace; and he agreed and said he would block for the aircraft. I waited until aircraft 1 was about 5 miles outside of the airspace; watching to make sure it turned back but it did not. I called aircraft 1 and advised him that I was showing him outside the confines of the airspace he was cleared into and asked him to say his intentions. Aircraft 1 answered that he had meant to get clearance into the tiger north and south airspaces for his return to base; and apologized for the mistake. I coordinated the tiger airspaces with the next sector over; and then got a d-side to help with the rest of the coordination for aircraft 1 and the other traffic in my sector. I don't believe that uav aircraft are safe enough to put in the mix of regular air traffic. I don't think the pilots of these aircraft understand well enough how they affect our operations. I've had a couple uav's deviate from their clearances with no communication at all; and showing a lack of knowledge about the national airspace system and how control instructions and communication work. I think there needs to be more training for everyone involved with the uav flights. I have been told that they want to hire uav pilots that do not have regular pilot's licenses; and I think that will cause even more problems than what we have now.

Google
 

Original NASA ASRS Text

Title: ZMP Controller reports a UAV he is controlling flying out of its designated airspace. When the UAV pilot is contacted he states he meant to get a clearance but forgot.

Narrative: Aircraft 1 was a UAV and was cleared to delay in the A4 airspace from FL500-590. I observed Aircraft 1 maneuvering close to the edge of the boundary for some time. I continued my scan and clearances for other aircraft. When I scanned back to Aircraft 1; it was still close to the boundary. As I watched; it got close enough to the edge of the airspace that I alerted the Controller in the adjacent sector; the A4 boundary is the same as the sector boundary. I told the Controller I didn't think Aircraft 1 would be able to turn fast enough to stay in the airspace; and he agreed and said he would block for the aircraft. I waited until Aircraft 1 was about 5 miles outside of the airspace; watching to make sure it turned back but it did not. I called Aircraft 1 and advised him that I was showing him outside the confines of the airspace he was cleared into and asked him to say his intentions. Aircraft 1 answered that he had meant to get clearance into the Tiger North and South airspaces for his return to base; and apologized for the mistake. I coordinated the Tiger airspaces with the next sector over; and then got a D-Side to help with the rest of the coordination for Aircraft 1 and the other traffic in my sector. I don't believe that UAV aircraft are safe enough to put in the mix of regular air traffic. I don't think the pilots of these aircraft understand well enough how they affect our operations. I've had a couple UAV's deviate from their clearances with no communication at all; and showing a lack of knowledge about the National Airspace System and how control instructions and communication work. I think there needs to be more training for everyone involved with the UAV flights. I have been told that they want to hire UAV pilots that do not have regular pilot's licenses; and I think that will cause even more problems than what we have now.

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.