 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Phl local controller describes close call involving aircraft exiting runway on high speed and aircraft taxiing for departure.
| Attributes | |
| ACN | 647402 |
| Time | |
| Date | 200502 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : phl.airport |
| State Reference | PA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | landing : roll landing other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : phl.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B777 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : radar |
| Experience | controller non radar : 18 controller radar : 14 controller time certified in position1 : 15 |
| ASRS Report | 647402 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : ground critical |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Intra Facility Coordination Failure |
Narrative:
Air carrier X was landing runway 9R and knew there was an aircraft close behind him. Air carrier X exited runway 9R on taxiway S6; a high speed. Air carrier Y reported that he was almost hit by air carrier X exiting runway 9R. Air carrier Y taxied to runway 9L via the 'Z' flow via txwys J; Z; eastbound on taxiway south; to taxiway west to runway 9L. Air carrier Y looked like he was west of taxiway S6 on taxiway south. Who was in the wrong? Air carrier X helped out by exiting early and used a high speed. Is there an far that states taxiing aircraft should hold short of all high speeds? We don't have any procedures at phl that warn aircraft that some of our txwys are blocked for our arrs on runway 9R. Should we include on our arrival ATIS that we are on a 'Z' flow and arrs should plan to exit runway 9R after taxiway Y?
Original NASA ASRS Text
Title: PHL LCL CTLR DESCRIBES CLOSE CALL INVOLVING ACFT EXITING RWY ON HIGH SPD AND ACFT TAXIING FOR DEP.
Narrative: ACR X WAS LNDG RWY 9R AND KNEW THERE WAS AN ACFT CLOSE BEHIND HIM. ACR X EXITED RWY 9R ON TXWY S6; A HIGH SPD. ACR Y RPTED THAT HE WAS ALMOST HIT BY ACR X EXITING RWY 9R. ACR Y TAXIED TO RWY 9L VIA THE 'Z' FLOW VIA TXWYS J; Z; EBOUND ON TXWY S; TO TXWY W TO RWY 9L. ACR Y LOOKED LIKE HE WAS W OF TXWY S6 ON TXWY S. WHO WAS IN THE WRONG? ACR X HELPED OUT BY EXITING EARLY AND USED A HIGH SPD. IS THERE AN FAR THAT STATES TAXIING ACFT SHOULD HOLD SHORT OF ALL HIGH SPDS? WE DON'T HAVE ANY PROCS AT PHL THAT WARN ACFT THAT SOME OF OUR TXWYS ARE BLOCKED FOR OUR ARRS ON RWY 9R. SHOULD WE INCLUDE ON OUR ARR ATIS THAT WE ARE ON A 'Z' FLOW AND ARRS SHOULD PLAN TO EXIT RWY 9R AFTER TXWY Y?
Data retrieved from NASA's ASRS site as of January 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.