Small aircraft pilot reports inadvertently entering a tfr and being intercepted by a military aircra...

Narrative:

While flying northeast of palm springs a fighter jet approached very fast flying in front of the plane then circling around several times rocking his wings and trying to get my attention. I knew something was wrong so I searched for radio frequencies that I could use to find out what the problem was; I even looked on the ipad to check for tfr's and did not see any there. Then I heard palm springs control tower tell the aircraft northeast of the airport to turn east immediately and that there was a tfr for 30 miles around palm springs. After turning east I was told to contact control. After several failed attempts trying to contact control; I tried to reach palm springs tower again but could not get anyone. The fighter jet followed me to the east out of the tfr and I did not hear anything else. I had told the tower that the foreflight on the ipad was updated that very morning. But upon returning home I found that the viewing of the tfr feature on the ipad was turned off. The cause of the problem began when I failed to make 100% sure of the settings on the ipad. Something that could be done to prevent this from happening again is using more than one form of information (such as a computer) for planning the flight.

Original NASA ASRS Text

Title: Small aircraft pilot reports inadvertently entering a TFR and being intercepted by a military aircraft. It was discovered that the iPad ForeFlight program had been set to not display TFR's and no other source had been checked prior to flight.

Narrative: While flying northeast of Palm Springs a fighter jet approached very fast flying in front of the plane then circling around several times rocking his wings and trying to get my attention. I knew something was wrong so I searched for radio frequencies that I could use to find out what the problem was; I even looked on the iPad to check for TFR's and did not see any there. Then I heard Palm Springs Control Tower tell the aircraft northeast of the airport to turn east immediately and that there was a TFR for 30 miles around Palm Springs. After turning east I was told to contact Control. After several failed attempts trying to contact Control; I tried to reach Palm Springs Tower again but could not get anyone. The fighter jet followed me to the east out of the TFR and I did not hear anything else. I had told the Tower that the ForeFlight on the iPad was updated that very morning. But upon returning home I found that the viewing of the TFR feature on the iPad was turned off. The cause of the problem began when I failed to make 100% sure of the settings on the iPad. Something that could be done to prevent this from happening again is using more than one form of information (such as a computer) for planning the flight.

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.

Attributes
ACN	1181308
Time
Date	201406
Local Time Of Day	0001-0600
Place
Locale Reference	PSP.Airport
State Reference	CA
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	None
Flight Plan	None
Component
Aircraft Component	Tablet
Person 1
Function	Pilot Flying
Qualification	Flight Crew Commercial
Experience	Flight Crew Last 90 Days 85 Flight Crew Total 1140 Flight Crew Type 450
Events
Anomaly	Airspace Violation All Types Deviation - Procedural Published Material / Policy

Small aircraft pilot reports inadvertently entering a tfr and being intercepted by a military aircraft. It was discovered that the ipad foreflight program had been set to not display tfr's and no other source had been checked prior to flight.