Second airport, Dulles-style

Shepard

Senior Member
Joined
Mar 20, 2009
Messages
3,518
Reaction score
65
Did anyone see this article from the Globe?

Aerotropolis
The rise of a vibrant new kind of city ? and how Massachusetts missed a chance to have one
By Peter Canellos

Globe Staff / October 31, 2010

CHANTILLY, VA. ? Forty years ago, the road to the still-new Dulles Airport cut through miles of loamy forest, darkening the view of the few cars that made their way along it. Then, in a sudden glade, appeared the swooping roof of the Eero Saarinen-designed terminal, gleaming as if poised for takeoff. But there were only a few flights per hour, each announced on a loudspeaker in the accented voice of a ?Masterpiece Theater? host. Known more for its architecture than its functionality, Dulles was called the white elephant, the rarest and loneliest of species.
Tweet ..Yahoo! Buzz ShareThis .
Today, the access road from the Beltway to Dulles is a city unto itself, packed with tens of thousands of homes, plus malls, arts centers, and area attractions. Mostly, there are hundreds of office buildings emblazoned with the most dazzling names in global high tech: UNISYS, IBM, Oracle, ITT. If Dulles were a city, it would be among the hundred most populated in the country. And among the richest: The Northern Virginia boom has sparked changes in the Washington-area economy. Once purely a government town, it now glistens with commerce.

Dulles is no longer an airport but an aerotropolis, a term coined by a University of North Carolina business professor. An aerotropolis is a city of the 21st century, built around a runway in roughly the same way that historic cities grew up around water or rail lines, with a close-in network of businesses, an outer loop of service industries, and suburbs full of homes.

Aerotropolises have emerged in places like the former no man?s zone between Dallas and Fort Worth, in suburban Atlanta, and around Schiphol Airport in the Netherlands, near Amsterdam, Rotterdam, and The Hague. They provide what John D. Kasarda, the UNC professor, calls ?connectivity? to the global marketplace. International companies want to locate where their executives can step out their doors and be on another continent eight hours later. Firms producing the highest-value goods want to ship them to markets around the world. (?The Web won?t move a box,? Kasarda declares. ?High-end products move by air.?) And businesses with tentacles around the globe want a place where all their people can fly in easily for meetings.

Such firms are, of course, precisely the type that draw on the innovations created in Boston, but then often move elsewhere. Their major operations ? executive offices, high-end manufacturing ? get established outside New England. Northern Virginia is one such place, whose growth in high-tech industries has paralleled the Boston area?s decline.

Massachusetts does not have an aerotropolis. When confronted with the opportunity to lay the groundwork for a second major airport, 20 years ago, the state passed it up. It was, in the eyes of some economists, a big mistake, the kind that separates the truly global metropolises from the boutique cities.

The reasons were, to a large extent, the usual ones in Massachusetts. Hubris ? the sense among many policy makers that economic growth was inevitable, a force to be channeled and, if necessary, limited, rather than given any special encouragement. Local resistance ? the belief that any change would harm the quality of life rather than enhance it. And short-sightedness ? a sense that transportation was meant to serve those already living here, rather than to be a magnet to attract more.

But there was also a change that few, if anyone, could see.

Corporations that once thought of themselves as rooted in one place began to think of themselves as being everywhere, and wanting a base of operations that was as monolithic, generic, and peripatetic as they were.

They wanted to be at an airport. And while Massachusetts has a fine one, its extremely limited environs are too dense, too crowded, to serve the needs of the most expansive corporations.

Boston was in the midst of the greatest boom in recent history when members of the Massachusetts Aeronautical Commission began planning for a second major airport ? a Bay State version of Dulles, suitable for handling international traffic. Passengers commuting to the city center would keep using Logan Airport, much the way Reagan National Airport serves the capital.

In the five years between 1983 and 1988, the ?Massachusetts miracle? had produced 400,000 new jobs, many of them of the high-wage, high-tech variety that elevates a region to wealth and importance. When computer visionaries considered the most technology-friendly areas of the country, first was Silicon Valley, near San Francisco, and second was the Route 128 belt around Boston. Everywhere else was far behind.

Logan was under increasing strain. It wasn?t just the aging facilities and rows of angry protesters who appeared like clockwork whenever expansion was mentioned: Even with a third harbor tunnel and significant upgrading of facilities, Logan was deemed to be too crowded to meet the future needs of a major economic center.

