Narrative:

IFR trip glen falls, ny. Broke off IFR and went VFR 30 mi west to look at some land. Proceeded east VFR to glen falls. No indication of direction of traffic pattern on approach plates. Called unicom 3 times. On third try voice responded saying 19, no pattern entry information and called back with no answer. I approached airport and was set up for base leg right-hand runway 19. I called it on unicom frequency and about 30 seconds later a voice responded that I was violating some FAA regulations. Since by that time I was about to turn final I responded by calling final approach. Upon landing I was informed that the FAA was on the field and I would be written up. I feel under the circumstances this violation/write-up from the FAA is unjust. I am a good and careful pilot and if the system worked for me, I would not be in trouble.

Google
 

Original NASA ASRS Text

Title: SMA PLT MAKES INCORRECT PATTERN ENTRY AT GFL.

Narrative: IFR TRIP GLEN FALLS, NY. BROKE OFF IFR AND WENT VFR 30 MI W TO LOOK AT SOME LAND. PROCEEDED E VFR TO GLEN FALLS. NO INDICATION OF DIRECTION OF TFC PATTERN ON APCH PLATES. CALLED UNICOM 3 TIMES. ON THIRD TRY VOICE RESPONDED SAYING 19, NO PATTERN ENTRY INFO AND CALLED BACK WITH NO ANSWER. I APCHED ARPT AND WAS SET UP FOR BASE LEG RIGHT-HAND RWY 19. I CALLED IT ON UNICOM FREQ AND ABOUT 30 SECS LATER A VOICE RESPONDED THAT I WAS VIOLATING SOME FAA REGS. SINCE BY THAT TIME I WAS ABOUT TO TURN FINAL I RESPONDED BY CALLING FINAL APCH. UPON LNDG I WAS INFORMED THAT THE FAA WAS ON THE FIELD AND I WOULD BE WRITTEN UP. I FEEL UNDER THE CIRCUMSTANCES THIS VIOLATION/WRITE-UP FROM THE FAA IS UNJUST. I AM A GOOD AND CAREFUL PLT AND IF THE SYS WORKED FOR ME, I WOULD NOT BE IN TROUBLE.

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.