37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 973742 |
Time | |
Date | 201110 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I am reporting this to add to the data collection of problems with similar sounding call signs with the flights. Although we trapped and mitigated this error on the part of oak ARTCC; if we had been less alert; a conflict could have occurred. After crean waypoint; oak ARTCC cleared us 'direct pirat; direct XXX; direct YYY'. We acknowledged and proceeded with the assigned route. Oak ARTCC then issued the following clearance; very clearly. 'Carrier XX6; cross pirat at 10;000'. That aircraft acknowledged the clearance with a clear readback. (We were carrier YY6). A few minutes later; oak ARTCC issued the following clearance. 'Carrier XX6; cleared direct pirat; direct osi; 370'; to which carrier XX6 acknowledged. It was; at this point obvious to us; that an error was developing. We then asked 'can carrier YY6 expect a crossing restriction at pirat'; to which oak ARTCC replied; 'I cleared you to cross pirat at 10;000'. We replied that he had issued that clearance to another aircraft. There was a pause; and then carrier XX6 asked for confirmation of his previous clearance to cross pirat at 10;000. The controller then straightened everything out and instructed us to cross pirat at 10;000 and carrier XX6 to maintain his altitude. Similar sounding call sign for similarly routed flights makes it more difficult for controllers as well as pilots.
Original NASA ASRS Text
Title: An Air Carrier Captain reported ATC and flight crew confusion caused by closely spaced aircraft with similar sounding call signs arriving on oceanic routes over the same fixes.
Narrative: I am reporting this to add to the data collection of problems with similar sounding call signs with the flights. Although we trapped and mitigated this error on the part of OAK ARTCC; if we had been less alert; a conflict could have occurred. After CREAN waypoint; OAK ARTCC cleared us 'direct PIRAT; direct XXX; direct YYY'. We acknowledged and proceeded with the assigned route. OAK ARTCC then issued the following clearance; very clearly. 'Carrier XX6; cross PIRAT at 10;000'. That aircraft acknowledged the clearance with a clear readback. (We were Carrier YY6). A few minutes later; OAK ARTCC issued the following clearance. 'Carrier XX6; cleared direct PIRAT; direct OSI; 370'; to which Carrier XX6 acknowledged. It was; at this point obvious to us; that an error was developing. We then asked 'Can Carrier YY6 expect a crossing restriction at PIRAT'; to which OAK ARTCC replied; 'I cleared you to cross PIRAT at 10;000'. We replied that he had issued that clearance to another aircraft. There was a pause; and then Carrier XX6 asked for confirmation of his previous clearance to cross PIRAT at 10;000. The Controller then straightened everything out and instructed us to cross PIRAT at 10;000 and Carrier XX6 to maintain his altitude. Similar sounding call sign for similarly routed flights makes it more difficult for controllers as well as pilots.
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.