Hi all,I'm using a 3DRobotics teletry kit and I'm trying to make my 3DR qaudcopter to communicate realtime withMATLAB. Since the telemetry kit has a UART interface, I tried creating a serial object…Continue

Comment Wall

You need to be a member of ArduCopter User Group to add comments!

I will recommend that the feature be enabled by default and operators may go into "Configure tab" and disable from view. I do however feel that it should be automatically turned back on when the operator flies up to 400" AGL and once below that the circles will disappear.

yes that's true perhaps an altitude ceiling be imposed from the data collected for the specific areas reported, the markings would be still there and flight possible but a sort of geofence be applied for altitude in the effected area

NOTAMS etc. while informative are really directed at pilots of full scale aircraft. If we are staying below the 400' ceiling, as I know we all do right, this shouldn't be a problem. I don't want to start a debate here about the legal or ethical issues. As such I'm not going to respond further. I will say however that I agree with the spirit of your statement. It is the responsibility of each individual to be aware of any and all restrictions that effect their ability to fly in the NAS. As such I think having the ability to turn off the markings identifying these zones to be acceptable. It could be made like any GPS device these days. Every time you turn on MP and navigate to an effeted zone the markings are displayed, then you are made aware of the restriction and can act accordingly. It should also be noted that there are two AMA sanctioned club fields in these zones within 25 miles of where Doug lives, he might even be a member of one of them. If model aircraft weren't permitted to fly at all within the zone AMA wouldn't sanction the site.

since they are regulated no fly zones anyway ,by turning off you knowingly break the regulations

just one quote from the link you provided:

PILOTS WHO DO NOT ADHERE TO THE FOLLOWING PROCEDURES MAY BE INTERCEPTED, DETAINED AND INTERVIEWED BY LAW ENFORCEMENT/SECURITY PERSONNEL. ANY OF THE FOLLOWING ADDITIONAL ACTIONS MAY ALSO BE TAKEN AGAINST A PILOT WHO DOES NOT COMPLY WITH THE REQUIREMENTS OR ANY SPECIAL INSTRUCTIONS OR PROCEDURES ANNOUNCED IN THIS NOTAM

Yeah that's what's going on for sure. I looked a bit further and that commit pulls TFR Overlay information from http://www.jepptech.com/tfr/Query.asp?UserID=Public If you go browse that location and read some of the TFRs you will quickly see they correspond with the zones we are now seeing in the MP. Wish I had better news, best raise an issue and lets hope we get the option to turn it off!

I am by no means an expert, however I took a look at the MP code looking for anything that might explain this. What I found may have nothing to do with the situation, however it might be a place to start. About 10 days ago there was a commit that added "TFRs" (TemporaryFlightRestrictions). You can browse this code addition here as well as other history. I see other references recently to TFRs, so I think this is something that the devs have been working on for a while. Hopefully it's just something that made it in to the current release without creating an option to turn it off. I wouldn't be very pleased if I lived in an area that was 'blacked' out by one of these zones.

I don't think there is a way to disable it. You can turn off the airports, but I don't see a way to disable the display of these zones. It's interesting that it doesn't effect the Flight Planning page, just the Flight Data page. That really makes the Flight Data screen unusable for the Baltimore area in the zone.

It is the airport overlay, if you hover your pointer over the red circles they will show you the airport name. Baically to show you when you are close to an airport. You can turn it off in the configuration tab, as detailed in this post: