Air carrier operating with sct; reportedly was vectored into a potential conflict with a parachute o...

Narrative:

We were on the LYNDI2 arrival into san and were cleared to descend and cross trixi at 12;000 ft. While in the descent we were given a speed restriction of 280 KTS then 270 KTS; which we complied with. The controller appeared to forget about us and by baret intersection we were still at 12;000 ft and had to request a lower altitude. The controller was obviously overloaded and with the great visibility that we had we called the field in sight so as to be cleared for the visual approach. The controller gave us a clearance direct to vydda; descend to 6;000 ft and cleared for the visual approach to runway 27. Prior to reaching vydda; the controller canceled our clearance and gave us a turn to 180 degrees. [The controller] then gave us a turn to 240 degrees while still level at 6;000 ft south of okain. While in the turn to 240 degrees; another controller came on and gave us a further turn to 350 degrees with the following exchange: controller: air carrier X turn right to 350 degrees. Air carrier X: we are currently in the turn to 350 degrees. Controller: air carrier X I need you to turn right immediately to 350 deg. Air carrier X: we are in the turn to 350 degrees. Controller: air carrier X you have parachute jumping activity at 12 o'clock; ? Mile at 10;500 ft. Air carrier X: we are looking for the traffic. We never saw the traffic that was over 4;000 ft above us and no TCAS warning was received. The controller did not say anything else after that other than to once again clear us for the visual approach. No explanation; no apology; no nothing. The controller seemed upset that we were in the airspace that another controller had vectored us into. I made a comment on the radio that this was the worst controlling I had ever seen and received no response whatsoever. This was obviously a close call with traffic that we knew nothing about. No warning about parachute jumping in the vicinity of our location; no traffic call out other than as a last minute evasive maneuver; no explanation; no nothing. The impression we got was that controller training was in progress and the instructor took over at the last minute. The airspace we entered was exactly where the controller vectored us into and the close call was certainly not of our doing.

Original NASA ASRS Text

Title: Air Carrier operating with SCT; reportedly was vectored into a potential conflict with a parachute operation with no prior notification; the reporter suspecting controller training was in progress.

Narrative: We were on the LYNDI2 arrival into SAN and were cleared to descend and cross TRIXI at 12;000 FT. While in the descent we were given a speed restriction of 280 KTS then 270 KTS; which we complied with. The Controller appeared to forget about us and by BARET Intersection we were still at 12;000 FT and had to request a lower altitude. The Controller was obviously overloaded and with the great visibility that we had we called the field in sight so as to be cleared for the visual approach. The Controller gave us a clearance direct to VYDDA; descend to 6;000 FT and cleared for the visual approach to Runway 27. Prior to reaching VYDDA; the Controller canceled our clearance and gave us a turn to 180 degrees. [The Controller] then gave us a turn to 240 degrees while still level at 6;000 FT south of OKAIN. While in the turn to 240 degrees; another Controller came on and gave us a further turn to 350 degrees with the following exchange: Controller: Air Carrier X turn right to 350 degrees. Air Carrier X: We are currently in the turn to 350 degrees. Controller: Air Carrier X I need you to turn right immediately to 350 deg. Air Carrier X: We are in the turn to 350 degrees. Controller: Air Carrier X you have parachute jumping activity at 12 o'clock; ? mile at 10;500 FT. Air Carrier X: We are looking for the traffic. We never saw the traffic that was over 4;000 FT above us and no TCAS warning was received. The Controller did not say anything else after that other than to once again clear us for the visual approach. No explanation; no apology; no nothing. The Controller seemed upset that we were in the airspace that another Controller had vectored us into. I made a comment on the radio that this was the worst controlling I had ever seen and received no response whatsoever. This was obviously a close call with traffic that we knew nothing about. No warning about parachute jumping in the vicinity of our location; no traffic call out other than as a last minute evasive maneuver; no explanation; no nothing. The impression we got was that Controller training was in progress and the instructor took over at the last minute. The airspace we entered was exactly where the Controller vectored us into and the close call was certainly not of our doing.

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	929225
Time
Date	201101
Local Time Of Day	0001-0600
Place
Locale Reference	SAN.Airport
State Reference	CA
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	STAR LYNDI2
Flight Plan	IFR
Person 1
Function	Pilot Flying Captain
Experience	Flight Crew Last 90 Days 215 Flight Crew Total 14098 Flight Crew Type 7489
Person 2
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 200 Flight Crew Total 11000 Flight Crew Type 5000
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Other / Unknown

Air carrier operating with sct; reportedly was vectored into a potential conflict with a parachute operation with no prior notification; the reporter suspecting controller training was in progress.