Date: 201404
Local time of day: 1201-1800
Location: DAL.Airport, TX
Flight conditions: VMC
Weather elements / visibility: Windshear
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B DFW
ATC / advisory: TRACON D10; Tower DAL
Second aircraft: Small Transport
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Communication Breakdown; Distraction
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Airport; Procedure; Weather
Primary problem: Ambiguous

Narrative: While working the Departure One position in a south flow; I had Aircraft X check on frequency climbing out of 2;700 FT for 5;000 FT off DAL field. He was only 1 to 2 miles off the departure end and I noticed another target on an S tag (Dallas South satellite position) just off Aircraft X's right side. I didn't call traffic; assuming it was a VFR departure going to Dallas South. Aircraft X several minutes later asked what had happened at Love Field; there was some confusion on DAL Tower frequency and he knew he was close to another aircraft.There was an issue with the departure headings off DAL just before I took the position. Winds were very strong from the southwest and the previous Departure Controller requested DAL use a 140 heading rather than 130 to correct for it. DAL and DFW TMU were having a difference of opinion as to whether or not a heading could be issued with a 'Climb Via'. Departures were actually stopped for a while as the departure issue was debated. After doing this job for thirty years there is one thing I know; procedures need to clear; specific and properly communicated to the workforce. There is no time to discuss ambiguous or less than fully developed procedure while attempting to work traffic (especially busy). I'm not sure if this played a role in the situation but it didn't help.


Second narrative: During the takeoff at Dallas Love Field we had an indication that another aircraft got very close to us and we came close to a near mid air collision. We were approximately 200 - 1000 FT when it occurred because I was doing the After Takeoff Checklist. The Captain first noticed; or rather heard; the Tower Controller telling another aircraft to 'Return to runway heading; NOW' he repeated it a few times. I was focused on the checklist and only heard the last command to turn back to runway heading for the other aircraft. I then looked at the TCAS on my side which was set to ABOVE and 6 miles. I noticed there was an aircraft within 1 mile and -300 FT below us on our 4 to 5 o'clock position (behind us on our right). I tried to look out the window to see this aircraft but I could not see it. I then looked back at the TCAS to see the aircraft getting closer and closer laterally but remained within 300 FT vertically of us for the next 15-20 seconds or so. It appeared that the other aircraft came within less than 1 mile of us. I would estimate the other aircraft was nearly a 1/4 mile away or less and -300 FT below us for about 15 seconds; based on the indication on my TCAS. We were instructed to contact Departure; at which time I asked Departure about the other aircraft. He indicated that they were aware of the situation and would let me know what happened. We never found out what would happen and I received the phone number for Dallas Departure. Every time I tried to call them; the line was busy. After reviewing the tape on the internet it sounded like there was an aircraft that executed a missed approach; because they never received a landing clearance because of our immediate takeoff; which conflicted with another aircraft that was told to turn into their missed approach path during takeoff from [Runway] 13R. We were taking off from [Runway] 13L. The [conflict] was caused by too many aircraft given overlapping flight path instructions. We were close to another aircraft because of the aircraft behind us that executed a missed approach or the aircraft that took off from [Runway] 13R. I am still not sure which one. We need to always maintain good situational awareness by listening to the other aircraft on the frequency and estimating their position relative to ours. However; we did exactly as Tower and Departure instructed.


Synopsis: Three reports about an aircraft coming too close to another aircraft and what may have happened to cause this. Winds may have been a factor or a pilot not flying the assigned heading may also be the factor. Congestion on frequency may have played a part.