Narrative:

On landing rollout for runway 18R, we were told to contact ramp control. This is not unusual at charlotte since we often land and rollout short enough that contacting ground is unnecessary as the taxi distance from runway to ramp is not very far. On this night, however, we used most of the runway for rollout. We contacted ramp and were cleared to our gate. While this necessitated crossing the departure of runway 23 (there was landing traffic on final), we had been cleared by ramp control. As we approached the gate, ramp asked us to call ground, who gave us a tower land line number to call on termination. I believe the problem occurred because: 1) we expected to contact ramp control as part of business as usual, 2) tower told us to contact ramp as part of the same mindset, 3) ramp cleared us to the gate without really knowing where we were, and 4) because we had been cleared, we didn't get suspicious until we were crossing runway 23. The corrective action is obvious, but implementing it may cause delays during congestion. We should always be told to contact ground, who should hand us off to ramp control. As pilots who operate in charlotte occasionally, we cannot know, nor should we be expected to know, when and where ground control has delegated aircraft movement control to ramp control. Callback conversation with reporter revealed the following information: the reporter flies the CL65 regularly into clt. The ramp control frequency is 122.8 and the ground control frequency is 121.8. It is possible that the reporter misheard the ATCT local controller and mistakenly switched to ramp vice ground. It is also possible that the local controller may have said 'contact ground on point eight' and the reporter switched to the wrong point eight. He will listen more carefully. There has been no change in procedure that the reporter is aware of. He has heard nothing from the FAA on this.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR CL65 FO RPTS THAT HE CROSSED AN ACTIVE RWY WITHOUT PROPER CLRNC FROM GND CTL. RAMP CTL GAVE CLRNC TO CROSS. THE FO THINKS THAT HE MAY HAVE SWITCHED TO RAMP VICE GND CTL AS THIS IS THE USUAL PROC AT CLT. POSSIBLE ERROR ADMITTED.

Narrative: ON LNDG ROLLOUT FOR RWY 18R, WE WERE TOLD TO CONTACT RAMP CTL. THIS IS NOT UNUSUAL AT CHARLOTTE SINCE WE OFTEN LAND AND ROLLOUT SHORT ENOUGH THAT CONTACTING GND IS UNNECESSARY AS THE TAXI DISTANCE FROM RWY TO RAMP IS NOT VERY FAR. ON THIS NIGHT, HOWEVER, WE USED MOST OF THE RWY FOR ROLLOUT. WE CONTACTED RAMP AND WERE CLRED TO OUR GATE. WHILE THIS NECESSITATED XING THE DEP OF RWY 23 (THERE WAS LNDG TFC ON FINAL), WE HAD BEEN CLRED BY RAMP CTL. AS WE APCHED THE GATE, RAMP ASKED US TO CALL GND, WHO GAVE US A TWR LAND LINE NUMBER TO CALL ON TERMINATION. I BELIEVE THE PROB OCCURRED BECAUSE: 1) WE EXPECTED TO CONTACT RAMP CTL AS PART OF BUSINESS AS USUAL, 2) TWR TOLD US TO CONTACT RAMP AS PART OF THE SAME MINDSET, 3) RAMP CLRED US TO THE GATE WITHOUT REALLY KNOWING WHERE WE WERE, AND 4) BECAUSE WE HAD BEEN CLRED, WE DIDN'T GET SUSPICIOUS UNTIL WE WERE XING RWY 23. THE CORRECTIVE ACTION IS OBVIOUS, BUT IMPLEMENTING IT MAY CAUSE DELAYS DURING CONGESTION. WE SHOULD ALWAYS BE TOLD TO CONTACT GND, WHO SHOULD HAND US OFF TO RAMP CTL. AS PLTS WHO OPERATE IN CHARLOTTE OCCASIONALLY, WE CANNOT KNOW, NOR SHOULD WE BE EXPECTED TO KNOW, WHEN AND WHERE GND CTL HAS DELEGATED ACFT MOVEMENT CTL TO RAMP CTL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR FLIES THE CL65 REGULARLY INTO CLT. THE RAMP CTL FREQ IS 122.8 AND THE GND CTL FREQ IS 121.8. IT IS POSSIBLE THAT THE RPTR MISHEARD THE ATCT LCL CTLR AND MISTAKENLY SWITCHED TO RAMP VICE GND. IT IS ALSO POSSIBLE THAT THE LCL CTLR MAY HAVE SAID 'CONTACT GND ON POINT EIGHT' AND THE RPTR SWITCHED TO THE WRONG POINT EIGHT. HE WILL LISTEN MORE CAREFULLY. THERE HAS BEEN NO CHANGE IN PROC THAT THE RPTR IS AWARE OF. HE HAS HEARD NOTHING FROM THE FAA ON THIS.

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.