Regulators may add conditions to US Airways-American merger
For much of his 36 years in Congress, former U.S. Rep. James Oberstar kept a close eye on the nation's airline industry. Often, he didn't like what he saw, particularly as the number of players kept shrinking through mergers.
For a number of reasons, he hopes that Congress and the Justice Department take a close look at the proposed merger of American Airlines Inc. and US Airways Inc.
"The real victim in this process is the traveling public," said the Minnesota Democrat, who lost his bid for a 19th term in the 2010 elections. "The reduction of choices, the increasing power of the fortress hub makes it unlikely that other carriers would enter those markets where both American and US Airways serve, because they'll be competing with a much bigger presence, with more power to serve those markets."
Despite his misgivings, the chances of the deal being blocked appear minimal, particularly on the heels of four mergers of major carriers since 2005: US Airways and America West Airlines Inc. in 2005, Delta Air Lines Inc. and Northwest Airlines Inc. in 2008, Continental Airlines Inc. and United Airlines Inc. in 2010, and Southwest Airlines Co. and AirTran Airways Inc. in 2011.
But regulators may put conditions on the sale if they decide the two carriers have too much market share on certain routes or at certain airports.
A particular point of interest for regulators will be the airports where the federal government limits the number of takeoffs and landings permitted by the carriers.
In past cases, regulators have required airlines to give up slots to create more competition.
That's how Southwest got a foothold at the Newark airport in 2011. Regulators pushed Continental to lease the Dallas-based carrier sufficient slots to begin service at Newark and operate 18 departures a day.
Similarly, in 2010, the Department of Transportation conditioned its approval of an American-British Airways PLC alliance with a requirement that they surrender a handful of slots at London Heathrow Airport to permit other U.S. airlines to compete with them.
If regulatory eyebrows are raised anywhere, it's most likely to be at Ronald Reagan Washington National Airport, where US Airways has a clear lead in market share with its mainline flights and an even bigger lead with its commuter partners included.
US Airways' mainline flights handled 18.5 percent of Washington's passengers in 2012. And combined with US Airways Express flights offered by three regional carriers, the airline carried more than double that number.
Delta and American each carried just under 12 percent of National's passengers, but American's share climbed to nearly 15 percent if American Eagle flights were included.
Add the mainline and regional partners together, and US Airways and American would have around half of Washington's passengers.
When the two airlines announced their merger on Feb. 14, US Airways chairman and chief executive Doug Parker played down potential problems.
"Adding American to US Airways' current operation at (Washington National) doesn't, we believe, raise anything that should remotely concern the Department of Justice," Parker told reporters. "But we'll see."
In contrast with their market share at Washington National, the combined American and US Airways would still trail Delta at New York LaGuardia, another airport where the government apportions takeoff and landing slots. Delta carried 36.3 percent of LaGuardia's passengers in 2012, to 19.7 percent for American and 12.7 percent for US Airways.
Show commenting policy
TribLive commenting policy
You are solely responsible for your comments and by using TribLive.com you agree to our Terms of Service.
We moderate comments. Our goal is to provide substantive commentary for a general readership. By screening submissions, we provide a space where readers can share intelligent and informed commentary that enhances the quality of our news and information.
While most comments will be posted if they are on-topic and not abusive, moderating decisions are subjective. We will make them as carefully and consistently as we can. Because of the volume of reader comments, we cannot review individual moderation decisions with readers.
We value thoughtful comments representing a range of views that make their point quickly and politely. We make an effort to protect discussions from repeated comments either by the same reader or different readers.
We follow the same standards for taste as the daily newspaper. A few things we won't tolerate: personal attacks, obscenity, vulgarity, profanity (including expletives and letters followed by dashes), commercial promotion, impersonations, incoherence, proselytizing and SHOUTING. Don't include URLs to Web sites.
We do not edit comments. They are either approved or deleted. We reserve the right to edit a comment that is quoted or excerpted in an article. In this case, we may fix spelling and punctuation.
We welcome strong opinions and criticism of our work, but we don't want comments to become bogged down with discussions of our policies and we will moderate accordingly.
We appreciate it when readers and people quoted in articles or blog posts point out errors of fact or emphasis and will investigate all assertions. But these suggestions should be sent via e-mail. To avoid distracting other readers, we won't publish comments that suggest a correction. Instead, corrections will be made in a blog post or in an article.
- Corporate missteps hurt reputations, profits, sometimes in long run
- Farmers fund research on gluten-free wheat
- Heinz merging with Kraft in mega-deal; headquarters to stay in Pittsburgh
- Increased credit card use reflects confidence, flat wages
- If you get this letter from the IRS, it’s legitimate
- Home appraisal is below sales price — now what?
- Stop foreign dumping, U.S. Steel CEO Longhi tells Congress
- U.S. Steel to idle Illinois plant, shed up to 2,080 more workers
- Komando: Boost cellphone signal when nixing landline
- Tourists rush to visit Cuba before American influence felt
- Highmark delays payment to UPMC over in-network issue