Narrative:

I had just taken and split the position with another controller who had previously had both grounds combined. The push was just getting started and I had a few opposite direction conflicts to work out; involving traffic in and out of the GA ramp at the northeast part of the airport. Aircraft X was one of several aircraft I asked to standby at their outbound spots because I had numerous runway crossings to coordinate. I then went back and started taxiing aircraft; including aircraft X. I recall hearing; and later confirmed from playback a good read-back of the instructions to taxi 'runway 27 left via hotel and echo; hold short runway 27 right.' I went back to planning and resolving my arrival/departure traffic from the GA ramp; and accomplishing runway crossings. I was alerted by the ground west controller of something wrong when he asked; 'what's aircraft X doing?' looking at the asde-X I could see that aircraft X had turned left out of hotel and taken echo 4 across runway 35; joining delta 4. I advised aircraft X that they had taken a wrong turn and crossed a runway and began working out the now increasingly complex set of conflicts presented by their deviation. Aircraft X continued taxi to runway 27 left without much further incident.what's odd about this incursion is that it happened at what has long been a hotspot for phl; the hotel/echo intersection; but in a way that I've never heard of or seen before. Taxiway hotel east of echo and crossing runway 35 is currently closed precisely because aircraft leaving spots xx and xy sometimes fail to make the right turn onto echo and instead continue straight on hotel and across runway 35. But aircraft X; in order to have this incursion; had to make a hard left off of hotel; onto echo 4; and took that across runway 35; a scenario that I would not have considered very likely prior to this event. I can only speculate on why aircraft X mistakenly turned left instead of what seems like the obvious correct choice to turn right onto echo; joined the wrong taxiway (echo 4 instead of echo) and crossed a runway. But the intersection occasionally still gives pilots trouble; in spite of or perhaps because of the taxiway closure. In fact later in that same push; a 757 stopped on hotel short of echo and requested confirmation of his instructions to turn right on echo. He seemed confused at first but quickly figured it out. I've never seen the hotel/echo/echo 4 intersection from ground level at night but judging from the close proximity of all the taxiways and runways; I'd imagine it's a confusing sight to an unfamiliar pilot. Maybe the blinking barrier lights showing the closed portion of hotel make this situation worse? Without getting more detail from the pilots; I can only speculate. In the future; I'd consider specifying 'hotel; turn right on echo; hold short;' to avoid what seems like a very unlikely error by the pilot.

Google
 

Original NASA ASRS Text

Title: PHL Controller and pilots report of a runway incursion caused by possibly bad lighting on the taxiways and runway.

Narrative: I had just taken and split the position with another controller who had previously had both grounds combined. The push was just getting started and I had a few opposite direction conflicts to work out; involving traffic in and out of the GA ramp at the northeast part of the airport. Aircraft X was one of several aircraft I asked to standby at their outbound spots because I had numerous runway crossings to coordinate. I then went back and started taxiing aircraft; including Aircraft X. I recall hearing; and later confirmed from playback a good read-back of the instructions to taxi 'Runway 27 Left via Hotel and Echo; hold short Runway 27 Right.' I went back to planning and resolving my arrival/departure traffic from the GA ramp; and accomplishing runway crossings. I was alerted by the Ground West controller of something wrong when he asked; 'What's Aircraft X doing?' Looking at the ASDE-X I could see that Aircraft X had turned left out of Hotel and taken Echo 4 across Runway 35; joining Delta 4. I advised Aircraft X that they had taken a wrong turn and crossed a runway and began working out the now increasingly complex set of conflicts presented by their deviation. Aircraft X continued taxi to Runway 27 left without much further incident.What's odd about this incursion is that it happened at what has long been a hotspot for PHL; the Hotel/Echo intersection; but in a way that I've never heard of or seen before. Taxiway Hotel east of Echo and crossing Runway 35 is currently closed precisely because aircraft leaving spots XX and XY sometimes fail to make the right turn onto Echo and instead continue straight on Hotel and across Runway 35. But Aircraft X; in order to have this incursion; had to make a hard left off of Hotel; onto Echo 4; and took that across Runway 35; a scenario that I would not have considered very likely prior to this event. I can only speculate on why Aircraft X mistakenly turned left instead of what seems like the obvious correct choice to turn right onto Echo; joined the wrong taxiway (echo 4 instead of echo) and crossed a runway. But the intersection occasionally still gives pilots trouble; in spite of or perhaps because of the taxiway closure. In fact later in that same push; a 757 stopped on Hotel short of Echo and requested confirmation of his instructions to turn right on Echo. He seemed confused at first but quickly figured it out. I've never seen the Hotel/Echo/Echo 4 intersection from ground level at night but judging from the close proximity of all the taxiways and runways; I'd imagine it's a confusing sight to an unfamiliar pilot. Maybe the blinking barrier lights showing the closed portion of Hotel make this situation worse? Without getting more detail from the pilots; I can only speculate. In the future; I'd consider specifying 'Hotel; turn RIGHT on Echo; hold short;' to avoid what seems like a very unlikely error by the pilot.

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.