Pilot reported flying nearby an area of smoke and was unable to find an associated tfr. After the fl...

Attributes
ACN	1760614
Time
Date	202009
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	Direct
Flight Plan	None
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private
Experience	Flight Crew Last 90 Days 22 Flight Crew Total 1366 Flight Crew Type 871
Events
Anomaly	Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy

Narrative:

During a personal flight; I observed smoke associated with a fire; and lots of aerial traffic swarming around that area; according to ads-B. The location of the fire was approximately X NM northwest of ZZZ1; while I was flying a line between ZZZ and ZZZ1. My efb software was not showing a tfr in this location; but did show other tfr's. The activity suggested there was a tfr; so I adjusted my position to be further east. Checking the FAA tfr site on my phone upon landing ZZZ1 showed there was a tfr created since my preflight briefing at home; but before entering the area in the flight. I believe I remained clear; but very close.contributing factors:tfr was created in that window of time between briefing and flight. In-flight data is relied on for these updates; but the tfr did not post in time. ATC has been difficult to get flight following since pandemic made them busier; so I stopped trying for short flights.discovery was recognizing the situation; and corrective action was making room for fire fighting.

Original NASA ASRS Text

Title: Pilot reported flying nearby an area of smoke and was unable to find an associated TFR. After the flight; pilot confirmed a TFR was active but did not post in time on EFB software.

Narrative: During a personal flight; I observed smoke associated with a fire; and lots of aerial traffic swarming around that area; according to ADS-B. The location of the fire was approximately X NM NW of ZZZ1; while I was flying a line between ZZZ and ZZZ1. My EFB software was not showing a TFR in this location; but did show other TFR's. The activity suggested there was a TFR; so I adjusted my position to be further east. Checking the FAA TFR site on my phone upon landing ZZZ1 showed there was a TFR created since my preflight briefing at home; but before entering the area in the flight. I believe I remained clear; but very close.Contributing factors:TFR was created in that window of time between briefing and flight. In-flight data is relied on for these updates; but the TFR did not post in time. ATC has been difficult to get flight following since Pandemic made them busier; so I stopped trying for short flights.Discovery was recognizing the situation; and corrective action was making room for fire fighting.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Pilot reported flying nearby an area of smoke and was unable to find an associated tfr. After the flight; pilot confirmed a tfr was active but did not post in time on efb software.