Narrative:

Our trainer needed a nitrogen charge in the nosewheel strut. This caused a delay in my schedule and my last training flight terminated at XA50 with a planned departure time of XB00 for an aerial science monitor flight of 4 hours duration. I had monitored WX reports and forecasts throughout the day and the WX picture was benign. Since sep/tue/01, our regional automated FSS has made available a recorded list of fdc NOTAMS affecting the NAS. This list is sequentially tagged with a phonetic identify each time it is updated. After verifying NOTAM information was still current (recorded on aug/fri/03) via the telephone information briefing service, I felt comfortable that no new tfr's applied to my planned operation. However, when I reported my position to grand forks approach, I was informed that I had penetrated a tfr relating to a police operation surrounding a recent civil event. I did not speak directly to an AFSS briefer. Instead I relied solely upon tibs. And, I was aware of the investigation, but it did not trigger in my mind the potential of a tfr. This tfr was not mentioned in 2 ATIS broadcasts from gfk. The tfr is based upon the grk VORTAC. When radar contact was established with gfk approach, my target was idented within the tfr. I climbed immediately after approach described the structure of the tfr. After the flight, I initiated contact with grk AFSS (the FAA's coordinator for this tfr) to discuss the event and identify myself in order to facilitate whatever required process to follow.

Google
 

Original NASA ASRS Text

Title: PA34 PLT INADVERTENTLY ENTERS A TFR DURING A CONTRACTED FLT IN THE VICINITY OF GFK.

Narrative: OUR TRAINER NEEDED A NITROGEN CHARGE IN THE NOSEWHEEL STRUT. THIS CAUSED A DELAY IN MY SCHEDULE AND MY LAST TRAINING FLT TERMINATED AT XA50 WITH A PLANNED DEP TIME OF XB00 FOR AN AERIAL SCIENCE MONITOR FLT OF 4 HRS DURATION. I HAD MONITORED WX RPTS AND FORECASTS THROUGHOUT THE DAY AND THE WX PICTURE WAS BENIGN. SINCE SEP/TUE/01, OUR REGIONAL AUTOMATED FSS HAS MADE AVAILABLE A RECORDED LIST OF FDC NOTAMS AFFECTING THE NAS. THIS LIST IS SEQUENTIALLY TAGGED WITH A PHONETIC IDENT EACH TIME IT IS UPDATED. AFTER VERIFYING NOTAM INFO WAS STILL CURRENT (RECORDED ON AUG/FRI/03) VIA THE TELEPHONE INFO BRIEFING SVC, I FELT COMFORTABLE THAT NO NEW TFR'S APPLIED TO MY PLANNED OP. HOWEVER, WHEN I RPTED MY POS TO GRAND FORKS APCH, I WAS INFORMED THAT I HAD PENETRATED A TFR RELATING TO A POLICE OP SURROUNDING A RECENT CIVIL EVENT. I DID NOT SPEAK DIRECTLY TO AN AFSS BRIEFER. INSTEAD I RELIED SOLELY UPON TIBS. AND, I WAS AWARE OF THE INVESTIGATION, BUT IT DID NOT TRIGGER IN MY MIND THE POTENTIAL OF A TFR. THIS TFR WAS NOT MENTIONED IN 2 ATIS BROADCASTS FROM GFK. THE TFR IS BASED UPON THE GRK VORTAC. WHEN RADAR CONTACT WAS ESTABLISHED WITH GFK APCH, MY TARGET WAS IDENTED WITHIN THE TFR. I CLBED IMMEDIATELY AFTER APCH DESCRIBED THE STRUCTURE OF THE TFR. AFTER THE FLT, I INITIATED CONTACT WITH GRK AFSS (THE FAA'S COORDINATOR FOR THIS TFR) TO DISCUSS THE EVENT AND IDENT MYSELF IN ORDER TO FACILITATE WHATEVER REQUIRED PROCESS TO FOLLOW.

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