PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Flight Crew Private
Flight Crew Last 90 Days 25; Flight Crew Total 220; Flight Crew Type 160
Situational Awareness
Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Airspace Structure; Human Factors; Procedure
Upon landing; I was notified by the Tower operators at FFZ that I needed to contact Phoenix Approach Control due to a possible pilot deviation. I immediately parked; shut down the aircraft and contacted Phoenix at the number given by the FFZ Tower. I spoke with Mr. X and explained I had been instructed to call due to a possible pilot deviation. I was told I may have violated a TFR between Phoenix and Scottsdale. As requested; I gave my name; address; contact phone number and pilot certificate number to Mr. X. I explained I was unaware of any TFR in my flight path. I was told that a VIP transport TFR was in place up to 4;100 FT MSL. I had planned that day to just fly around the pattern and do some touch and go landings. However; it was a beautiful day and I decided to venture further than planned. I flew out toward Maricopa; Arizona and then decided to head to Gila Bend. I continued to E63. After landing I decided to head back to FFZ via BXK and then across the valley. I carry a Garmin 695 GPS and took great care to avoid the airspace of GYR and GEU and stay out of the Class B airspace surrounding PHX passing north of the airport without having to contact PHX Approach to transition their airspace. A trip I have made in the past without incident. On my way across the valley I monitored each airports Tower frequencies including PHX Approach. I contacted FFZ Tower after descending below the 4;000 FT floor of the Class B airspace northwest of Falcon Field for landing instructions. Later; Mr. X from Phoenix commented on the very nice job I had done staying out of their Class B airspace as they were tracking me across the valley. Unfortunately; in doing so; I may have caught the edge of the TFR while descending to get under the 4;000 FT floor on the east edge of the TFR. This I discovered after arriving home and looking up the information regarding the restrictions. I should have contacted FSS and been informed for my flight. Even after being airborne and changing my plan; I should have contacted Prescott radio before continuing. I have relied too much on the regular e-mails I receive regarding things like this such as the President's visit only a short time ago. It was a poor choice and; regardless of the late nature of this VIP visit; I should have known better. I do know better. I can assure you this is a mistake I will not repeat. Pre-flight planning and changes in flight plan during flight require more professional behavior than I exhibited that day and the resources are available to avoid situations like this. Since this occurrence; I have reacquainted myself with the FAA web site and its resources; the ADDS (Aviation Digital Data Service) web site; and even called the Prescott FSS about setting up my profile so they'll know who I am by the number I call from. I have purchased and installed the Foreflight application for my IPAD and IPHONE where the TFR's are shown quite clearly right on the sectional and with a tap of the finger all pertinent information is right there.
Reporter states that his Garmin 695 is not data link capable and could not display TFR's.
A PA28 possibly entered a TFR east of PHX that he was not aware of. The top of the TFR was into the base of the Class B making a flight to FFZ from the northwest difficult.