Flight Crew Air Transport Pilot (ATP)
Communication Breakdown
ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Human Factors; Procedure
Told to descend by ATC; checked TCAS and noticed an aircraft climbing into that altitude. Fl320 to Fl300. Pilot Flying CAPTAIN; asked to query ATC on traffic/altitude by Pilot Not Flying First Officer. During query a TCAS RA was issued and complied with both our aircraft and an Airbus flight opposite direction; they descended and we climbed. Multiple aircraft and ATC communications followed but still conflicted with TCAS RA. Aircraft were in close proximity but remained in visual separation while complying with TCAS instructions. ATC finally issued a higher altitude for us after event at FL 340. Late instructions; conflicting resolutions (ATC; pilot; TCAS) and communication failure/ similar call signs all were threats in a time compressed manner. Could be possible that ATC confused which aircraft was which and issued opposite instructions than intended.... No further conflicts arose and we continued to destination.Communication was the largest threat. Although not ideal; Captain Pilot Flying; could have communicated directly to ATC about possible conflict decreasing time to action; both with ATC instructions and resolutions.
When ATC cleared an EMB-145 flight crew to an altitude already inhabited by another aircraft; a TCAS RA was received and complied with in a timely fashion.