Narrative:

I planned and executed a round trip flight. This path takes one very close to the sba class C airspace; and in this case directly through a firefighting tfr. I use the foreflight program on an ipad to monitor my position very closely to ensure I do not violate the class C airspace. Before I left my home I checked metar and tafs for both airports and then checked the currency of the foreflight program. When it linked to the internet it showed 44 downloads required. Since I knew that would take about 30 minutes; I allowed the relevant files (airport database; all california charts and data) to download; pausing the chart files from other states. This took about 15 minutes of connection time; during which I assumed critical information like tfrs would be updated; since these do not require manual download (foreflight tech support subsequently verified that tfrs should have been immediately updated). I then proceeded with the flight. My standard display on foreflight is VFR chart with tfrs displayed; as was the case on this day. At no time during my flight was the tfr in question displayed on my ipad. I was therefore completely unaware of its existence as I flew directly through it. After being informed of my transgression by sba approach I took the ipad home to ascertain why the tfr was not displayed; checking to see if I had the display set up correctly. It was. After just a couple of minutes of connection to the wifi; the tfr popped up on the screen. Why the ipad had not updated during the previous wifi session is unknown (tech support could provide no explanation). I am a professional pilot with 34 years of military; commercial and general aviation experience. I take flying and safety very seriously. I had followed thorough and customary flight planning procedures; but a tiny technical glitch deprived me of vital information of which I was unaware. Although tech support has subsequently informed me how to verify the currency of tfr data; there is no discussion in the foreflight manual on how to do this.

Related reports:

Google
 

Original NASA ASRS Text

Title: An RV-6A pilot; utilizing an iPad for navigation on a VFR cross country entered a TFR enroute despite his belief the tablet had been properly updated to display restricted airspace immediately prior to his departure.

Narrative: I planned and executed a round trip flight. This path takes one very close to the SBA Class C airspace; and in this case directly through a firefighting TFR. I use the Foreflight program on an iPad to monitor my position very closely to ensure I do not violate the Class C airspace. Before I left my home I checked METAR and TAFs for both airports and then checked the currency of the Foreflight program. When it linked to the internet it showed 44 downloads required. Since I knew that would take about 30 minutes; I allowed the relevant files (airport database; all California charts and data) to download; pausing the chart files from other states. This took about 15 minutes of connection time; during which I assumed critical information like TFRs would be updated; since these do not require manual download (Foreflight tech support subsequently verified that TFRs should have been immediately updated). I then proceeded with the flight. My standard display on Foreflight is VFR chart with TFRs displayed; as was the case on this day. At no time during my flight was the TFR in question displayed on my iPad. I was therefore completely unaware of its existence as I flew directly through it. After being informed of my transgression by SBA Approach I took the iPad home to ascertain why the TFR was not displayed; checking to see if I had the display set up correctly. It was. After just a couple of minutes of connection to the WiFi; the TFR popped up on the screen. Why the iPad had not updated during the previous WiFi session is unknown (tech support could provide no explanation). I am a professional pilot with 34 years of military; commercial and general aviation experience. I take flying and safety very seriously. I had followed thorough and customary flight planning procedures; but a tiny technical glitch deprived me of vital information of which I was unaware. Although tech support has subsequently informed me how to verify the currency of TFR data; there is no discussion in the Foreflight manual on how to do this.

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.