Narrative:

My flight began at moraine airpark (I73) dayton, oh, with a short flight to middletown, oh. Middletown is located about 30 mi from dayton. After lunch, I flew back to I73. During the flight, most of which was conducted at 2500 ft MSL, I flew through the wilmington control zone and contacted them for clearance. They had an aircraft depart after I passed the center of their airport and I continued on their frequency until I departed their area to the northwest, en route to I73. I then changed frequency to dayton tower ATIS 125.8 and listened for advisories and the current dayton area WX. They advised that dayton airport was closed to GA aircraft due to the tfr and that the air carrier traffic was not effected by the tfr. There was no mention of the size of the tfr and it really did not occur to me that I73 was included in the tfr. When I was approximately 8 mi from I73, I noted an F16 pass over me and make a right turn in the direction of wright patterson AFB, which was not really unusual because they sometimes have a large pattern at about 3500 ft. A few mins later, when I was only a couple mi from I73 and beginning my descent to pattern altitude, a second F16 passed over me. I announced my downwind on unicom and proceeded with a normal landing. The airport manager greeted me with the news that I had violated the tfr and ATC needed to speak with me. I had a short interview with the dayton supervisor. The day after my tfr infractions, I phoned to see if there was anything I should know about my situation and any advice that they might have about actions I should take. They advised that I was one of many who have stumbled into a tfr and that I would be getting notification from the FAA of what punitive action would be taken. Yesterday, I73 hosted a fly-in. Our cincinnati based FAA representative conducted a seminar which I attended. During the seminar, the tfr implementation was discussed. She advised that it would be well advised to send in this NASA form. Callback conversation with reporter revealed the following information: pilot advised that the tfr was a 20 mi radius of day airport, 16000 ft and below. The pilot recalled that he was outside the 20 mi radius when initially listening to the day ATIS, but since he was not landing at day, and no specifics were transmitted about the tfr, he felt comfortable proceeding to I73. That is, until the second F16 fly-by. The reporter alleges that the next tfr that day was only a 10 mi radius. Reporter suggests that a standard tfr radius and altitude be implemented. This would give non participating pilots a 'running chance' to avoid subsequent tfr's.

Google
 

Original NASA ASRS Text

Title: C172 PLT, ENRTE TO I73 ARPT, TRANSITS DAY AIRSPACE IN VIOLATION OF A TFR.

Narrative: MY FLT BEGAN AT MORAINE AIRPARK (I73) DAYTON, OH, WITH A SHORT FLT TO MIDDLETOWN, OH. MIDDLETOWN IS LOCATED ABOUT 30 MI FROM DAYTON. AFTER LUNCH, I FLEW BACK TO I73. DURING THE FLT, MOST OF WHICH WAS CONDUCTED AT 2500 FT MSL, I FLEW THROUGH THE WILMINGTON CTL ZONE AND CONTACTED THEM FOR CLRNC. THEY HAD AN ACFT DEPART AFTER I PASSED THE CTR OF THEIR ARPT AND I CONTINUED ON THEIR FREQ UNTIL I DEPARTED THEIR AREA TO THE NW, ENRTE TO I73. I THEN CHANGED FREQ TO DAYTON TWR ATIS 125.8 AND LISTENED FOR ADVISORIES AND THE CURRENT DAYTON AREA WX. THEY ADVISED THAT DAYTON ARPT WAS CLOSED TO GA ACFT DUE TO THE TFR AND THAT THE ACR TFC WAS NOT EFFECTED BY THE TFR. THERE WAS NO MENTION OF THE SIZE OF THE TFR AND IT REALLY DID NOT OCCUR TO ME THAT I73 WAS INCLUDED IN THE TFR. WHEN I WAS APPROX 8 MI FROM I73, I NOTED AN F16 PASS OVER ME AND MAKE A R TURN IN THE DIRECTION OF WRIGHT PATTERSON AFB, WHICH WAS NOT REALLY UNUSUAL BECAUSE THEY SOMETIMES HAVE A LARGE PATTERN AT ABOUT 3500 FT. A FEW MINS LATER, WHEN I WAS ONLY A COUPLE MI FROM I73 AND BEGINNING MY DSCNT TO PATTERN ALT, A SECOND F16 PASSED OVER ME. I ANNOUNCED MY DOWNWIND ON UNICOM AND PROCEEDED WITH A NORMAL LNDG. THE ARPT MGR GREETED ME WITH THE NEWS THAT I HAD VIOLATED THE TFR AND ATC NEEDED TO SPEAK WITH ME. I HAD A SHORT INTERVIEW WITH THE DAYTON SUPVR. THE DAY AFTER MY TFR INFRACTIONS, I PHONED TO SEE IF THERE WAS ANYTHING I SHOULD KNOW ABOUT MY SIT AND ANY ADVICE THAT THEY MIGHT HAVE ABOUT ACTIONS I SHOULD TAKE. THEY ADVISED THAT I WAS ONE OF MANY WHO HAVE STUMBLED INTO A TFR AND THAT I WOULD BE GETTING NOTIFICATION FROM THE FAA OF WHAT PUNITIVE ACTION WOULD BE TAKEN. YESTERDAY, I73 HOSTED A FLY-IN. OUR CINCINNATI BASED FAA REPRESENTATIVE CONDUCTED A SEMINAR WHICH I ATTENDED. DURING THE SEMINAR, THE TFR IMPLEMENTATION WAS DISCUSSED. SHE ADVISED THAT IT WOULD BE WELL ADVISED TO SEND IN THIS NASA FORM. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: PLT ADVISED THAT THE TFR WAS A 20 MI RADIUS OF DAY ARPT, 16000 FT AND BELOW. THE PLT RECALLED THAT HE WAS OUTSIDE THE 20 MI RADIUS WHEN INITIALLY LISTENING TO THE DAY ATIS, BUT SINCE HE WAS NOT LNDG AT DAY, AND NO SPECIFICS WERE XMITTED ABOUT THE TFR, HE FELT COMFORTABLE PROCEEDING TO I73. THAT IS, UNTIL THE SECOND F16 FLY-BY. THE RPTR ALLEGES THAT THE NEXT TFR THAT DAY WAS ONLY A 10 MI RADIUS. RPTR SUGGESTS THAT A STANDARD TFR RADIUS AND ALT BE IMPLEMENTED. THIS WOULD GIVE NON PARTICIPATING PLTS A 'RUNNING CHANCE' TO AVOID SUBSEQUENT TFR'S.

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.