37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 610257 |
Time | |
Date | 200402 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : zla.airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zla.artcc |
Operator | general aviation : corporate |
Make Model Name | Gulfstream II |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zla.artcc |
Operator | general aviation : corporate |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 11000 flight time type : 3000 |
ASRS Report | 610259 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 2880 flight time type : 150 |
ASRS Report | 610258 |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Ambiguous |
Narrative:
We departed vny. Our flight plan was to fly over las vegas, NM. This route was selected to take advantage of favorable winds. As we were climbing out and handed over to la, we were getting vectored left off course. Unbeknownst to us, there was another aircraft with a similar call sign on frequency. The other aircraft acknowledged a radio transmission that I now realize was for us which was 'cleared direct las vegas, nv.' while the other aircraft is turning the wrong way I'm still expecting a right turn direct las vegas. Eventually the controller asked us what we were doing which was 'still on a vector' which he said go direct las vegas and we turned direct las vegas. (I believe the controller phonetically spelled las and we entered lvs not knowing and not advised that our clearance had changed.) once the controller saw we were not going where he thought, we got a vector to the left toward las and queried the controller about our routing. It was now that he said we were going to las and not lvs. So now we are on a vector and as we are about to roll out 020 degrees direct las, the controller asks us to turn 40 degrees right which we did. As he sees us turning right, he makes the statement, 'that 40 degree turn was for the other aircraft.' obviously if I didn't think it was for us I would not have acknowledged it. Now the controller is in trouble -- I'm not going where he thinks I am and the other aircraft is also heading in the wrong direction. And with la arrs overhead and restr areas everywhere and maximum number of aircraft to control -- there is chaos. Once everything is sorted out he asked me to call his supervisor, which I did. The supervisor said there were no violations but we should 'listen up.' I feel we were. There was a lot of confusion with the similar call signs, las vegas, nv, and las vegas, NM, and not being advised of my rerte in a 'standard' manner.
Original NASA ASRS Text
Title: G2 DEP FROM VNY EXPERIENCED CONFUSION WITH ZLA CTLR REGARDING SIMILAR ACFT NUMBER AND ROUTING.
Narrative: WE DEPARTED VNY. OUR FLT PLAN WAS TO FLY OVER LAS VEGAS, NM. THIS RTE WAS SELECTED TO TAKE ADVANTAGE OF FAVORABLE WINDS. AS WE WERE CLBING OUT AND HANDED OVER TO LA, WE WERE GETTING VECTORED L OFF COURSE. UNBEKNOWNST TO US, THERE WAS ANOTHER ACFT WITH A SIMILAR CALL SIGN ON FREQ. THE OTHER ACFT ACKNOWLEDGED A RADIO XMISSION THAT I NOW REALIZE WAS FOR US WHICH WAS 'CLRED DIRECT LAS VEGAS, NV.' WHILE THE OTHER ACFT IS TURNING THE WRONG WAY I'M STILL EXPECTING A R TURN DIRECT LAS VEGAS. EVENTUALLY THE CTLR ASKED US WHAT WE WERE DOING WHICH WAS 'STILL ON A VECTOR' WHICH HE SAID GO DIRECT LAS VEGAS AND WE TURNED DIRECT LAS VEGAS. (I BELIEVE THE CTLR PHONETICALLY SPELLED LAS AND WE ENTERED LVS NOT KNOWING AND NOT ADVISED THAT OUR CLRNC HAD CHANGED.) ONCE THE CTLR SAW WE WERE NOT GOING WHERE HE THOUGHT, WE GOT A VECTOR TO THE L TOWARD LAS AND QUERIED THE CTLR ABOUT OUR ROUTING. IT WAS NOW THAT HE SAID WE WERE GOING TO LAS AND NOT LVS. SO NOW WE ARE ON A VECTOR AND AS WE ARE ABOUT TO ROLL OUT 020 DEGS DIRECT LAS, THE CTLR ASKS US TO TURN 40 DEGS R WHICH WE DID. AS HE SEES US TURNING R, HE MAKES THE STATEMENT, 'THAT 40 DEG TURN WAS FOR THE OTHER ACFT.' OBVIOUSLY IF I DIDN'T THINK IT WAS FOR US I WOULD NOT HAVE ACKNOWLEDGED IT. NOW THE CTLR IS IN TROUBLE -- I'M NOT GOING WHERE HE THINKS I AM AND THE OTHER ACFT IS ALSO HEADING IN THE WRONG DIRECTION. AND WITH LA ARRS OVERHEAD AND RESTR AREAS EVERYWHERE AND MAX NUMBER OF ACFT TO CTL -- THERE IS CHAOS. ONCE EVERYTHING IS SORTED OUT HE ASKED ME TO CALL HIS SUPVR, WHICH I DID. THE SUPVR SAID THERE WERE NO VIOLATIONS BUT WE SHOULD 'LISTEN UP.' I FEEL WE WERE. THERE WAS A LOT OF CONFUSION WITH THE SIMILAR CALL SIGNS, LAS VEGAS, NV, AND LAS VEGAS, NM, AND NOT BEING ADVISED OF MY RERTE IN A 'STANDARD' MANNER.
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.