37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 448742 |
Time | |
Date | 199909 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dfw.airport |
State Reference | TX |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : dfw.tower |
Operator | common carrier : air carrier |
Make Model Name | MD-88 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : flight engineer pilot : multi engine pilot : atp pilot : cfi |
Experience | flight time last 90 days : 200 flight time total : 16000 flight time type : 5000 |
ASRS Report | 448742 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : commercial |
Events | |
Anomaly | incursion : taxiway non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | controller : issued alert none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew Other |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We had just landed on runway 17C at dfw. We were cleared to cross runway 17R on taxiway B, and an air carrier Y flight was cleared to cross runway 17R on taxiway a, just south of our position. After crossing the runway and as we switched to ground control, the air carrier Y flight had already checked in with dfw ground control and was told to give way to a commuter taxiing east on taxiway a who would join taxiway K. He said to follow the air carrier X jet on taxiway a, which was us, and taxi to park on taxiway K. We tried to acknowledge to dfw ground control that we had received his instructions, but our call was blocked and the ground controller chose to talk to a flight further north. As there were no other aircraft in the vicinity except for the air carrier Y who was instructed to follow us and the commuter, we joined taxiway K behind the commuter per the controller's instructions. The controller then demanded to know who the jet was on taxiway K. We responded with our flight number and told him our call was blocked but had received his instructions. He told us we were on 'his taxiway' and we should have talked to him first. We explained that we received his instructions but he said that it did not matter. My understanding is that it is the ground controller's duty to provide safe and efficient flow of ground traffic. Rather than stopping on taxiway B and causing the air carrier Y flight next to us who had already received instructions to stop, and possibly preventing aircraft behind us on taxiway B from crossing runway 17R, we felt it would be proper for us to continue taxiing per the controller's instructions. In my opinion he should have issued us a clearance immediately after air carrier Y to ensure the flow of traffic. I would never knowingly taxi without a clearance and did not feel like I was doing so.
Original NASA ASRS Text
Title: CAPT OF AN MD88 FAILED TO STOP ON TXWY AFTER LNDG BEFORE ENTERING ANOTHER TXWY SINCE NO ACTUAL CONTACT WITH THE TWR GND CTLR HAD BEEN ESTABLISHED.
Narrative: WE HAD JUST LANDED ON RWY 17C AT DFW. WE WERE CLRED TO CROSS RWY 17R ON TXWY B, AND AN ACR Y FLT WAS CLRED TO CROSS RWY 17R ON TXWY A, JUST S OF OUR POS. AFTER XING THE RWY AND AS WE SWITCHED TO GND CTL, THE ACR Y FLT HAD ALREADY CHKED IN WITH DFW GND CTL AND WAS TOLD TO GIVE WAY TO A COMMUTER TAXIING E ON TXWY A WHO WOULD JOIN TXWY K. HE SAID TO FOLLOW THE ACR X JET ON TXWY A, WHICH WAS US, AND TAXI TO PARK ON TXWY K. WE TRIED TO ACKNOWLEDGE TO DFW GND CTL THAT WE HAD RECEIVED HIS INSTRUCTIONS, BUT OUR CALL WAS BLOCKED AND THE GND CTLR CHOSE TO TALK TO A FLT FURTHER N. AS THERE WERE NO OTHER ACFT IN THE VICINITY EXCEPT FOR THE ACR Y WHO WAS INSTRUCTED TO FOLLOW US AND THE COMMUTER, WE JOINED TXWY K BEHIND THE COMMUTER PER THE CTLR'S INSTRUCTIONS. THE CTLR THEN DEMANDED TO KNOW WHO THE JET WAS ON TXWY K. WE RESPONDED WITH OUR FLT NUMBER AND TOLD HIM OUR CALL WAS BLOCKED BUT HAD RECEIVED HIS INSTRUCTIONS. HE TOLD US WE WERE ON 'HIS TXWY' AND WE SHOULD HAVE TALKED TO HIM FIRST. WE EXPLAINED THAT WE RECEIVED HIS INSTRUCTIONS BUT HE SAID THAT IT DID NOT MATTER. MY UNDERSTANDING IS THAT IT IS THE GND CTLR'S DUTY TO PROVIDE SAFE AND EFFICIENT FLOW OF GND TFC. RATHER THAN STOPPING ON TXWY B AND CAUSING THE ACR Y FLT NEXT TO US WHO HAD ALREADY RECEIVED INSTRUCTIONS TO STOP, AND POSSIBLY PREVENTING ACFT BEHIND US ON TXWY B FROM XING RWY 17R, WE FELT IT WOULD BE PROPER FOR US TO CONTINUE TAXIING PER THE CTLR'S INSTRUCTIONS. IN MY OPINION HE SHOULD HAVE ISSUED US A CLRNC IMMEDIATELY AFTER ACR Y TO ENSURE THE FLOW OF TFC. I WOULD NEVER KNOWINGLY TAXI WITHOUT A CLRNC AND DID NOT FEEL LIKE I WAS DOING SO.
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.