Narrative:

On may/wed/00, I was part of a flight crew that departed olv -- olive branch, ms, at XA30 am-XB30Z in citation aircraft X VFR to memphis international. Olv is only 11 NM east of memphis international airport. Upon departure from olv I immediately contacted memphis international approach control for a clearance into their class B airspace. I was given a vector to intercept the runway 27 final and told I was 'cleared for the approach' and contact the tower. This instruction was complied with and I heard the tower say 'cleared to land.' upon landing and rollout I contacted ground control once clear of the runway. The ground controller then asked me if I had received landing clearance which I told him I did. Because the approach controller was busy that morning he was late turning me over to the tower so I only had time to call for landing clearance once. Before I could ask the tower operator for landing clearance again I was already over the numbers of runway 27. Either my radio transmission requesting clearance to land was walked on (stepped on) or I heard the landing clearance for another aircraft in error. The only recommendation I could offer is that the approach control be contacted on the ground before departure at olive branch airport but this is also not possible because the remote transmitter site is inoperative or the volume is turned down. Because of the close proximity of the olive branch airport to memphis it is difficult to contact approach and tower if they are experiencing a saturation period. Another potential problem is that sometimes both memphis international and nashville, tn, combine clearance, ground, tower, approach and departure frequencys into one common frequency. This is an accident waiting to happen. It also causes frequency congestion, unnecessary delays and numerous mistakes on the one lone controller who has been placed in this undesirable position.

Related reports:

Google
 

Original NASA ASRS Text

Title: C500 CREW REPOSITIONING ACFT ON SHORT 11 NM FLT FROM OLV TO MEM, WAS HURRIED, AFTER HDOF TO TWR BY APCH CTL, TO RECEIVE A LNDG CLRNC.

Narrative: ON MAY/WED/00, I WAS PART OF A FLC THAT DEPARTED OLV -- OLIVE BRANCH, MS, AT XA30 AM-XB30Z IN CITATION ACFT X VFR TO MEMPHIS INTL. OLV IS ONLY 11 NM E OF MEMPHIS INTL ARPT. UPON DEP FROM OLV I IMMEDIATELY CONTACTED MEMPHIS INTL APCH CTL FOR A CLRNC INTO THEIR CLASS B AIRSPACE. I WAS GIVEN A VECTOR TO INTERCEPT THE RWY 27 FINAL AND TOLD I WAS 'CLRED FOR THE APCH' AND CONTACT THE TWR. THIS INSTRUCTION WAS COMPLIED WITH AND I HEARD THE TWR SAY 'CLRED TO LAND.' UPON LNDG AND ROLLOUT I CONTACTED GND CTL ONCE CLR OF THE RWY. THE GND CTLR THEN ASKED ME IF I HAD RECEIVED LNDG CLRNC WHICH I TOLD HIM I DID. BECAUSE THE APCH CTLR WAS BUSY THAT MORNING HE WAS LATE TURNING ME OVER TO THE TWR SO I ONLY HAD TIME TO CALL FOR LNDG CLRNC ONCE. BEFORE I COULD ASK THE TWR OPERATOR FOR LNDG CLRNC AGAIN I WAS ALREADY OVER THE NUMBERS OF RWY 27. EITHER MY RADIO XMISSION REQUESTING CLRNC TO LAND WAS WALKED ON (STEPPED ON) OR I HEARD THE LNDG CLRNC FOR ANOTHER ACFT IN ERROR. THE ONLY RECOMMENDATION I COULD OFFER IS THAT THE APCH CTL BE CONTACTED ON THE GND BEFORE DEP AT OLIVE BRANCH ARPT BUT THIS IS ALSO NOT POSSIBLE BECAUSE THE REMOTE XMITTER SITE IS INOP OR THE VOLUME IS TURNED DOWN. BECAUSE OF THE CLOSE PROX OF THE OLIVE BRANCH ARPT TO MEMPHIS IT IS DIFFICULT TO CONTACT APCH AND TWR IF THEY ARE EXPERIENCING A SATURATION PERIOD. ANOTHER POTENTIAL PROB IS THAT SOMETIMES BOTH MEMPHIS INTL AND NASHVILLE, TN, COMBINE CLRNC, GND, TWR, APCH AND DEP FREQS INTO ONE COMMON FREQ. THIS IS AN ACCIDENT WAITING TO HAPPEN. IT ALSO CAUSES FREQ CONGESTION, UNNECESSARY DELAYS AND NUMEROUS MISTAKES ON THE ONE LONE CTLR WHO HAS BEEN PLACED IN THIS UNDESIRABLE POS.

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.