A B737-800 on approach to dfw experienced a conflict with a departure from a crossing runway.

Attributes
ACN	713624
Time
Date	200610
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : dfw.airport
State Reference	TX
Altitude	msl single value : 1000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : dfw.tower tower : dfw.tower
Operator	common carrier : air carrier
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : dfw.tower
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff climbout : initial
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	713624
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : airborne less severe
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Miss Distance	horizontal : 2500 vertical : 0
Supplementary
Problem Areas	ATC Human Performance Weather
Primary Problem	ATC Human Performance

Narrative:

On final to runway 17L at dfw inside the FAF we heard a flight cleared for takeoff on runway 13L. We were IMC at this time. We broke out at about 1000 ft and the first officer started looking for this flight. It took awhile because he expected the flight to be in the air or near there. It was in fact just beginning his roll. He called it in sight and said it was going to be close. I looked for the plane and had the same problem; expecting it to be farther along. We continued and the aircraft lifted off and climbed out right through our flight path (the aircraft actually went through the flight path vector on the HUD). We were approximately 1/2 mi from it at this point. It cleared and we continued and landed normal. I'm not sure if this meets the criteria for a near miss. At the least it would have been very disconcerting to have been at the closest point and just popping out to the clouds and have a plane 'boresighted' in the HUD. The first officer's situational awareness was superb and helped me immensely with this situation. As I said I don't think there was much risk of collision since our courses were so divergent; but it was still a little uncomfortable.

Original NASA ASRS Text

Title: A B737-800 ON APCH TO DFW EXPERIENCED A CONFLICT WITH A DEP FROM A XING RWY.

Narrative: ON FINAL TO RWY 17L AT DFW INSIDE THE FAF WE HEARD A FLT CLRED FOR TKOF ON RWY 13L. WE WERE IMC AT THIS TIME. WE BROKE OUT AT ABOUT 1000 FT AND THE FO STARTED LOOKING FOR THIS FLT. IT TOOK AWHILE BECAUSE HE EXPECTED THE FLT TO BE IN THE AIR OR NEAR THERE. IT WAS IN FACT JUST BEGINNING HIS ROLL. HE CALLED IT IN SIGHT AND SAID IT WAS GOING TO BE CLOSE. I LOOKED FOR THE PLANE AND HAD THE SAME PROB; EXPECTING IT TO BE FARTHER ALONG. WE CONTINUED AND THE ACFT LIFTED OFF AND CLBED OUT RIGHT THROUGH OUR FLT PATH (THE ACFT ACTUALLY WENT THROUGH THE FLT PATH VECTOR ON THE HUD). WE WERE APPROX 1/2 MI FROM IT AT THIS POINT. IT CLRED AND WE CONTINUED AND LANDED NORMAL. I'M NOT SURE IF THIS MEETS THE CRITERIA FOR A NEAR MISS. AT THE LEAST IT WOULD HAVE BEEN VERY DISCONCERTING TO HAVE BEEN AT THE CLOSEST POINT AND JUST POPPING OUT TO THE CLOUDS AND HAVE A PLANE 'BORESIGHTED' IN THE HUD. THE FO'S SITUATIONAL AWARENESS WAS SUPERB AND HELPED ME IMMENSELY WITH THIS SITUATION. AS I SAID I DON'T THINK THERE WAS MUCH RISK OF COLLISION SINCE OUR COURSES WERE SO DIVERGENT; BUT IT WAS STILL A LITTLE UNCOMFORTABLE.

Data retrieved from NASA's ASRS site as of January 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.