DJI Mavic, Air and Mini Drones
Friendly, Helpful & Knowledgeable Community
Join Us Now

Flying drove over the Pacific - Is the entire Oregon Coast really off-limits?

I knew that. What I was getting at is the statement that there is a restriction from Coos Bay south jetty down to Brandon. I can't find any restriction other than a few state parks. I drone that stretch often as there is no known restrictions.

Cheers!
Sunset Bay State Park runs right up next to the south jetty and then abuts Shore Acres which is right next to Cape Arago. I was eyeballing Sunset Bay State Park since I used to stay at that campground a lot while I was still working (there is no internet or cell service there and no one could call me from work). All three of those parks mention No Drones. I also stayed quite a few nights at the Bullard's Beach and saw the note above. This is what the web page for Facerock State Scenic area shows in their FAQ:

Screenshot 2022-12-21 at 9.13.33 AM.png
 
You are correct about park drone policy there. Sunset Bay sp does not go to the southern jetty, there is Yoakim pt sp and Bastendorf park between Sunset Bay sp and Coos Bay south jetty. Outside of the parks you mentioned there is no drone restrictions between Coos Bay Jetty and Bandon. One can park at the parks and fly on the beach as it is a public highway administrated by ODOT.

Cheers!
 
Interesting - I need to add that back onto my list of places to go. I could launch from the County park and shoot the Cape Arago Lighthouse :)
 
You can ignore most of that. It has been brought to the attention of Oregon department that did this.

We talked about this in a previous newscast.

Check it out here.

Thanks Vic! Kenji and you have summed up the source of the issue and why this bogus wilderness designation is showing up on Aloft and elsewhere. For those interested you can get the info by searching to about 29:40 in the video clip.

Thanks also for noting that various FAA-sanctioned platforms have been opened up for other fed, state, and local agencies to add info… and that some of it is wrong! And is being repeated without verification by some LAANC providers, B4UFLY, etc.

What a mess! This will take a minute to straighten out…

Again, thanks for all you’re doing.
 
So this is all v-e-r-y interesting to me. I have another example where it appears there may have been a massive airspace "closure" or restriction imposed by someone (an ArcGIS employee?) who has no authority to do that and who had no idea what they were doing.

For some context...I've flown around the Pacific Northwest in my little Cessna for decades. I'm very familiar (I think) with all the airspace restrictions in the neighborhood (things change occasionally, but not often). I see one depicted in B4UFLY/Aloft that I believe is wrong -- just like the Oregon Islands Marine Sancuary "wilderness" designation.

The following annotated screenshot from B4UFLY shows the northwest quadrant of Washington state (which happens to be my favorite place to fly my plane). The important bits to note:

