Sna controller described a conflict event when traffic just transferred to the tower frequency exper...

Narrative:

I was working local one when air carrier X called me on about a 7 mile final. As I was answering him I noticed a head on target with the altitude of 4;500 feet. My assist clicked on the target to find out that it was a C206 opposite direction of air carrier X. Air carrier X was descending out of 5;000. I immediately called traffic and when he did not have the aircraft in sight I issued a traffic alert. I could hear in the background 'climb; climb' from his TCAS. My assist called the sector and it is my understanding that the controller was completely oblivious to the situation as his main point of the call was; 'if air carrier X can't descend from there then...' alternate instructions. When air carrier X landed I asked him if he was told about traffic as it was very close. He said he had not heard about the traffic until he got to me and that he got an RA and responded to it. The targets merged and air carrier X had to climb to avoid a collision. These types of situations are becoming more frequent with the sectors we work with; mainly because of the large amount of training and newer controllers. This situation was very bad and very close. Recommendation; I think people are getting checked out too rapidly at times; as things that are common knowledge to us are unknown to some of the controllers we speak to. Take for example the run-down patch. When there's an amendment; we run the aircraft down and put AM1 at the end. A couple of days ago; a certified controller asked us what that meant. It is in the LOA and should definitely be common knowledge to an approach controller working in the coast area. We are coming across many of these situations and I think that perhaps the training is being cut to short; I'm not quite sure; but there is definitely a growing amount of situations like this.

Original NASA ASRS Text

Title: SNA Controller described a conflict event when traffic just transferred to the tower frequency experienced a TCAS alert; the reporter noting traffic was not issued by the SCT Controller and questioned SCT Controllers' training and experience levels.

Narrative: I was working Local One when Air Carrier X called me on about a 7 mile final. As I was answering him I noticed a head on target with the altitude of 4;500 feet. My assist clicked on the target to find out that it was a C206 opposite direction of Air Carrier X. Air Carrier X was descending out of 5;000. I immediately called traffic and when he did not have the aircraft in sight I issued a traffic alert. I could hear in the background 'Climb; Climb' from his TCAS. My assist called the sector and it is my understanding that the controller was completely oblivious to the situation as his main point of the call was; 'If Air Carrier X can't descend from there then...' alternate instructions. When Air Carrier X landed I asked him if he was told about traffic as it was VERY close. He said he had not heard about the traffic until he got to me and that he got an RA and responded to it. The targets merged and Air Carrier X had to climb to avoid a collision. These types of situations are becoming more frequent with the sectors we work with; mainly because of the large amount of training and newer controllers. This situation was very bad and very close. Recommendation; I think people are getting checked out too rapidly at times; as things that are common knowledge to us are unknown to some of the controllers we speak to. Take for example the run-down patch. When there's an amendment; we run the aircraft down and put AM1 at the end. A couple of days ago; a Certified Controller asked us what that meant. It is in the LOA and should definitely be common knowledge to an Approach Controller working in the Coast Area. We are coming across many of these situations and I think that perhaps the training is being cut to short; I'm not quite sure; but there is definitely a growing amount of situations like this.

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

Attributes
ACN	877387
Time
Date	201003
Local Time Of Day	0001-0600
Place
Locale Reference	SNA.Tower
State Reference	CA
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

Sna controller described a conflict event when traffic just transferred to the tower frequency experienced a TCAS alert; the reporter noting traffic was not issued by the sct controller and questioned sct controllers' training and experience levels.