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

Remote ID sub 250g used for rec and 107

I'm one of those ones who use the images from my mini-2 for commercial purposes. I do not do business that requires clients to hire me but I do take some wicked good "art" photographs (attached is Long Pond in Belvidere Vermont) And because I have this up for sale, this mission is a part 107 mission. EVERY mission I take off with the mini 2 is a Part 107 because while it is wildly FUN to fly... IT IS NOT a recreational flight because my intent is to make a dollar or two from my images... So this summer (2023) I am looking at buying a Mavic 3 (some variant) so RID will be built in. I simply do not want to buy a 200-300$ add-on just to be able to use my images for sales.
This isn't commercial in the sense of drone delivery which is an entirely different part 135. Intent may have something with most laws, but I really don't understand what intent of flight has to do with drone regulations.
 
Something else that I noticed, the difference between the details of what a Drone with built-in "Standard Remote ID Drones" & a "Remote ID Broadcast Module" equipped Drone:

So for example, is a Drone with a built-in module not subject to VLS?

What about Control Station Location and Elevation?

What about Emergency Status?

1682332320183.png
 
Last edited:
Something else that I noticed, the difference between the details of what a Drone with built-in "Standard Remote ID Drones" & a "Remote ID Broadcast Module" equipped Drone:

So for example, is a Drone with a built-in module not subject to VLS?

What about Control Station Location and Elevation?

What about Emergency Status?

View attachment 163010
Supposedly the built in module will be compliant for when they allow bvlos whereas the others won't. What difference that makes I don't know. Somebody just went to sleep and woke up. Eureka! Remote id is the solution in need of a problem. Let's get the faa to strong arm everyone into having to have it in order to operate.
 
Thank God these FAA drone rules are so concise and easy to understand and comply with.
Would you like the Reader's Digest compressed version? It's 15 pages longer and still doesn't make it any easier to understand. They scrambled to get some rules slapped together and now it makes no sense to anyone. One size fits nothing.
 
Something else that I noticed, the difference between the details of what a Drone with built-in "Standard Remote ID Drones" & a "Remote ID Broadcast Module" equipped Drone:

So for example, is a Drone with a built-in module not subject to VLS?

What about Control Station Location and Elevation?

What about Emergency Status?
Drones with native remote ID will be eligible for BVLOS waivers as mentioned before. Doesn't mean that VLOS rules don't apply, just that simply put, you can apply for a waiver. You can't get a waiver for BVLOS with an attached RID module type of compliance.
 
Drones with native remote ID will be eligible for BVLOS waivers as mentioned before. Doesn't mean that VLOS rules don't apply, just that simply put, you can apply for a waiver. You can't get a waiver for BVLOS with an attached RID module type of compliance.
I don't understand what the remote ID module provides that allows for BVLOS. It misses any function to provide that, as being it is only for LEOs to identify a drone, but not for BVLOS flight.
 
I don't understand what the remote ID module provides that allows for BVLOS. It misses any function to provide that, as being it is only for LEOs to identify a drone, but not for BVLOS flight.
Native RemoteID can provide live update of the drone's status as well as the pilot's position. RID Module doesn't know what the status of the drone is, and only knows the take off position of the drone but not the up to date controller position.

So if for example a drone is flying a few miles away, doing something it shouldn't, they would have a live position of the pilot itself, not just where they took off from. (they don't know if you're BVLOS or not if you're using a module, so if you're not within the immediate vicinity, you are likely flying BVLOS).

It's probably setting up for the eventual push for networked remote ID.
 
Native RemoteID can provide live update of the drone's status as well as the pilot's position. RID Module doesn't know what the status of the drone is, and only knows the take off position of the drone but not the up to date controller position.

So if for example a drone is flying a few miles away, doing something it shouldn't, they would have a live position of the pilot itself, not just where they took off from. (they don't know if you're BVLOS or not if you're using a module, so if you're not within the immediate vicinity, you are likely flying BVLOS).

It's probably setting up for the eventual push for networked remote ID.
They started off with Network Remote ID, and some countries are still going to go with that, but here in the states, it got shot down for logistical reasons. And when you think about it, if you're out in the middle of nowhere where there is no cell coverage, you most likely don't need to call in. There's nothing out there, but because they couldn't get network remote ID, they want broadcast to broadcast everywhere regardless. So, no it really isn't necessary to have network remote ID, there wasn't enough reason for it anyhow. It's another one of those bite my tongue to spite my face situations, as government typically doesn't use a reasonable approach to everything. They just want non stop surveillance on all activities all the time without a court ordered warrant. As if it is going to deter crime.

But Remote ID wasn't created with BVLOS in mind, and they need scrap remote ID until they get the security and safety actually into focus as the purpose of requiring it in the first place. It's a waste of money in the current implementation IMHO. The government has deviated from the rules to push more draconian measures.
 
They started off with Network Remote ID, and some countries are still going to go with that, but here in the states, it got shot down for logistical reasons. And when you think about it, if you're out in the middle of nowhere where there is no cell coverage, you most likely don't need to call in. There's nothing out there, but because they couldn't get network remote ID, they want broadcast to broadcast everywhere regardless. So, no it really isn't necessary to have network remote ID, there wasn't enough reason for it anyhow. It's another one of those bite my tongue to spite my face situations, as government typically doesn't use a reasonable approach to everything. They just want non stop surveillance on all activities all the time without a court ordered warrant. As if it is going to deter crime.

But Remote ID wasn't created with BVLOS in mind, and they need scrap remote ID until they get the security and safety actually into focus as the purpose of requiring it in the first place. It's a waste of money in the current implementation IMHO. The government has deviated from the rules to push more draconian measures.
Gonna need to push congress more to accomplish that rather than pushing at the FAA.
 
Gonna need to push congress more to accomplish that rather than pushing at the FAA.
I'm not getting any responses from Congress. They are scratching their heads trying to figure out what we are talking about. They are pandering to the LEOs who are paranoid about drones.
 
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Reauthorization for 2023 coming out. Looks like they are only concerned with part 135 operations, for BVLOS, they're going to need UTM/network remote ID. So maybe the cat is out of the bag, that we are being subjected to this drone delivery mania.

Sure, your sub 250g isn't going to be a problem. We'll just wipe that bug off our windshield.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Ty,

On another point, I don't know whether a drone that was registered one way (Rec or Com) can be re-registered. I don't know where I saw it, so I can't provide a link, but I'm pretty sure I read on an FAA document, that once a drone is registered, it cannot be changed.

If you (or anyone) can prove or disprove this, please provide the link. I'd really like to know for sure.
Your drone can be "re-registered." I just did it at the suggestion of a well-known pilot. I unregistered my Mini 2 under part 107 and re-registered it under Recreational.
 

Attachments

  • Screenshot 2023-08-29 102040.jpg
    Screenshot 2023-08-29 102040.jpg
    677.6 KB · Views: 4
  • Screenshot 2023-08-29 103005.jpg
    Screenshot 2023-08-29 103005.jpg
    468.2 KB · Views: 4

DJI Drone Deals

New Threads

Forum statistics

Threads
134,633
Messages
1,597,083
Members
163,126
Latest member
Dandoloriom
Want to Remove this Ad? Simply login or create a free account