Narrative:

Flight VFR from teb to gai, receiving advisories as is my practice VFR. I had made this flight IFR or VFR possibly 40 times in last 10 yrs. While receiving advisories from baltimore approach, their radar went down. Conditions at the field per baltimore ATIS were IFR due to 2 1/2 mi visibility. Conditions in the area were 20-30 mi visibility. I could see fog and haze to the east, low to the ground in the area of the airport. I was advised by ATC to remain clear of the TCA, and I acknowledged. I remained at 4500' and continued LORAN direct still squawking discrete code while I checked my NOAA VFR chart. I believed I would pass 15 NM west of baltimore at 4500' and would remain clear of the arsa. When baltimore approach got their radar back. I was admonished by the controller for remaining in the TCA and was told to remain clear. Still on discrete advisory squawk. I replied, 'heading 270 and descending to remain clear.' confused, I checked my VFR chart and realized it was 2 weeks out of date. Upon landing, I purchased a new NOAA VFR washington chart and discovered that I was in a newly created TCA for baltimore, instead of being 5 NM west of and 500' over the old arsa. Although I was in good VFR and never saw another aircraft during the incident, I clearly had the responsibility to be aware of this new TCA. I will go back to mail subscription for my charts to ensure timely receipt of new ones, and will check those in the aircraft more regularly for currency.

Related reports:

Google
 

Original NASA ASRS Text

Title: PLT OF SMA ENTERED NEWLY CREATED TCA IN DCA AREA.

Narrative: FLT VFR FROM TEB TO GAI, RECEIVING ADVISORIES AS IS MY PRACTICE VFR. I HAD MADE THIS FLT IFR OR VFR POSSIBLY 40 TIMES IN LAST 10 YRS. WHILE RECEIVING ADVISORIES FROM BALTIMORE APCH, THEIR RADAR WENT DOWN. CONDITIONS AT THE FIELD PER BALTIMORE ATIS WERE IFR DUE TO 2 1/2 MI VISIBILITY. CONDITIONS IN THE AREA WERE 20-30 MI VISIBILITY. I COULD SEE FOG AND HAZE TO THE E, LOW TO THE GND IN THE AREA OF THE ARPT. I WAS ADVISED BY ATC TO REMAIN CLR OF THE TCA, AND I ACKNOWLEDGED. I REMAINED AT 4500' AND CONTINUED LORAN DIRECT STILL SQUAWKING DISCRETE CODE WHILE I CHKED MY NOAA VFR CHART. I BELIEVED I WOULD PASS 15 NM W OF BALTIMORE AT 4500' AND WOULD REMAIN CLR OF THE ARSA. WHEN BALTIMORE APCH GOT THEIR RADAR BACK. I WAS ADMONISHED BY THE CTLR FOR REMAINING IN THE TCA AND WAS TOLD TO REMAIN CLR. STILL ON DISCRETE ADVISORY SQUAWK. I REPLIED, 'HDG 270 AND DSNDING TO REMAIN CLR.' CONFUSED, I CHKED MY VFR CHART AND REALIZED IT WAS 2 WKS OUT OF DATE. UPON LNDG, I PURCHASED A NEW NOAA VFR WASHINGTON CHART AND DISCOVERED THAT I WAS IN A NEWLY CREATED TCA FOR BALTIMORE, INSTEAD OF BEING 5 NM W OF AND 500' OVER THE OLD ARSA. ALTHOUGH I WAS IN GOOD VFR AND NEVER SAW ANOTHER ACFT DURING THE INCIDENT, I CLEARLY HAD THE RESPONSIBILITY TO BE AWARE OF THIS NEW TCA. I WILL GO BACK TO MAIL SUBSCRIPTION FOR MY CHARTS TO ENSURE TIMELY RECEIPT OF NEW ONES, AND WILL CHK THOSE IN THE ACFT MORE REGULARLY FOR CURRENCY.

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.