General aviation pilot reports discovering airborne via his garmin 496 that a tfr had gone into effe...

Attributes
ACN	1024909
Time
Date	201207
Local Time Of Day	0601-1200
Place
Locale Reference	HAO.Airport
State Reference	OH
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	Direct
Flight Plan	VFR
Component
Aircraft Component	GPS & Other Satellite Navigation
Person 1
Function	Pilot Flying Single Pilot
Experience	Flight Crew Last 90 Days 15 Flight Crew Total 300 Flight Crew Type 300
Events
Anomaly	Aircraft Equipment Problem Less Severe Airspace Violation All Types Deviation - Procedural Published Material / Policy

Narrative:

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.

Original NASA ASRS Text

Title: 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.

Narrative: 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.

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

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.