Narrative:

I was on my flight from ZZZ to ZZZ1. Prior to departing from ZZZ airport I obtained a WX update from the local FBO. I did not get a flight brief from FSS and therefore was not aware of the new tfr for restr area. Prior to departure I called the clearance delivery and stated my intended route ZZZ direct ZZZ1 and altitude, 3000 ft. The controller made no mention of the tfr affecting ZZZ1. I departed ZZZ and made a GPS direct trip to ZZZ1, avoiding controlled airspace along the way. The approach and landing were uneventful, to ZZZ1 the next day when filing an IFR flight plan from ZZ1 to ZZZ2 I saw the NOTAM on the WX briefing report. That is when I realized the possible violation. The only possible way I can see to avoid this in the future, especially because of the latest events, is to always get a complete briefing, I know I certainly will.

Google
 

Original NASA ASRS Text

Title: A SMA PLT VIOLATED A TFR INVOLVING A GOVERNMENT FAC.

Narrative: I WAS ON MY FLT FROM ZZZ TO ZZZ1. PRIOR TO DEPARTING FROM ZZZ ARPT I OBTAINED A WX UPDATE FROM THE LCL FBO. I DID NOT GET A FLT BRIEF FROM FSS AND THEREFORE WAS NOT AWARE OF THE NEW TFR FOR RESTR AREA. PRIOR TO DEP I CALLED THE CLRNC DELIVERY AND STATED MY INTENDED RTE ZZZ DIRECT ZZZ1 AND ALT, 3000 FT. THE CTLR MADE NO MENTION OF THE TFR AFFECTING ZZZ1. I DEPARTED ZZZ AND MADE A GPS DIRECT TRIP TO ZZZ1, AVOIDING CONTROLLED AIRSPACE ALONG THE WAY. THE APCH AND LNDG WERE UNEVENTFUL, TO ZZZ1 THE NEXT DAY WHEN FILING AN IFR FLT PLAN FROM ZZ1 TO ZZZ2 I SAW THE NOTAM ON THE WX BRIEFING RPT. THAT IS WHEN I REALIZED THE POSSIBLE VIOLATION. THE ONLY POSSIBLE WAY I CAN SEE TO AVOID THIS IN THE FUTURE, ESPECIALLY BECAUSE OF THE LATEST EVENTS, IS TO ALWAYS GET A COMPLETE BRIEFING, I KNOW I CERTAINLY WILL.

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.