Flight Crew Last 90 Days 15; Flight Crew Total 300; Flight Crew Type 300
Communication Breakdown; Other / Unknown
Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert
Aircraft; Procedure; Human Factors
I departed HAO and flew direct to RID on a VFR flight. I thought I was departing just prior to the presidential TFR which I believed to be starting in 15 minutes. My plan was to fly out of the TFR stop in Richmond for 30 minutes and then fly to Port Columbus to pick up a passenger. Unfortunately I was mistaken on the TFR start time either due to a change or an error on my part but the TFR went into effect 2 minutes before I departed. I was asked upon landing at RID to call the FAA which I did. I then took off and flew with VFR flight following to Port Columbus. Unfortunately the AWOS at HAO and LUK that I checked via phone prior to departure did not have any special NOTAMs for the TFR prior to my departure. In addition my Garmin 496 must have been delayed with the data feed because I only saw the TFR pop up on my display as I was leaving the TFR.
General Aviation pilot reports discovering airborne via his Garmin 496 that a TFR had gone into effect 15 minutes earlier than expected. NOTAMs were not checked directly just prior to departure; relying instead on local AWOS.