Narrative:

I received WX briefing and filed IFR from a to B. I also filed a return IFR flight plan for B to C. After an uneventful flight to B, I decided to cancel my return IFR flight plan and file VFR, as the WX was acceptable and I felt I could get better winds at the lower altitude VFR permitted. I filed the VFR flight plan with FSS via the 800 number at about XA40. Filed flight plan was direct, with initial cruise altitude of 5500 ft. No mention was made of the tfr. I opened my flight plan via radio over the ZZZ VOR. I flew back VFR first at 5500 ft to clear xy airspace, and then descended to 3500 ft. I flew via the published corridor at 3500 ft with transponder code. I closed my flight plan with FSS after clearing the corridor to the south, and continued my descent to a landing at C. It was then I was asked to call approach. I had flown this route to B on friday in VFR, and returned from B to a on VFR saturday. Both times I had verbal briefing with FSS. On returning home, I reviewed the briefing more carefully, and found the tfr in the fdc NOTAMS section, separate from the numerous tfr's for the nuclear power plants and enhanced class B restrs. I should have seen it. I also believe that this information should be more prominently placed, perhaps in the NOTAMS associated with the airways and facilities related to the flight. How could this be avoided in the future? 1. A more careful reading of all the briefing. The data was there, just lost to my awareness in the clutter of the fdc NOTAM page. 2. Perhaps all the tfr's could be put in the same area of the fdc NOTAMS, or have a separate section of tfr's. 3. Clearly, using flight following would have alerted me to this earlier. 4. Always talk to a briefer before the flight. They have a better feel for which NOTAMS affect your specific flight. 5. Always file IFR or use flight following.

Related reports:

Google
 

Original NASA ASRS Text

Title: A PA-32 CFI VIOLATES A TFR DURING HIS VFR FLT USING A CORRIDOR WITH A XPONDER CODE NEAR ZZZ, U.S.

Narrative: I RECEIVED WX BRIEFING AND FILED IFR FROM A TO B. I ALSO FILED A RETURN IFR FLT PLAN FOR B TO C. AFTER AN UNEVENTFUL FLT TO B, I DECIDED TO CANCEL MY RETURN IFR FLT PLAN AND FILE VFR, AS THE WX WAS ACCEPTABLE AND I FELT I COULD GET BETTER WINDS AT THE LOWER ALT VFR PERMITTED. I FILED THE VFR FLT PLAN WITH FSS VIA THE 800 NUMBER AT ABOUT XA40. FILED FLT PLAN WAS DIRECT, WITH INITIAL CRUISE ALT OF 5500 FT. NO MENTION WAS MADE OF THE TFR. I OPENED MY FLT PLAN VIA RADIO OVER THE ZZZ VOR. I FLEW BACK VFR FIRST AT 5500 FT TO CLR XY AIRSPACE, AND THEN DSNDED TO 3500 FT. I FLEW VIA THE PUBLISHED CORRIDOR AT 3500 FT WITH XPONDER CODE. I CLOSED MY FLT PLAN WITH FSS AFTER CLEARING THE CORRIDOR TO THE S, AND CONTINUED MY DSCNT TO A LNDG AT C. IT WAS THEN I WAS ASKED TO CALL APCH. I HAD FLOWN THIS RTE TO B ON FRIDAY IN VFR, AND RETURNED FROM B TO A ON VFR SATURDAY. BOTH TIMES I HAD VERBAL BRIEFING WITH FSS. ON RETURNING HOME, I REVIEWED THE BRIEFING MORE CAREFULLY, AND FOUND THE TFR IN THE FDC NOTAMS SECTION, SEPARATE FROM THE NUMEROUS TFR'S FOR THE NUCLEAR POWER PLANTS AND ENHANCED CLASS B RESTRS. I SHOULD HAVE SEEN IT. I ALSO BELIEVE THAT THIS INFO SHOULD BE MORE PROMINENTLY PLACED, PERHAPS IN THE NOTAMS ASSOCIATED WITH THE AIRWAYS AND FACILITIES RELATED TO THE FLT. HOW COULD THIS BE AVOIDED IN THE FUTURE? 1. A MORE CAREFUL READING OF ALL THE BRIEFING. THE DATA WAS THERE, JUST LOST TO MY AWARENESS IN THE CLUTTER OF THE FDC NOTAM PAGE. 2. PERHAPS ALL THE TFR'S COULD BE PUT IN THE SAME AREA OF THE FDC NOTAMS, OR HAVE A SEPARATE SECTION OF TFR'S. 3. CLEARLY, USING FLT FOLLOWING WOULD HAVE ALERTED ME TO THIS EARLIER. 4. ALWAYS TALK TO A BRIEFER BEFORE THE FLT. THEY HAVE A BETTER FEEL FOR WHICH NOTAMS AFFECT YOUR SPECIFIC FLT. 5. ALWAYS FILE IFR OR USE FLT FOLLOWING.

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.