Part 107 UAS pilot reported learning the Remote ID Broadcast Module stopped operating for an unknown amount of time during the flight.

Date: 2025-01 · Aircraft: DJI Mini 2 · Phase: landing

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-unauthorized-flight-operations-uas

Synopsis

Part 107 UAS pilot reported learning the Remote ID Broadcast Module stopped operating for an unknown amount of time during the flight.

Narrative

While performing flight; my DroneTag Beacon cease to operate. It was fully charge with all of my equipment before I departed for the flight. Preflight checks were good. Beacon confirmed to have GPS lock prior to launch. Upon return; all indications were black. Device would not activate or even indicate charge level when button was push. I do not know how much of the flight was without RID (Remote ID). Upon return to home; I searched the web for answers. Suggestion was to press and hold button for 15 seconds. At 10 seconds; device activated. Device had full charge still. Used DroneTag toolbox app to troubleshoot; but no indication of an issue. Device was able to obtain full GPS lock with location verified through app. Only deviation noted was that there was a firmware update available. I performed the update; but the device was functioning properly without the update. I have no idea why it failed in flight. It was very cold; about 33 degrees at the time of flight. That is the only possible cause that I can imagine; other than software glitch.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.