GA pilot reported being informed after landing that he had flown through a tfr over mco that he was ...

Narrative:

I piloted my aircraft; overflying the orlando international airport (mco) class B airspace at 10;500 feet. I was flying VFR (squawking 1200); I did not file the optional VFR flight plan; and I did not use VFR flight following as I have made several similar flights in the past and was familiar with the route. I did not call flight services to check for temporary flight restrictions (tfrs) because I am on auto-distribution for tfrs via my e-mail address.upon landing at sef; I was met by the airport manager; who informed me that I had violated a presidential tfr (18;000 feet and 30 NM) over orlando. Mortified; I spoke with an FAA representative over the phone and provided him with all the requested information. I explained to the FAA representative that I rely on tfr notifications via e-mail; and I did not receive a tfr notification for orlando. I also explained that I am very sensitive to tfr and sfra incursions given that I am based in northern virginia. I did ask why jets were not scrambled to intercept me; and he explained that it was because I flew absolutely straight and level over the entire orlando class B airspace without any deviation; whatsoever. He explained that it was obvious; given the extent of the tfr incursion (46 minutes in duration) and the slow speed of my aircraft; that I was unaware of the tfr and likely not an immediate threat. Had I deviated anything (altitude; direction or squawk code); I would have been intercepted.upon checking into the hotel; I searched for the orlando tfr online and could not find any record of it. I screen-captured the following four (4) tfrs for florida:1) 10/2016: air show in jacksonville; fl from 11/2016 - 11/2016.2) 10/2016: air show in stuart; fl from 11/2016 - 11/2016.3) 10/2016: air show in homestead arb; fl from 10/2016 to 11/2016.4) 10/2016: security tfr over disney world (permanent).I then spoke with a colleague whose father is a pilot. Her father searched and also could not find any presidential tfr published for orlando for that date. I went back and reviewed the following presidential tfrs that I did receive via e-mail for the weeks prior and following:1) 10/2016: unspecified - dayton; oh on 10/2016 (no map)2) 10/2016: 30NMR/10NMR - raleigh; nc on 11/2016 (no map)3) 10/2016: unspecified - rock hill; sc / charlotte; nc on 11/16 (no map)4) 10/2016: 10/30 nmr - greensboro; nc on 11/16 (no map)5) 10/2016: 10/30 nmr - columbus; oh on 11/16 (no map)6) 10/2016: 10NMR - raleigh/durham; nc on 11/16 (with map)7) 11/2016: 10NMR/32NMR - charlotte; nc on 11/16 (no map)8) 11/2016: 32NMR/10NMR - fayetteville; nc on 11/16 (no map)because I never received notification of the presidential tfr over orlando; fl; I wonder if there is a radius-based filter on the tfr notifications that I receive from the FAA. It is obvious that I don't receive tfr notifications for california; but since I receive tfr notifications for as far north as boston; I made the false presumption that I would receive them for the entire east coast. I am sickened that I made such an avoidable mistake; and it has been an absolute wake-up call for me.

Original NASA ASRS Text

Title: GA pilot reported being informed after landing that he had flown through a TFR over MCO that he was not aware of. He had relied on TFR notifications via e-mail which he did not receive and no record of the TFR could be found on the FAA website.

Narrative: I piloted my aircraft; overflying the Orlando International Airport (MCO) Class B airspace at 10;500 feet. I was flying VFR (squawking 1200); I did not file the optional VFR flight plan; and I did not use VFR flight following as I have made several similar flights in the past and was familiar with the route. I did not call flight services to check for Temporary Flight Restrictions (TFRs) because I am on auto-distribution for TFRs via my e-mail address.Upon landing at SEF; I was met by the airport manager; who informed me that I had violated a presidential TFR (18;000 feet and 30 NM) over Orlando. Mortified; I spoke with an FAA representative over the phone and provided him with all the requested information. I explained to the FAA representative that I rely on TFR notifications via e-mail; and I did not receive a TFR notification for Orlando. I also explained that I am very sensitive to TFR and SFRA incursions given that I am based in Northern Virginia. I did ask why jets were not scrambled to intercept me; and he explained that it was because I flew absolutely straight and level over the entire Orlando Class B airspace without any deviation; whatsoever. He explained that it was obvious; given the extent of the TFR incursion (46 minutes in duration) and the slow speed of my aircraft; that I was unaware of the TFR and likely not an immediate threat. Had I deviated anything (altitude; direction or squawk code); I would have been intercepted.Upon checking into the hotel; I searched for the Orlando TFR online and could not find any record of it. I screen-captured the following four (4) TFRs for Florida:1) 10/2016: Air Show in Jacksonville; FL from 11/2016 - 11/2016.2) 10/2016: Air Show in Stuart; FL from 11/2016 - 11/2016.3) 10/2016: Air Show in Homestead ARB; FL from 10/2016 to 11/2016.4) 10/2016: Security TFR over Disney World (permanent).I then spoke with a colleague whose father is a pilot. Her father searched and also could not find any presidential TFR published for Orlando for that date. I went back and reviewed the following presidential TFRs that I did receive via e-mail for the weeks prior and following:1) 10/2016: unspecified - Dayton; OH on 10/2016 (no map)2) 10/2016: 30NMR/10NMR - Raleigh; NC on 11/2016 (no map)3) 10/2016: unspecified - Rock Hill; SC / Charlotte; NC on 11/16 (no map)4) 10/2016: 10/30 NMR - Greensboro; NC on 11/16 (no map)5) 10/2016: 10/30 NMR - Columbus; OH on 11/16 (no map)6) 10/2016: 10NMR - Raleigh/Durham; NC on 11/16 (with map)7) 11/2016: 10NMR/32NMR - Charlotte; NC on 11/16 (no map)8) 11/2016: 32NMR/10NMR - Fayetteville; NC on 11/16 (no map)Because I never received notification of the presidential TFR over Orlando; FL; I wonder if there is a radius-based filter on the TFR notifications that I receive from the FAA. It is obvious that I don't receive TFR notifications for California; but since I receive TFR notifications for as far north as Boston; I made the false presumption that I would receive them for the entire East Coast. I am sickened that I made such an avoidable mistake; and it has been an absolute wake-up call for me.

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.

Attributes
ACN	1399126
Time
Date	201610
Local Time Of Day	1801-2400
Place
Locale Reference	MCO.Airport
State Reference	FL
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Small Aircraft High Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Direct
Flight Plan	None
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private
Experience	Flight Crew Last 90 Days 46 Flight Crew Total 1272 Flight Crew Type 1253
Events
Anomaly	Airspace Violation All Types Deviation - Procedural FAR

GA pilot reported being informed after landing that he had flown through a tfr over mco that he was not aware of. He had relied on tfr notifications via e-mail which he did not receive and no record of the tfr could be found on the FAA website.