Light Transport; Low Wing; 2 Turbojet Eng
Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Flight Crew Last 90 Days 30; Flight Crew Total 17100; Flight Crew Type 3855
Situational Awareness; Distraction; Communication Breakdown
ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Clearance
Flight Crew Took Evasive Action
Procedure; Airspace Structure; Human Factors
We were cleared for takeoff at FTW on Runway 34 to fly runway heading to 3;000 ft. MSL. At approximately 800 ft. were are advised of Aircraft Y off to our right and that Aircraft Y had us in sight. We received a TA at the same time we were issued the traffic from ATC.At the same time a second TA popped up on the TCAS at 12 O'clock on our flight path. This TA immediately turned into a red RA! I reduced power to slow our rate and started to level below our assigned altitude about 2;600 ft. to comply with the RA. The TCAS said to descend. When I looked out the window I viewed what appeared to be Aircraft Z making a hard left turn. I looked at the TCAS and it showed he was 400 ft. above us. As Aircraft Z was moving away the TCAS advised 'Clear of conflict' and we continued our climb to 3;000 ft. MSL. In my opinion this was a near miss!We were not advised before take-off of either of these airplanes. We fly in and out of FTW frequently and this happen several times a year. Either right after takeoff or just as we switch to DFW we are given traffic that is very close. This incident is the worst experience we have had. [I believe] there is a lack of communication between DFW and FTW Tower. All of the DFW and FTW controllers are excellent but this has to be addressed. Aircraft departing should be advised of traffic before takeoff and not while handling initial climb and after takeoff checklists.
Pilot reported not receiving a traffic alert from ATC regarding another aircraft on a similar departure.