37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 739506 |
Time | |
Date | 200705 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : gcn.vortac |
State Reference | CA |
Altitude | msl single value : 9000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sct.tracon tower : zzz.tower |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 135 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : intermediate altitude |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : sct.tracon |
Operator | common carrier : air carrier |
Make Model Name | Brasilia EMB-120 All Series |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : developmental |
Experience | controller limited radar : 8.5 controller military : 1 controller radar : 5 controller time certified in position1 : 0.5 |
ASRS Report | 739506 |
Events | |
Anomaly | conflict : airborne less severe |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
Busy traffic en route into lax; between lax and san; and off sna to all points. I was sequencing a number of lax arrs from san and points east. The rj was coming in on the lax vista arrival descending to 12000 ft. The E120 was in cruise at 9000 ft between lax and san on the route. Complicating factors included a slow climbing P46T going to 13000 ft that one ZLA sector did not point out to another sector; which created an almost instant conflict with the 12000 ft rj landing lax. I had to turn the rj almost immediately to avoid conflict with the P46T. Since the rj was last in line and still moving fast; I chose to descend to 8000 ft with a turn to the west to set him up for the sequence. At the same time; sna launched an air carrier jet with a route change; but they had not issued the correct altitudes and he took the wrong frequency so he climbed to 7000 ft NORDO in the middle of my arrival sequence which was at 8000 ft. He was roughly 12 mi from the airport when 2-WAY was restored and put on a vector to get out of the way. At that time; the controller next to me pointed to the rj and said 'that's not good.' the rj was on a course that would pass near the E120 and they were near the same altitude. I issued immediate turns to the rj and E120 to ensure that they were further apart and did not issue traffic because there was not time to do so. They were about 4 mi apart at the closest point; but it could have been much closer had I not acted. I was rattled; but continued working until I was relieved. There were approximately 8-11 aircraft on frequency at the time. Complicating factors included the mistake by sna; the number of aircraft on frequency and on varied rtes; plus the slow-climbing traffic that was not accounted for by ZLA. Better handling would have been to slow the rj and leave him at 10000 ft until the E120 passed or continued his track toward sli until I could turn him safely into the sequence. I would also have asked the ZLA controller to descend the rj to 14000 ft and requested control.
Original NASA ASRS Text
Title: SCT CTLR DESCRIBED NEAR SEPARATION LOSS AT 9000 WITH LAX ARR AND ENROUTE TFC; ISSUED TURNS; BUT FAILED TO ISSUE TFC INFO.
Narrative: BUSY TFC ENRTE INTO LAX; BTWN LAX AND SAN; AND OFF SNA TO ALL POINTS. I WAS SEQUENCING A NUMBER OF LAX ARRS FROM SAN AND POINTS E. THE RJ WAS COMING IN ON THE LAX VISTA ARR DSNDING TO 12000 FT. THE E120 WAS IN CRUISE AT 9000 FT BTWN LAX AND SAN ON THE RTE. COMPLICATING FACTORS INCLUDED A SLOW CLBING P46T GOING TO 13000 FT THAT ONE ZLA SECTOR DID NOT POINT OUT TO ANOTHER SECTOR; WHICH CREATED AN ALMOST INSTANT CONFLICT WITH THE 12000 FT RJ LNDG LAX. I HAD TO TURN THE RJ ALMOST IMMEDIATELY TO AVOID CONFLICT WITH THE P46T. SINCE THE RJ WAS LAST IN LINE AND STILL MOVING FAST; I CHOSE TO DSND TO 8000 FT WITH A TURN TO THE W TO SET HIM UP FOR THE SEQUENCE. AT THE SAME TIME; SNA LAUNCHED AN ACR JET WITH A RTE CHANGE; BUT THEY HAD NOT ISSUED THE CORRECT ALTS AND HE TOOK THE WRONG FREQ SO HE CLBED TO 7000 FT NORDO IN THE MIDDLE OF MY ARR SEQUENCE WHICH WAS AT 8000 FT. HE WAS ROUGHLY 12 MI FROM THE ARPT WHEN 2-WAY WAS RESTORED AND PUT ON A VECTOR TO GET OUT OF THE WAY. AT THAT TIME; THE CTLR NEXT TO ME POINTED TO THE RJ AND SAID 'THAT'S NOT GOOD.' THE RJ WAS ON A COURSE THAT WOULD PASS NEAR THE E120 AND THEY WERE NEAR THE SAME ALT. I ISSUED IMMEDIATE TURNS TO THE RJ AND E120 TO ENSURE THAT THEY WERE FURTHER APART AND DID NOT ISSUE TFC BECAUSE THERE WAS NOT TIME TO DO SO. THEY WERE ABOUT 4 MI APART AT THE CLOSEST POINT; BUT IT COULD HAVE BEEN MUCH CLOSER HAD I NOT ACTED. I WAS RATTLED; BUT CONTINUED WORKING UNTIL I WAS RELIEVED. THERE WERE APPROX 8-11 ACFT ON FREQ AT THE TIME. COMPLICATING FACTORS INCLUDED THE MISTAKE BY SNA; THE NUMBER OF ACFT ON FREQ AND ON VARIED RTES; PLUS THE SLOW-CLBING TFC THAT WAS NOT ACCOUNTED FOR BY ZLA. BETTER HANDLING WOULD HAVE BEEN TO SLOW THE RJ AND LEAVE HIM AT 10000 FT UNTIL THE E120 PASSED OR CONTINUED HIS TRACK TOWARD SLI UNTIL I COULD TURN HIM SAFELY INTO THE SEQUENCE. I WOULD ALSO HAVE ASKED THE ZLA CTLR TO DSND THE RJ TO 14000 FT AND REQUESTED CTL.
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.