DJI's Avata is has been approved by the FAA as 'in compliance' with Remote ID. Late last week, the Federal Aviation Ad...

Remote ID for drones pushed back to December, but a few DJI models are already compliant

DJI's Avata is has been approved by the FAA as 'in compliance' with Remote ID.

Late last week, the Federal Aviation Administration (FAA) announced through the Federal Register that Remote ID compliance for drones has been pushed back from this Friday, September 16th, to December 16, 2022. This August 11th announcement filing means that manufacturers have more time to test and develop unmanned aircraft and modules that meet Remote ID standards.

Remote ID, which will enable a drone to broadcast its location and the operator's identity to law enforcement officials, as well as the public, has been a hotly debated topic since its notice of proposed rulemaking (NPRM) was first released at the end of 2019. Well over 50,000 comments were submitted and a lawsuit was subsequently filed against the FAA.

While privacy concerns have arisen, Remote ID, if implemented properly, will allow for more complex drone operations including flights over people and beyond visual line of sight (BVLOS). The FAA acknowledges that preparing for this transition is complex, hence the additional time frame given to become compliant near the end of this year.

Even with the extension, there are already several models, primarily from DJI, that have been approved by the FAA for compliance with Remote ID. These include:

Basically, drone manufacturers are expected to comply with Remote ID requirements by September 16, 2022. However, the FAA isn't expected to take action against anyone who doesn't meet standards until December 16th. By September 16, 2023, only drones that meet Remote ID requirements, or are flown in FRIAs (FAA-recognized Identification Areas), or weigh less than 250g and are used for recreational purposes will be considered compliant and legal to operate.



from Articles: Digital Photography Review (dpreview.com) https://ift.tt/CoHXq3n
via IFTTT

0 comments: