Cary,
The point remains, however, that the FAA has in fact, structured "recommendations" for the operation of "model aircraft", and essentially stated that as long as we operate these devices within those guidelines, they won't take any punitive action. It seems to me that what the Board is saying here is that the respondent in this case operated outside those guidelines, and therefore it is reasonable for the FAA to take enforcement action as "careless and reckless".
While there is indeed discretion here in enforcing the regulations, the discretion is quite clearly spelled out in an Advisory Circular, so that in effect, there really is no discretion....if you operate within these guidelines, we won't enforce the regs....operate outside these guidelines, and you're going to be subject to the full force of the regs.
The question of unmanned or manned is a red herring, in my opinion. As the Board says, and aircraft is an aircraft....it makes no difference if there's a human aboard. A spacecraft carrying a mouse is still a spacecraft, even though it's not carrying a human. And, an umanned aircraft operating in the National Airspace System must operate within all the regulations, including "see and avoid" to protect all the users of the NAS.
The big sticking point, and I suspect the one that is giving the FAA the most heartburn, is how do you ensure separation between a manned aircraft and a drone? See and Avoid simply doesn't work. And, "Sense and avoid" supposedly enabled by ADS-B isn't functional yet. And, it may never be functional, at least in the airspace that many of us operate in.
It's a real conundrum, and I am really happy I'm not the FAA supervisor who's in charge of integrating drones into the NAS. THAT has to be a really shitty job.
MTV