Narrative:

Flying for a scheduled cargo company, mhr (mather, ca) to phx (phoenix, az). Controller was working multiple sectors and frequencys during our nightly push from mhr. We have 9 flts departing within a short time in various directions. Our flight (air carrier X) was on 127.95 and told FL290 would be our final altitude. Same controller was contacted on 125.75 (ZOA). After a few mins, we were cleared to FL330. As we passed FL305, controller asked us for our altitude. We responded 'passing FL305, climbing to FL330 as cleared.' controller advised we were supposed to maintain FL290, but no problem, he stated. First officer stated we had been cleared to FL330 by call sign air carrier X, and he had read back clearance 'from FL290 to FL330, air carrier X.' controller responded 'yeah, too many air carrier X call signs.' problem was caused by too few controllers working too many sectors late at night. Complicating this is our nightly push of aircraft with similar call signs heading in multiple directions. Luckily, there was no conflict in this incident. We were off of published airways, proceeding direct to bty VOR, late at night. One more controller working at ZOA during this time period would be a tremendous help as mhr will become our permanent hub, day and night, and traffic will increase. We could/should have challenged the controller because of his earlier statement, FL290 will be your final.

Google
 

Original NASA ASRS Text

Title: ARTCC CTLR MISTAKENLY CLRED A B727 CARGO ACFT TO CLB DURING ENRTE DUE TO DISTR OR SEVERAL SAME COMPANY SIMILAR CALL SIGNS.

Narrative: FLYING FOR A SCHEDULED CARGO COMPANY, MHR (MATHER, CA) TO PHX (PHOENIX, AZ). CTLR WAS WORKING MULTIPLE SECTORS AND FREQS DURING OUR NIGHTLY PUSH FROM MHR. WE HAVE 9 FLTS DEPARTING WITHIN A SHORT TIME IN VARIOUS DIRECTIONS. OUR FLT (ACR X) WAS ON 127.95 AND TOLD FL290 WOULD BE OUR FINAL ALT. SAME CTLR WAS CONTACTED ON 125.75 (ZOA). AFTER A FEW MINS, WE WERE CLRED TO FL330. AS WE PASSED FL305, CTLR ASKED US FOR OUR ALT. WE RESPONDED 'PASSING FL305, CLBING TO FL330 AS CLRED.' CTLR ADVISED WE WERE SUPPOSED TO MAINTAIN FL290, BUT NO PROB, HE STATED. FO STATED WE HAD BEEN CLRED TO FL330 BY CALL SIGN ACR X, AND HE HAD READ BACK CLRNC 'FROM FL290 TO FL330, ACR X.' CTLR RESPONDED 'YEAH, TOO MANY ACR X CALL SIGNS.' PROB WAS CAUSED BY TOO FEW CTLRS WORKING TOO MANY SECTORS LATE AT NIGHT. COMPLICATING THIS IS OUR NIGHTLY PUSH OF ACFT WITH SIMILAR CALL SIGNS HDG IN MULTIPLE DIRECTIONS. LUCKILY, THERE WAS NO CONFLICT IN THIS INCIDENT. WE WERE OFF OF PUBLISHED AIRWAYS, PROCEEDING DIRECT TO BTY VOR, LATE AT NIGHT. ONE MORE CTLR WORKING AT ZOA DURING THIS TIME PERIOD WOULD BE A TREMENDOUS HELP AS MHR WILL BECOME OUR PERMANENT HUB, DAY AND NIGHT, AND TFC WILL INCREASE. WE COULD/SHOULD HAVE CHALLENGED THE CTLR BECAUSE OF HIS EARLIER STATEMENT, FL290 WILL BE YOUR FINAL.

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.