Part 107 UAS pilot reported flying in a TFR without authorization.

Narrative

I; as the single pilot of the UAS failed to check for TFR prior to launching drone to fly a preprogrammed survey route over a construction site which I have flown a few times previously. I flew my UAS briefly into restricted airspace but landed the drone within a couple of minutes of learning the details of the TFR which I had violated I overrode the built-in automatic lockout feature on my Phantom 4 RTK drone as I have done many times previously to allow the drone to fly. Typically the GPS automatic lockout provided by DJI as part of the command and control software is not super precise and is more a of a 2D feature; often automatically blocking flights that are near but not technically inside or below restricted airspace. I incorrectly assumed that this lockout was the same issue on this flight as all of the others I have ever had. However as the drone was climbing to the pattern height; I did check the TFR notice that was provided by the software and saw that it was something unusual and it was for a VIP in town and extended from the ground all the way to 18;000 feet. So I landed the drone immediately and did not complete the survey. I did not attempt to relaunch after that and terminated my planned flights for the rest of the day.I explained what happened to my bother; and he recommended that I file this incident report. As a result of this incident I have downloaded a new app to my phone - b4ufly application so that I can check TFRs and NOTAMs right before I fly and not rely solely on my initial airspace checks and previous flight experience at each site. I do not expect this to ever happen again and I apologize for my mistake.