37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 459237 |
Time | |
Date | 200001 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | intersection : derb |
State Reference | CA |
Altitude | msl bound lower : 31800 msl bound upper : 33000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zla.artcc |
Operator | common carrier : air carrier |
Make Model Name | B737-400 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : enroute altitude change |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zla.artcc |
Operator | common carrier : air carrier |
Make Model Name | B737-400 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : enroute altitude change |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : multi engine pilot : flight engineer |
Experience | flight time last 90 days : 211 flight time total : 17001 flight time type : 5041 |
ASRS Report | 459237 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | controller : non radar controller : radar pilot : atp |
Experience | controller military : 21 controller non radar : 5 controller radar : 24 controller supervisory : 13 flight time last 90 days : 230 flight time total : 4000 flight time type : 1740 |
ASRS Report | 459237 |
Events | |
Anomaly | conflict : airborne critical non adherence : published procedure non adherence : required legal separation |
Independent Detector | aircraft equipment : tcas other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : returned to assigned altitude |
Consequence | faa : reviewed incident with flight crew other |
Miss Distance | vertical : 800 |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance Company |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
We were flying flight abc, a B737-400. Flight abd (another B737-400) going to psp was right behind us and on the same frequency. We were near the top of descent point and anticipating a descent clearance. I was flying, the first officer was on company radio getting a gate assignment and ATIS when ZLA gave us a descend now to FL280 for traffic and then to FL240 pilot's discretion. I read the clearance back, 'this is flight abc descend now to FL280 and then pilot's discretion to FL240.' he said that's correct. Flight abd was on the same frequency. I started to descend and then noticed a possible traffic conflict on the map. I stopped the descent at about FL318 and started a slow climb. The first officer had come back on radio #1 (ATC) and I explained the clearance to him. We got a TA and I continued to climb and got an RA which said 'don't descend.' ATC asked for our altitude and the first officer responded. ZLA said climb back to FL330. He responded and mentioned that we had been cleared lower. The ATC controller said the clearance was for flight abd. Flight abd didn't respond to the clearance and must have also thought it was for us or missed it. We spoke to the ZLA supervisor who had pulled the tape. He said that I did read back the clearance as flight abc and got an 'ok' from the controller, but that the controller had called it for flight abd. The supervisor said that it was an operational error. We have asked our company not to run similar flight numbers together, but it still happens. Hopefully, this procedure can be changed. Supplemental information from acn 459366: it was jan/xa/00, and airspace over southern california was saturated with airplanes.
Original NASA ASRS Text
Title: A B737-300 CREW READ BACK A DSCNT CLRNC MEANT FOR COMPANY ACFT FOLLOWING BEHIND. THE CAPT READ BACK THE PROPER CALL SIGN AND CLRNC WITH NO CORRECTION FROM ATC.
Narrative: WE WERE FLYING FLT ABC, A B737-400. FLT ABD (ANOTHER B737-400) GOING TO PSP WAS RIGHT BEHIND US AND ON THE SAME FREQ. WE WERE NEAR THE TOP OF DSCNT POINT AND ANTICIPATING A DSCNT CLRNC. I WAS FLYING, THE FO WAS ON COMPANY RADIO GETTING A GATE ASSIGNMENT AND ATIS WHEN ZLA GAVE US A DSND NOW TO FL280 FOR TFC AND THEN TO FL240 PLT'S DISCRETION. I READ THE CLRNC BACK, 'THIS IS FLT ABC DSND NOW TO FL280 AND THEN PLT'S DISCRETION TO FL240.' HE SAID THAT'S CORRECT. FLT ABD WAS ON THE SAME FREQ. I STARTED TO DSND AND THEN NOTICED A POSSIBLE TFC CONFLICT ON THE MAP. I STOPPED THE DSCNT AT ABOUT FL318 AND STARTED A SLOW CLB. THE FO HAD COME BACK ON RADIO #1 (ATC) AND I EXPLAINED THE CLRNC TO HIM. WE GOT A TA AND I CONTINUED TO CLB AND GOT AN RA WHICH SAID 'DON'T DSND.' ATC ASKED FOR OUR ALT AND THE FO RESPONDED. ZLA SAID CLB BACK TO FL330. HE RESPONDED AND MENTIONED THAT WE HAD BEEN CLRED LOWER. THE ATC CTLR SAID THE CLRNC WAS FOR FLT ABD. FLT ABD DIDN'T RESPOND TO THE CLRNC AND MUST HAVE ALSO THOUGHT IT WAS FOR US OR MISSED IT. WE SPOKE TO THE ZLA SUPVR WHO HAD PULLED THE TAPE. HE SAID THAT I DID READ BACK THE CLRNC AS FLT ABC AND GOT AN 'OK' FROM THE CTLR, BUT THAT THE CTLR HAD CALLED IT FOR FLT ABD. THE SUPVR SAID THAT IT WAS AN OPERROR. WE HAVE ASKED OUR COMPANY NOT TO RUN SIMILAR FLT NUMBERS TOGETHER, BUT IT STILL HAPPENS. HOPEFULLY, THIS PROC CAN BE CHANGED. SUPPLEMENTAL INFO FROM ACN 459366: IT WAS JAN/XA/00, AND AIRSPACE OVER SOUTHERN CALIFORNIA WAS SATURATED WITH AIRPLANES.
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.