Super King Air 300
Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Flight Crew Last 90 Days 40; Flight Crew Total 3500; Flight Crew Type 1300
Communication Breakdown
ATC Issue All Types; Conflict Ground Conflict; Critical
Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Procedure; Airport; Human Factors
We were instructed to taxi to Runway 36C via D; left on Romeo; hold short Runway 36R [at] Romeo. As we were holding short of 36R [at] Romeo; the Ground Controller instructed the pilot flying to expedite; cross Runway 36R and join Alpha taxiway. The pilot flying quickly looked left and advanced the power levers to expedite as instructed. The PF then slammed on the brakes as a B737 nose wheel touched down in front of us. It appears the 737 was in a flare as ground ATC instructed us to expedite across the runway. The PF did look before crossing; but Taxiway 'R' positions the aircraft at a 45 degree angle away from the landing traffic on 36R. This makes seeing down the runway a bit difficult. We were instructed to call the Tower when we land at our destination. Once at our destination; the FP called CLT Tower as requested. The manager stated they played the tapes and we did nothing wrong and followed directions as they were given. The Controller did in fact call our tail number; however it was not meant for us. Mix up by the Controller. Mistake that we caught pretty quickly. I believe CLT could minimize this issue by having all GA aircraft use the closest runway to the FBO; 36R/18L. This would minimize runway crossings and would make it safer for all. I tend to believe that work load for the controllers would drop as well.
BE350 First Officer reports a critical ground conflict with a landing B737 after being cleared to cross Runway 36R at Taxiway R. A collision is avoided by a quick stop and it is later determined that Controller error was responsible for the close call.