Part 107 UAS pilot reported they inadvertently flew above 400 AGL for a few moments. Upon realizing the error; they descended.

Date: 2024-06 · Aircraft: Small UAS (At or above 0.55 lbs and less than 55 lbs) · Phase: climb

Anomalies: airspace-violation-all-types|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-unauthorized-flight-operations-uas|deviation-discrepancy-procedural-published-material-policy

Synopsis

Part 107 UAS pilot reported they inadvertently flew above 400 AGL for a few moments. Upon realizing the error; they descended.

Narrative

On day 0 at XA:54; I was the PIC of a UAS using DroneSense as the operating software. It was a training mission for familiarization with the UAS platform. The flight took place in ZZZ and was operated in class G airspace. Weather conditions were overcast with light rain. It was my first flight utilizing the UAS and I was not aware the AGL restrictions placed in the DroneSense operating software did not function with the UAS platform. My AGL restriction was set to 394ft AGL. During the operation I inadvertently operated the UAS into a climb to 667ft AGL. This occurred because; I relied on the operating software to stop my UAS platform at the set AGL restriction and I was observing my camera feed during the climb. My VO notified me that the UAS looked above 400ft AGL. I immediately check the AGL and brought the UAS platform below 400ft AGL. The UAS was operated above 400ft AGL from XB:02 to XB:04; with the max AGL of 667ft occurring at XB:03. This operation did not interfere with any other aircraft in the area.

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