These conclusions were spelled out in the aeronautics commission?s initial report, released in 1990. In light of what?s happened over the succeeding two decades, it?s clearly a document from another era. The expansionist impulse reflected in its projections is as much a part of Boston?s past as the Revolutionary War. It cited studies envisioning an annual increase in air traffic of up to 4 percent. ?They all point to the fact that by the year 2010, the existing New England airport system will not be able to handle all the passengers who wish to travel,? the report declared.

The commission examined sites that could be held in a land bank while plans were drawn for an airport that would serve between 5 million and 7 million passengers in 2010 and grow to a whopping 30 million in 2020. This would be in addition to Logan?s growth, and that of other New England airports. The New England Council, a business policy group, insisted that without a second major airport the Massachusetts economy would be squeezed. In the go-go ?80s, Massachusetts was marching to a different beat.

But not entirely. Even as the commission was completing its work, inspecting 182 sites before recommending the surplus Army base at Fort Devens as the likeliest spot, local opposition began to arise, as communities throughout the Boston area rallied in fear of noise, traffic, and disruption. It soon became apparent that political will was lacking as well. Interviews with many who were involved in the project suggest that while some senior officials of both the Dukakis and Weld administrations were intrigued by a second airport, the governors themselves were not.

Dukakis felt that adding high-speed rail to New York would relieve enough air traffic to obviate the need for another airport. He also believed that the blossoming of high-tech industries would be the key to reviving old mill cities outside Boston; new manufacturing plants would spring up on the old bones of Worcester, Lawrence, and Haverhill, just as Wang computers had helped revitalize Lowell. A new airport, he reasoned, might pull jobs from the cities, creating sprawl and congestion.

Weld, for his part, spent part of the 1990 campaign addressing audiences in the high-income towns west of Boston who were convinced a new airport would have planes bearing down on their roofs. Their fears were overblown but understandable. For years, East Boston neighbors had claimed that class bias had deafened policy makers to the airport noise that plagued their communities. The new airport, many believed, would be a form of justice, afflicting suburbanites in the same way that people in Eastie had suffered.

Weld promised to reexamine the projections, ordering a new study by the consulting firm of Arthur D. Little. By 1991, the Massachusetts economy had been battered by recession, and those fast-growth assumptions were off the mark, the Little report concluded. Betty Desrosiers, the chief aviation planner for Massport who had been project manager for the second-airport siting study, recalls that a fresh examination of the winds swirling around Logan turned up the surprising fact that the existing airport could increase its capacity substantially with a new runway to handle takeoffs of commuter aircraft.

It seemed a perfect solution. Communities around Fort Devens and other proposed sites were relieved. Desrosiers remembers having sat at angry community meetings where protesters carried signs with pictures of Dulles Airport and a caricature of a white elephant. There would be no big, new airport on the open fields beyond Route 128. Close-in Logan, with more traffic on a footprint of its size than any airport on the planet, would have to bear the load.

The two succeeding decades have proven either the prescience of the second-airport opponents, or their utter folly. Growth has been sluggish.

Massachusetts? position at the vanguard of the high-tech revolution has diminished. From 2001 to 2009, according to the Bureau of Labor Statistics, high-tech employment shrunk by 14.7 percent. Virginia now has more high-tech workers per capita than Massachusetts.

Between 2000 and 2009, the number of flights at the refurbished Logan actually dropped, though passenger traffic held steady. In the late ?80s, the air-travel passenger demand for booming Boston had been 12th highest in the world; now, it?s no longer in the top 50. Logan is the world?s 43d busiest airport, but many other cities split their traffic between multiple airports, pushing Boston further down the list of busiest cities.

Massachusetts business leaders can only wonder whether this decline was inevitable, or if having a second major airport would have changed the face of the state economy. One who believes a second airport would have created a whole new economic engine is the private equity investor Steve Pagliuca of Boston?s Bain Capital. ?Airports are the highways of the 21st century,? he says, noting that two decades ago, few firms thought primarily in terms of the global market; now, almost all do.

Indeed, the two factors that fueled the explosive growth around Dulles, Dallas-Fort Worth International Airport, and Chicago-O?Hare were the new global focus of many industries combined with the availability of land on which big expansions are possible.

When DFW airport opened, in 1973, it was as isolated as Dulles, laid down on a slice of Texas prairie with nothing but fast-food joints for company; now, it?s the world?s eighth-busiest airport and its once-tiny host community of Las Colinas is home to the headquarters of four Fortune 500 companies. The factor that initially turned locals against it ? they found it too far away from downtown, and many preferred the convenience of Dallas?s close-in Love Field ? was what fueled the boom: There was ample land for economic development.

