 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A G159 turboprop flight stops taxi after landing roll and fails to clear the runway completely when the crew is confused as to what ATC wanted in the way of taxiway use at iad, va.
| Attributes | |
| ACN | 528262 |
| Time | |
| Date | 200110 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : iad.airport |
| State Reference | DC |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : iad.tower tower : smf.tower |
| Operator | common carrier : air taxi |
| Make Model Name | Gulfstream I (Large Turboprop) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | landing : roll |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : iad.tower |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | ground : taxi |
| Person 1 | |
| Affiliation | company : air taxi |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 30 flight time total : 15000 flight time type : 300 |
| ASRS Report | 528262 |
| Person 2 | |
| Affiliation | company : air taxi |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 30 flight time total : 14000 flight time type : 100 |
| ASRS Report | 528263 |
| Events | |
| Anomaly | conflict : ground less severe incursion : runway non adherence : clearance |
| Independent Detector | other controllera other flight crewa other flight crewb |
| Resolutory Action | controller : separated traffic controller : issued new clearance controller : issued alert flight crew : executed go around |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | ATC Human Performance Flight Crew Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
We were cleared to land on runway 19R at iad. On our rollout, we were told to take taxiway Y7 by a controller who seemed to be anxious. As we were making our turn off the runway, the controller again said to take taxiway Y7 and added the words 'the forward taxiway on the most forward taxiway,' which created some confusion in the cockpit. My copilot immediately expressed his confusion as there was the highspd taxiway which led to taxiway Y7, which is what we were doing until we heard the words 'forward taxiway.' the fact that we were both not sure what we were to do, we took the immediate left turn and stopped to confirm exactly what was intended. At that point the controller simply had to ask us to continue taxiing and we would have been fine and out of everyone's way, but he continued a dialogue expressing the fact that we were going to create a go around situation. At that point, we told him, or asked him, if there was anything we could do, ie, make 180 degree turn or whatever to rectify the situation. No response was given and an airplane was told to go around. There was plenty of time for us to move forward if we were asked to and looking back, I should have continued to beyond the runway markings, but in today's climate, you don't want to make any mistakes. We were then told to taxi to the FBO and call him when we got to a phone. I called and explained where we thought the confusion arose and he didn't seem to think there should have been any confusion. He indicated there was no incident created from the events, but wanted me to understand the importance of compliance which, of course, I already did after flying for 25 yrs. We were trying to adhere to the controller's direction but in today's climate, everyone -- including controllers and pilots -- is saying too much.
Original NASA ASRS Text
Title: A G159 TURBOPROP FLT STOPS TAXI AFTER LNDG ROLL AND FAILS TO CLR THE RWY COMPLETELY WHEN THE CREW IS CONFUSED AS TO WHAT ATC WANTED IN THE WAY OF TXWY USE AT IAD, VA.
Narrative: WE WERE CLRED TO LAND ON RWY 19R AT IAD. ON OUR ROLLOUT, WE WERE TOLD TO TAKE TXWY Y7 BY A CTLR WHO SEEMED TO BE ANXIOUS. AS WE WERE MAKING OUR TURN OFF THE RWY, THE CTLR AGAIN SAID TO TAKE TXWY Y7 AND ADDED THE WORDS 'THE FORWARD TXWY ON THE MOST FORWARD TXWY,' WHICH CREATED SOME CONFUSION IN THE COCKPIT. MY COPLT IMMEDIATELY EXPRESSED HIS CONFUSION AS THERE WAS THE HIGHSPD TXWY WHICH LED TO TXWY Y7, WHICH IS WHAT WE WERE DOING UNTIL WE HEARD THE WORDS 'FORWARD TXWY.' THE FACT THAT WE WERE BOTH NOT SURE WHAT WE WERE TO DO, WE TOOK THE IMMEDIATE L TURN AND STOPPED TO CONFIRM EXACTLY WHAT WAS INTENDED. AT THAT POINT THE CTLR SIMPLY HAD TO ASK US TO CONTINUE TAXIING AND WE WOULD HAVE BEEN FINE AND OUT OF EVERYONE'S WAY, BUT HE CONTINUED A DIALOGUE EXPRESSING THE FACT THAT WE WERE GOING TO CREATE A GAR SIT. AT THAT POINT, WE TOLD HIM, OR ASKED HIM, IF THERE WAS ANYTHING WE COULD DO, IE, MAKE 180 DEG TURN OR WHATEVER TO RECTIFY THE SIT. NO RESPONSE WAS GIVEN AND AN AIRPLANE WAS TOLD TO GO AROUND. THERE WAS PLENTY OF TIME FOR US TO MOVE FORWARD IF WE WERE ASKED TO AND LOOKING BACK, I SHOULD HAVE CONTINUED TO BEYOND THE RWY MARKINGS, BUT IN TODAY'S CLIMATE, YOU DON'T WANT TO MAKE ANY MISTAKES. WE WERE THEN TOLD TO TAXI TO THE FBO AND CALL HIM WHEN WE GOT TO A PHONE. I CALLED AND EXPLAINED WHERE WE THOUGHT THE CONFUSION AROSE AND HE DIDN'T SEEM TO THINK THERE SHOULD HAVE BEEN ANY CONFUSION. HE INDICATED THERE WAS NO INCIDENT CREATED FROM THE EVENTS, BUT WANTED ME TO UNDERSTAND THE IMPORTANCE OF COMPLIANCE WHICH, OF COURSE, I ALREADY DID AFTER FLYING FOR 25 YRS. WE WERE TRYING TO ADHERE TO THE CTLR'S DIRECTION BUT IN TODAY'S CLIMATE, EVERYONE -- INCLUDING CTLRS AND PLTS -- IS SAYING TOO MUCH.
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.