Narrative:

VFR flight from ZZZ to ZZZ1. Checked NOTAMS, WX, other relevant information on commercial website and duats DOT communication. Obtained duats briefing, paying attention for NOTAMS and tfrs. Because of stronger than forecast winds. Decided to make an unscheduled fuel stop at ZZZ2. Called unicom 20 to 25 miles out and got no response. Called unicom again and gave position reports numerous times, with no response. Upon landing, notified by FBO at ZZZ2 that a tfr was violated and was given 2 numbers to call, ZZZ center and someone in charge of the tfr. I called both numbers immediately and gave them a full description of the events and planning. Was then told they would file the paperwork. Also, contacted next morning by the FAA. Steps I will take in future: check all available sources in more detail. Check a wider corridor on route to allow for unexpected deviations. Suggestions: add tfrs to electronic sources of navigation information such as my IFR GPS database, which I update every 28 days. Add tfrs to new printed material charts, etc. Encourage unicoms to use their radios. ZZZ2 had a base station, and had ample time to mention the tfr given our radio calls. However, their radio was off, even though the FBO was manned by several people. Note: I believe this tfr was removed 1 day after the violation.

Google
 

Original NASA ASRS Text

Title: SMA PLT FLEW THROUGH TEMPORARY RESTR AIRSPACE DURING AN UNSCHEDULED STOP FOR FUEL AT A NON CTLED ARPT.

Narrative: VFR FLT FROM ZZZ TO ZZZ1. CHKED NOTAMS, WX, OTHER RELEVANT INFO ON COMMERCIAL WEBSITE AND DUATS DOT COM. OBTAINED DUATS BRIEFING, PAYING ATTENTION FOR NOTAMS AND TFRS. BECAUSE OF STRONGER THAN FORECAST WINDS. DECIDED TO MAKE AN UNSCHEDULED FUEL STOP AT ZZZ2. CALLED UNICOM 20 TO 25 MILES OUT AND GOT NO RESPONSE. CALLED UNICOM AGAIN AND GAVE POSITION REPORTS NUMEROUS TIMES, WITH NO RESPONSE. UPON LNDG, NOTIFIED BY FBO AT ZZZ2 THAT A TFR WAS VIOLATED AND WAS GIVEN 2 NUMBERS TO CALL, ZZZ CENTER AND SOMEONE IN CHARGE OF THE TFR. I CALLED BOTH NUMBERS IMMEDIATELY AND GAVE THEM A FULL DESCRIPTION OF THE EVENTS AND PLANNING. WAS THEN TOLD THEY WOULD FILE THE PAPERWORK. ALSO, CONTACTED NEXT MORNING BY THE FAA. STEPS I WILL TAKE IN FUTURE: CHK ALL AVAILABLE SOURCES IN MORE DETAIL. CHK A WIDER CORRIDOR ON ROUTE TO ALLOW FOR UNEXPECTED DEVIATIONS. SUGGESTIONS: ADD TFRS TO ELECTRONIC SOURCES OF NAVIGATION INFO SUCH AS MY IFR GPS DATABASE, WHICH I UPDATE EVERY 28 DAYS. ADD TFRS TO NEW PRINTED MATERIAL CHARTS, ETC. ENCOURAGE UNICOMS TO USE THEIR RADIOS. ZZZ2 HAD A BASE STATION, AND HAD AMPLE TIME TO MENTION THE TFR GIVEN OUR RADIO CALLS. HOWEVER, THEIR RADIO WAS OFF, EVEN THOUGH THE FBO WAS MANNED BY SEVERAL PEOPLE. NOTE: I BELIEVE THIS TFR WAS REMOVED 1 DAY AFTER THE VIOLATION.

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