Air carrier first officer expresses concern with ATC communication clearance during rollout.

Attributes
ACN	523910
Time
Date	200109
Day	Tue
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-80 Super 80
Operating Under FAR Part	Part 121
Flight Phase	landing : roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	523910
Events
Anomaly	non adherence : published procedure
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew other
Supplementary
Problem Areas	ATC Human Performance Environmental Factor Flight Crew Human Performance
Primary Problem	ATC Human Performance
Situations
ATC Facility	procedure or policy : zzz.tower

Narrative:

One area of communication that has not received a great deal of publicized emphasis with regards to runway incursions is that of received by the flight crew's from the tower on landing roll. On landing roll, the aircraft is being brought to a stop by the flight crew, callouts are being made, thrust reversers, brakes and spoilers are being used, and it is very noisy and busy. The last thing that needs to be added to all that confusion is a call from the tower directing us where to clear, what frequency to use for ground, and what, if any, runway we are to hold short of or taxi across. As a personal rule, I ignore all xmissions from the tower until we are a safe taxi speed, then I ask for the communication to be repeated. Generally, this is not a problem, but some controllers become obviously agitated at having to repeat themselves. All clrncs from ATC to which I respond are, in effect, regulatory in nature. During landing roll, I am not in a position to adequately determine what was said, or whether we are even able to comply. It is simply too busy a time to be communicating on the radio. I believe this period of time needs to be quiet over the radio, unless there is an 'urgent' need for the tower to talk to us. I have spoken to tower controllers regarding this issue, and, surprisingly, most are completely unaware of this problem. On that same note, most are quite understanding when it is brought to their attention.

Original NASA ASRS Text

Title: ACR FO EXPRESSES CONCERN WITH ATC COM CLRNC DURING ROLLOUT.

Narrative: ONE AREA OF COM THAT HAS NOT RECEIVED A GREAT DEAL OF PUBLICIZED EMPHASIS WITH REGARDS TO RWY INCURSIONS IS THAT OF RECEIVED BY THE FLC'S FROM THE TWR ON LNDG ROLL. ON LNDG ROLL, THE ACFT IS BEING BROUGHT TO A STOP BY THE FLC, CALLOUTS ARE BEING MADE, THRUST REVERSERS, BRAKES AND SPOILERS ARE BEING USED, AND IT IS VERY NOISY AND BUSY. THE LAST THING THAT NEEDS TO BE ADDED TO ALL THAT CONFUSION IS A CALL FROM THE TWR DIRECTING US WHERE TO CLR, WHAT FREQ TO USE FOR GND, AND WHAT, IF ANY, RWY WE ARE TO HOLD SHORT OF OR TAXI ACROSS. AS A PERSONAL RULE, I IGNORE ALL XMISSIONS FROM THE TWR UNTIL WE ARE A SAFE TAXI SPD, THEN I ASK FOR THE COM TO BE REPEATED. GENERALLY, THIS IS NOT A PROB, BUT SOME CTLRS BECOME OBVIOUSLY AGITATED AT HAVING TO REPEAT THEMSELVES. ALL CLRNCS FROM ATC TO WHICH I RESPOND ARE, IN EFFECT, REGULATORY IN NATURE. DURING LNDG ROLL, I AM NOT IN A POS TO ADEQUATELY DETERMINE WHAT WAS SAID, OR WHETHER WE ARE EVEN ABLE TO COMPLY. IT IS SIMPLY TOO BUSY A TIME TO BE COMMUNICATING ON THE RADIO. I BELIEVE THIS PERIOD OF TIME NEEDS TO BE QUIET OVER THE RADIO, UNLESS THERE IS AN 'URGENT' NEED FOR THE TWR TO TALK TO US. I HAVE SPOKEN TO TWR CTLRS REGARDING THIS ISSUE, AND, SURPRISINGLY, MOST ARE COMPLETELY UNAWARE OF THIS PROB. ON THAT SAME NOTE, MOST ARE QUITE UNDERSTANDING WHEN IT IS BROUGHT TO THEIR ATTN.

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.