I like the concept, but altitude matters. Airport control areas are like an inverted layer cake:
<a href="http://upload.wikimedia.org/wikipedia/commons/f/f2/Airspace_classes_(United_States).gif" rel="nofollow">http://upload.wikimedia.org/wikipedia/commons/f/f2/Airspace_...</a><p>It would be nice to add a feature to drone navigation software to prevent accidental entry into an exclusion zone.
I would not trust this map, since after doing a 10 seconds check of the airspace that I am personally familiar with I have noticed that restricted area R-2531 above Lawrence Livermore Lab is not marked. Who knows what else they have missed and what sources they are basing their data on.
Some guy in my neighbor occasionally play with motor helicopter in his backyard and it happens to be in no fly zone. Should I call polices to get him arrested?
I just usually use <a href="http://vfrmap.com/" rel="nofollow">http://vfrmap.com/</a> but for those unfamiliar with the charts and even for those who are, this probably provides an interesting and easier breakdown.
Interesting but a bit silly, thus landing it in credibility buster territory for anyone who puts a moment of thought into it. Take Boise as an example. Within the five mile radius is downtown Boise. On any given day guess how many planes fly at a low altitude over the downtown corridor? That's right, zero. They all stick to a southerly route over mostly dessert.