Narrative:

About 20 minutes out of okk I tried to contact flight watch but was not able after several attempts. I then tuned in the VOR and listened to the airport information and determined the wind favored runway 23. I called 5 miles out and then again 3 miles out on 123.0 for an airport advisory from unicom or any aircraft that might be in the pattern. I received no response. I then entered downwind and called the entry; base; and 2 calls on final for runway 23. There was no answer to any calls. I landed a bit long as the runway was 5;000 ft and far more than required. I saw no markings on the runway to indicate an abnormal situation. After parking and entering the FBO I was told '23 is closed for landing'. I asked why no one mentioned on the unicom; and no markings were on the runway; and apologized; as it was an honest mistake; but I am not sure what else I could have done. I then asked if this was the case why did they not X out the runway; or put the info on the AWOS; if they couldn't monitor the unicom. I was then told it was open for take off for some of the corporate jets that use the airport. As we stood there a piper saratoga also announced he was entering the pattern for 23. I can only assume he also repeated the process I experienced. This time the FBO replied to his call entering the pattern and he changed to another runway. The people at the airport are very nice; but if a runway is closed it should be noted on the automated info if the unicom is not monitored faithfully.

Related reports:

Google
 

Original NASA ASRS Text

Title: C140 pilot reports landing on Runway 23 at OKK and being informed by the FBO that Runway 23 is closed. There was no indication the runway was closed and no response on Unicom when advisories were requested; although the frequency was being monitored in the FBO.

Narrative: About 20 minutes out of OKK I tried to contact Flight Watch but was not able after several attempts. I then tuned in the VOR and listened to the airport information and determined the wind favored Runway 23. I called 5 miles out and then again 3 miles out on 123.0 for an airport advisory from UNICOM or any aircraft that might be in the pattern. I received no response. I then entered downwind and called the entry; base; and 2 calls on final for Runway 23. There was no answer to any calls. I landed a bit long as the runway was 5;000 FT and far more than required. I saw no markings on the runway to indicate an abnormal situation. After parking and entering the FBO I was told '23 is closed for landing'. I asked why no one mentioned on the UNICOM; and no markings were on the runway; and apologized; as it was an honest mistake; but I am not sure what else I could have done. I then asked if this was the case why did they not X out the runway; or put the info on the AWOS; if they couldn't monitor the UNICOM. I was then told it was open for take off for some of the corporate jets that use the airport. As we stood there a Piper Saratoga also announced he was entering the pattern for 23. I can only assume he also repeated the process I experienced. This time the FBO replied to his call entering the pattern and he changed to another runway. The people at the airport are very nice; but if a runway is closed it should be noted on the automated info if the UNICOM is not monitored faithfully.

Data retrieved from NASA's ASRS site as of April 2012 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.