Aerial survey pilot reports discovering airborne that a firefighting tfr exists in his area that is ...

Narrative:

During my pre-flight for my survey mission I checked tfr's that may be a factor via my ipad and the foreflight app. Nothing was found. Foreflight says they update tfr information direct from the FAA every 15 minutes. I then flew from the pvu airport towards my photo site. During the climb I saw nothing that resembled a fire in the area. As it turns out there was a firefighting tfr right off my left side surface to 12;000 MSL. I missed it by about 3 miles; maybe a little less. I only missed this tfr by luck; since I had not yet reached an altitude where I felt I could reach salt lake center I did not have a flight following. I worked my photo mission and on my way back to pvu ATC asked me if I was aware of the tfr ahead of me. He helped me avoid it on the way in. I feel a lesson can be learned from this. Tfr's appear out of nowhere without much warning. Foreflight is a great tool however from now on I will take the extra few minutes to call a briefer and make sure the areas I am working in contain no sudden tfr's. The tfr finally appeared on foreflight nearly 45 minutes after I landed; it had been in effect for nearly 7 hours at that point.

Original NASA ASRS Text

Title: Aerial Survey pilot reports discovering airborne that a firefighting TFR exists in his area that is not displayed on his iPad with a Foreflight application. Notam's were not checked prior to flight and the TFR did not appear on the iPad until seven hours after it had been activated.

Narrative: During my pre-flight for my survey mission I checked TFR's that may be a factor via my iPad and the ForeFlight App. Nothing was found. Foreflight says they update TFR information direct from the FAA every 15 minutes. I then flew from the PVU airport towards my photo site. During the climb I saw nothing that resembled a fire in the area. As it turns out there was a firefighting TFR right off my left side surface to 12;000 MSL. I missed it by about 3 miles; maybe a little less. I only missed this TFR by luck; since I had not yet reached an altitude where I felt I could reach Salt Lake Center I did not have a flight following. I worked my photo mission and on my way back to PVU ATC asked me if I was aware of the TFR ahead of me. He helped me avoid it on the way in. I feel a lesson can be learned from this. TFR's appear out of nowhere without much warning. Foreflight is a great tool however from now on I will take the extra few minutes to call a briefer and make sure the areas I am working in contain no sudden TFR's. The TFR finally appeared on Foreflight nearly 45 minutes after I landed; it had been in effect for nearly 7 hours at that point.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	1102259
Time
Date	201307
Local Time Of Day	0601-1200
Place
Locale Reference	PVU.Airport
State Reference	UT
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 2 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Climb
Flight Plan	None
Component
Aircraft Component	Tablet
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 1450 Flight Crew Type 400
Events
Anomaly	Deviation - Procedural Other / Unknown

Aerial survey pilot reports discovering airborne that a firefighting tfr exists in his area that is not displayed on his ipad with a foreflight application. Notam's were not checked prior to flight and the tfr did not appear on the ipad until seven hours after it had been activated.