Companies that locate near airports don?t follow a single script. Some are there for the proximity to air freight, the value of which has grown exponentially. (Over the 30 years between 1976 and 2006, national GDP swelled by 154 percent while exports by air expanded by 1,395 percent.) Others are there for access to regional transportation; large airports outside major cities tend to have ribbons of highway heading in all directions, making them ideal distribution centers. Still other companies are there for the ease of bringing in executives from distant branches around the world.

In most of these factors, Logan doesn?t even compete ? it simply doesn?t have the space to be an airport city. Even with the improved access of the Ted Williams Tunnel, it is too crowded to attract manufacturers looking to build major facilities. There?s relatively little room for trucks to fan out and distribute goods throughout New England. And the old, historic neighborhoods surrounding the airport have their own charms and appeals, but aren?t right for companies building global headquarters.

What?s noticeable around Dulles is the international character of the buildings ? the Euro and Asian texture of the designs. (Only the strip malls and housing developments adhere to the faux-Williamsburg look of Northern Virginia.) These offices could be anywhere, from Frankfurt to Osaka. And it?s easy to believe that their global functionality appeals to people from outside the United States ? or, for that matter, those within the United States who want to expand globally. Their aspirations are written in their architecture, and in their location, next to an airport.

To serve their needs, planners in Bangkok, Beijing, and Dubai have laid out entire pre-fab cities of hundreds of thousands of people to be built around giant new airports. The $35 billion airport city being built outside Incheon, South Korea ? the largest private development in the world ? will be precisely the size of downtown Boston.

The spaces around American airports have grown up organically, without the rampant planning of Asian and Middle Eastern governments. But their growth has been just as impressive. Given what?s happened over the past 20 years at Dulles, DFW, and Chicago-O?Hare, there?s no reason to believe a second major airport in New England wouldn?t have become a global hub, a bright new face for the region.

In retrospect, the Massachusetts Aeronautics Commission did its job only too well. The former Fort Devens is directly on Route 495, amid huge swaths of open land between economically needy Worcester and Lawrence ? a nearly perfect setting for an aerotropolis. It connects easily to Route 128 and is a direct shot up Route 2 from Cambridge.

The long, empty expanse of roadway ending at a beltway is almost eerily similar to the landscape encountered by those planning Dulles. Instead of building an airport, though, Massachusetts chose to make Devens a special economic development district ? an aerotropolis without the airport. It hasn?t taken off, despite some sporadic successes. Some high-tech and pharma firms, led by Bristol-Myers Squibb, have built new facilities there.

But even after 20 years, Devens promises more than it delivers. Vast expanses still look like a surplus military base, with cracked pavement and abandoned low-rise buildings. Other sections have that empty ?Truman Show? quality of a planned community that hasn?t quite gelled ? flags planted where buildings should be, a sleepy quiet interrupted only by recorded announcements from the Rapid Refill gas station/mini-mart: ?Arizona Tea water, two for two dollars.?

Almost everywhere are signs attesting to a disappointing reality: ?Office/lab space to rent,? ?Office space for lease,? ?Build to Suit.? And there are political signs for candidates who decry the state of the economy. Some promise tax cuts. Others propose casinos. But like the voters in the struggling towns nearby, most of the candidates seem blissfully unaware of what could have been ? and almost certainly should have been ? built there.

Peter Canellos is the editorial page editor of The Boston Globe.

Here's my opinion:

1) The writer seems to be advocating the development of Corporate Anywhereville, Exurbia. Meanwhile, the DC area has been struggling and not easily succeeding at turning these airport-convenient office parks into cities. Isn't this a development we should feel lucky to have missed?

2) Companies located in Boston and Cambridge have always had very easy airport access - one of the best in the country. Would we have preferred these companies to have relocated to Fort Devons?

3) Given the convenient location of Logan already, wouldn't more density and expanded public transportation in the city itself (and out to Lynn and elsewhere) be a better option than runway-centric office parks out by 495?

4) No mention of Providence, Worcester, Manchester... hmm...?
 
I read it.

