37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 589019 |
Time | |
Date | 200307 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : mdw.airport |
State Reference | IL |
Altitude | msl single value : 10000 |
Environment | |
Flight Conditions | Mixed |
Weather Elements | Thunderstorm Turbulence |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : c90.tracon tower : phx.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach descent : intermediate altitude |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 748 flight time total : 8500 flight time type : 4000 |
ASRS Report | 589019 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 150 flight time total : 15000 flight time type : 9000 |
ASRS Report | 589216 |
Events | |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | other |
Consequence | other |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
Attempted contact with approach on 120.12 as directed (3 times), no answer for 60-90 seconds. Maintained 10000 ft MSL as previously assigned. Went to 119.35 as a known approach frequency. Controller said not quite in his airspace, but stay with him and he would coordinate for us. Stayed on frequency 2-3 mins, was called on company frequency and told to monitor 120.12 again, did so on #2 radio and controller said must descend to 6000 ft 'immediately.' frequency 119.35 was busy, so descended to 6000 ft per other controller. Then sent over to 118.4 (same controller was also working 119.35), who asked why we had descended. We related the previous events. No further discussion/issues. Supplemental information from acn 589216: center handed us off to approach. No contact on the first frequency -- went to another frequency from chart, where contact was made. Somehow we lost communication with that controller and by the time we were able to establish contact we were somewhat chastised by ATC for not being in contact. No conflicts occurred to the best of my knowledge.
Original NASA ASRS Text
Title: B737-300 CREW WAS NOT ABLE TO ESTABLISH COM WITH APCH CTLR #1, ON A HDOF FREQ. THE CREW THEN ESTABLISHED COM WITH APCH CTLR #2, ON THE FREQ LISTED ON THE APCH CHART. AFTER TALKING WITH CTLR #1, HE ADMONISHED THE CREW FOR THE COM PROB.
Narrative: ATTEMPTED CONTACT WITH APCH ON 120.12 AS DIRECTED (3 TIMES), NO ANSWER FOR 60-90 SECONDS. MAINTAINED 10000 FT MSL AS PREVIOUSLY ASSIGNED. WENT TO 119.35 AS A KNOWN APCH FREQ. CTLR SAID NOT QUITE IN HIS AIRSPACE, BUT STAY WITH HIM AND HE WOULD COORDINATE FOR US. STAYED ON FREQ 2-3 MINS, WAS CALLED ON COMPANY FREQ AND TOLD TO MONITOR 120.12 AGAIN, DID SO ON #2 RADIO AND CTLR SAID MUST DSND TO 6000 FT 'IMMEDIATELY.' FREQ 119.35 WAS BUSY, SO DSNDED TO 6000 FT PER OTHER CTLR. THEN SENT OVER TO 118.4 (SAME CTLR WAS ALSO WORKING 119.35), WHO ASKED WHY WE HAD DSNDED. WE RELATED THE PREVIOUS EVENTS. NO FURTHER DISCUSSION/ISSUES. SUPPLEMENTAL INFO FROM ACN 589216: CTR HANDED US OFF TO APCH. NO CONTACT ON THE FIRST FREQ -- WENT TO ANOTHER FREQ FROM CHART, WHERE CONTACT WAS MADE. SOMEHOW WE LOST COM WITH THAT CTLR AND BY THE TIME WE WERE ABLE TO ESTABLISH CONTACT WE WERE SOMEWHAT CHASTISED BY ATC FOR NOT BEING IN CONTACT. NO CONFLICTS OCCURRED TO THE BEST OF MY KNOWLEDGE.
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.