Helicopter pilot reports discovering after landing that he had been operating in a tfr. A 496 garmin...

Attributes
ACN	1087345
Time
Date	201305
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Eurocopter AS 350/355/EC130 - Astar/Twinstar/Ecureuil
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Flight Plan	None
Component
Aircraft Component	GPS & Other Satellite Navigation
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Commercial
Experience	Flight Crew Last 90 Days 90 Flight Crew Total 12000 Flight Crew Type 4000
Events
Anomaly	Aircraft Equipment Problem Less Severe Airspace Violation All Types Deviation - Procedural Published Material / Policy

Narrative:

Flying electronic news gathering we were sent up to near the state border to a very small town for a bank robbery. We launched almost immediately to go flyover the scene for the tv station. Before we departed I did not check for tfr's but did check weather considering I did turn down the flight earlier in the day for less than ideal flying conditions. We were over the scene for about 30 minutes and judging by the seriousness of what took place I did maintain a higher than normal altitude but was limited to the ceilings of about 1;700 ft MSL at the time. Upon my return I was notified by a fellow pilot about the tfr and after I returned I checked the FAA website and the tfr was in place. I operate with a 496 garmin GPS with tfr information and it showed nothing in the vicinity and this feature has not let me down in the past. I was surprised not only by the nature of the tfr; its' location; and not showing up on the GPS that it existed at all. I will from now on make sure I check for tfr's before each flight and not rely on the GPS for that information.

Original NASA ASRS Text

Title: Helicopter pilot reports discovering after landing that he had been operating in a TFR. A 496 Garmin GPS with TFR information was in use during the flight and did not show the TFR.

Narrative: Flying Electronic News Gathering we were sent up to near the state border to a very small town for a bank robbery. We launched almost immediately to go flyover the scene for the TV station. Before we departed I did not check for TFR's but did check weather considering I did turn down the flight earlier in the day for less than ideal flying conditions. We were over the scene for about 30 minutes and judging by the seriousness of what took place I did maintain a higher than normal altitude but was limited to the ceilings of about 1;700 FT MSL at the time. Upon my return I was notified by a fellow pilot about the TFR and after I returned I checked the FAA website and the TFR was in place. I operate with a 496 Garmin GPS with TFR information and it showed nothing in the vicinity and this feature has not let me down in the past. I was surprised not only by the nature of the TFR; its' location; and not showing up on the GPS that it existed at all. I will from now on make sure I check for TFR's before each flight and not rely on the GPS for that information.

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.

Helicopter pilot reports discovering after landing that he had been operating in a tfr. A 496 garmin GPS with tfr information was in use during the flight and did not show the tfr.