Narrative:

I departed ldj for a flight to ZZZ. Having not been able to contact ewr tower from the ground due to poor radio reception at ldj; I departed with the intent to clear the traffic pattern to the south; circle and contact ewr tower from the air; where reception might be better. At approximately 1000 ft MSL and 1.5 mi south of ldj; I was able to contact ewr tower to get flight following through and around the new york class B airspace. The controller informed me that I was about to enter or had entered a tfr (an apparent police action lasting 3 hours). I responded that I had not heard about it and he gave me a vector to exit the tfr area. He then continued to vector me through the hudson river VFR corridor. After the flts; I called FSS to get information on the tfr and was informed that they were not advising pilots about it until it had almost expired because of the slowness in the way they get tfr information. The briefer cited an occurrence that same day where he failed to inform a different pilot about the same tfr; even though it was technically 'in effect.' contributing factors: no information was available about the tfr on the duats or FAA website due to the immediate nature of the tfr and slowness of the posting system. FSS was not advising pilots about the tfr until after it went into effect due to the slowness in the way they get tfr information. Neither new york approach nor ewr tower advised me of the tfr as I was inbound to ldj. Perhaps they did not know of it at that time either. Had I been able to contact ewr tower on the ground at ldj prior to departure; they might have informed me of the tfr; though they did not advise me on my way in. Corrective actions: I should call FSS prior to departing all legs of a flight. Even though; in this case; I would still not have been informed about the tfr; I would have been considered 'compliant.'

Google
 

Original NASA ASRS Text

Title: C177 PLT INADVERTENTLY ENCROACHES ON A RAPIDLY IMPLEMENTED LAW ENFORCEMENT TFR WHILE DEPARTING FROM UNCONTROLLED AIRPORT.

Narrative: I DEPARTED LDJ FOR A FLT TO ZZZ. HAVING NOT BEEN ABLE TO CONTACT EWR TWR FROM THE GND DUE TO POOR RADIO RECEPTION AT LDJ; I DEPARTED WITH THE INTENT TO CLEAR THE TFC PATTERN TO THE S; CIRCLE AND CONTACT EWR TWR FROM THE AIR; WHERE RECEPTION MIGHT BE BETTER. AT APPROX 1000 FT MSL AND 1.5 MI S OF LDJ; I WAS ABLE TO CONTACT EWR TWR TO GET FLT FOLLOWING THROUGH AND AROUND THE NEW YORK CLASS B AIRSPACE. THE CTLR INFORMED ME THAT I WAS ABOUT TO ENTER OR HAD ENTERED A TFR (AN APPARENT POLICE ACTION LASTING 3 HRS). I RESPONDED THAT I HAD NOT HEARD ABOUT IT AND HE GAVE ME A VECTOR TO EXIT THE TFR AREA. HE THEN CONTINUED TO VECTOR ME THROUGH THE HUDSON RIVER VFR CORRIDOR. AFTER THE FLTS; I CALLED FSS TO GET INFO ON THE TFR AND WAS INFORMED THAT THEY WERE NOT ADVISING PLTS ABOUT IT UNTIL IT HAD ALMOST EXPIRED BECAUSE OF THE SLOWNESS IN THE WAY THEY GET TFR INFO. THE BRIEFER CITED AN OCCURRENCE THAT SAME DAY WHERE HE FAILED TO INFORM A DIFFERENT PLT ABOUT THE SAME TFR; EVEN THOUGH IT WAS TECHNICALLY 'IN EFFECT.' CONTRIBUTING FACTORS: NO INFO WAS AVAILABLE ABOUT THE TFR ON THE DUATS OR FAA WEBSITE DUE TO THE IMMEDIATE NATURE OF THE TFR AND SLOWNESS OF THE POSTING SYS. FSS WAS NOT ADVISING PLTS ABOUT THE TFR UNTIL AFTER IT WENT INTO EFFECT DUE TO THE SLOWNESS IN THE WAY THEY GET TFR INFO. NEITHER NEW YORK APCH NOR EWR TWR ADVISED ME OF THE TFR AS I WAS INBOUND TO LDJ. PERHAPS THEY DID NOT KNOW OF IT AT THAT TIME EITHER. HAD I BEEN ABLE TO CONTACT EWR TWR ON THE GND AT LDJ PRIOR TO DEP; THEY MIGHT HAVE INFORMED ME OF THE TFR; THOUGH THEY DID NOT ADVISE ME ON MY WAY IN. CORRECTIVE ACTIONS: I SHOULD CALL FSS PRIOR TO DEPARTING ALL LEGS OF A FLT. EVEN THOUGH; IN THIS CASE; I WOULD STILL NOT HAVE BEEN INFORMED ABOUT THE TFR; I WOULD HAVE BEEN CONSIDERED 'COMPLIANT.'

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