New Traffic Patterns PHL

[ One added fact: the pattern change was requested by a new entrant to the PHL market to speed things up and reduce ramp congestion.
[/quote]

Maybe so. But I will give ATC at PHL a star for at least trying something different. This has been going on off and on since last summer, and it seems to me to be working at least a little better, despite the extra taxi time after landing. Also...we may have more taxi time rolling off 27L to get back to the ramp..but timewise it is not that much more than being stuck in ramp traffic after leaving 27R. I have not flown into PHL in a couple of months, but one UNfair practice was spacing departures based on check in to ground control...airlines on the East side could check in right after push..airline(s,) pretty much all of U, could not check into ground until quite a good bit of taxi, expecially under the 27L landing flow. A bit of sour grapes on my part..but unfair none the less. Again..at least PHL is trying to improve the operation, and anyone or any airline that promoted that gets my thanks. Greeter.
 
  • Thread Starter
  • Thread starter
  • #17
algflyer flies the E170 for US Airways. That flight number is Piedmont, a dash 8.

Fly,

Thanks for the info. I was using the "alg" to assume that algflyer might have stayed with Allegheny when it was folded into Piedmont.

Algflyer, I wish you the very best and hope you land on your feet with the MA nonsense.

My best to you all.....
 
Thanks Art. While I do fly the 170 (for now), I flew the Dash into ISP for many years while at Allegheny. I'm sure I have gotten you home on more than one occasion. With a nice smooth landing of course...
 
In a westerly ONLY no 17/35 arrivals or departures, this departure plan ensures that there is not an active runway crossing operation. The change to landing runway 27L and departing runway 27R results in a reduction in runway incursions by simplifying ground movements. Departing 27R and landing 27L de-conflicts ground operations, with 17/35, closed outbound and inbound traffic does not cross any active runways. This is the reason, upon landing on 27L, taxi all the way to Zulu taxiway so that there is not a runway crossing event. The choice of the flow is entirely up to the operations supervisor on duty and will, at times, change. Some of the conditions affecting the change would be peak and non-peak arrival and departures, noise impact, and whether the supervisor requests the flow pattern. The arrival flow rate increases from 52 to 58 operations/hr. with higher potential rates if more aircraft accept Runway 26.
 

Latest posts

Back
Top