Date: 201503
Local time of day: 1801-2400
Location: ATL.Airport, GA
Flight conditions: VMC
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ATL
Reporter organization: Air Carrier
Reporter function: Captain
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness; Troubleshooting
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Flight X; to ATL proceeded uneventfully.  We were initially assigned the KOLTT 1 Arrival and then later changed to the BNELE 1 Arrival.  All restrictions and speed assignments were complied with.  A Visual Approach was flown 2.5 miles in trail of a Regional Jet. As LAHSO operations were in effect; but not assigned; and there was a high arrival demand; minimum time on the runway was planned.  A smooth accurate touchdown followed and the aircraft exited Runway 26R at the first available taxiway (first high speed) as per AIM 4.3.20; a. The taxi instructions that followed as we understood them were to proceed via B and V (standard Victor Loop) and to monitor Ground which we did.  As we proceeded on B; I noticed an aircraft exiting the runway at the high speed ahead of us and called the First Officers (FO) attention to that.  We were both aware that it is undesirable to stop the flow of traffic at ATL; but it did not appear that the exiting aircraft was intending to stop; so I brought the aircraft to a comfortable stop short of the taxiway.  The exiting aircraft also stopped short of B.  Ground Control was advised and we were instructed to continue our taxi. Upon reaching Ramp we were given a number to contact the Tower.  A one minute conversation followed and I was told that we had been instructed to taxi via B and V; to remain on Tower frequency until reaching V and then to monitor Ground; that multiple attempts were made to assign us a hold short clearance for the exiting aircraft from the Tower without response.  It was also explained that most aircraft exit the runway at the second high speed and that this was considered customary and expected by the Tower.  Exiting at the first high speed required Tower to provide both Ground Control to aircraft on B and Tower Control of exiting aircraft and that this information could be found in our publications. It has been routine for me to exit at the first available taxiway at ATL in the past; and my last trip was allowed to taxi straight across to Ramp with a 'nice job' which my FO and I actually briefed prior to this arrival.  After reviewing 10-7; 10-9; and ATL [company information chart]; we were unable to find a published preference to roll to the second high speed; but will plan to do so in the future.Ultimately; it is likely that the issue was our understanding of 'monitor Ground'.  If it was Tower's intention for us to monitor Ground (but remain on Tower until V) the situation would not have resulted.  Perhaps 'taxi via B and V stay with me' or remain on Tower would have been more clear.  It was never our intention to switch from Tower to Ground without instruction.  I sincerely appreciate ATL Tower taking the time to provide this insight to their local procedures and hope that it is useful to other Crews as well.




Synopsis: A pilot reports of landing at ATL and following instructions from Tower. An aircraft exits runway ahead of them; they stop to allow aircraft to exit then continue. Later they are chastised for leaving Tower frequency even though Tower told them to monitor Ground.