Narrative:

A tfr was in effect over the foothills north west of the field. I was using in-plane garmin 696 hardware receiving xm satellite updates displaying the graphical depiction of the tfr over a forest fire. I had departed for a one hour VFR flight and was curious if I could see my father-in-laws house which was near the fire. The xm satellite info depicted 12;000 MSL to surface tfr as well as a graphical area hashed in red. I flew over the tfr at 17;500 and circled down to 13;000 near the south eastern corner of the tfr. I was careful to not go below 13;000 in the hashed area I was displaying on the G696 navigator. We descended below 13;000 only after exiting the tfr displayed and landed. I was told to call center by the attendant at the FBO. He informed me center had increased the tfr to 13;000 MSL to surface and the area had increased. Those changes had occurred sometime that morning; he did not specify. I explained the xm satellite information had not updated or did not show the changes during my flight over the tfr; and if they had I would not have inadvertently entered the corner at 13;000 MSL. He explained no harm was done but to be aware that the area had increased in size and altitude for my departure. Upon departure the next day the G696 was showing the tfr larger and at FL180 to surface. He explained he was trying to make sure center was getting info out to all areas of notification; and he wasn't sure why xm was not updated in a timely manner. Next time I will call the local center and verify the tfr parameters before flying over it or near it. Xm information is not always immediate as I had been led to believe.

Google
 

Original NASA ASRS Text

Title: C414 pilot reports inadvertently entering a fire fighting TFR when his G696 with XM does not depict an increase in the dimensions of the airspace that occurs after takeoff.

Narrative: A TFR was in effect over the foothills north west of the field. I was using in-plane Garmin 696 hardware receiving XM satellite updates displaying the graphical depiction of the TFR over a forest fire. I had departed for a one hour VFR flight and was curious if I could see my father-in-laws house which was near the fire. The XM satellite info depicted 12;000 MSL to surface TFR as well as a graphical area hashed in red. I flew over the TFR at 17;500 and circled down to 13;000 near the south eastern corner of the TFR. I was careful to not go below 13;000 in the hashed area I was displaying on the G696 navigator. We descended below 13;000 only after exiting the TFR displayed and landed. I was told to call Center by the attendant at the FBO. He informed me Center had increased the TFR to 13;000 MSL to surface and the area had increased. Those changes had occurred sometime that morning; he did not specify. I explained the XM satellite information had not updated or did not show the changes during my flight over the TFR; and if they had I would not have inadvertently entered the corner at 13;000 MSL. He explained no harm was done but to be aware that the area had increased in size and altitude for my departure. Upon departure the next day the G696 was showing the TFR larger and at FL180 to surface. He explained he was trying to make sure Center was getting info out to all areas of notification; and he wasn't sure why XM was not updated in a timely manner. Next time I will call the local Center and verify the TFR parameters before flying over it or near it. XM information is not always immediate as I had been led to believe.

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.