Narrative:

Upon entering the office to pay the landing fee; I was told to call TRACON that I violated a tfr. Earlier that morning I obtained duats briefing online and NOTAMS are listed at the end of the duats session and this tfr did not appear. I spoke to someone in the office who also said they did not see this NOTAM. Additionally; I get email notification from a pilot website concerning tfr's and I did not get an email about this one. Someone in the office also indicated they did not as well. The unicom office started looking for a tfr notice and found something for south hampton and it said 'no airports affected.' after learning of this I started searching for information and found an airspace NOTAM for hto which said; 'airspace see flight data center;' with a link to a phone number which was out of service. A search of the FAA website for the issue date days earlier; which is when this tfr was issued results in no such tfr. At the time of this writing I have been thus far unable to find any more information about this tfr. I believe this tfr violation occurred because the tfr was poorly published.

Google
 

Original NASA ASRS Text

Title: VFR pilot is told to call TRACON after landing for a possible TFR violation. No information can be found concerning the TFR in question.

Narrative: Upon entering the office to pay the landing fee; I was told to call TRACON that I violated a TFR. Earlier that morning I obtained DUATS briefing online and NOTAMS are listed at the end of the DUATS session and this TFR did not appear. I spoke to someone in the office who also said they did not see this NOTAM. Additionally; I get email notification from a pilot website concerning TFR's and I did not get an email about this one. Someone in the office also indicated they did not as well. The Unicom office started looking for a TFR notice and found something for South Hampton and it said 'no airports affected.' After learning of this I started searching for information and found an airspace NOTAM for HTO which said; 'airspace see flight data center;' with a link to a phone number which was out of service. A search of the FAA website for the issue date days earlier; which is when this TFR was issued results in no such TFR. At the time of this writing I have been thus far unable to find any more information about this TFR. I believe this TFR violation occurred because the TFR was poorly published.

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