37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 344972 |
Time | |
Date | 199608 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : sjn |
State Reference | AZ |
Altitude | msl bound lower : 29500 msl bound upper : 33000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zab |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | descent other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time total : 22000 |
ASRS Report | 344972 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : private pilot : instrument |
Experience | flight time last 90 days : 80 flight time total : 2200 flight time type : 80 |
ASRS Report | 344970 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were on air carrier X flight xaa from sat to las. About half way from elp to pgs, we were given a descent from FL350 to FL330, then as we were in the descent, received and acknowledged descent on to FL280. As we were passing about FL295 ZAB asked us 'what altitude are you cleared to?' we replied FL280. ZAB then said that the clearance to FL280 was for another air carrier X flight and for us to continue descent to FL290. I noted at least 2 other air carrier X flts on the frequency at that time. I feel that we obviously copied another air carrier X flight's clearance and on our readback ZAB did not catch the wrong call sign on the reply. (We may have responded simultaneously.) to prevent this from happening again, we'll have to be more alert for similar call signs and flight numbers. The next day we were on a flight from slc to oak as air carrier X axdb. On 1 center frequency we were also on with air carrier X axeb and air carrier X axfb. I would like to see the company make an effort to not number flts that will cause possible radio confusion.
Original NASA ASRS Text
Title: MLG CREW TOOK CLRNC MEANT FOR ANOTHER FLT, SAME AIRLINE, AND DSNDED THROUGH THEIR ASSIGNED ALT.
Narrative: WE WERE ON ACR X FLT XAA FROM SAT TO LAS. ABOUT HALF WAY FROM ELP TO PGS, WE WERE GIVEN A DSCNT FROM FL350 TO FL330, THEN AS WE WERE IN THE DSCNT, RECEIVED AND ACKNOWLEDGED DSCNT ON TO FL280. AS WE WERE PASSING ABOUT FL295 ZAB ASKED US 'WHAT ALT ARE YOU CLRED TO?' WE REPLIED FL280. ZAB THEN SAID THAT THE CLRNC TO FL280 WAS FOR ANOTHER ACR X FLT AND FOR US TO CONTINUE DSCNT TO FL290. I NOTED AT LEAST 2 OTHER ACR X FLTS ON THE FREQ AT THAT TIME. I FEEL THAT WE OBVIOUSLY COPIED ANOTHER ACR X FLT'S CLRNC AND ON OUR READBACK ZAB DID NOT CATCH THE WRONG CALL SIGN ON THE REPLY. (WE MAY HAVE RESPONDED SIMULTANEOUSLY.) TO PREVENT THIS FROM HAPPENING AGAIN, WE'LL HAVE TO BE MORE ALERT FOR SIMILAR CALL SIGNS AND FLT NUMBERS. THE NEXT DAY WE WERE ON A FLT FROM SLC TO OAK AS ACR X AXDB. ON 1 CTR FREQ WE WERE ALSO ON WITH ACR X AXEB AND ACR X AXFB. I WOULD LIKE TO SEE THE COMPANY MAKE AN EFFORT TO NOT NUMBER FLTS THAT WILL CAUSE POSSIBLE RADIO CONFUSION.
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.