37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 788654 |
Time | |
Date | 200805 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : ord.airport |
State Reference | IL |
Altitude | agl single value : 0 |
Environment | |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | landing : roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
ASRS Report | 788654 |
Events | |
Anomaly | conflict : ground less severe |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Airport Flight Crew Human Performance ATC Human Performance |
Primary Problem | Ambiguous |
Air Traffic Incident | Intra Facility Coordination Failure |
Narrative:
Many times; when feasible; while landing on runway 10; I plan on exiting at taxiway F to expedite ground taxi times. However; frequently as we approach that intersection we find other aircraft blocking that exit as they wait to cross. There is no mention of this other traffic to landing aircraft; and it's not until tower sees that landing traffic may be intending to turn off at taxiway F that they then direct rollout to a later taxiway. At night; many times when landing you do not see that intersection traffic until you are just about there. This requires an immediate change to turnoff plans; requiring even more time on the runway as you are now rolling up to the next available taxiway at a slower speed. Once or twice tower didn't have time to initiate turnoff instructions until it would have been too late. I strongly suggest that tower keep all feasible exiting txwys clear or; if unable; then they communicate that to landing traffic immediately upon landing clearance!
Original NASA ASRS Text
Title: B757 FO REQUESTS ORD TOWER INFORM FLT CREWS WHEN TXWY F IS BLOCKED DURING RWY 10 LANDING.
Narrative: MANY TIMES; WHEN FEASIBLE; WHILE LNDG ON RWY 10; I PLAN ON EXITING AT TXWY F TO EXPEDITE GND TAXI TIMES. HOWEVER; FREQUENTLY AS WE APCH THAT INTXN WE FIND OTHER ACFT BLOCKING THAT EXIT AS THEY WAIT TO CROSS. THERE IS NO MENTION OF THIS OTHER TFC TO LNDG ACFT; AND IT'S NOT UNTIL TWR SEES THAT LNDG TFC MAY BE INTENDING TO TURN OFF AT TXWY F THAT THEY THEN DIRECT ROLLOUT TO A LATER TXWY. AT NIGHT; MANY TIMES WHEN LNDG YOU DO NOT SEE THAT INTXN TFC UNTIL YOU ARE JUST ABOUT THERE. THIS REQUIRES AN IMMEDIATE CHANGE TO TURNOFF PLANS; REQUIRING EVEN MORE TIME ON THE RWY AS YOU ARE NOW ROLLING UP TO THE NEXT AVAILABLE TXWY AT A SLOWER SPD. ONCE OR TWICE TWR DIDN'T HAVE TIME TO INITIATE TURNOFF INSTRUCTIONS UNTIL IT WOULD HAVE BEEN TOO LATE. I STRONGLY SUGGEST THAT TWR KEEP ALL FEASIBLE EXITING TXWYS CLR OR; IF UNABLE; THEN THEY COMMUNICATE THAT TO LNDG TFC IMMEDIATELY UPON LNDG CLRNC!
Data retrieved from NASA's ASRS site as of May 2009 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.