Rendered at 21:43:18 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
Bluestrike2 17 hours ago [-]
A couple thoughts:
> Your landing point is 7 ft (2 m) from a 164 ft (50 m)-tall building — taller than drones may fly, so we keep at least 80 ft (25 m) from it.
The numbers are from just clicking a random spot, but I'm kind of confused about how you're interpreting the regulations. In the US, the maximum allowable altitude is 400 feet AGL per § 107.51(b), albeit with a structure exemption for Part 107 pilots. Within a 400 foot radius around a structure, you can fly 400 feet above said structure's maximum height. That drops down to 400 feet AGL the moment you go beyond that radius, however.
Setting aside both the math error with the building height and the structure exemption, what's the basis for the exclusion zone that's being referenced? Granted, you absolutely want horizontal separation near buildings to account for winds that can easily slam a drone into a window, but the error message could imply that your 80 foot clearance is a nonexistent regulatory rule. I'm guessing that's just a conservative safety margin to make flight planning easier, but you should explicitly identify it as such so as to avoid ambiguity or the implication that it's a prescriptive FAA regulation. There's a reason why clarity and precision are so critical in pretty much any aviation document.
Anyhow, it's an interesting concept, one that I could see it being useful in planning but I'd double check some of the altitude logic. I'd also add references to error messages that point to the relevant regulations that trigger the warnings.
What math error with the building's height? Assuming it's what you quoted, 164 ft converts to 49.9872 m so "50 m" seems excellent as the value to present?
Bluestrike2 1 hours ago [-]
I'm assuming that the application first compares building heights to the nominal 400-foot AGL altitude limit: 400-164 equals 236 feet of vertical airspace in which it's legal to fly even before you consider the structure exemption that would permit 564 foot AGL within a 400-foot radius of the building. Calling it a math error was a bit of a misnomer on my part.
I'm still not quite sure what calculation would have a marked location like that as a "no-go," and re-reading the error messages doesn't really clarify the logic. When it says "too tall to clear safely from there" I'm reading that as the building is too tall and thus you can't fly above it, but that's clearly wrong on two levels. Likewise, the building height + 400 feet was still well below the floors of the relevant Class B and Class C airspace shelves around SFO and OAK. Best guess is that the 80 foot exclusion zone around a building the program applies is probably to blame.
There are some other problems I noticed, but I'll send those to the OP via the feedback form on the site.
nimitmehra 16 hours ago [-]
[flagged]
solyin 21 hours ago [-]
Oh you have to hit edit flight to get access to the button. Cool project. Bad UI.
> Your landing point is 7 ft (2 m) from a 164 ft (50 m)-tall building — taller than drones may fly, so we keep at least 80 ft (25 m) from it.
The numbers are from just clicking a random spot, but I'm kind of confused about how you're interpreting the regulations. In the US, the maximum allowable altitude is 400 feet AGL per § 107.51(b), albeit with a structure exemption for Part 107 pilots. Within a 400 foot radius around a structure, you can fly 400 feet above said structure's maximum height. That drops down to 400 feet AGL the moment you go beyond that radius, however.
Setting aside both the math error with the building height and the structure exemption, what's the basis for the exclusion zone that's being referenced? Granted, you absolutely want horizontal separation near buildings to account for winds that can easily slam a drone into a window, but the error message could imply that your 80 foot clearance is a nonexistent regulatory rule. I'm guessing that's just a conservative safety margin to make flight planning easier, but you should explicitly identify it as such so as to avoid ambiguity or the implication that it's a prescriptive FAA regulation. There's a reason why clarity and precision are so critical in pretty much any aviation document.
Anyhow, it's an interesting concept, one that I could see it being useful in planning but I'd double check some of the altitude logic. I'd also add references to error messages that point to the relevant regulations that trigger the warnings.
0. https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F...
1. https://pilotinstitute.com/drone-altitute/
I'm still not quite sure what calculation would have a marked location like that as a "no-go," and re-reading the error messages doesn't really clarify the logic. When it says "too tall to clear safely from there" I'm reading that as the building is too tall and thus you can't fly above it, but that's clearly wrong on two levels. Likewise, the building height + 400 feet was still well below the floors of the relevant Class B and Class C airspace shelves around SFO and OAK. Best guess is that the 80 foot exclusion zone around a building the program applies is probably to blame.
There are some other problems I noticed, but I'll send those to the OP via the feedback form on the site.
I would like to integrate this w/ the agentic state, my email is on profile, please LMK if we can chat.
- TY Arion