Narrative:

I planned to depart bridgeport; ct and fly VFR to [virginia] approximately xa:30. My preflight preparation for this VFR flight was to review the weather; NOTAMS and tfr's for the continuation of my day which began approximately [5 hours earlier]. I relied on foreflight for data for winds and notams. I also relied on foreflight for information on tfrs. I noted that a tfr surrounding newark (ewr) that could affect my route of flight. The tfr was shown to begin at xc:00 and I calculated that I would be well though that area prior to the tfr becoming effective.I departed bdr and flew a heading of 250 degrees and climbed to 2;500. Upon reaching 2;500; I contacted ny approach for flight following direct westchester county and was given a squawk code. I informed ny approach of my intentions to fly the hudson river corridor. Ten miles from hpn; I was handed off to the tower for transition through their class D airspace. Upon passing over hpn; I informed the controllers of my intention to turn south over the hudson and fly the corridor. Hpn tower discontinued flight following as I exited the class D airspace to the west. During the period from departing bdr and turning south over the hudson; I was tracking my location; progress and the only tfr shown on foreflight. Neither ny approach nor hpn asked if I was familiar with the tfr along my announced route of flight.I reported at the alpine tower and the george washington bridge on 123.05. Just south of the gwb; I was contacted by teterboro tower and was told to return to bridgeport and call ny TRACON. I immediately complied with headings; altitude and destination and called ny TRACON immediately upon my return to bdr. I spoke with the supervisor and much to my surprise and concern learned that I had violated a tfr. I am an ATP; have over 2;800 hours and am working toward an instructor rating. I knew well enough to be concerned. I was shocked because the operative tfr was not on foreflight. To substantiate the mismatch between the tfr and the information on foreflight; I took a screenshot at time xb:37. I can provide the screen shot for support of my belief that foreflight information was incomplete and I that I had briefed myself appropriately. The larger tfr was just not displayed.I believe that it is reasonable to rely on foreflight for tfrs and reasonably expect it to display in a timely manner. In addition; I do not believe that it was unreasonable to expect two separate contacts with ATC to point out that a tfr exists when certain violation appears likely.

Related reports:

Google
 

Original NASA ASRS Text

Title: General aviation pilot reported entering a TFR that was not displayed on his Foreflight app. Flight following was being used at the time and no warning of the TFR was given until the reporter was told to turn around; return to his departure airport; and contact NY TRACON upon landing.

Narrative: I planned to depart Bridgeport; CT and fly VFR to [Virginia] approximately XA:30. My preflight preparation for this VFR flight was to review the weather; NOTAMS and TFR's for the continuation of my day which began approximately [5 hours earlier]. I relied on Foreflight for data for winds and NOTAMs. I also relied on ForeFlight for information on TFRs. I noted that a TFR surrounding Newark (EWR) that could affect my route of flight. The TFR was shown to begin at XC:00 and I calculated that I would be well though that area prior to the TFR becoming effective.I departed BDR and flew a heading of 250 degrees and climbed to 2;500. Upon reaching 2;500; I contacted NY Approach for flight following direct Westchester County and was given a squawk code. I informed NY Approach of my intentions to fly the Hudson River corridor. Ten miles from HPN; I was handed off to the tower for transition through their Class D airspace. Upon passing over HPN; I informed the controllers of my intention to turn south over the Hudson and fly the corridor. HPN tower discontinued flight following as I exited the Class D airspace to the west. During the period from departing BDR and turning south over the Hudson; I was tracking my location; progress and the only TFR shown on Foreflight. Neither NY approach nor HPN asked if I was familiar with the TFR along my announced route of flight.I reported at the Alpine tower and the George Washington Bridge on 123.05. Just south of the GWB; I was contacted by Teterboro Tower and was told to return to Bridgeport and call NY TRACON. I immediately complied with headings; altitude and destination and called NY TRACON immediately upon my return to BDR. I spoke with the supervisor and much to my surprise and concern learned that I had violated a TFR. I am an ATP; have over 2;800 hours and am working toward an instructor rating. I knew well enough to be concerned. I was shocked because the operative TFR was not on ForeFlight. To substantiate the mismatch between the TFR and the information on Foreflight; I took a screenshot at time XB:37. I can provide the screen shot for support of my belief that ForeFlight information was incomplete and I that I had briefed myself appropriately. The larger TFR was just not displayed.I believe that it is reasonable to rely on ForeFlight for TFRs and reasonably expect it to display in a timely manner. In addition; I do not believe that it was unreasonable to expect two separate contacts with ATC to point out that a TFR exists when certain violation appears likely.

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