Part 107 UAS pilot reported an issue with the approved time of a LAANC authorization. The pilot flew the mission during a time when he did not have LAANC authorization.

Date: 2022-06 · Aircraft: DJI Phantom 4 Pro · Phase: takeoff

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

Synopsis

Part 107 UAS pilot reported an issue with the approved time of a LAANC authorization. The pilot flew the mission during a time when he did not have LAANC authorization.

Narrative

I made a LAANC request on a Samsung tablet through AirMap for approval to fly a drone between XA:52 p.m. and XB:52 p.m. Local Time with 200 feet altitude limitation. This was for a building inspection mission; flying close to a church building. The flight was close to and below the height of the building and no other air traffic nearby. Days before the flight; I received an authorization message; but did not notice until days after the mission; that it listed times as XC:52 UTC - XD:52 UTC; and that the UTC time did not correspond to my request which was made on 12 hour style display interface. This approval message maybe used wrong time in messaging; but actually was responding to the time I requested. Because I had not requested a later flight and there would have been issues getting approval for the later time. Such as twilight flight lighting equipment requirements; which I had stated in the LAANC application I was not using for these flights. Also a stadium was being used later that evening. I checked the settings on the tablet and it has a setting to automatically use the network provided time; which in ZZZ is Local Time. The time displayed on the device was Local Time; including on a small information bar above the AirMap map display (although that is probably provided by the Android system; not AirMap). But the time zone selection setting in the tablet was [another time zone]. The Android tablet does not use that setting in its clock and displays when it is set to automatically use the network provided time. But apparently AirMap was picking up on that time at least for some uses; even though Android system said the network provided time Local Time was being used. I have since reset the device time zone to Central Daylight Time to avoid any confusion. When I changed the time zone on the tablet; it had no effect on the time displayed. The tablet was still using the same network provided time Local Time. I did find a screen later in AirMap with a reference to the tablet time zone. And I noticed the time defaulted to that time in the time setting; but it did not flag the time as the same or different from the automatic setting in the tablet Android system.I am sorry for the confusion. I think AirMap should coordinate better with the Android time system settings.

NASA callback

The reporter had no additional information to share.

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