Part 107 UAS pilot reported landing as a precaution after realizing they were flying in controlled airspace without authorization.

Narrative

Earlier in the day; I had been operating under an approved FAA authorization to fly within the LAANC approved area at <100 ft. AGL; north of CHA for the purpose of aerial photography. Later that day; I had repositioned west of CHA to continue photographing. I referenced the manufacturer's website which did not show I was in the restricted airspace of CHA. The drone software was still operating under the previous uploaded authorization which allowed me to takeoff off within the surface area Class C airspace. After receiving a notification that I was within the Class C airspace; I landed the aircraft. I confirmed that the class airspace extended over the area in which I was operating via VFR sectional and Aloft/LAANC app. After reviewing the flown flight path; I was able to see that I flew the UAS within an area that was outside of my previous LAANC authorization and that I flew above the 100 ft. AGL (31 ft. higher than the max for that LAANC zone) restriction as I was navigating around wires. The drone app was showing a different overlay of approved flight areas surrounding the CHA Class C.Discovered upon receiving drone notification. Corrected by landing and discontinuing flight in the area.Human factors: Lack of situational awareness. Not doing a thorough job of cross referencing UAS apps and navigational charts. Relying and trusting in equipment that was not fully aware of the situation given outdated information. Future actions: Confirming with sectionals; drone app; and LAANC prior to launching.