Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Remote Pilot (UAS); Flight Crew Commercial
Flight Crew Last 90 Days (UAS) 100; Flight Crew Total 3500; Flight Crew Total (UAS) 1500; Flight Crew Type (UAS) 200
Workload; Situational Awareness; Confusion
Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS)
General None Reported / Taken
Chart Or Publication; Environment - Non Weather Related; Human Factors; Software and Automation
I had been operating the UAS from early morning through approximately XA:00 am; providing news coverage of the tornado disaster in City; State. I had been checking periodically for TFR's using Foreflight on my cell phone and none were being imposed. I resumed flying at approximately XC:00 and again checked for TFR's using the same method.Upon returning to the hotel that evening I checked again when online as I was preparing for flights the next day and also to see if a VIP TFR may be upcoming; and saw to my surprise that a TFR had been imposed for the area that I had been flying in that took effect at XB:30 that day. I do not know why it did not appear on Foreflight other than I was in an area of poor cell coverage and perhaps the map loaded but the application was not communicating for updates. In the future when doubt is cast on the reliability of internet based mapping applications; a phone call to FSS is in order. Then there is no doubt.
Reporter had no additional information to share.
Part 107 UAS pilot was flying in an area of a natural disaster. Prior to the flight the UAS pilot checked for NOTAMs/TFRs and saw none. Reporter learned during post flight that they flew in a TFR that had been created after takeoff.