Narrative:

I planned a VFR flight from maryland (to virginia) in a single engine aircraft. I obtained a WX briefing, but did not file a flight plan. The WX was not a factor with ceiling greater than 10000 ft AGL and greater than 10 miles visibility. I had not made a north to south flight in the dc area since prior to 09/tue/02. I was aware of many temporary flight restrs in the area and obtained recent NOTAMS as posted in the FBO prior to departure. I had a recent tac and sectional which has been published since 09/tue/02, showing no restr for VFR pilots over dc other than class B airspace. A VFR corridor was still present on the published chart between regan national and dulles international, so I made the mistake of assuming that was current information. Because it was a VFR day, I did not contact washington approach as I was not in their airspace according to the chart. I arrival at my destination without incident. Two days later I departure for home with the same flight plan. I obtained WX from the internet and checked for change to NOTAMS. I proceeded through the published VFR corridor without contacting washington approach and landed at my destination around XA00 eastern time. Upon landing, I was asked to contact washington approach and informed that I had violated a temporary flight restr around washington. After having the tfr area explained to me, I do not contest that I clearly violated that airspace. The problem arose from poor judgement and lack of communication with washington approach. I had the appropriate information making me aware of the tfr, but I misinterpreted the information. I made the mistake of basing my decisions on the published charts, not realizing that the temporary flight restrs took precedence over the published information.

Related reports:

Google
 

Original NASA ASRS Text

Title: A SMA PLT VIOLATED A TFR INVOLVING ENHANCED CLASS B AIRSPACE.

Narrative: I PLANNED A VFR FLT FROM MARYLAND (TO VIRGINIA) IN A SINGLE ENGINE ACFT. I OBTAINED A WX BRIEFING, BUT DID NOT FILE A FLT PLAN. THE WX WAS NOT A FACTOR WITH CEILING GREATER THAN 10000 FT AGL AND GREATER THAN 10 MILES VISIBILITY. I HAD NOT MADE A N TO S FLT IN THE DC AREA SINCE PRIOR TO 09/TUE/02. I WAS AWARE OF MANY TEMPORARY FLT RESTRS IN THE AREA AND OBTAINED RECENT NOTAMS AS POSTED IN THE FBO PRIOR TO DEP. I HAD A RECENT TAC AND SECTIONAL WHICH HAS BEEN PUBLISHED SINCE 09/TUE/02, SHOWING NO RESTR FOR VFR PLTS OVER DC OTHER THAN CLASS B AIRSPACE. A VFR CORRIDOR WAS STILL PRESENT ON THE PUBLISHED CHART BETWEEN REGAN NATL AND DULLES INTL, SO I MADE THE MISTAKE OF ASSUMING THAT WAS CURRENT INFO. BECAUSE IT WAS A VFR DAY, I DID NOT CONTACT WASHINGTON APCH AS I WAS NOT IN THEIR AIRSPACE ACCORDING TO THE CHART. I ARR AT MY DEST WITHOUT INCIDENT. TWO DAYS LATER I DEP FOR HOME WITH THE SAME FLT PLAN. I OBTAINED WX FROM THE INTERNET AND CHKED FOR CHANGE TO NOTAMS. I PROCEEDED THROUGH THE PUBLISHED VFR CORRIDOR WITHOUT CONTACTING WASHINGTON APCH AND LANDED AT MY DEST AROUND XA00 EASTERN TIME. UPON LNDG, I WAS ASKED TO CONTACT WASHINGTON APCH AND INFORMED THAT I HAD VIOLATED A TEMPORARY FLT RESTR AROUND WASHINGTON. AFTER HAVING THE TFR AREA EXPLAINED TO ME, I DO NOT CONTEST THAT I CLEARLY VIOLATED THAT AIRSPACE. THE PROB AROSE FROM POOR JUDGEMENT AND LACK OF COM WITH WASHINGTON APCH. I HAD THE APPROPRIATE INFO MAKING ME AWARE OF THE TFR, BUT I MISINTERPRETED THE INFO. I MADE THE MISTAKE OF BASING MY DECISIONS ON THE PUBLISHED CHARTS, NOT REALIZING THAT THE TEMPORARY FLT RESTRS TOOK PRECEDENCE OVER THE PUBLISHED INFO.

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.