Narrative:

I had canceled an IFR flight plan in order to avoid vectors around class B airspace en route to pdk airport. My LORAN was set on pdk and indicated 29 mi southeast of pdk. After a long, hard IFR trip, I was tired and somehow mistook the indication as being from atl not pdk. At 25 mi I turned on the garmin 95XL I use as a backup in order to xchk the class B airspace against my other references. As it locked on and gave 1 pictorial of my position, I was immediately aware of being closer to atl than I thought my LORAN indicated. I had started down out of 4500 ft and I think I still avoided the class B at the 4000 ft level, but the indication on the GPS locked on just as I was descending so it may have been close. I was concerned and immediately descended further as well as began monitoring the local approach frequency for possible conflicts. The rest of the trip was uneventful and no comments were made regarding a possible violation. My own physical and attentive level contributed to this oversight. The long IFR through bad WX, the longer trip due to the usual vectors around atl, and the welcome relief of being able to continue VFR direct must have dulled my sense of the impending possible incursion. I found out that the trip is not over until the aircraft is safely tied down.

Google
 

Original NASA ASRS Text

Title: PROX OF TCA. PLT DID NOT VIOLATE THE CLASS B AIRSPACE IF HE HAS RPTED HIS LOCATION CORRECTLY.

Narrative: I HAD CANCELED AN IFR FLT PLAN IN ORDER TO AVOID VECTORS AROUND CLASS B AIRSPACE ENRTE TO PDK ARPT. MY LORAN WAS SET ON PDK AND INDICATED 29 MI SE OF PDK. AFTER A LONG, HARD IFR TRIP, I WAS TIRED AND SOMEHOW MISTOOK THE INDICATION AS BEING FROM ATL NOT PDK. AT 25 MI I TURNED ON THE GARMIN 95XL I USE AS A BACKUP IN ORDER TO XCHK THE CLASS B AIRSPACE AGAINST MY OTHER REFS. AS IT LOCKED ON AND GAVE 1 PICTORIAL OF MY POS, I WAS IMMEDIATELY AWARE OF BEING CLOSER TO ATL THAN I THOUGHT MY LORAN INDICATED. I HAD STARTED DOWN OUT OF 4500 FT AND I THINK I STILL AVOIDED THE CLASS B AT THE 4000 FT LEVEL, BUT THE INDICATION ON THE GPS LOCKED ON JUST AS I WAS DSNDING SO IT MAY HAVE BEEN CLOSE. I WAS CONCERNED AND IMMEDIATELY DSNDED FURTHER AS WELL AS BEGAN MONITORING THE LCL APCH FREQ FOR POSSIBLE CONFLICTS. THE REST OF THE TRIP WAS UNEVENTFUL AND NO COMMENTS WERE MADE REGARDING A POSSIBLE VIOLATION. MY OWN PHYSICAL AND ATTENTIVE LEVEL CONTRIBUTED TO THIS OVERSIGHT. THE LONG IFR THROUGH BAD WX, THE LONGER TRIP DUE TO THE USUAL VECTORS AROUND ATL, AND THE WELCOME RELIEF OF BEING ABLE TO CONTINUE VFR DIRECT MUST HAVE DULLED MY SENSE OF THE IMPENDING POSSIBLE INCURSION. I FOUND OUT THAT THE TRIP IS NOT OVER UNTIL THE ACFT IS SAFELY TIED DOWN.

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.