37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 509159 |
Time | |
Date | 200104 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : las.vortac |
State Reference | NV |
Altitude | msl bound lower : 31000 msl bound upper : 37000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zla.artcc tower : fsd.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-500 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other Other other vortac |
Flight Phase | cruise : level descent : intermediate altitude |
Route In Use | enroute airway : j9.airway |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zla.artcc |
Operator | common carrier : air carrier |
Make Model Name | MD-90 Series (DC-9-90) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 20000 flight time type : 12000 |
ASRS Report | 509159 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 240 flight time total : 5000 flight time type : 3000 |
ASRS Report | 509349 |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued advisory |
Consequence | faa : investigated |
Miss Distance | horizontal : 2400 vertical : 1400 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
It was the captain's leg and we were cruising at FL370 on J9 between las VOR and mlf VOR. We were 30-40 NM north of las VOR talking to lax on frequency 135.55. Center cleared us to FL310 and my first officer read back our call sign and that we were leaving FL370 for FL310. I entered a gentle descent at 1000 FPM for passenger comfort. Approaching FL330 (about 4 mins later) ZLA gave us a frequency change to 125.75 and we acknowledged. This frequency was in error and the controller told us to return to our previous frequency, so we complied. At this time, while approaching FL324, we noticed an aircraft on TCASII passing 1400 ft beneath us at FL310 -- our clearance altitude. We knew something was wrong even though a TCASII traffic alert was never heard. By the time we could re-establish contact on frequency 135.55, we had leveled at FL310 approximately 50 NM south of mlf VOR. We knew that we had a different controller due to a distinctively different voice. He queried us on our altitude and we told him that we were level at FL310. He expressed some confusion as to why we were at FL310 and we assured him that it was our previous clearance altitude. He told us to maintain FL310 and not much else was said by him regarding the incident. However, we quickly got yet another controller and he soon told us that we had been involved in a possible deviation and instructed us to phone ZLA upon arrival. Later in-flight, ZLC told us on frequency 133.9 that ZLA had called to tell us that they were accepting full responsibility for the incident. Upon arrival in slc, I spoke with ZLA. He reaffirmed that ZLA had accepted full responsibility for the incident.
Original NASA ASRS Text
Title: ACR FLC RESPOND TO AND ACKNOWLEDGE ALT CHANGE AND MULTIPLE FREQ CHANGES BEFORE BEING NOTIFIED OF A POSSIBLE ZLA OPERROR.
Narrative: IT WAS THE CAPT'S LEG AND WE WERE CRUISING AT FL370 ON J9 BTWN LAS VOR AND MLF VOR. WE WERE 30-40 NM N OF LAS VOR TALKING TO LAX ON FREQ 135.55. CTR CLRED US TO FL310 AND MY FO READ BACK OUR CALL SIGN AND THAT WE WERE LEAVING FL370 FOR FL310. I ENTERED A GENTLE DSCNT AT 1000 FPM FOR PAX COMFORT. APCHING FL330 (ABOUT 4 MINS LATER) ZLA GAVE US A FREQ CHANGE TO 125.75 AND WE ACKNOWLEDGED. THIS FREQ WAS IN ERROR AND THE CTLR TOLD US TO RETURN TO OUR PREVIOUS FREQ, SO WE COMPLIED. AT THIS TIME, WHILE APCHING FL324, WE NOTICED AN ACFT ON TCASII PASSING 1400 FT BENEATH US AT FL310 -- OUR CLRNC ALT. WE KNEW SOMETHING WAS WRONG EVEN THOUGH A TCASII TFC ALERT WAS NEVER HEARD. BY THE TIME WE COULD RE-ESTABLISH CONTACT ON FREQ 135.55, WE HAD LEVELED AT FL310 APPROX 50 NM S OF MLF VOR. WE KNEW THAT WE HAD A DIFFERENT CTLR DUE TO A DISTINCTIVELY DIFFERENT VOICE. HE QUERIED US ON OUR ALT AND WE TOLD HIM THAT WE WERE LEVEL AT FL310. HE EXPRESSED SOME CONFUSION AS TO WHY WE WERE AT FL310 AND WE ASSURED HIM THAT IT WAS OUR PREVIOUS CLRNC ALT. HE TOLD US TO MAINTAIN FL310 AND NOT MUCH ELSE WAS SAID BY HIM REGARDING THE INCIDENT. HOWEVER, WE QUICKLY GOT YET ANOTHER CTLR AND HE SOON TOLD US THAT WE HAD BEEN INVOLVED IN A POSSIBLE DEV AND INSTRUCTED US TO PHONE ZLA UPON ARR. LATER INFLT, ZLC TOLD US ON FREQ 133.9 THAT ZLA HAD CALLED TO TELL US THAT THEY WERE ACCEPTING FULL RESPONSIBILITY FOR THE INCIDENT. UPON ARR IN SLC, I SPOKE WITH ZLA. HE REAFFIRMED THAT ZLA HAD ACCEPTED FULL RESPONSIBILITY FOR THE INCIDENT.
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.