Narrative:

This problem arose when we were given vectors across the localizer 19R at orange county airport (270 degrees, 3000 ft) for spacing. Then vectors of 090 degrees, 3000 ft to position us for approach. We received the first TCASII RA (descend) and did so. We saw the traffic about 1/2 mi. We descended to about 2400 ft when TCASII was resolved and ATC was advised of TCASII deviation. Controller said 'roger.' we then started climb back to 3000 ft and our 040 degree heading and received a second TCASII RA. We responded (descended) but did not see this traffic. We were given a 140 degree heading and we were climbing toward 3000 ft when we received a third TCASII RA and descended again before it was resolved. We saw this traffic and other traffic. We were then given a 165 degree intercept to ILS 19R at any altitude. No further events occurred, normal approach. Contributing factors: a lot of friday afternoon light airplane traffic in this area, some with TCASII, some not. The conflicts were discovered 3 times by TCASII, twice verified visually, but other traffic added to the problem. Correction action on all TCASII RA's was by TCASII command sectors. The decision to vector us in this area with the known traffic was wrong and potentially dangerous. The pilots flying in that area uncontrolled and without TCASII showed a lack of judgement so close to a final approach. I feel the TCASII was instrumental in helping our situation and every aircraft flying should have the TCASII system. Supplemental information from acn 253004: to correct this type of problem from recurring, traffic in the area needs to be limited or better controled. At certain times during the day in the sna area, there is more traffic than ATC can control safely, both VFR and IFR. Another solution would be for sna traffic to hold outside the area so a direct turn can be made to the 19R ILS without a 270 degree past the airport as is common during heavy traffic times.

Related reports:

Google
 

Original NASA ASRS Text

Title: LGT HAS 3 TCASII RA'S ON APCH VECTORS.

Narrative: THIS PROB AROSE WHEN WE WERE GIVEN VECTORS ACROSS THE LOC 19R AT ORANGE COUNTY ARPT (270 DEGS, 3000 FT) FOR SPACING. THEN VECTORS OF 090 DEGS, 3000 FT TO POS US FOR APCH. WE RECEIVED THE FIRST TCASII RA (DSND) AND DID SO. WE SAW THE TFC ABOUT 1/2 MI. WE DSNDED TO ABOUT 2400 FT WHEN TCASII WAS RESOLVED AND ATC WAS ADVISED OF TCASII DEV. CTLR SAID 'ROGER.' WE THEN STARTED CLB BACK TO 3000 FT AND OUR 040 DEG HDG AND RECEIVED A SECOND TCASII RA. WE RESPONDED (DSNDED) BUT DID NOT SEE THIS TFC. WE WERE GIVEN A 140 DEG HDG AND WE WERE CLBING TOWARD 3000 FT WHEN WE RECEIVED A THIRD TCASII RA AND DSNDED AGAIN BEFORE IT WAS RESOLVED. WE SAW THIS TFC AND OTHER TFC. WE WERE THEN GIVEN A 165 DEG INTERCEPT TO ILS 19R AT ANY ALT. NO FURTHER EVENTS OCCURRED, NORMAL APCH. CONTRIBUTING FACTORS: A LOT OF FRIDAY AFTERNOON LIGHT AIRPLANE TFC IN THIS AREA, SOME WITH TCASII, SOME NOT. THE CONFLICTS WERE DISCOVERED 3 TIMES BY TCASII, TWICE VERIFIED VISUALLY, BUT OTHER TFC ADDED TO THE PROB. CORRECTION ACTION ON ALL TCASII RA'S WAS BY TCASII COMMAND SECTORS. THE DECISION TO VECTOR US IN THIS AREA WITH THE KNOWN TFC WAS WRONG AND POTENTIALLY DANGEROUS. THE PLTS FLYING IN THAT AREA UNCTLED AND WITHOUT TCASII SHOWED A LACK OF JUDGEMENT SO CLOSE TO A FINAL APCH. I FEEL THE TCASII WAS INSTRUMENTAL IN HELPING OUR SIT AND EVERY ACFT FLYING SHOULD HAVE THE TCASII SYS. SUPPLEMENTAL INFO FROM ACN 253004: TO CORRECT THIS TYPE OF PROB FROM RECURRING, TFC IN THE AREA NEEDS TO BE LIMITED OR BETTER CTLED. AT CERTAIN TIMES DURING THE DAY IN THE SNA AREA, THERE IS MORE TFC THAN ATC CAN CTL SAFELY, BOTH VFR AND IFR. ANOTHER SOLUTION WOULD BE FOR SNA TFC TO HOLD OUTSIDE THE AREA SO A DIRECT TURN CAN BE MADE TO THE 19R ILS WITHOUT A 270 DEG PAST THE ARPT AS IS COMMON DURING HVY TFC TIMES.

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.