|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : phx|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Operator||common carrier : air carrier|
|Make Model Name||Medium Large Transport, Low Wing, 2 Turbojet Eng|
|Navigation In Use||Other|
|Flight Phase||ground : preflight|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : instrument|
pilot : flight engineer
pilot : cfi
pilot : commercial
pilot : atp
|Experience||flight time last 90 days : 200|
flight time total : 9900
flight time type : 4500
|Anomaly||other anomaly other|
|Air Traffic Incident||other|
My company flies daily into some of the busiest airports in this country. We do it in a 2 engine, 2-M aircraft, that requires the utmost in concentration (to avoid all of the pitfalls that ASRS usually hears about) for an experienced crew on a good day. Turn that day into a bad one, running late, MEL's, bad WX and a new first officer--the margin for error is nil. Yet in light of the factors facing us, our company clings to an obsolete procedure that was effective with 3 aircraft, difficult with 10 aircraft, and now ridiculous with 85+ aircraft. They require us to monitor company radio at all times. I can't tell you how many times I have missed or misunderstood an ATC transmission while trying to separate the 2 conversations taking place in my earpiece. The obvious solution is to turn off company radio switch when it interferes (which, again, is frequently). This prevents the requirement for constant contact and leaves the pilot in violation of company and FAA regulation's. In essence he is forced to break the rules, in the interest of safety, to allow the company to continue an obsolete procedure as opposed to installing ACARS and SELCAL (catch 22!). I love this company, but I gotta tell it like it is. Callback conversation with reporter revealed the following: company policy requires 1 pilot to monitor both ATC communication and company frequency. Have had cases where aci will request dispatch to demonstrate their ability to contact en route flts. They still require the same procedure in the terminal environment. Has discussed the mgt and they are aware of the problem. Consideration is being given to equipping the fleet with ACARS, but no final decision has been made.
Original NASA ASRS Text
Title: CLRNC FREQUENTLY MISSED ACCOUNT COMPANY POLICY REQUIRES MONITORING COMPANY FREQ AT ALL TIMES.
Narrative: MY COMPANY FLIES DAILY INTO SOME OF THE BUSIEST ARPTS IN THIS COUNTRY. WE DO IT IN A 2 ENG, 2-M ACFT, THAT REQUIRES THE UTMOST IN CONCENTRATION (TO AVOID ALL OF THE PITFALLS THAT ASRS USUALLY HEARS ABOUT) FOR AN EXPERIENCED CREW ON A GOOD DAY. TURN THAT DAY INTO A BAD ONE, RUNNING LATE, MEL'S, BAD WX AND A NEW F/O--THE MARGIN FOR ERROR IS NIL. YET IN LIGHT OF THE FACTORS FACING US, OUR COMPANY CLINGS TO AN OBSOLETE PROC THAT WAS EFFECTIVE WITH 3 ACFT, DIFFICULT WITH 10 ACFT, AND NOW RIDICULOUS WITH 85+ ACFT. THEY REQUIRE US TO MONITOR COMPANY RADIO AT ALL TIMES. I CAN'T TELL YOU HOW MANY TIMES I HAVE MISSED OR MISUNDERSTOOD AN ATC XMISSION WHILE TRYING TO SEPARATE THE 2 CONVERSATIONS TAKING PLACE IN MY EARPIECE. THE OBVIOUS SOLUTION IS TO TURN OFF COMPANY RADIO SWITCH WHEN IT INTERFERES (WHICH, AGAIN, IS FREQUENTLY). THIS PREVENTS THE REQUIREMENT FOR CONSTANT CONTACT AND LEAVES THE PLT IN VIOLATION OF COMPANY AND FAA REG'S. IN ESSENCE HE IS FORCED TO BREAK THE RULES, IN THE INTEREST OF SAFETY, TO ALLOW THE COMPANY TO CONTINUE AN OBSOLETE PROC AS OPPOSED TO INSTALLING ACARS AND SELCAL (CATCH 22!). I LOVE THIS COMPANY, BUT I GOTTA TELL IT LIKE IT IS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: COMPANY POLICY REQUIRES 1 PLT TO MONITOR BOTH ATC COM AND COMPANY FREQ. HAVE HAD CASES WHERE ACI WILL REQUEST DISPATCH TO DEMONSTRATE THEIR ABILITY TO CONTACT ENRTE FLTS. THEY STILL REQUIRE THE SAME PROC IN THE TERMINAL ENVIRONMENT. HAS DISCUSSED THE MGT AND THEY ARE AWARE OF THE PROB. CONSIDERATION IS BEING GIVEN TO EQUIPPING THE FLEET WITH ACARS, BUT NO FINAL DECISION HAS BEEN MADE.
Data retrieved from NASA's ASRS site as of August 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.