L30 controller observed 2 aircraft experienced TCASII RA events with issued VFR traffic below by 500 ft but on another controller's frequency.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	648687
Time
Date	200502
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : las.vortac
State Reference	NV
Altitude	msl single value : 12500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : l30.tracon
Operator	general aviation : personal
Make Model Name	PA-24 Comanche
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Route In Use	enroute airway : v394.airway
Flight Plan	VFR
Aircraft 2
Controlling Facilities	tracon : l30.tracon
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller military : 4 controller non radar : 2 controller radar : 8 controller time certified in position2 : 10 flight time total : 40
ASRS Report	647687
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	conflict : airborne critical
Independent Detector	aircraft equipment : tcas other controllera
Resolutory Action	controller : issued advisory flight crew : took evasive action
Miss Distance	horizontal : 6000 vertical : 500
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Aircraft X; VFR on V394 at 12500 ft; working with another sector in my airspace assist for departure advised me of this traffic and was advised that I was 'watching him.' air carrier Y checked on my frequency and was instructed to maintain 13000 ft for traffic. Traffic was then called to air carrier Y at 12 O'clock position; 10 mi; swbound at 12500 ft (a PA24). Air carrier Y questioned his altitude since his TCASII showed the traffic only 300 ft below him. I offered air carrier Y a turn to avoid the traffic; at which time he advised he was receiving an RA and climbed. (He also asked if this PA24's altitude was verified. I instructed him it was.) air carrier Z; an airbus 320; was 10 mi in trail and checked on. He was instructed to maintain 13000 ft for traffic. My attention was diverted to another situation and a traffic call on the traffic was made after the pilot reported responding to an RA. At the time the traffic call was made. The separation was 3 mi and 500 ft. In the future; I will reach out and take radar on traffic so that I may provide a better service in this situation.

Original NASA ASRS Text

Title: L30 CTLR OBSERVED 2 ACFT EXPERIENCED TCASII RA EVENTS WITH ISSUED VFR TFC BELOW BY 500 FT BUT ON ANOTHER CTLR'S FREQ.

Narrative: ACFT X; VFR ON V394 AT 12500 FT; WORKING WITH ANOTHER SECTOR IN MY AIRSPACE ASSIST FOR DEP ADVISED ME OF THIS TFC AND WAS ADVISED THAT I WAS 'WATCHING HIM.' ACR Y CHKED ON MY FREQ AND WAS INSTRUCTED TO MAINTAIN 13000 FT FOR TFC. TFC WAS THEN CALLED TO ACR Y AT 12 O'CLOCK POS; 10 MI; SWBOUND AT 12500 FT (A PA24). ACR Y QUESTIONED HIS ALT SINCE HIS TCASII SHOWED THE TFC ONLY 300 FT BELOW HIM. I OFFERED ACR Y A TURN TO AVOID THE TFC; AT WHICH TIME HE ADVISED HE WAS RECEIVING AN RA AND CLBED. (HE ALSO ASKED IF THIS PA24'S ALT WAS VERIFIED. I INSTRUCTED HIM IT WAS.) ACR Z; AN AIRBUS 320; WAS 10 MI IN TRAIL AND CHKED ON. HE WAS INSTRUCTED TO MAINTAIN 13000 FT FOR TFC. MY ATTN WAS DIVERTED TO ANOTHER SIT AND A TFC CALL ON THE TFC WAS MADE AFTER THE PLT RPTED RESPONDING TO AN RA. AT THE TIME THE TFC CALL WAS MADE. THE SEPARATION WAS 3 MI AND 500 FT. IN THE FUTURE; I WILL REACH OUT AND TAKE RADAR ON TFC SO THAT I MAY PROVIDE A BETTER SVC IN THIS SIT.

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.