The area highlighted in bright red is marked as "Restricted operations" in B4UFLY/Aloft (the app highlights it in a faint red, I've made it bright red to make it easy to see). This airspace is NOT depicted on a sectional chart.

I know, from living and flying around here for decades, what this region actually depicts: these are the waters that are used by the Navy's "Trident" nuclear-missile submarines, as they make their way between their base at Bangor, Washington (see the big blue arrow on the map), and the open ocean (and the world beyond the US territorial waters), at upper left on this map. The US Navy (really!) wants you to stay away from their ships in this area.

boomers_running.jpg

I've see these "boomers" occasionally, coming and going, running on the surface, for years. I keep a respectful distance (and altitude) when flying over (in my plane). They are hard to miss: they're big ships, ominous-looking (each one carries enough nuclear warheads to wipe out a large nation...) and when running on the surface, are escorted by multiple small surface support vessels. I can easily imagine that when I fly by, I'm being watched v-e-r-y carefully. I get it, they are very expensive, strategic military assets, and the people sailing and caring for them take their jobs very seriously (and I'm glad they do, because...nukes). Lots of good reasons for behaving as a responsible adult around them (not the least of which is that they are authorized to use deadly force if they feel it's necessary).

But all the airspace depicted in bright red on that chart is NOT marked as restricted on a sectional or TAC chart (there is a lot of OTHER special use airspace around there that IS on the charts, including some that is obsolete/nonsensical...eg Chinook-A and -B MOAs, which I believe have not been used in 30-40+ years, but that's a bigger/separate question).

This is a little tricky, and to be honest, I don't know what the right depiction should be in this case. The submarines do not go through there every day (and I'm quite sure they do not publish their sailing schedules in advance, for obvious reasons). There are no TFRs issued.

Local (airplane) pilots know about the Trident subs (one of the unusual artifacts of living near one of the largest concentrations of nuclear weapons in the world); everyone I know who flies (airplanes) around here understands you give them some room when you see one running on the surface, but there's no TFR or other restrictions, and nothing on the chart about them. I think it's assumed that local pilots have some "common sense" (or learned behavior that has been transmitted from instructors to student pilots). But, with a much lower "barrier to entry" for drone pilots (only a wave of a credit card needed to get airborne), that kind of knowledge/common-sense transfer does not happen, and I'm not sure what's appropriate.

But I'm pretty sure that this massive swath of airspace that's depicted in B4UFLY/Aloft is NOT restricted, Yet, if you click any spot in that sea of red, you'll get the warning that you need to call the Coast Guard to "coordinate" your flight with them and get an authorization (good luck with THAT!). I bet the Coasties have better things to do.

This looks wrong to me. No?

I can break this out and post a separate thread if appropriate, but I think it is another example of an incorrect classification of airspace that has been made by someone somewhere, and I don't want it it to "stick" (I wonder how many others there are...). Ideally, I'd like to see some kind of less intrusive warning depicted, letting new drone pilots follow a link to learn some basics (eg, ghostrider: stay the hell away from armed warships, if you see any...). But as currently depicted, I read it as a massive airspace restriction that is not correct or appropriate (and may not even be intentional -- ie it's just a "bug" in some GIS system).

Am I wrong?
 
Last edited:
You are correct - this is quite curious. This would likely get a wider discussion audience in a thread of its own and not tucked out of the way in a regional discussion of legal flying areas along the Oregon Coast.

B4UFly seems like it losing credibility in rather short order with the examples we have seen in these cases. Seems like a topic worth further discussion in the wider community.
 
@Aerophile I think you’re missing connecting the phrase “in close proximity to vessels” in your interpretation of what’s stated.

I’m finding what you’re finding in B4UFLY, but reading closely it states: Operators needing to operate in the defined airspace in close proximity to vessels for overriding reasons of public interest or necessity must coordinate…
(bold emphasis added)

If you’re giving deference and lots of clearance to naval vessels piloting your Cessna or drone I read this as an advisory, not an airspace restriction. My opinion only, and I don’t have even a Pt. 61 certificate.

Checking that same area on Airmap (LAANC) only shows an advisory based on the lat/long, with no overlay.
 
@Aerophile I think you’re missing connecting the phrase “in close proximity to vessels” in your interpretation of what’s stated.

I’m finding what you’re finding in B4UFLY, but reading closely it states: Operators needing to operate in the defined airspace in close proximity to vessels for overriding reasons of public interest or necessity must coordinate…
(bold emphasis added)

If you’re giving deference and lots of clearance to naval vessels piloting your Cessna or drone I read this as an advisory, not an airspace restriction. My opinion only, and I don’t have even a Pt. 61 certificate.

Checking that same area on Airmap (LAANC) only shows an advisory based on the lat/long, with no overlay.
No argument on that. Though it does show this...

restricted_ops.jpg
What's a reasonable interpretation of that symbol? As someone who has worked professionally in user experience, I would hope that symbols convey their intended message quickly, "at a glance."

Yes, the large text says "Restricted" rather than "prohibited" (though that's also what the large text says about the Oregon Islands wilderness designation - and the "fine print" for that does say "drones are prohibited in all wilderness areas").

Maybe there need to be more granular depictions, more symbols: if it's a "restriction" (rather than a "prohibition"), don't use the same "no drone" icon, don't use the red banner.

Worth considering: there's lots of different symbology on aeronautical charts depicting the multiple kinds of "special use airspace" - maybe B4UFLY needs to have more nuanced ways of depicting things. Yes, I know, it needs to be kept simple, too (personally, I LOVE sectional charts, think they are beautiful and wonderful tools that convey such dense, complex data and make it quick and easy to interpret at a glance....but I understand not every drone owner shares my fetish for maps...).

But to the original, and I think still valid, larger point: we are seeing examples where B4UFLY gets (big) things wrong, or at least fails to provide good, appropriate information. Is B4UFLY set up to be successful, or does it need some better way to vet the information (fact-checkers) and depict/present it the best way it can? I dunno, but I'm guessing there are lots of other places where it falls short of what some of us expect from it (and yes, I understand, maybe we just need to lower our expectations of it as a tool...which is kind of sad).
 
Last edited:
No argument on that. Through it does show this...

View attachment 158576
What's a reasonable interpretation of that symbol? As someone who has worked professionally in user experience, I would hope that symbols convey their intended message quickly, "at a glance."

Yes, the large text says "Restricted" rather than "prohibited" (though that's also what the large text says about the Oregon Islands wilderness designation - and the "fine print" for that does say "drones are prohibited in all wilderness areas").

Maybe there need to be more granular depictions, more symbols: if it's a "restriction" (rather than a "prohibition"), don't use the same "no drone" icon, don't use the red banner.

Worth considering: there's lots of different symbology on aeronautical charts depicting the multiple kinds of "special use airspace" - maybe B4UFLY needs to have more nuanced ways of depicting things. Yes, I know, it needs to be kept simple, too (personally, I LOVE sectional charts, think they are beautiful and wonderful tools that convey such dense, complex data and make it quick and easy to interpret at a glance....but I understand not every drone owner shares my fetish for maps...).

But to the original, and I think still valid, larger point: we are seeing examples where B4UFLY gets (big) things wrong, or at least fails to provide good, appropriate information. Is B4UFLY set up to be successful, or does it need some better way to vet the information (fact-checkers) and depict/present it the best way it can? I dunno, but I'm guessing there are lots of other places where it falls short of what some of us expect from it (and yes, I understand, maybe we just need to lower our expectations of it as a tool...which is kind of sad).
I have to agree with @Aerophile on every point!

I guess the biggest concern for me is that inaccurate info is being distributed on FAA-sanctioned channels. We were used to not finding complete info in any one single place.

It’s great that we now seem to be on the road to one single multi-jurisdictional gov source… BUT, untrustworthy info is way too high a price to pay, it will only lead to loss of reputation and credibility which will nullify the benefits of having a single source.

(Single source other than DJI FlySafe/Geozones that is)
 
Last edited:
Wow, interesting thread ... but it makes me want to return my drone for a refund.

I got certified, have all the correct licensing and even have my FAA reflective yellow drone jacket and my drone tagged with license ID and have my Remote IDs. But when I simply wanted to go to the Oregon coast (Seaside or Cannon or close proximity), I find this thread and now I don't trust any of the apps (especially B4UFLY) nor FAA charts and have NO IDEA if any area along the Oregon coast is actually legal to fly?

I even called Cape Meares National Wildlife and left a message (nobody home I guess).

Reading this thread (be it almost a year old) has left me incredibly discouraged. I have no interest in disturbing wildlife (any where at any time) but it seems restrictions are so ad-hoc and inconsistent as to make it a risk to fly a drone anywhere.

B4UFLY, if I click on what I know now is a restricted location it comes back and says "Clear for Takeoff" ... which I know is false.

EDIT: I have a Mini 4 Pro (<250g) but that really doesn't matter much for local restrictions.

Rob.
 

DJI Drone Deals

New Threads

Forum statistics

Threads
131,138
Messages
1,560,273
Members
160,109
Latest member
brokerman