37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1313001 |
Time | |
Date | 201511 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | DFW.Airport |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Dfw ground cleared us to taxi to runway 17R via the standard taxi route. The first officer read back the clearance and since we didn't have that page pulled up on our ipads; we did not start our taxi until the first officer pulled up the page and we both verified the taxi route. All told; this took us about 30 to 45 seconds for the first officer to search for the correct page on his ipad and verify the correct taxi route before we started the taxi. During this time of having this process completed; I saw a regional jet taxiing eastbound on the bridge towards our direction and I voiced my concern about having a taxiing conflict with the oncoming aircraft. Checking my right one more time before I started to taxi I released the brakes and started taxiing while focusing on the aircraft towards my left that was now approaching the intersection. From releasing the brakes; adding power and our airplane finally moving; it took about 5-10 seconds. Moving no more than 20 feet the first officer yelled to stop. I immediately stopped the aircraft and looking to my right I saw [another aircraft] that was quickly approaching us that was westbound on the taxiway. The first officer notified ground that we stopped our taxi due to the [other aircraft] that was crossing in front of us. Ground control informed us that since he didn't see us taxiing; he cleared the [other aircraft] to continue his taxi. To paraphrase the first officer's reply; he said that it took us some time to locate the page with the taxi instructions before we were to start our taxi. At no time did ground control revise our clearance to give way to the oncoming traffic prior to taxiing; nor did we ever hear a previous clearance for the [other aircraft] to initially give way to us when we were cleared to taxi. This was probably due to the fact that the [other aircraft] was so far away when he cleared us to taxi that ground control didn't anticipate seeing a conflict. Bravo zulu to the first officer for seeing a potential ground collision and being aggressive in having me stop the aircraft.while we did the right thing of ensuring we completely understood the taxi clearance by having the right page up before starting our taxi; I should have ensured that prior to gate departure that we had the standard taxi routes readily available. Also; I should have been more vigilant of keeping an active scan prior to and during taxiing (head on a swivel). While I didn't initially see the [other aircraft] on my right; I shouldn't have fixated on the other aircraft; or at least asked ground control about who; between us; were to give way to the other. Crew communication worked as planned with having the first officer being vocal about a potential conflict.ground control noting our taxiing delay should have inquired us about his clearance for us to taxi. As a minimum he should have revised our taxi clearance for us to hold for the [other aircraft].in my experience; [dfw] ground control more often than not typically gives a full route taxi instruction from the terminal to the runway. To the point that using the standard taxi routes is the exception and not the norm. Maybe complacency on our part; but when given these standard taxi routes; we typically have to search our ipads (which isn't always the easiest to navigate) for the correct page (there are 3 of them) and verify the correct taxi route. Finding the correct page and verifying the route can take some time before starting our taxi. A simple recommendation is either to use the standard taxi routes all the time so flight crews get in the practice of using them or don't use them at all. If they are only to be used during increased ground operations; then state so on the departure ATIS so crews will be well prepared.
Original NASA ASRS Text
Title: After some delay in interpreting a 'Standard Taxi Route' clearance at DFW; the crew began to taxi; but had to made a sudden stop for conflicting traffic.
Narrative: DFW Ground cleared us to taxi to Runway 17R via the standard taxi route. The FO read back the clearance and since we didn't have that page pulled up on our iPads; we did not start our taxi until the FO pulled up the page and we both verified the taxi route. All told; this took us about 30 to 45 seconds for the FO to search for the correct page on his iPad and verify the correct taxi route before we started the taxi. During this time of having this process completed; I saw a Regional Jet taxiing eastbound on the bridge towards our direction and I voiced my concern about having a taxiing conflict with the oncoming aircraft. Checking my right one more time before I started to taxi I released the brakes and started taxiing while focusing on the aircraft towards my left that was now approaching the intersection. From releasing the brakes; adding power and our airplane finally moving; it took about 5-10 seconds. Moving no more than 20 feet the FO yelled to stop. I immediately stopped the aircraft and looking to my right I saw [another aircraft] that was quickly approaching us that was westbound on the taxiway. The FO notified ground that we stopped our taxi due to the [other aircraft] that was crossing in front of us. Ground Control informed us that since he didn't see us taxiing; he cleared the [other aircraft] to continue his taxi. To paraphrase the FO's reply; he said that it took us some time to locate the page with the taxi instructions before we were to start our taxi. At no time did Ground Control revise our clearance to give way to the oncoming traffic prior to taxiing; nor did we ever hear a previous clearance for the [other aircraft] to initially give way to us when we were cleared to taxi. This was probably due to the fact that the [other aircraft] was so far away when he cleared us to taxi that Ground Control didn't anticipate seeing a conflict. Bravo Zulu to the FO for seeing a potential ground collision and being aggressive in having me stop the aircraft.While we did the right thing of ensuring we completely understood the taxi clearance by having the right page up before starting our taxi; I should have ensured that prior to gate departure that we had the standard taxi routes readily available. Also; I should have been more vigilant of keeping an active scan prior to and during taxiing (head on a swivel). While I didn't initially see the [other aircraft] on my right; I shouldn't have fixated on the other aircraft; or at least asked Ground Control about who; between us; were to give way to the other. Crew communication worked as planned with having the FO being vocal about a potential conflict.Ground Control noting our taxiing delay should have inquired us about his clearance for us to taxi. As a minimum he should have revised our taxi clearance for us to hold for the [other aircraft].In my experience; [DFW] Ground Control more often than not typically gives a full route taxi instruction from the terminal to the runway. To the point that using the standard taxi routes is the exception and not the norm. Maybe complacency on our part; but when given these standard taxi routes; we typically have to search our iPads (which isn't always the easiest to navigate) for the correct page (there are 3 of them) and verify the correct taxi route. Finding the correct page and verifying the route can take some time before starting our taxi. A simple recommendation is either to use the standard taxi routes all the time so flight crews get in the practice of using them or don't use them at all. If they are only to be used during increased ground operations; then state so on the departure ATIS so crews will be well prepared.
Data retrieved from NASA's ASRS site 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.