PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Flight Crew Private
Flight Crew Last 90 Days 6; Flight Crew Total 275; Flight Crew Type 175
Other / Unknown; Situational Awareness; Human-Machine Interface
Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance
Human Factors; Aircraft
I was flying to PLK and the trip was uneventful until my approach to land. I had a current chart and downloaded info for PLK and BBG. I used an older Garman 295 which was out of date; but with a current chart and downloaded information (reference only) I thought I would be fine. As I got close and had airport insight approximately 5 miles out I called PLK Tower with my position and intent. No answer; no problem 122.7. I called an extended left base then noticed my GPS reading I was at the airport. But I wasn't there yet; I had a mile or so to go (nothing clicked yet). I called base to final. I was looking for other traffic during this time and saw none. I called final; and then saw the runway markings. PLK is a 12-30 I saw 14-32 (click). Then I saw a green light from the Tower. Nearing the threshold I landed. [I] taxied up to a young man that gave me a phone number to call. So I did; and after a polite but firm ass chewing/lesson [Tower] let me fly back to PLK. I landed at BBG having never seen PLK; which I flew right over. BBG is a newer airport which did not show up on my GPS. Note to self even flying VFR have an updated GPS and pay attention when approaching controlled airspace. That is about it; the rest of the trip went fine.
PA28 pilot reports mistaking BBG for PLK due to using an older Garmin 295 without a current data base. BBG is a newer airport and Tower controled.