Narrative:

The decision was made to request flight following rather than delay takeoff by filing IFR. About 3 mins after departure, I contacted ZKC and was provided a squawk code and asked for the destination and route. I responded with GPS direct to gtu. Somewhere just north of waco, tx, I lost communications with regional and again received no handoff. Since I was within 60-75 mi from my destination and did not know the next frequency, I decided to squawk 1200 and proceed direct to gtu, but avoided the sometimes busy area around waco by flying to the east of ih-35. South of waco, near temple, tx, I was severely rattled by a fighter (hard enough to cause scrapes, bruises and contusions to my passenger and myself). He rocked his wings, meaning to follow, which I immediately did and I tried to contact him on 121.5. He sped off to the north until I could no longer see him and I never heard him respond to my 2 or 3 calls. I was confused by the action and not having any direction, decided that I must have wandered into an MOA not shown on the GPS database (it was current), so I returned to course. About 10-15 mins later, I was rattled even harder. This rattle actually broke a hand held radio, caused some damage to the aircraft, additional injury and frighten my passenger. This time the fighter responded to my call on 121.5 and provided a contact frequency to waco approach. Approach requested I return and land at act for an interview. Being based in gtu (less than 75 mi south of act) and flying from gtu to rbd frequently, I am very well aware of the P49 tfr. After this call, I strongly suspected I had entered the tfr. After landing, I was asked to call the tower. It was confirmed by the tower controller that I had, in his words 'nicked the tfr.' I was also interviewed after about 1 hour delay by the secret service who released me to complete the trip, which was uneventful. During the flight, I spoke with controllers and gave my destination as GPS direct to gtu, which requires a flight almost directly over the act VOR, well within the expanded tfr around P49. None of the controllers notified me that P49 had expanded and was active. In addition, losing communication with the controller twice, exacerbated the problem, since I did not know the next frequency. Reflecting upon the incident, I believe pilots would be better served if controllers advised of the next expected frequency. In addition, it is totally unnecessary to rattle an aircraft so hard as to cause injury and frighten passenger just to attract attention, a little more delicate handling is suggested.

Related reports:

Google
 

Original NASA ASRS Text

Title: PLT AND PAX OF M20 WERE INTERCEPTED BY FGT WHEN THEY ENTERED P49 EXPANDED TFR. FGT PASSED TWICE, WHICH CAUSED DAMAGE TO RPTR'S ACFT AND INJURY TO BOTH OCCUPANTS.

Narrative: THE DECISION WAS MADE TO REQUEST FLT FOLLOWING RATHER THAN DELAY TKOF BY FILING IFR. ABOUT 3 MINS AFTER DEP, I CONTACTED ZKC AND WAS PROVIDED A SQUAWK CODE AND ASKED FOR THE DEST AND RTE. I RESPONDED WITH GPS DIRECT TO GTU. SOMEWHERE JUST N OF WACO, TX, I LOST COMS WITH REGIONAL AND AGAIN RECEIVED NO HDOF. SINCE I WAS WITHIN 60-75 MI FROM MY DEST AND DID NOT KNOW THE NEXT FREQ, I DECIDED TO SQUAWK 1200 AND PROCEED DIRECT TO GTU, BUT AVOIDED THE SOMETIMES BUSY AREA AROUND WACO BY FLYING TO THE E OF IH-35. S OF WACO, NEAR TEMPLE, TX, I WAS SEVERELY RATTLED BY A FIGHTER (HARD ENOUGH TO CAUSE SCRAPES, BRUISES AND CONTUSIONS TO MY PAX AND MYSELF). HE ROCKED HIS WINGS, MEANING TO FOLLOW, WHICH I IMMEDIATELY DID AND I TRIED TO CONTACT HIM ON 121.5. HE SPED OFF TO THE N UNTIL I COULD NO LONGER SEE HIM AND I NEVER HEARD HIM RESPOND TO MY 2 OR 3 CALLS. I WAS CONFUSED BY THE ACTION AND NOT HAVING ANY DIRECTION, DECIDED THAT I MUST HAVE WANDERED INTO AN MOA NOT SHOWN ON THE GPS DATABASE (IT WAS CURRENT), SO I RETURNED TO COURSE. ABOUT 10-15 MINS LATER, I WAS RATTLED EVEN HARDER. THIS RATTLE ACTUALLY BROKE A HAND HELD RADIO, CAUSED SOME DAMAGE TO THE ACFT, ADDITIONAL INJURY AND FRIGHTEN MY PAX. THIS TIME THE FIGHTER RESPONDED TO MY CALL ON 121.5 AND PROVIDED A CONTACT FREQ TO WACO APCH. APCH REQUESTED I RETURN AND LAND AT ACT FOR AN INTERVIEW. BEING BASED IN GTU (LESS THAN 75 MI S OF ACT) AND FLYING FROM GTU TO RBD FREQUENTLY, I AM VERY WELL AWARE OF THE P49 TFR. AFTER THIS CALL, I STRONGLY SUSPECTED I HAD ENTERED THE TFR. AFTER LNDG, I WAS ASKED TO CALL THE TWR. IT WAS CONFIRMED BY THE TWR CTLR THAT I HAD, IN HIS WORDS 'NICKED THE TFR.' I WAS ALSO INTERVIEWED AFTER ABOUT 1 HR DELAY BY THE SECRET SVC WHO RELEASED ME TO COMPLETE THE TRIP, WHICH WAS UNEVENTFUL. DURING THE FLT, I SPOKE WITH CTLRS AND GAVE MY DEST AS GPS DIRECT TO GTU, WHICH REQUIRES A FLT ALMOST DIRECTLY OVER THE ACT VOR, WELL WITHIN THE EXPANDED TFR AROUND P49. NONE OF THE CTLRS NOTIFIED ME THAT P49 HAD EXPANDED AND WAS ACTIVE. IN ADDITION, LOSING COM WITH THE CTLR TWICE, EXACERBATED THE PROB, SINCE I DID NOT KNOW THE NEXT FREQ. REFLECTING UPON THE INCIDENT, I BELIEVE PLTS WOULD BE BETTER SERVED IF CTLRS ADVISED OF THE NEXT EXPECTED FREQ. IN ADDITION, IT IS TOTALLY UNNECESSARY TO RATTLE AN ACFT SO HARD AS TO CAUSE INJURY AND FRIGHTEN PAX JUST TO ATTRACT ATTN, A LITTLE MORE DELICATE HANDLING IS SUGGESTED.

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.