B767 flight crew reported the ground controller created a taxiway conflict along with clearance onto an active runway with traffic on takeoff roll resulted in critical ground conflicts requiring evasive action. Flight crew also stated that ATC ICAO procedures were not followed with use of multiple languages leading to confusion.
Synopsis
B767 flight crew reported the ground controller created a taxiway conflict along with clearance onto an active runway with traffic on takeoff roll resulted in critical ground conflicts requiring evasive action. Flight crew also stated that ATC ICAO procedures were not followed with use of multiple languages leading to confusion.
Narrative
In Santo Domingo on the outbound leg of SDQ to ZZZ; the Captain (pilot flying and taxiing) and FO (pilot monitoring). The following narrative is from the captain seating on the left seat. I uploaded a MDSD airport Diagram to facilitate clarity if needed. During Ground operations at MDSD airport. Ground operations were conducted on Runway 35 as per ATIS. Our clearance was for departure Runway 35. Aircraft X landed on Runway 17 which at the time created a jam on the taxiway Juliet heading to RW 35. As Aircraft X vacated the runway and started taxing on Juliet Taxiway. They held short off Taxiway C so we can exit. We were coming out from the gate which Aircraft X was supposed to use next after we leave. We received clearance to taxi on to Charlie. Midway between the ramp and Juliet and the ramp; we received a clearance to enter the runway back track on the runway and exit on Delta to join again on Juliet to continue taxing on Juliet to Runway 35 at hotel taxiway and hold short. We read back the clearance and we proceeded to taxi towards the active runway. We had all the intention to taxi on to the runway because we were clear to it. Is our procedure to clear loudly and make sure is clear before turning so I cleared my left and look right but we can't see the runway because the angle of the taxi way Charlie and the runway. Additionally; there is hump on the runway and we can't see the approach end of Runway 35. So; we could not clear verbally totally the right side. Suddenly we heard on the radio to hold short of the runway. I stop the airplane immediately and abruptly; soon we see an airplane passing in front of us taking off. Our airplane was clear of the runway with the nose passed the hold short line slightly. Somehow; we were cleared to taxi on to an active runway to backtrack and another aircraft was clear for takeoff at the same time.The nature of that airport where they speak English to the foreign carriers and Spanish to others makes it difficult to keep ground situational awareness.Because of that we did not realize that another aircraft was cleared for takeoff. To be clear; at no time we received an instruction to hold short of the Runway 35 for departing traffic. ATC made a mistake of clearing two aircraft to move in a collision course and we did not catch the mistake. Although tower cleared us to taxi on to runway; they ultimately realized the mistake and at the last second instructed us to hold short of the runway.After that we continue safely ground operations and came back to ZZZ without further incident.We; the crew believe; there was a gross negligence from the Dominican ATC part on almost causing a near miss. The Santo Domingo allowing an incoming aircraft to land on the opposite runway in use created a chain of events that led to a near ground / in flight collision. The dual language nature of that international airport takes away situational awareness from the flight crews as one or the others don't speak both languages. Improper ATC procedures to clear 2 aircraft's on to an active runway. Dominican ATC must adhere to strict ICAO procedures for aircraft handling. That particular controller was doing clearance; ground and tower in two languages. Needless to say; he was most likely very overload. That on itself deserves a more detailed examination.
Second reporter narrative
While taxiing to Runway 35; we were instructed to follow Taxiway C and backtrack along Runway 35 and then exit on Taxiway D to avoid Aircraft Y heading north on Taxiway F. Aircraft Y just landed Runway 17 and was taxiing to the gate. MDSD ATCT initially gave Aircraft Y taxi instructions that didn't provide any separation from our aircraft. At the time Aircraft Y received their taxi instructions; we had already been cleared to push and start onto the ramp and told to expect Runway 35. Once I saw Aircraft Y land Runway 17; I immediately mentioned it to the captain. Then upon hearing the taxi instructors that MDSD provided to Aircraft Y; I called MDSD ATCT to inform them of the pending head-to-head conflict along Taxiway C that would result from these instructions. Upon receiving my call; MDSD ATCT instructed Aircraft Y to hold short of Taxiway C so we could pass in front of them on our way to Runway 17/35. We were given instructions to pass in front of Aircraft Y on Taxiway C and then backtrack Runway 35 then exit on Taxiway D then continue to holding point Runway 35 along Taxiway F. Just prior to entering Runway 35; MDSD ATCT gave us hold short of runway instructions for a departing Aircraft Y off Runway 35. This was the first mention MDSD ATCT made of the departing Aircraft Y to us. We resumed our taxi instructions after Aircraft Y departed. All safety procedures for entering a runway were properly followed. The rest of the flight to ZZZ was conducted without incident. Traffic conflict between taxiing and departing aircraft that was not initially detected or resolved by MDSD ATCT. Poor ATC instructions - The initial taxi instructions given to Aircraft Y didn't account for the fact that we were blocking their path to gate XX. Language - Aircraft Y received their takeoff clearance in Spanish. Opposite direction landing by Aircraft Y- The opposite direction landing began the entire sequence of events that required us to use Runway 17/35 as a parallel taxiway to Taxiway F so we could bypass the northbound Aircraft Y on taxiway F between taxiways C and D.MDSD Airport layout - There is a rise in terrain along Runway 17/35 between Taxiway C and the approach end of Runway 35. Also; Taxiway C approaches Runway 35 at an acute angle such that it is difficult to get a clear view of the approach end of Runway 35 from either pilot seats.Given the confusion with the opposite direction Aircraft Y; I thought to confirm our clearance to enter Runway 35. But I never acted in this impulse. Even though the clearance to enter was given and read back previously. Had I requested an additional verification of our clearance to enter the runway; the conflict with the departing Aircraft Y might have been avoided. I could have also done a more thorough visual scan; moving my head around the blind spots; rather than the more cursory check with limited visibility that I actually did. We put too much of the see and avoid burden on MDSD ATCT. I'll be more vigilant in the future with enhanced visual scanning of the runway and a secondary radio call to confirm clearance to enter the runway whenever there is any chance confusion.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.