Narrative:

ATC facility: dfw tower. The dfw ATIS states, 'concurrent landing and runway crossing operations in effect.' this is the landing and hold short operation advisory. The problem is that since you are supposed to tell the first approach controller whether or not you can accept any landing and hold short operation and the ATIS fails to inform which runways and which intxns are involved, you can't do one without the other. Also we are required to look up on our charts whether we are allowed to do any particular one and the first time you are told what the intersection involved is, is on final with the tower -- way too late to be looking at a landing and hold short operation chart. Callback conversation with reporter revealed the following information: reporter defined the problem as not being able to comply with his air carrier's policy of having to reference the landing distances to the intersection prior to accepting a landing clearance, hold short of. Time is another problem since the ATIS fails to give the runway and/or intersection. It's too late after intersection notification by tower at the LOM for chart referencing. One basic problem is that if the first approach controller is not given a 'no' on the hold short scenario, everyone else down line assumes you are accepting the hold short clearance. Reporter had no choice in this instance to give a 'no' to the approach controller. Procedure as is with deficiency in the ATIS information affects the traffic volume and flow. Runways that reporter mentioned were: runway 18R hold short taxiway B. Runway 36L hold short taxiway Z. Runway 35C hold short taxiway ej. (If runway 35C is wet it is an automatic 'no'.)

Related reports:

Google
 

Original NASA ASRS Text

Title: S80 PIC RPT ON THE LNDG AND HOLD SHORT OP AT DFW. ARR TFC DOESN'T GET ADVANCE INFO REGARDING RWY AND INTXN USE FROM ATIS.

Narrative: ATC FACILITY: DFW TWR. THE DFW ATIS STATES, 'CONCURRENT LNDG AND RWY XING OPS IN EFFECT.' THIS IS THE LNDG AND HOLD SHORT OP ADVISORY. THE PROB IS THAT SINCE YOU ARE SUPPOSED TO TELL THE FIRST APCH CTLR WHETHER OR NOT YOU CAN ACCEPT ANY LNDG AND HOLD SHORT OP AND THE ATIS FAILS TO INFORM WHICH RWYS AND WHICH INTXNS ARE INVOLVED, YOU CAN'T DO ONE WITHOUT THE OTHER. ALSO WE ARE REQUIRED TO LOOK UP ON OUR CHARTS WHETHER WE ARE ALLOWED TO DO ANY PARTICULAR ONE AND THE FIRST TIME YOU ARE TOLD WHAT THE INTXN INVOLVED IS, IS ON FINAL WITH THE TWR -- WAY TOO LATE TO BE LOOKING AT A LNDG AND HOLD SHORT OP CHART. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR DEFINED THE PROB AS NOT BEING ABLE TO COMPLY WITH HIS ACR'S POLICY OF HAVING TO REF THE LNDG DISTANCES TO THE INTXN PRIOR TO ACCEPTING A LNDG CLRNC, HOLD SHORT OF. TIME IS ANOTHER PROB SINCE THE ATIS FAILS TO GIVE THE RWY AND/OR INTXN. IT'S TOO LATE AFTER INTXN NOTIFICATION BY TWR AT THE LOM FOR CHART REFING. ONE BASIC PROB IS THAT IF THE FIRST APCH CTLR IS NOT GIVEN A 'NO' ON THE HOLD SHORT SCENARIO, EVERYONE ELSE DOWN LINE ASSUMES YOU ARE ACCEPTING THE HOLD SHORT CLRNC. RPTR HAD NO CHOICE IN THIS INSTANCE TO GIVE A 'NO' TO THE APCH CTLR. PROC AS IS WITH DEFICIENCY IN THE ATIS INFO AFFECTS THE TFC VOLUME AND FLOW. RWYS THAT RPTR MENTIONED WERE: RWY 18R HOLD SHORT TXWY B. RWY 36L HOLD SHORT TXWY Z. RWY 35C HOLD SHORT TXWY EJ. (IF RWY 35C IS WET IT IS AN AUTOMATIC 'NO'.)

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.