Air carrier flight crew reported a ground conflict during taxi in at ORD airport with a Heavy aircraft. Captain stated ATC was extremely busy and that gate related communications issues contributed to the event.
Synopsis
Air carrier flight crew reported a ground conflict during taxi in at ORD airport with a Heavy aircraft. Captain stated ATC was extremely busy and that gate related communications issues contributed to the event.
Narrative
While taxiing to gate after landing on [Runway] 27R inbound from ZZZ we were on Taxiway H on the northern side of the field. We notified ATC of our gate multiple times. We were told to make a right turn on Taxiway B and to the gate. This was strange as they normally bring us down Taxiway A to cross the A bridge on the way to the X gates. As I rounded the turn near Taxiway V the FO and I saw a large aircraft coming towards us on B and he was passing the western side of the international terminal. I immediately stopped my aircraft because I was not sure what the oncoming aircraft's instructions were. He continued towards us coming from our left to go on what looked like Taxiway EE. As he taxied by I could tell it was a Heavy Aircraft Y. The Aircraft Y continued taxiing but slowed their speed as they saw us stopped. Both aircraft cleared each other; however; Aircraft Y's wing tip passed directly over my flight deck.ATC was extremely busy that night with a multitude of arrivals and departures. Upon this incident happening I instructed the FO to contact Ground and tell them about it. The Ground Controller told us he believed we were going the gate Y not X even though we told them our gate multiple times to multiple controllers that night.I think it would help immensely if ORD had a ground frequency for inbound aircraft and a different one for outbound aircraft. Assigning standard taxi routes will help reduce radio chatter as well. For example DFW utilizes standard inbound and outbound taxi routes.
Second reporter narrative
Upon arrival in ORD; notified ground of our gate on 121.9. Told 'right turn Bravo' from crossing 4L on Hotel. Upon reaching the area of A18/V1 on Bravo; I noticed a dark shadow coming down Bravo taxiing opposite direction per normal. I noticed the green light was on the left with taxi light on towards us. I brought this to the Captain's attention who immediately stopped the aircraft. At this position; and prior while moving; Aircraft Y was to our left; and we were to their right. We attempted to contact ground 2-3 times before getting their attention on the radio. By said time; the Aircraft Y had passed; with their wingtip passing directly over our nose cone; height cleared our aircraft.Ground stated they thought our gate was Y and would have turned before; to which I stated for the third time the gate was X. They apologized and we continued via Bravo to gate after the Aircraft Y was well past.The cause is DIRECTLY links to two factors: 1- ATC listed our gate in their system as Y; but never gives entry instructions (ever) to ramp. The taxi instructions ended with 'Bravo' and we are expected to make a turn into the gate from Bravo. 2- The use of inbound/outbound (121.9/121.75) frequencies instead of east/west or north/south like every other airport with multiple ground frequencies means that aircraft will be passing; cutting in front of; etc. without every hearing what the other aircraft is doing. This adds major confusion daily.ATC should give terminal directions to the ramp. For example; 'Taxi via bravo; use A15 to ramp.' This would have triggered us to say 'we are going to the Lima gates; not Y gates.' Change ground frequencies so that everyone on ground near each other are on the same frequencies. Divide the airport into east/west north/south; not inbound/outbound.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.