S80 flight crew experiences a slight overshoot of runway centerline during visual approach. They get...

Attributes
ACN	349370
Time
Date	199610
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : dfw
State Reference	TX
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : dfw
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	cruise other descent : approach
Route In Use	approach : visual arrival other enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent : approach
Route In Use	approach : visual enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	349370
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	conflict : airborne less severe non adherence : clearance non adherence : required legal separation other anomaly other other spatial deviation
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	flight crew : became reoriented flight crew : returned to intended course or assigned course
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

ATC facility: regional approach. Location: downwind e-side dfw. First officer was flying on the downwind leg of dfw. We had been given expect runway 35C and briefed the approach. We were level at 11000 ft and told to descend to 6000 ft. After we had started our descent we were given a frequency change to 119. After I checked in we were told to expect runway 35R. I briefed the approach quickly and we were then given a turn to 270 degrees. We noticed a TCASII target at slightly above our altitude but coming in our direction. Shortly thereafter, we were told to turn to 310 degrees and asked if we had the airport. After asking my first officer if he had the runway he said yes and I told approach that we did. Approach then cleared us for a visual to runway 35R. We were in close and high when we turned into the final. Because the approach controller had us in tight on downwind and base we overshot the final approach a little. Just as we started our turn the previous TCASII target became an TA, with an RA following quickly to descend command. At no time did approach call out this traffic or tell us that he was coming from the w-side landing on runway 35C. Our only indication was the various TCASII alerts. Approach control's vector was 310 degrees prior to asking if we had the airport. Had I known that the oncoming traffic was being set up for runway 35C, I would have my first officer to make a much harder turn to not overshoot the final approach. I asked the controller why he didn't point out the traffic and he said it wasn't his responsibility to do so. I was under the impression that he had to.

Original NASA ASRS Text

Title: S80 FLC EXPERIENCES A SLIGHT OVERSHOOT OF RWY CTRLINE DURING VISUAL APCH. THEY GET A TCASII RA FROM OPPOSITE DIRECTION TFC ON A VISUAL FOR ANOTHER RWY. PIC COMPLAINS OF 'CTLR ERROR' IN TA NOT GIVEN. POTENTIAL CONFLICT.

Narrative: ATC FACILITY: REGIONAL APCH. LOCATION: DOWNWIND E-SIDE DFW. FO WAS FLYING ON THE DOWNWIND LEG OF DFW. WE HAD BEEN GIVEN EXPECT RWY 35C AND BRIEFED THE APCH. WE WERE LEVEL AT 11000 FT AND TOLD TO DSND TO 6000 FT. AFTER WE HAD STARTED OUR DSCNT WE WERE GIVEN A FREQ CHANGE TO 119. AFTER I CHKED IN WE WERE TOLD TO EXPECT RWY 35R. I BRIEFED THE APCH QUICKLY AND WE WERE THEN GIVEN A TURN TO 270 DEGS. WE NOTICED A TCASII TARGET AT SLIGHTLY ABOVE OUR ALT BUT COMING IN OUR DIRECTION. SHORTLY THEREAFTER, WE WERE TOLD TO TURN TO 310 DEGS AND ASKED IF WE HAD THE ARPT. AFTER ASKING MY FO IF HE HAD THE RWY HE SAID YES AND I TOLD APCH THAT WE DID. APCH THEN CLRED US FOR A VISUAL TO RWY 35R. WE WERE IN CLOSE AND HIGH WHEN WE TURNED INTO THE FINAL. BECAUSE THE APCH CTLR HAD US IN TIGHT ON DOWNWIND AND BASE WE OVERSHOT THE FINAL APCH A LITTLE. JUST AS WE STARTED OUR TURN THE PREVIOUS TCASII TARGET BECAME AN TA, WITH AN RA FOLLOWING QUICKLY TO DSND COMMAND. AT NO TIME DID APCH CALL OUT THIS TFC OR TELL US THAT HE WAS COMING FROM THE W-SIDE LNDG ON RWY 35C. OUR ONLY INDICATION WAS THE VARIOUS TCASII ALERTS. APCH CTL'S VECTOR WAS 310 DEGS PRIOR TO ASKING IF WE HAD THE ARPT. HAD I KNOWN THAT THE ONCOMING TFC WAS BEING SET UP FOR RWY 35C, I WOULD HAVE MY FO TO MAKE A MUCH HARDER TURN TO NOT OVERSHOOT THE FINAL APCH. I ASKED THE CTLR WHY HE DIDN'T POINT OUT THE TFC AND HE SAID IT WASN'T HIS RESPONSIBILITY TO DO SO. I WAS UNDER THE IMPRESSION THAT HE HAD TO.

Data retrieved from NASA's ASRS site as of July 2007 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.

S80 flight crew experiences a slight overshoot of runway centerline during visual approach. They get a TCASII RA from opposite direction traffic on a visual for another runway. PIC complains of 'controller error' in TA not given. Potential conflict.