Narrative:

On jul/fri/04 around XA55 local time I contacted flight service and specifically inquired about the boundary of the tfr and the specific location it originated from. I learned that the airport that I had planned to depart from (1g5) was just within the boundary of the tfr scheduled to become active at XD20 local time and remain active until the next morning. I made it to the airport by XD10 local. I immediately called flight service to file a VFR flight plan, get a standard WX brief and obtain further information concerning the tfr and any other NOTAMS that would affect my flight. In the flight plan, I specifically informed flight service of my intentions to maneuver 6 NM southwest of 1g5 and return for touch and go lndgs. For the route of flight, I specified that I would depart 1g5 on a heading of 240 degrees 6 NM southwest and return. I was unaware that you could not maneuver within a tfr never having dealt with one before. At the end of the briefing, I inquired as to the appropriate frequency to contact cleveland approach. I was given 135.87. I then asked if the tfr goes down to the surface, unsure about how it works. I was told that 135.87 or a call to flight service would be sufficient to receive the required discrete beacon code. After my pre-flight was completed my student got into the airplane and I returned to the flight school to call flight service. After being on hold for a time, I thought that I would try to pick up approach on the ground or perhaps right after liftoff. I tried to transmit on the ground with no success, so I opted to try to reach them immediately after liftoff. Climbing out of 200 ft AGL, I contacted cleveland approach. I was not acknowledged until I was climbing through 700 ft AGL crosswind turning left downwind for runway 27. I requested a discrete beacon code and informed them that I was in the pattern at 1g5. Immediately, I was informed that I had violated the tfr, so I made a short approach and landed on final. I was issued a code and a request was made for my information. I replied that I was on the ground. The controller asked if I had landed while he was talking to me. I replied in the affirmative. That was the last transmission that I was able to receive. I immediately taxied into the ramp and proceeded inside to call ATC. When I arrived, someone from washington was already on the phone requesting my information. I cooperated and explained that I thought I could pick up the beacon code immediately after takeoff. In hindsight, I can see I was wrong and I now know that you cannot maneuver within a tfr. Unfortunately, I did not encounter this in a different situation as not to cause a problem. I simply was mistaken. I should have canceled the lesson and rescheduled.

Related reports:

Google
 

Original NASA ASRS Text

Title: UNAUTH TFR ENTRY BY A C172 TRAINING FLT WITHOUT A DISCRETE XPONDER CODE DISPLAYED AFTER A VFR DEP FROM 1G5.

Narrative: ON JUL/FRI/04 AROUND XA55 LCL TIME I CONTACTED FLT SVC AND SPECIFICALLY INQUIRED ABOUT THE BOUNDARY OF THE TFR AND THE SPECIFIC LOCATION IT ORIGINATED FROM. I LEARNED THAT THE ARPT THAT I HAD PLANNED TO DEPART FROM (1G5) WAS JUST WITHIN THE BOUNDARY OF THE TFR SCHEDULED TO BECOME ACTIVE AT XD20 LCL TIME AND REMAIN ACTIVE UNTIL THE NEXT MORNING. I MADE IT TO THE ARPT BY XD10 LCL. I IMMEDIATELY CALLED FLT SVC TO FILE A VFR FLT PLAN, GET A STANDARD WX BRIEF AND OBTAIN FURTHER INFO CONCERNING THE TFR AND ANY OTHER NOTAMS THAT WOULD AFFECT MY FLT. IN THE FLT PLAN, I SPECIFICALLY INFORMED FLT SVC OF MY INTENTIONS TO MANEUVER 6 NM SW OF 1G5 AND RETURN FOR TOUCH AND GO LNDGS. FOR THE RTE OF FLT, I SPECIFIED THAT I WOULD DEPART 1G5 ON A HDG OF 240 DEGS 6 NM SW AND RETURN. I WAS UNAWARE THAT YOU COULD NOT MANEUVER WITHIN A TFR NEVER HAVING DEALT WITH ONE BEFORE. AT THE END OF THE BRIEFING, I INQUIRED AS TO THE APPROPRIATE FREQ TO CONTACT CLEVELAND APCH. I WAS GIVEN 135.87. I THEN ASKED IF THE TFR GOES DOWN TO THE SURFACE, UNSURE ABOUT HOW IT WORKS. I WAS TOLD THAT 135.87 OR A CALL TO FLT SVC WOULD BE SUFFICIENT TO RECEIVE THE REQUIRED DISCRETE BEACON CODE. AFTER MY PRE-FLT WAS COMPLETED MY STUDENT GOT INTO THE AIRPLANE AND I RETURNED TO THE FLT SCHOOL TO CALL FLT SVC. AFTER BEING ON HOLD FOR A TIME, I THOUGHT THAT I WOULD TRY TO PICK UP APCH ON THE GND OR PERHAPS RIGHT AFTER LIFTOFF. I TRIED TO XMIT ON THE GND WITH NO SUCCESS, SO I OPTED TO TRY TO REACH THEM IMMEDIATELY AFTER LIFTOFF. CLBING OUT OF 200 FT AGL, I CONTACTED CLEVELAND APCH. I WAS NOT ACKNOWLEDGED UNTIL I WAS CLBING THROUGH 700 FT AGL XWIND TURNING L DOWNWIND FOR RWY 27. I REQUESTED A DISCRETE BEACON CODE AND INFORMED THEM THAT I WAS IN THE PATTERN AT 1G5. IMMEDIATELY, I WAS INFORMED THAT I HAD VIOLATED THE TFR, SO I MADE A SHORT APCH AND LANDED ON FINAL. I WAS ISSUED A CODE AND A REQUEST WAS MADE FOR MY INFO. I REPLIED THAT I WAS ON THE GND. THE CTLR ASKED IF I HAD LANDED WHILE HE WAS TALKING TO ME. I REPLIED IN THE AFFIRMATIVE. THAT WAS THE LAST XMISSION THAT I WAS ABLE TO RECEIVE. I IMMEDIATELY TAXIED INTO THE RAMP AND PROCEEDED INSIDE TO CALL ATC. WHEN I ARRIVED, SOMEONE FROM WASHINGTON WAS ALREADY ON THE PHONE REQUESTING MY INFO. I COOPERATED AND EXPLAINED THAT I THOUGHT I COULD PICK UP THE BEACON CODE IMMEDIATELY AFTER TKOF. IN HINDSIGHT, I CAN SEE I WAS WRONG AND I NOW KNOW THAT YOU CANNOT MANEUVER WITHIN A TFR. UNFORTUNATELY, I DID NOT ENCOUNTER THIS IN A DIFFERENT SIT AS NOT TO CAUSE A PROB. I SIMPLY WAS MISTAKEN. I SHOULD HAVE CANCELED THE LESSON AND RESCHEDULED.

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.