Moderators: jsumali2, richierich, ua900, PanAm_DC10, hOMSaR
GSP psgr wrote:Let's suppose that somehow, there was the opportunity to add a single new runway at one of the three big New York City airports (LGA, JFK, or EWR). What and where do you build it and why? I tend to think that the answer is not another runway at LGA, and that the answer is either a third parallel at EWR (the 'Ikea Store Runway') or another parallel to 13R/31L at JFK (where the need is arguably greatest and you can add terminal capacity to handle the additional traffic).
PatrickZ80 wrote:None of these are possible, the land is all occupied otherwise. That's one of the disadvantages of having airports within the city limits. They cannot be expanded.
Eventually there will be need for a relief airport outside the city limits, Stewart seems the most logical for this. Build some good high-speed connections between Stewart Airport and New York City and you don't need to expand any airport within the city.
leader1 wrote:Uhhh...no. Stewart is much too far and there is no money or will to build a high-speed rail connection there (or anywhere else in this country, for that matter). Not going to happen. Even PANYNJ has given up on this airport.
leader1 wrote:Another 13/31 just north of 13L/31R at JFK where the northern cargo area is. Plenty of space there and all the cargo ops can be consolidated at the western side of the airport. I guess you could also add another 4/22 runway between 4R/22L and 4L/22R, but the runways would be really close together and there would be taxiing issues.
The real problem, though, is the airspace. That hampers all three airports from running efficiently, even with their current runway configurations.
jfklganyc wrote:You need to actually close LaGuardia
You would actually increase runway capacity by simplifying the airspace
N649DL wrote:Definitely EWR. I say built one over I-95 and make it a tunnel below it for cars like at LAX.
leader1 wrote:Another 13/31 just north of 13L/31R at JFK where the northern cargo area is. Plenty of space there and all the cargo ops can be consolidated at the western side of the airport. I guess you could also add another 4/22 runway between 4R/22L and 4L/22R, but the runways would be really close together and there would be taxiing issues.
The real problem, though, is the airspace. That hampers all three airports from running efficiently, even with their current runway configurations.PatrickZ80 wrote:None of these are possible, the land is all occupied otherwise. That's one of the disadvantages of having airports within the city limits. They cannot be expanded.
Eventually there will be need for a relief airport outside the city limits, Stewart seems the most logical for this. Build some good high-speed connections between Stewart Airport and New York City and you don't need to expand any airport within the city.
Uhhh...no. Stewart is much too far and there is no money or will to build a high-speed rail connection there (or anywhere else in this country, for that matter). Not going to happen. Even PANYNJ has given up on this airport.
airlineworker wrote:jfklganyc wrote:You need to actually close LaGuardia
You would actually increase runway capacity by simplifying the airspace
JFK & EWR would not be able to absorb the LGA flights.
DCA-ROCguy wrote:I'll give my usual short speech regarding New York City, it's airports and airspace, tailored to this thread. For what it's worth.
Politically, none of the three airports are going anywhere. NYC isn't going to be the only major Northeastern business center without its own downtown airport (BOS, DCA, and PHL are all effectively downtown airports). So LGA isn't going anywhere.
Politically, none of the three airports are getting new runways. But, if I had anything to say about it, EWR and JFK would get those nice new runways discussed in the RPA report.
Politically, how much airspace reconfiguration can be done? If I had anything to say, airspace would be reconfigured for maximum capacity, period. But I'd guess there's limited ability to do that. For instance, DC's wealthy neighborhoods got all up in arms over DCA's airspace realignment. All those environmentally-conscious progressives in Georgetown and Potomac don't care about reducing fuel burn when there are more AA E175's over their house.
As I see it, to make New York City work and stop being a nationally-impacting congestion-and-delay hairball, two steps are needed. (If things have improved significantly recently, please correct me, but my understanding is that NYC still has delay issues.)
First, re-slot EWR at 10 percent lower than its old total, and cut slots at JFK and LGA 10 percent. That should make the airspace less congested in all weather conditions. Cut each carrier proportionally, except say those with fewer than 10 daily departures
Second, require that all smaller markets that currently have service to each airport keep it. So, sorry, you're flying a few flights a day from LGA to Greensboro and Rochester and Columbus, you're going to keep serving them. Deal with it. Airports are public facilities. Cut frequencies at larger markets and upgauge.
Fewer airplanes and upgauging would make New York City work.
Jim
United857 wrote:N649DL wrote:Definitely EWR. I say built one over I-95 and make it a tunnel below it for cars like at LAX.
The problem with building another 4/22 runway at EWR is there's no way to get arrivals onto it or departures off it without compromising traffic flow to an existing runway due to traffic conflicts with LGA. This is because all the arrivals to LGA from the south fly over the Hudson when LGA is landing on 22 at just 4000 ft, which limits EWR to only a left hand traffic pattern on the 4s and a right hand traffic pattern on the 22s, both of which are to the west of the airport over NJ and essentially the same, just with the planes flying in opposite directions.
In order for any type of parallel arrival to be performed, you need both a left hand and a right hand traffic pattern, one for each runway, like how SFO does it for 28L/R. The same thing is needed for departures, with the left hand runway turning left after departure and the right hand runway turning right (again see SFO departures off 1LR). This is currently not possible due to airspace constraints, and since a 3rd runway will only really be beneficial if you can run dual arrivals and dual departures (what would be the point of a 3rd runway if you can only have 1 runway departing and 1 runway arriving at any given moment), unless some airspace magic happens, an extra runway over I95 can't really improve the traffic situation all that much.
As a result, the current traffic pattern uses 1 runway for departures and 1 runway for arrivals. Arrivals approach over NJ before making a final left turn for 4R or right turn for 22L (4L/22R is used exclusively for departures). Departures off the 4s stay west of the Hudson over NJ until the aircraft passes LGA before turning east if that's were the flight is headed. Departures from the 22s, if going east, make a right hand 180 degree turn and then follow the same path as the departures off 4s to stay clear of LGA traffic. UA has been trying for years to get parallel departure/arrival operations at EWR, but was never approved due to the lack of airspace available on the east side of the airport to give 4R/22L its own separate traffic pattern.
maps4ltd wrote:United857 wrote:N649DL wrote:Definitely EWR. I say built one over I-95 and make it a tunnel below it for cars like at LAX.
The problem with building another 4/22 runway at EWR is there's no way to get arrivals onto it or departures off it without compromising traffic flow to an existing runway due to traffic conflicts with LGA. This is because all the arrivals to LGA from the south fly over the Hudson when LGA is landing on 22 at just 4000 ft, which limits EWR to only a left hand traffic pattern on the 4s and a right hand traffic pattern on the 22s, both of which are to the west of the airport over NJ and essentially the same, just with the planes flying in opposite directions.
In order for any type of parallel arrival to be performed, you need both a left hand and a right hand traffic pattern, one for each runway, like how SFO does it for 28L/R. The same thing is needed for departures, with the left hand runway turning left after departure and the right hand runway turning right (again see SFO departures off 1LR). This is currently not possible due to airspace constraints, and since a 3rd runway will only really be beneficial if you can run dual arrivals and dual departures (what would be the point of a 3rd runway if you can only have 1 runway departing and 1 runway arriving at any given moment), unless some airspace magic happens, an extra runway over I95 can't really improve the traffic situation all that much.
As a result, the current traffic pattern uses 1 runway for departures and 1 runway for arrivals. Arrivals approach over NJ before making a final left turn for 4R or right turn for 22L (4L/22R is used exclusively for departures). Departures off the 4s stay west of the Hudson over NJ until the aircraft passes LGA before turning east if that's were the flight is headed. Departures from the 22s, if going east, make a right hand 180 degree turn and then follow the same path as the departures off 4s to stay clear of LGA traffic. UA has been trying for years to get parallel departure/arrival operations at EWR, but was never approved due to the lack of airspace available on the east side of the airport to give 4R/22L its own separate traffic pattern.
Great info, thanks. You seem very knowledgeable on the subject. Do you know why departures off 4L and 22R veer slightly left after departure? Also, do you know how 11/29 ops work? For 29, I've seen planes fly south parallel to 22L landings (but a bit to the east), and turn right for final very close to the airport.
I've been on that odd 180 and tracking up before turning left across north NJ when departing from 22R before. It's somewhat annoying.
DCA-ROCguy wrote:your plan is to regulate air travel. Not gonna happen. It’s illegal.I'll give my usual short speech regarding New York City, it's airports and airspace, tailored to this thread. For what it's worth.
Politically, none of the three airports are going anywhere. NYC isn't going to be the only major Northeastern business center without its own downtown airport (BOS, DCA, and PHL are all effectively downtown airports). So LGA isn't going anywhere.
Politically, none of the three airports are getting new runways. But, if I had anything to say about it, EWR and JFK would get those nice new runways discussed in the RPA report.
Politically, how much airspace reconfiguration can be done? If I had anything to say, airspace would be reconfigured for maximum capacity, period. But I'd guess there's limited ability to do that. For instance, DC's wealthy neighborhoods got all up in arms over DCA's airspace realignment. All those environmentally-conscious progressives in Georgetown and Potomac don't care about reducing fuel burn when there are more AA E175's over their house.
As I see it, to make New York City work and stop being a nationally-impacting congestion-and-delay hairball, two steps are needed. (If things have improved significantly recently, please correct me, but my understanding is that NYC still has delay issues.)
First, re-slot EWR at 10 percent lower than its old total, and cut slots at JFK and LGA 10 percent. That should make the airspace less congested in all weather conditions. Cut each carrier proportionally, except say those with fewer than 10 daily departures
Second, require that all smaller markets that currently have service to each airport keep it. So, sorry, you're flying a few flights a day from LGA to Greensboro and Rochester and Columbus, you're going to keep serving them. Deal with it. Airports are public facilities. Cut frequencies at larger markets and upgauge.
Fewer airplanes and upgauging would make New York City work.
Jim
bpat777 wrote:Reading this post makes me realize how close the 3 major NYC area airports are to one another. I now have a better understanding to how quickly and easily things go down hill during not so perfect weather conditions. Then to add TEB into the mix.
maps4ltd wrote:United857 wrote:N649DL wrote:Definitely EWR. I say built one over I-95 and make it a tunnel below it for cars like at LAX.
The problem with building another 4/22 runway at EWR is there's no way to get arrivals onto it or departures off it without compromising traffic flow to an existing runway due to traffic conflicts with LGA. This is because all the arrivals to LGA from the south fly over the Hudson when LGA is landing on 22 at just 4000 ft, which limits EWR to only a left hand traffic pattern on the 4s and a right hand traffic pattern on the 22s, both of which are to the west of the airport over NJ and essentially the same, just with the planes flying in opposite directions.
In order for any type of parallel arrival to be performed, you need both a left hand and a right hand traffic pattern, one for each runway, like how SFO does it for 28L/R. The same thing is needed for departures, with the left hand runway turning left after departure and the right hand runway turning right (again see SFO departures off 1LR). This is currently not possible due to airspace constraints, and since a 3rd runway will only really be beneficial if you can run dual arrivals and dual departures (what would be the point of a 3rd runway if you can only have 1 runway departing and 1 runway arriving at any given moment), unless some airspace magic happens, an extra runway over I95 can't really improve the traffic situation all that much.
As a result, the current traffic pattern uses 1 runway for departures and 1 runway for arrivals. Arrivals approach over NJ before making a final left turn for 4R or right turn for 22L (4L/22R is used exclusively for departures). Departures off the 4s stay west of the Hudson over NJ until the aircraft passes LGA before turning east if that's were the flight is headed. Departures from the 22s, if going east, make a right hand 180 degree turn and then follow the same path as the departures off 4s to stay clear of LGA traffic. UA has been trying for years to get parallel departure/arrival operations at EWR, but was never approved due to the lack of airspace available on the east side of the airport to give 4R/22L its own separate traffic pattern.
Great info, thanks. You seem very knowledgeable on the subject. Do you know why departures off 4L and 22R veer slightly left after departure? Also, do you know how 11/29 ops work? For 29, I've seen planes fly south parallel to 22L landings (but a bit to the east), and turn right for final very close to the airport.
I've been on that odd 180 and tracking up before turning left across north NJ when departing from 22R before. It's somewhat annoying.
United857 wrote:maps4ltd wrote:United857 wrote:
The problem with building another 4/22 runway at EWR is there's no way to get arrivals onto it or departures off it without compromising traffic flow to an existing runway due to traffic conflicts with LGA. This is because all the arrivals to LGA from the south fly over the Hudson when LGA is landing on 22 at just 4000 ft, which limits EWR to only a left hand traffic pattern on the 4s and a right hand traffic pattern on the 22s, both of which are to the west of the airport over NJ and essentially the same, just with the planes flying in opposite directions.
In order for any type of parallel arrival to be performed, you need both a left hand and a right hand traffic pattern, one for each runway, like how SFO does it for 28L/R. The same thing is needed for departures, with the left hand runway turning left after departure and the right hand runway turning right (again see SFO departures off 1LR). This is currently not possible due to airspace constraints, and since a 3rd runway will only really be beneficial if you can run dual arrivals and dual departures (what would be the point of a 3rd runway if you can only have 1 runway departing and 1 runway arriving at any given moment), unless some airspace magic happens, an extra runway over I95 can't really improve the traffic situation all that much.
As a result, the current traffic pattern uses 1 runway for departures and 1 runway for arrivals. Arrivals approach over NJ before making a final left turn for 4R or right turn for 22L (4L/22R is used exclusively for departures). Departures off the 4s stay west of the Hudson over NJ until the aircraft passes LGA before turning east if that's were the flight is headed. Departures from the 22s, if going east, make a right hand 180 degree turn and then follow the same path as the departures off 4s to stay clear of LGA traffic. UA has been trying for years to get parallel departure/arrival operations at EWR, but was never approved due to the lack of airspace available on the east side of the airport to give 4R/22L its own separate traffic pattern.
Great info, thanks. You seem very knowledgeable on the subject. Do you know why departures off 4L and 22R veer slightly left after departure? Also, do you know how 11/29 ops work? For 29, I've seen planes fly south parallel to 22L landings (but a bit to the east), and turn right for final very close to the airport.
I've been on that odd 180 and tracking up before turning left across north NJ when departing from 22R before. It's somewhat annoying.
The departures of 4L/22R do a small "s-turn" to keep the flight path and thus noise over the highway spaghetti around the airport as long as possible (the specific flight path is actually published in the SID). Off of 4L you typically make a slight right turn after departure before turning back left while off 22R you make a slight left turn before turning back right.
11/29 ops are really only done when crosswinds on the 4/22s get very significant.
Usually what happens is that the wind is blowing very strong out of the west, and as a result arrivals run on 29. Again, to keep traffic spacing with LGA traffic over the Hudson, the flights fly the normal 22L arrival flight path, before breaking off to the left over the Meadowlands Sports Complex and making a sharp right turn to line up with 29 on an arrival called the "Stadium Visual." Departures in this case are also on 29 doing a normal straight out departure, except for the heavies to Asia that can't make it off 29. They will still use 22R. However, ATC is very reluctant to go to 29 ops simply because running both arrivals and departures on the same runway vs splitting them between 22L and 22R means almost a 50% capacity reduction that causes major delays.
Runway 11 ops on the other hand are very very rare. Arrivals don't use the standard 4R approach and is instead vectored to the west of that arrival path before making a right hand turn onto final. Departures make a sharp left turn after liftoff to stay clear of LGA traffic.