I agree that Boston could use a new airport. Logan has narrowly been on the brink of overcapacity for some time now and the outdated form of small, individual terminals is starting to show cracks in the armor (for instance, the headache Massport is dealing with trying to be complacent to it's new largest - and growing - airline, jetBlue, and finding appropriate space for the newly-merged United/Continental). A clean slate would be good for all.

However, I would say that Logan would have to close. Washington's airports (IAD and DCA) combined have over 40 million passengers a year, largely due to United's hub operation at Dulles. Prior to United opening a hub, Dulles was largely a ghost town due to the fact that many in the Federal Government lobbied to keep National open, albeit with a distance perimeter (today, 1,250 mi).

The road is littered with under-utilized airports that opened in concurrence with an existing airport. Milan is one such example. Traditionally, all flights went to Milan-Linate. More recently, Malpensa airport opened and Linate was closed to long-haul traffic. Later on, the Italian government then forced all European airlines to Malpensa whilst allowing Italian airlines (notably Alitalia) to remain. The case was brought before the European competition bureau (or whatever its called) they ruled in favour of the foreign airlines and now most European airlines offer service to both airports. Now, Milan was largely abandoned by Alitalia after they nearly went insolvent and the Italian government forced them to focus their operations in Rome, despite Milan being the business hub of the country, today leaving Malpensa vastly under-utilized.

Montreal is another. The Trudeau government, in an attempt to do something with the truckloads of money the government was putting into Quebec to stave off the growing independence movement, built Mirabel airport about 30 miles outside downtown Montreal. However, instead of closing the more central Dorval airport, both were kept open, Mirabel for international flights, and Dorval for domestic and US flights. However, Mirabel was built at a time when Montreal's star was falling as business moved to Toronto and when planes were built with longer range and were now overflying Montreal on their way to places like Chicago. Mirabel is now closed to all but cargo airlines and test flights at the Bombardier factory and the futuristic terminal has been turned into an indoor water park and entertainment complex.

Therefore, I'd say that to spare a hypothetical new airport the same pain of being seen as nothing but a white elephant, Logan should be closed and the land redeveloped (imagine what we could do with 2,800 acres located directly across from downtown with excellent transit and highway links). The caveat being, however, that high-speed (and I mean REAL high-speed) rail links should be built since it's a non-starter even considering closing Logan if realistic ground options don't exist between Boston and the rest of the Northeast Corridor.

However, many would disagree, and I will happily admit that one of Boston's greatest assets is that there is an international airport located as close to the city's CBD as possible with air links to most major cities in North America and Europe. However, I ask those people how they expect the airport to grow to accommodate new services to Asia and the Middle East (Emirates is growing at rapid-fire speed, it's only a matter of time before they start flying to Logan)? Furthermore, look at newer airports around the globe. The facilities offered at Logan are now worse than in many places we consider to be second or even third-world.

In summary, I wouldn't say that Boston, and New England, "missed out" on anything because we didn't build an airport surrounded by industrial wasteland and office parks. I do think we need to start looking at the possibility of life beyond Logan. I do think that we are screwing ourselves when we let opportunities like Fort Devens and NAS South Weymouth come up and not even entertain the idea that someday in the future we might need them. But, who knows. Maybe in 30 years we'll have new innovations that will allow Logan to still function competitively.
 
There are some differences between Boston and DC that need to be taken into account.

-Reagan airport is very small and only serves a small fraction of the DC air market.
it is more comparable to T.F. green in size and passenger boardings.

-Dulles is DC's main airport.(still less boardings than Logan, but it fills the role)

-Their situation is more conducive to growth far outside of the city, which is what they want since DC itself is maxed out with its building height limitations.

-DC's future is in its suburbs and exurbs. I don't think that's what we want. I would much rather see an extremely dense developed city. I've been there many times, and I guarantee no one here would want such a situation. Think, wealthy towns with good schools that somehow actually look pretty trashy.


That said, I do have to admit that their level of development if far outpacing us. I would like to see the same level of growth here, but it is going to take adjusting to some harsh realities:

1) A new or expanded airport will need to built in or close to the city in order to facilitate new growth. Location is going to be very difficult to determine which is basically the entire problem. I suggest building further out into the harbor, or converting the Providence Line to Rapid transit.
2) We will need to expand our CBD. I suggest rapidly developing Roxbury into another downtown given its proximity.
 
Wow I am surprised I had never heard of this before.

I think your skepticism is spot on. The author seems to think that any growth is good growth. Aerotropoli are by nature unsustainable cities which exist solely on a supply of cheap oil. While this type of growth my be a boost to the economy today, will it still be relevant in 25 years?

I don't think it is worth while to debate whether building an airport would have boosted the economy of the state since there are far too many factors which the author didn't address. Though, I do think it would have helped, it just would have added to the sprawl.

