Air carrier X TCASII RA with aircraft in VFR traffic pattern.

Attributes
ACN	260203
Time
Date	199312
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : eug
State Reference	OR
Altitude	agl bound lower : 365 agl bound upper : 365
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : eug
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach
Route In Use	approach : straight in
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	other
Flight Plan	None
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : radar
Experience	controller non radar : 2 controller radar : 5
ASRS Report	260203
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Air Traffic Incident	other

Narrative:

Air carrier X on final for runway 16 stated that he had a TCASII RA with an small aircraft Y that was on left downwind for runway 16. The crew member of the air carrier X then stated that he had the small aircraft Y in sight. This has happened several times at this airport in the last yr and TCASII passenger jets have actually made gars in response to receiving these RA's close to the airport. In all cases, it was a light aircraft in the touch and go pattern that caused the RA. Additionally, the light aircraft had already been sequenced to follow the jets and had reported their traffic 'in sight.' this causes extra workload and coordination on all controllers involved (approach, departure, local, etc.) and causes potential safety hazards because we often have traffic crossing the departure end of runway 16 in the pattern for the crossing runway (runway 21). I think it should be mandatory the pilots have their TCASII set to the 'traffic only' mode within 5 NM of the destination airport.

Original NASA ASRS Text

Title: ACR X TCASII RA WITH ACFT IN VFR TFC PATTERN.

Narrative: ACR X ON FINAL FOR RWY 16 STATED THAT HE HAD A TCASII RA WITH AN SMA Y THAT WAS ON L DOWNWIND FOR RWY 16. THE CREW MEMBER OF THE ACR X THEN STATED THAT HE HAD THE SMA Y IN SIGHT. THIS HAS HAPPENED SEVERAL TIMES AT THIS ARPT IN THE LAST YR AND TCASII PAX JETS HAVE ACTUALLY MADE GARS IN RESPONSE TO RECEIVING THESE RA'S CLOSE TO THE ARPT. IN ALL CASES, IT WAS A LIGHT ACFT IN THE TOUCH AND GO PATTERN THAT CAUSED THE RA. ADDITIONALLY, THE LIGHT ACFT HAD ALREADY BEEN SEQUENCED TO FOLLOW THE JETS AND HAD RPTED THEIR TFC 'IN SIGHT.' THIS CAUSES EXTRA WORKLOAD AND COORD ON ALL CTLRS INVOLVED (APCH, DEP, LCL, ETC.) AND CAUSES POTENTIAL SAFETY HAZARDS BECAUSE WE OFTEN HAVE TFC XING THE DEP END OF RWY 16 IN THE PATTERN FOR THE XING RWY (RWY 21). I THINK IT SHOULD BE MANDATORY THE PLTS HAVE THEIR TCASII SET TO THE 'TFC ONLY' MODE WITHIN 5 NM OF THE DEST ARPT.

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.