Slashdot Mirror
How A Civilian Drone Crashed Into the US Army's Helicopter (arstechnica.com)
"In September, Slashdot reported on an in-flight collision between an Army UA60 helicopter and a hobby drone over Staten Island," writes Slashdot reader ElizabethGreene. "The NTSB has released its final report on the incident, blaming the drone pilot." Ars Technica reports:
After waiting 30 minutes, [drone-owner] Tantashov assumed there had been a mechanical malfunction and that his drone had fallen into the water. He returned home. A week later, Tantashov received a call at work. It was an investigator from the National Transportation Safety Board... Would Tantashov be surprised to learn, the investigator asked, that his drone had not crashed into the water?
And that it had instead slammed into the main rotor of a US Army-operated Sikorsky UH-60M Black Hawk helicopter that was patrolling for the UN General Assembly in Manhattan? And that it had put a 1.5-inch dent in said rotor and led to the helicopter diverting back to its New Jersey base...? As the recently completed NTSB report on the incident puts it, "several [drone] components were lodged in the helicopter."
The drone's serial number was still legible on its motor, and investigators were able to track down its owner by contacting the manufacturer, who'd maintained a record of the sale. The drone's owner said he'd been unaware of "temporary flight restrictions" in effect that night, and "said that he relied on 'the app' to tell him if it was OK to fly." But for two months DJI had disabled the feature that checks for temporary flight restrictions (to perform troubleshooting), and the NTSB notes that that feature "is intended for advisory use only," and it's the responsibility of drone pilots to comply with FAA airspace regulations.
The NTSB also faults the drone's owner for letting it fly out of his line of sight.
And that it had instead slammed into the main rotor of a US Army-operated Sikorsky UH-60M Black Hawk helicopter that was patrolling for the UN General Assembly in Manhattan? And that it had put a 1.5-inch dent in said rotor and led to the helicopter diverting back to its New Jersey base...? As the recently completed NTSB report on the incident puts it, "several [drone] components were lodged in the helicopter."
The drone's serial number was still legible on its motor, and investigators were able to track down its owner by contacting the manufacturer, who'd maintained a record of the sale. The drone's owner said he'd been unaware of "temporary flight restrictions" in effect that night, and "said that he relied on 'the app' to tell him if it was OK to fly." But for two months DJI had disabled the feature that checks for temporary flight restrictions (to perform troubleshooting), and the NTSB notes that that feature "is intended for advisory use only," and it's the responsibility of drone pilots to comply with FAA airspace regulations.
The NTSB also faults the drone's owner for letting it fly out of his line of sight.
How much does a rotor blade on a UH-60M run anyway?
Use a thawed drone.
Ban assault drones!
The drone pilot was indeed an idiot.
The full report shows that he knew about the maximum permitted altitude of 400ft, yet logs showed he flew as high as 547ft 1.8 miles away. He also knew there were frequently helicopters in the area and still flew it 2.5miles away, well out of sight. This is why we can't have nice things.
https://app.ntsb.gov/pdfgenera...
I crashed my Phantom 3 a few years ago and decided it was best to just drop the hobby.
Military physicists have yet to prove that dark shrapnel exists - it's currently just theoretical.
#DeleteChrome
Yeah, that's the only workable path forward since Americans are too lazy to get their shit together and take an extra 5 fucking minutes
I have a drone. I know plenty of other people that have drones. I have NEVER checked for flight restrictions. The software shows "no-fly" areas, some of which are temporary, and I have always just assumed it was doing the job. Nobody I know checks either.
So maybe a mission critical dependence on a bunch of random civilians to be diligent, when there is overwhelming evidence that they are not, isn't such a bright idea.
1. DJI should not have shut off restriction updates.
2. The Army should not have been flying below the drone ceiling.
3. Trying to solve a problem by changing basic human nature is idiotic. You can't expect millions of people to be "not lazy" when YOUR life depends on it.
best solution then is simply to ban drones from people like yourself until such time you prove through training and certification that you are fully aware of the rules and regulations and understand your responsibilities, kinda like getting your drivers license.
Model rockets are in fact governed as aircraft in that one must also adhere to TFRs and other permanent airspace rules. The thing is that the typical Estes hobby rocket's incursion is so fleeting that it doesn't really matter, and the people engaged in this hobby are so comparatively few that they're pretty serious about it, along with handling things like tubes of packed black powder, that they generally don't cause trouble due to their innate sense of responsibility. The high-performance rocketeers even coordinate with the FAA to arrange NOTAMs and even TFRs for their activity so that other users of the airspace are notified and may plan accordingly.
But, I have to say this - your attitude, though, does fit 2 of the 5 Aviation Hazardous Attitudes[1]. Remember, these regulations are *not* about YOU.
Regulations cannot be tailor-made to everyone, and while you inspecting your roof with a drone 20 miles from the nearest airport is in reality a so-what deal, the FAA isn't going to spell out every possible exception to every FAR just to suit every drone-flying nerd in every possible situation. There are people (such as the one TFA is about) who completely flaunt the FARs and don't exercise even basic common sense on top of it. They don't understand that all drone pilots are now sharing airspace with actual aircraft, and thus all occupants of the airspace must play by the same rulebook. This matters most in the most congested airspace, and are largely the target audience of these rules.
We already have stories from around the world where dumbasses are flying their drones along major airport approach and departure paths, with near-misses now being a common report. These rules, as draconian to the non-pilot normies as they may seem, are an attempt to get people to act straight and not do this shit because no one wants to find out the hard way what happens when a drone collides with an aircraft that's on climb-out - an aircraft that might be experiencing a flame-out on one engine due to unrelated problems, only to have a drone get sucked into the one remaining operational one. No one thought USAir 1549 would happen - until it actually did. Same goes for a lot of other accidents, be they mechanical, environmental, or human-caused.
You have a drone, that's great. This also makes you a pilot. I highly suggest that you start thinking like one, and then follow that up with acting like one. Given your missive above, the below link would be a great place to start (and yes, these hazardous attitudes and their antidotes are questions indeed posed on the PPL written exam.)
[1] http://aviationknowledge.wikid...
Firstly you can't ban drones. The genie is out of the bottle and you can't shove it back. While DJI is the largest manufacturer of "ready to fly" drones you can build a drone very cheaply from readily available components. And unless you want to ban Arduinos or raspberry pis there isn't a way to control for the flight controllers, let alone trying to ban brushless motors.
Secondly there is no question that the drone operator was at fault. The reasoning is he flew beyond visual range in an area that has a high amount of manned air traffic. While he was under 400ft at the time of the incident there is still too much air traffic to be flying beyond visual range.
On the flip side though notams are difficult to read if your aren't familiar with the terminology. And accessing the information isn't simple and easy. Drones are not going away. What's more, at some point DJI will lose its dominant position and drones will be controlled by iNav, betaflight, cleanflight, ardupilot or what ever. All of which run on a generic STM chip. Regulation via manufacturer will not be possible either.
Sure, it would be great if people used their brains more. But it aint happening. So steps need to be taken to mitigate risk. CASA, the Australian Civil Aviation Safety Authority, has released an app which contains real time air safety information which drone users can use to check if their location is ok to fly their drone. This should become the standard approach world wide.
Oh, kinda like you can't expect drivers to bother stopping for a red light or checking what the speed limit is?
If it turned out that were temporary, unmarked speed restrictions that drivers could only find at the department of transportation's homepage I imagine there would be quite a few complaints no matter what the letter of the law said. A little googling says there's a free B4UFLY smartphone app that'll tell you of restrictions in place. If the control software isn't updated it wouldn't be unreasonable to "demand" that the user check compliance before taking off. By which I don't mean more than an OK button to push, but then you couldn't claim ignorance of that responsibility. And it would be incentive to fix their updates...
Live today, because you never know what tomorrow brings
There's a difference in the operator of a licensed manned airplane and random guy who picked up a toy at Best Buy on a lark.
Both in terms of training and in terms of incremental difficulty of checking TFR compared to the general involved process of preparing for flying and taking off.
Besides, it's bad enough for accidental interference, but if there *is* something that the patrol would catch, then you have an antagonistic adversary and it would not be a good idea for them to be able to knock out air support with an unarmed drone.
Of course, in this case it was more dramatic presumably because they could afford to be. They had an extra vehicle in the patrol, so they could peel off. Replacing the blade is also because they could afford to, in a more urgent situation they could have probably done other options safely.
XML is like violence. If it doesn't solve the problem, use more.