This reminds me of another, historical, infrastructure battle: to expand the port. The entire South Boston Waterfront was filled in because Boston saw its trade dwindling to New York. They figured huge new port would do the trick. When the new port opened trade still crept lower and the port lay empty of development. Their answer? Build a BIGGER port across the harbor in East Boston. This port was under construction will into the 1920s when someone realized that building a new port wasn't going to solve Boston's economic problems. They built Logan on the port grounds instead.

The point is that maybe we dodged another boondoggle. Imagine how much that airport would have cost? Do you think the State could have carried that and the Big Dig?
 
I think Dukakis had it right. The goal should be no flights between Boston and New York. True high speed rail would eliminate that need and open up plenty of additional flight slots for longer distance traffic.
 
I think your conclusions are spot on Shepard. I love that the author implies that Northern Virginia's growth was entirely at the expense of Boston and all thanks to Dulles. Couldn't it be that Northern Virginia is growing because of (pick one):
1. Increased federal spending.
2. Relatively cheap land (at least historically).
3. A general trend in the population moving South for climate and quality of life reasons.
 
It seems like the writer is missing a few things.


1. Washington D.C. can accomodate two airports. Mainly due to the fact that D.C. is the capital of the U.S. We need to accomodate pols, lobbyists, tourists, etc, etc. And those two airports.

2. Boston is geographically so close together with Providence and Manchester that the Hub doesn't really need another airport in the city.
 
Boost up the Northeast Corridor rail service, it's really lacking, get that N-S rail link, continue highspeed rail up to Montreal via Manchester (via Lowell or Lawrence (via Lowell Line-Wildcat Branch-Haverhill Line).

Start boosting freight possibilities via rail and ship. Also try to divert air freight to Hanscom, Norwood, and/or Weymouth.
 
Much of the commercial growth near Dulles was fueled by contractors doing business with the Federal government, specifically defense and intelligence.

BWI airport is a similar distance from downtown Washington, and was around before Dulles. Any case study of why the area around Dulles grew, and the area around BWI did not has to look at what promoted the Dulles growth.

Another factor is that professionals with families seem to prefer living in Virginia, in part because of Virginia's extensive and high-quality system of public universities and colleges, and neither Maryland or Massachusetts compare with Virginia in that respect.
 
This article shocked me, as someone who knows a little bit about this actual plan. The MAC plan was shot down because not a single citizen living outside 128 supported it, not because of a lack of cojones on the part of politicians. These guys have constituencies, and they have to listen to them. This was more than simple NIMBY rabble-rousing.

