Narrative:

Inbound to ism I was on mco approach frequency and was vectored thru the class B airspace. Upon getting closer to ism mco instructed me to resume own navigation and switch to ism common traffic frequency. I switched to 124.45 as per AFD and spoke with another aircraft and a helicopter that were already in the pattern. One of the aircraft was on a 2 mile straight in final for runway 6. I entered 45 degrees downwind right traffic for runway 6 and advised I would follow him in. Upon his landing he advised me of wind and I continued my approach. I landed on runway 6 and as I crossed runway 23 I observed a king air landing towards me. I turned to the left to allow extra space and immediately exited the runway. As I was taxiing the pilot of the other aircraft approached me and became belligerent stating that I crossed in front of him. I informed him that I was on the CTAF and was speaking with other traffic and that we never heard or saw him. He argued that the proper frequency is 122.95 which is the unicom for this field. I explained the orlando approach told us to contact traffic on the CTAF and that we were speaking with the other traffic. I again radioed mco approach and confirmed that we were on the proper frequency. Callback conversation with the reporter revealed the following information: reporter stated that the incident was the closest that he has come to another aircraft. Because of the limited conservation he had with the pilot of the king air. He believes that the king air pilot was unaware of the requirement to use the CTAF frequency and not the unicom, to advise other aircraft of his intentions.

Related reports:

Google
 

Original NASA ASRS Text

Title: AIRCRAFT X ON HIS LANDING ROLL ON RWY 6, ENCOUNTERED ACFT Y, ALSO ON HIS LNDG ROLL ON RWY 33, ACFT Y PASSED WITHIN 150 FT OF ACFT X. ACFT Y WAS NOT ON THE CORRECT FREQUENCY.

Narrative: INBOUND TO ISM I WAS ON MCO APCH FREQ AND WAS VECTORED THRU THE CLASS B AIRSPACE. UPON GETTING CLOSER TO ISM MCO INSTRUCTED ME TO RESUME OWN NAV AND SWITCH TO ISM COMMON TFC FREQ. I SWITCHED TO 124.45 AS PER AFD AND SPOKE WITH ANOTHER ACFT AND A HELICOPTER THAT WERE ALREADY IN THE PATTERN. ONE OF THE AIRCRAFT WAS ON A 2 MILE STRAIGHT IN FINAL FOR RWY 6. I ENTERED 45 DEGREES DOWNWIND R TFC FOR RWY 6 AND ADVISED I WOULD FOLLOW HIM IN. UPON HIS LNDG HE ADVISED ME OF WIND AND I CONTINUED MY APCH. I LANDED ON RWY 6 AND AS I CROSSED RWY 23 I OBSERVED A KING AIR LNDG TOWARDS ME. I TURNED TO THE LEFT TO ALLOW EXTRA SPACE AND IMMEDIATELY EXITED THE RWY. AS I WAS TAXIING THE PLT OF THE OTHER ACFT APCHED ME AND BECAME BELLIGERENT STATING THAT I CROSSED IN FRONT OF HIM. I INFORMED HIM THAT I WAS ON THE CTAF AND WAS SPEAKING WITH OTHER TFC AND THAT WE NEVER HEARD OR SAW HIM. HE ARGUED THAT THE PROPER FREQUENCY IS 122.95 WHICH IS THE UNICOM FOR THIS FIELD. I EXPLAINED THE ORLANDO APPROACH TOLD US TO CONTACT TFC ON THE CTAF AND THAT WE WERE SPEAKING WITH THE OTHER TFC. I AGAIN RADIOED MCO APCH AND CONFIRMED THAT WE WERE ON THE PROPER FREQUENCY. CALLBACK CONVERSATION WITH THE RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THE INCIDENT WAS THE CLOSEST THAT HE HAS COME TO ANOTHER ACFT. BECAUSE OF THE LIMITED CONSERVATION HE HAD WITH THE PLT OF THE KING AIR. HE BELIEVES THAT THE KING AIR PLT WAS UNAWARE OF THE REQUIREMENT TO USE THE CTAF FREQUENCY AND NOT THE UNICOM, TO ADVISE OTHER ACFT OF HIS INTENTIONS.

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.