EWR dangers

They make it seem like EWR is a rarity with intersecting runways. Do they not have any clue how common these configurations are? EWR is actually a bit tame compared to some others...
 
They make it seem like EWR is a rarity with intersecting runways. Do they not have any clue how common these configurations are?
Probably not.

Or they're from Texas, where we have DFW and IAH as the big airports...each with about 7 parallel runways. God bless Texas.
 
Didn't JFK have a near miss a while back between a Eagle EMB & a Korean 74 while conducting simultaneous ops?
 
They make it seem like EWR is a rarity with intersecting runways. Do they not have any clue how common these configurations are? EWR is actually a bit tame compared to some others...

Newark doesnt have a complex runway setup compared to say, ohare, but it does have a complex airspace setup around its runways. Going around on 11 requires turn before too long or you are heading for the traffic around the lady (and you are low to stay out of the way of LGA arrivals). The sequencing of arrivals can also get sketchy with tower alternating between "best forward airspeed" and "min approach speed" requests. I've landed 11 (with visual on the 22 traffic) and been practically over the threshold when the 22 traffic crosses my path. Thats about 5000 ft lateral seperation.

The real problem from what I've seen is when ATC sends the 11 arrival around for losing spacing and then the 22L arrival goes missed on its own, particularly when this happens close to the ground. That puts both airplanes on a climbing converging path and I believe is the cause behind some of the close misses.

I think it was all summed up by a controller one afternoon as many of us were sitting in the ballpark watching a pair of arrivals thinking "no way this is going to work". It ended up working, but only with a second or two in the spacing to make it work. One aircraft mentioned to the tower "That was art" and the controller quickly corrected him, "no, that was luck".
 
Newark doesnt have a complex runway setup compared to say, ohare, but it does have a complex airspace setup around its runways. Going around on 11 requires turn before too long or you are heading for the traffic around the lady (and you are low to stay out of the way of LGA arrivals). The sequencing of arrivals can also get sketchy with tower alternating between "best forward airspeed" and "min approach speed" requests. I've landed 11 (with visual on the 22 traffic) and been practically over the threshold when the 22 traffic crosses my path. Thats about 5000 ft lateral seperation.

The real problem from what I've seen is when ATC sends the 11 arrival around for losing spacing and then the 22L arrival goes missed on its own, particularly when this happens close to the ground. That puts both airplanes on a climbing converging path and I believe is the cause behind some of the close misses.

I think it was all summed up by a controller one afternoon as many of us were sitting in the ballpark watching a pair of arrivals thinking "no way this is going to work". It ended up working, but only with a second or two in the spacing to make it work. One aircraft mentioned to the tower "That was art" and the controller quickly corrected him, "no, that was luck".

I think that's exactly why they've recently been sending the 22L traffic around when spacing doesn't work out and letting the guy on 11 finish the approach. Then all they have to do is protect the centerline of 22L from the 22R departures ("fly runway heading" instead of the Newark7) and it works out with much better separation for everyone.
 
I've had a similar issue in Philly with a 35 - 27R conflict. Normally if it's too close (which is VERY close) they send the guy on 35 around, which is fine. That happened to us and as we started climbing straight out the Airbus on 27R got a gear issue at about 500 feet and went around, climbing directly up unto us. They saw us (and tower was screaming at them too) so they leveled off at about 1000 feet and passed about 500 feet underneath us, but it was way to close for comfort for me.
 
I think that's exactly why they've recently been sending the 22L traffic around when spacing doesn't work out and letting the guy on 11 finish the approach. Then all they have to do is protect the centerline of 22L from the 22R departures ("fly runway heading" instead of the Newark7) and it works out with much better separation for everyone.

This is nothing really new. According to the controller who comes to our recurrent ground schools every year, ATC should send the 22L traffic around if spacing is a concern, NOT the 11 traffic. Unfortunately as we all know, ATC doesn't like to send 75's, 76's, and 777s around, so they often make unrealistic request of RJs and turboprops.

As was mentioned, the 11 published missed approach is a nightmare. Luckily in practice you rarely hear it given.
 
They make it seem like EWR is a rarity with intersecting runways. Do they not have any clue how common these configurations are? EWR is actually a bit tame compared to some others...

I think what you are seeing is a very vocal group of controllers at EWR campaigning for the FAA to make changes. An EWR controller told us in class that every time there is an "incident" someone runs down stairs and calls the press. It's proved very effective for them.
 
I think what you are seeing is a very vocal group of controllers at EWR campaigning for the FAA to make changes. An EWR controller told us in class that every time there is an "incident" someone runs down stairs and calls the press. It's proved very effective for them.

.....more effective than what PATCOs idea in '81 was, I guess.
 
.....more effective than what PATCOs idea in '81 was, I guess.

Probably considering it puts pressure on the FAA from all sides in the name of safety...controllers, the flying public, and those operating the aircraft.
 
I've had a similar issue in Philly with a 35 - 27R conflict. Normally if it's too close (which is VERY close) they send the guy on 35 around, which is fine. That happened to us and as we started climbing straight out the Airbus on 27R got a gear issue at about 500 feet and went around, climbing directly up unto us. They saw us (and tower was screaming at them too) so they leveled off at about 1000 feet and passed about 500 feet underneath us, but it was way to close for comfort for me.

"Airliner 123 what's your speed?"

"250"

"Airliner 123 maintain your present speed, I'll call your reduction."

"Wilco"

"Airliner 123 reduce to your final, contact the tower."

"Over to the tower, Airliner 123."

"Philly tower, Airliner 123, visual runway 35."

"Airliner 123, your traffic's at 2 o'clock, a 7-5 over the shipyards."

"Airliner 123, we have the traffic in sight"

"Airliner 123, you're clear to land runway 35 behind the traffic."

"Clear to land runway 35, airliner 123."

It's always even more interesting when they clear you to land behind the traffic and tell you to cross through the intersection after they do. Uhhh, isn't that what landing behind the traffic means?
 
Back
Top