Roughly simultaneously, the skyrocketing demand which had made Logan seem imminently obsolete flatlined after 9-11. Some of it came back (partly in the form of airlines such as JetBlue and Southwest) after the Big Dig ended, but a lot of the discontent with Logan was driven by frustration in getting there (much easier now) and a sense of impending overcrowding (which hasn't really panned out).

The solution MAC and the FAA came up with was the New England Regional Airport System Plan (NERASP), which is now about 5 years old (I interned at the FAA at the time). The basic concept was that rather than building a big airport out in the hinterlands and leave Logan as a small business-oriented field, the then-booming airports in Manchester and Providence (and theoretically in Worcester) would serve as relievers for Logan. Different segments of the region would use different airports (the Route 3 area would go to MHT, the South Shore to PVD), and the traffic would redistribute to even the demand and reduce crowding at Logan.

It is shocking to me that this article could be written without mentioning NERASP, and particularly without mentioning some of the constraints on the outlying airports in question.

First, Manchester and Providence have stopped booming. The move of SWA and JetBlue into Logan, along with the economy, have largely stunted their growth. Also, the situation with getting to Logan isn't nearly as dire as it used to be.

Second, Providence is even more hemmed in by neighbors than Logan is. They're trying to extend their runway right now, and facing tremendous local opposition and land acquisition.

Finally, these things take a long time. The days when Dulles or DFW could be built in their final form immediately are largely gone. Any project to build a second airport for Boston would have to be phased, and once the first phase was in place, opposition might well kill any plans for a second. Meanwhile, the SBW provides a great preview of what would happen to the closed Logan site. If Boston does not have the demand/financing/political intelligence to develop SBW properly, how can we expect better across the harbor in an area that's harder to reach from Downtown?

That's not even getting into the issues around whether Tyson's Corner and Chantilly are what we want out on Route 2 (which would have had to have been expanded to at least 8 lanes, obliterating large sections of Acton, Concord, Lexington, etc, a fact the article conveniently ignores). I'm assuming most people on this board see the error there.
 
This article shocked me, as someone who knows a little bit about this actual plan. The MAC plan was shot down because not a single citizen living outside 128 supported it, not because of a lack of cojones on the part of politicians. These guys have constituencies, and they have to listen to them. This was more than simple NIMBY rabble-rousing.

Roughly simultaneously, the skyrocketing demand which had made Logan seem imminently obsolete flatlined after 9-11. Some of it came back (partly in the form of airlines such as JetBlue and Southwest) after the Big Dig ended, but a lot of the discontent with Logan was driven by frustration in getting there (much easier now) and a sense of impending overcrowding (which hasn't really panned out).

The solution MAC and the FAA came up with was the New England Regional Airport System Plan (NERASP), which is now about 5 years old (I interned at the FAA at the time). The basic concept was that rather than building a big airport out in the hinterlands and leave Logan as a small business-oriented field, the then-booming airports in Manchester and Providence (and theoretically in Worcester) would serve as relievers for Logan. Different segments of the region would use different airports (the Route 3 area would go to MHT, the South Shore to PVD), and the traffic would redistribute to even the demand and reduce crowding at Logan.
As someone who was around back then, I can say you are absolutely spot on !

We can argue how best to meet the transportation needs of the Boston area. This is at least a valid discussion. But when Peter Canellos suggests that large swaths of the Massachusetts countryside be converted to concrete and asphalt just so Bobby and Suzie from somewhere else can change planes and fly on to a different somewhere else, well he really has lost all touch with what Boston is all about. (Tell me, is Peter Canellos the kind of person who would brag that the biggest industry in his neighborhood is parking lots ?)
 
Per google:

Downtown DC to National:
6.5 miles, 17-25 minutes
Downtown DC to Dulles:
29 miles, 39-55 minutes
Downtown DC to BWI:
31.1 miles, 44-55 minutes


Downtown Boston to Logan:
4 miles, 12 minutes
Downtown Boston to Manchester:
54 miles, 60 minutes
Downtown Boston to Worcester:
46 miles, 65 minutes
Downtown Boston to Providence:
59 miles, 65 minutes


So even though their airports are closer, it takes just as long to get there.

So we...

-Have more airports
-Have a more convenient downtown airport
-Lack exurban megasprawl


Sounds like a win-win-win for us


The author needs move to Dallas or something

And the fact that Worcester has around 1 flight a day shows how much demand there is for more airport space.
 
Two questions come to my mind:

Isn't Kendall Square pretty close to Logan Airport, and already attracting the kind of high-tech development that the writer wants?

And isn't the Seaport even closer to Logan, with lots of still-vacant land that can be developed this way?
 
And isn't the Seaport even closer to Logan, with lots of still-vacant land that can be developed this way?
Right.

And for that matter, DC has experienced a lot of growth in Roslyn and Crystal City, in large part due to their easy access to National (DC's equivalent to Logan). Of course, the presence of the Pentagon nearby also helps.
 
This article shocked me, as someone who knows a little bit about this actual plan.
Thanks for all the interesting incite.
I'm assuming most people on this board see the error there.

I think we all see many errors in the "thoughts" presented in the article.
 
And the regional governments in the DC area are extending the Metro subway line to Dulles at a cost of $2.5 billion (largely paid for by highway tolls in Virginia) because eight lanes of highway between Dulles and DC are congested much of the days.
 
Another thing to remember is Regan National is slot restricted and have very few slots/flight allocated for flights outside a 1,250 mile radius (and no international flights either).
 
Okay. Since building a new airport 45 miles west of Boston wouldn't work due to distance and NIMBY's, and since Logan Airport is over capacity, and since South Weymouth is no longer an option, how about constructing an off-shore airport. A good location would be east of the Deer Island Water Treatment Plant, on Winthrop Island, in Massachusetts Bay. The airport would be modeled on Hong Kong Airport and Oslo Airport, with a large capacity and 24-hour operations. A connection would be made with the Ted Williams Tunnel, which would require all the skills of Arup to make it happen, as well as a subway and rail connection. All in all, it would be a good replacement. If anyone has doubts, just remember that New Doha Airport is being built 5km away from the old one. Discuss.
 
That is even less feasible for so many reasons, most of all that I doubt the traffic through the new airport would justify the extreme cost.

I still don't think that building a large new airport is even warranted. All I see in the future is rising fuel prices and fewer flyers. We should be more efficient with the infrastructure and technology we have, not continually building bigger, more environmentally damaging projects.
 

Back
Top