Skip to main content

FAA can’t regulate small RC aircraft as “drones,” judge rules | Ars Technica

FAA can't regulate small RC aircraft as "drones," judge rules

NTSB judge strikes down $10,000 fine against man for unlicensed "commercial use."

Raphael Pirker prepares to launch his "FPV" remote controlled plane in New York City in a video he posted in 2010.
In 2011, Raphael Pirker used a RiteWing Zephyr II remote-controlled flying wing to record aerial video of a hospital campus for use in a television advertisement. That act resulted in the Federal Aviation Administration issuing a fine to Pirker of $10,000 for that commercial use of an unmanned aircraft. But now an administrative judge with the National Transportation Safety Board has struck down that fine, contending that FAA regulations can't be applied to the styrofoam drone Pirker flew.

Pirker, an Austrian who lives in Hong Kong, is also known as "Trappy" of Team BlackSheep, a company that specializes in creating "first-person view" aerial video with remote-controlled aircraft. In November of 2010, he posted a video filmed from a drone flying over New York City—including a close buzz of the Statue of Liberty. Law enforcement did not interfere with Pirker, and he even gave the New York Police Department and the National Parks Service a shout-out for "staying friendly, professional, and positive." But the FAA was not amused.
The Academy of Model Aeronautics (AMA), which lobbies for "model aviators" and acts as a liaison to the FAA for them, was also taken aback by how close Pirker's remote aircraft—flown in first-person view mode from a distance—came to buildings, ships, bridges, and a national landmark. In a statement for the AMA, spokesperson Rich Hanson said, "The nature of the flight was outside the realm of recreational aeromodeling activity as defined by the AMA Safety Code and posed a significant threat to people and property."

"Trappy" and Team BlackSheep buzz NYC in 2010.
In the case of the Virginia flight, Pirker allegedly flew his styrofoam plane within 100 feet of an active helicopter pad and 20 feet above a crowded street. The FAA claimed one person had to take "evasive maneuvers" to avoid being hit by the plane, and the administration issued its fine for operating the drone "in a careless or reckless manner so as to endanger the life or property of another."
But yesterday, NTSB administrative law judge Patrick Geraghty ruled in favor of Pirker, stating in his decision that at the time Pirker recorded the video, "there was no enforceable FAA rule or [Federal Aviation Regulation], applicable to model aircraft or for classifying model aircraft as [an unmanned aerial system, or drone]." By the FAA's interpretation of regulations, he wrote, "The extension of that conclusion would then result in the risible argument that a flight in the air of… a paper aircraft, or a toy balsa wood glider, could subject the 'operator' to the regulatory provisions of FAA [regulations]."
Ars could not reach Pirker or an FAA spokesperson for comment on the case.
Evernote helps you remember everything and get organized effortlessly. Download Evernote.

Comments

Popular posts from this blog

Setting up the Tarot T4-3D gimbal on the Pixhawk 2.4.8 with Specktrum dx6 Gen2 toggle switch

So i took the challenge of setting up the Tarot gimbal not just for inherent stable video footage but also the flexibility of controlling it from the radio control. However, I encountered quite a few challenges which made me aware that I'm not the one only in this battle . It's quite clear that the setup of the Tarot gimbal using its own software is completely different from how it's been described in the Ardupilot/Arducopter webpage and in mission Planner. In Mission Planner and it's associated site makes one believe that it should be done through software, only to realize that in actual fact the setup is more complex than that.  After two evenings of trying various combinations, I realized the getting the pixhawk Aux channels to communicate with the T4 gimbal requires the following steps: - The Pixhawk Pin9 (Aux1) needed to be activated to pass through user-chosen channel from the transmitter. For the Dx6 Gen2 it was the channel 6, which can assigned the

Matlab to C/C++ code development - Some learning points

Over the last few years, the engineers at the company have invested both their time and sleepless nights in formulating a process for the development of Machine learning algorithms that will satisfy real-time constraints with minimal RAM usage. This is quite a tall task as per default, that would force one to do their development directly in C language. Although that seems like the right choice, the downside is the direct correlation of the debugging time with algorithm complexity.  Such a time could have been rather used in optimizing the algorithm within the MATLAB environment which has excellent tools for the analysis, plotting and debugging. So it was decided to rather learn the Code generation process with the hope that future algorithm could be designed in a similar fashion without the hassle of the compiler-specific run-time issues. The development of this machine learning algorithm would eventually be implemented in a 32bit, 160Mhz speed, 260KB RAM microcontroller.

The hard climb of innovation

For the last couple of months, our design team has been hard at work at detail development of our drone concept which we hope to make public early 2021. These have been unprecedented times with so many changes within our company: people moving countries, stuck at airports, universities closing and transitioning to online classes and exams; all in the space of one year! Nevertheless, one of the fundamental challenges facing the drone industry in developing countries next year, is how to operate within an environment where shipping of critical parts (amongst other things) has been disrupted due to the covid-19 pandemic. If the most critical items (propellers, batteries, sensors, etc. ) of the system are also associated with the longest lead time, this has a significant impact on the operating cost and service coverage that can be achieved. Unfortunately, there's no easy way of solving this issue except if it was envisioned as part of the development process. But this is seldom the ca