Key Takeaways
Treat aircraft leadership as temporary: the market rewards timing, not crowns
The lead keeps moving. In 1990, Boeing held 62 percent of the market, McDonnell Douglas 23 percent, and Airbus 15 percent. By 2004 and 2005, Airbus was outselling Boeing. The book’s central argument is that neither company can secure permanent dominance: an airplane takes years to develop and may serve airlines for decades, while demand, fuel costs, and route patterns keep changing.
Bad timing compounds mistakes. Lockheed’s admired L-1011 lost $2.5 billion before production ended in 1981. McDonnell Douglas, meanwhile, chose a three-engine rival to the L-1011 instead of building the smaller twin-engine wide-body that became Airbus’s A300. Both American manufacturers withdrew from commercial aircraft. A product can be technically impressive and still arrive at the wrong moment, at the wrong cost, or in the wrong size.
The industry resembles a long-cycle investment market: decisions are made under uncertainty, but the consequences last far longer than a typical business plan. That makes humility a strategic asset, not a personality preference. Forecasts can guide investment, but they cannot turn an uncertain future into a known one. The comparison between the L-1011 and A300 also shows why engineering quality alone is insufficient. Still, timing should not become an excuse for every failure. Product choices, costs, and management decisions shape whether a company can survive the bad luck that no forecast can eliminate.
Keep engineers, customers, and service close to the people making decisions
Leadership changes the company’s instincts. Boeing’s T. Wilson and Airbus’s Jean Pierson understood factories as well as customers. Wilson once visited a Boston transit authority after Boeing-built trams failed repeatedly. He offered to repair them or return roughly $45 million rather than let a bad product damage Boeing’s name. That response reflected a leader willing to take responsibility and protect the company’s long-term reputation.
Airbus built customer credibility. Under Pierson, it invested in product support and created an American operation staffed by local employees. Its sales team learned that winning an order meant more than presenting a capable aircraft. Airlines needed fast answers, reliable service, and people who understood their market. Boeing’s increasingly layered, Seattle-centered organization often made those answers harder to get, even as customers complained.
This is a case for proximity between information and authority. Organizational research often describes this as reducing the distance between frontline knowledge and decision-making. In aircraft manufacturing, that distance matters because a late technical correction or a poorly handled customer concern can become costly across a long production program. Wilson’s tram response also illustrates reputational investment: the immediate financial loss can protect future trust. Yet heroic leaders are not a durable operating system. Their habits matter most when companies translate them into routines that remain after the leader leaves.
Build for how people travel, not for the biggest headline
Two aircraft, two forecasts. Airbus’s A380 was designed for hub-to-hub travel: carry as many as 550 passengers between major airports, then connect them to smaller destinations. Boeing’s 787 was designed for more direct routes, carrying roughly half as many people without requiring a stop at a hub. Boeing argued that travelers increasingly valued direct journeys; Airbus argued that crowded airports would need larger aircraft to move more people with fewer flights.
The bet carried consequences. Airbus expected the A380 to cost less per seat to operate than a 747, but production problems delayed deliveries. In 2006, a wiring installation problem, involving roughly 310 miles of wiring, prompted another six-to-seven-month delay and an estimated $625 million annual reduction in operating income from 2007 through 2010. The book presents the competing market forecasts as uncertain, not settled facts.
The contrast is a lesson in designing around systems, not isolated products. An aircraft’s value depends on airport capacity, connecting networks, passenger preferences, and airline schedules. This resembles infrastructure planning, where a locally efficient solution can create congestion elsewhere in the network. The A380’s case was not irrational: larger aircraft may help when airport slots are scarce and demand clusters at particular times. But that advantage depends on enough passengers wanting the same routes at the same times. A bold engineering achievement is not automatically a good match for a distributed, changing travel market.
A successful airplane becomes a trap when leaders stop improving it
Airbus entered through a gap. Its A320 brought fly-by-wire controls, a computer-based system that sends commands to an aircraft’s control surfaces, and a cockpit shared across Airbus models. Airlines valued this commonality because pilots and mechanics could move more easily among aircraft in the same family. The A320 helped Airbus win American customers, then supported its expansion into larger models.
Boeing protected an aging advantage. Rather than replace the 1960s-era 737 with a clean-sheet design, Boeing updated it with the 737 Next Generation. The derivative sold well, but its success helped delay a more fundamental response to Airbus. Airbus later used the A330-200 to seize Boeing’s profitable middle market. The 777 was a strong counterattack, but Boeing’s broader reluctance to launch new aircraft gave Airbus time to build a fuller product line.
This is the tension between exploiting an existing asset and exploring a new one. Exploitation protects cash flow and uses proven production knowledge. Exploration risks large sums on a product that may fail, but can prevent a rival from redefining the market. The mistake is not choosing derivatives; a derivative can be the right, lower-risk answer. The danger is treating success as proof that the underlying design will remain competitive. A useful test is whether customers are buying the refreshed product because it is genuinely best for them, or because the supplier has postponed the next hard decision.
Airlines that chase market share often buy growth with insolvency
More passengers did not mean more profit. After U.S. airline deregulation in 1978, carriers expanded routes, hubs, and fleets, often without retiring older aircraft. In 1990 and 1991, the industry lost $7 billion while carrying $75 billion in debt. The book argues that many airlines treated market share as the goal, even when winning it meant selling tickets below cost and buying more capacity than the business could support.
Southwest built a different machine. It prioritized low operating costs over size, flew one aircraft type, and emphasized quick turnarounds and direct routes. Its employees could help across job boundaries, unlike legacy carriers with restrictive work rules. JetBlue borrowed parts of this approach but added reserved seats and in-flight television. The distinction is coherence: a low fare works when aircraft, staffing, routes, and service fit together, not when an old airline simply adds a discount brand.
Southwest illustrates a principle from operations strategy: the parts of a business model reinforce one another. A single fleet simplifies training and maintenance; flexible work practices can speed aircraft turnaround; frequent, direct service supports the low-cost promise. Copying one visible feature, such as cheaper tickets, does not reproduce that system. The book’s sharp critique of airline expansion also needs a boundary: market share can matter when it creates durable network advantages or bargaining power. The mistake is pursuing share without a credible account of how it will produce returns after the discounts and added capacity are paid for.
In aircraft sales, customer trust can beat a familiar logo
Every order is a campaign. Aircraft deals involve years of evaluation, technical comparisons, and negotiations over price, service, and delivery. In 1998, British Airways compared an Airbus A319 and a Boeing 737 in person. The Airbus team let the airline’s executives inspect the cabin with flight attendants explaining its practical features. JetBlue, expected to buy Boeing aircraft, chose Airbus after finding the A320 better suited to its needs and after feeling Boeing had not taken its early proposal seriously.
Relationships must be maintained. Airbus worked with Air Berlin for more than eighteen months before securing an order after Boeing assumed the carrier would stay loyal. Price mattered, but so did the customer’s sense of urgency and respect. The engine business adds another layer: manufacturers may discount an engine heavily, then earn substantial revenue from maintenance and spare parts over its life.
These episodes show that business-to-business sales are not just persuasion; they are a test of how well a supplier listens, responds, and reduces the buyer’s risk. A familiar brand may reassure a customer, but a neglected customer has reason to reconsider. The engine example also exposes a lifecycle pricing model: an initial sale can be strategically valuable even when its margin is thin, because service and parts create later revenue. That model complicates simple comparisons of list prices. At the same time, a successful sales team cannot rescue a weak product indefinitely. Trust earns a fair evaluation; performance must justify the purchase.
Subsidy arguments distract from the harder test of building what sells
Both sides had government support. A 1992 U.S.-European agreement limited public financing of a new aircraft to 33 percent of development costs and restricted production subsidies. Airbus received direct development loans, often called launch aid. Boeing, in turn, benefited from government-funded research, military programs, and support linked to Japanese suppliers on the 787. Each side emphasized the other’s advantages and minimized its own.
The dispute became a strategic distraction. Boeing challenged the agreement in 2004, and both sides filed complaints with the World Trade Organization. The book argues that the fight risked retaliation and higher costs while doing little to address Boeing’s product and sales shortcomings. It does not claim support was irrelevant: public financing can change who bears the risk of a failed program. Its point is that Airbus’s rise and Boeing’s decline were also driven by product choices, manufacturing costs, and customer relationships.
The subsidy dispute is a classic problem of competing definitions. Direct loans are visible, while research spending, defense spillovers, tax provisions, and supplier financing are harder to compare. A single fairness test can therefore become a contest over which forms of support count. This does not make the underlying policy question trivial: subsidies can sustain capabilities that private investors would not finance, but they can also blunt incentives to stop a failing project. The strongest analysis separates three questions: what support exists, what it changes, and whether the resulting aircraft serves customers better than its rival.
Outsource production carefully, because outsourced work can become outsourced expertise
Boeing changed its role. For the 787, it planned to source about 70 percent of the aircraft’s parts from outside the United States and act primarily as a systems integrator, coordinating suppliers’ work and assembling the result. Japanese companies took major responsibility for the wing and other structures, with government-backed financing helping share development risk. The strategy was a sharp departure for a company proud of designing and building wings itself.
The savings were not self-evident. Japan was not a low-wage production base, and the book questions whether outsourcing saved Boeing much money. Engineers warned that suppliers could accumulate the practical knowledge needed to design and manufacture advanced composite structures, while Boeing’s own teams lost experience. That matters beyond the factory: the aircraft maker remains responsible for integrating components, meeting performance promises, and supporting aircraft for decades.
Outsourcing creates a transaction-cost question: can contracts coordinate work that depends on tacit knowledge, constant adjustment, and shared problem-solving? In a simple component purchase, specifications may be enough. In a novel aircraft structure, knowledge develops through repeated design and manufacturing decisions, so the boundary between supplier and integrator can shift over time. Risk-sharing can preserve cash and open markets, but it may also transfer bargaining power to partners that become indispensable. The right measure is not the percentage built in-house. It is whether the lead firm retains enough technical understanding to integrate, troubleshoot, and improve the system.
Give complex aircraft programs clear authority, or politics will run production
Boeing’s problems were organizational, too. In 1997, aggressive production increases, labor shortages, supplier delays, and weak cost control overwhelmed Boeing’s factories. The company halted production of the 737 and 747 for about three weeks and recorded a $2.6 billion charge. Its 1997 merger with McDonnell Douglas brought defense capabilities, but also a cultural shift that many Boeing employees believed weakened the commercial aircraft business.
Airbus faced a different governance problem. Its French-German parent structure divided top authority between national leaders. By 2006, political maneuvering and divided management were entangled with A380 production troubles. The book’s warning is practical: a complex multinational project needs decision-makers who can resolve problems quickly and accept responsibility. National balance may protect political support, but when every major decision must preserve that balance, commercial judgment can become slower and less clear.
Large engineering programs are coordination problems as much as technical ones. They require clear ownership of interfaces, quick escalation of bad news, and authority to reallocate people and money. Boeing’s production collapse shows the cost of setting ambitious output targets without reliable visibility into factory capacity. Airbus’s dual leadership shows a different hazard: governance designed to distribute power can make accountability diffuse. Neither case proves that centralization is always superior. Distributed expertise and national participation can add resources and legitimacy. The challenge is to preserve those benefits while making one role unmistakably responsible for operational outcomes.
Analysis
Newhouse tells the Boeing-Airbus rivalry as a sequence of reversals rather than a victory story. The contest is shaped by product design, but also by decisions that are easier to miss: whether senior leaders hear from airline customers, whether factories can meet promised delivery schedules, whether sales teams can negotiate without alienating buyers, and whether a company keeps the expertise needed to understand its own aircraft. The rivalry’s most useful lesson is that competitive advantage is not a possession. It is a temporary fit between a company’s capabilities and a market that keeps changing.
The book’s strongest comparisons are concrete. Airbus gained credibility with the A320 while Boeing kept refining the 737. Boeing later answered with the 787, while Airbus tied up engineering resources in the A380 and struggled to define a competitive midsize response. These episodes illustrate path dependence: past success creates production knowledge and cash, but it can also make replacement seem needlessly risky. The same history helps explain why subsidies alone cannot account for the companies’ fortunes. Public financing changes the risk of investment, but it cannot guarantee that airlines want the resulting airplane or that the manufacturer can deliver it reliably.
The account also resists a clean national stereotype. Airbus benefited from European state support, yet became an effective commercial competitor. Boeing possessed deep technical talent, yet organizational caution, production failures, and management choices weakened its position. At the same time, the narrative draws heavily on interviews with people close to the firms and often reports disputed interpretations. Its forecasts about the A380, the 787, and future Asian competition should therefore be read as judgments made around 2006, not as timeless verdicts. The durable insight is less about which aircraft won a particular cycle than about how difficult it is to align engineering, governance, finance, and customer demand over a decades-long product life.
Review Summary
Boeing Versus Airbus receives mixed reviews, with an average rating of 3.63/5. Readers appreciate the detailed industry insights and historical context but criticize the book's organization and lack of technical details. Some find it informative and well-researched, while others consider it repetitive and biased. The book is praised for its analysis of the companies' rivalry and management styles, but criticized for its dated information and occasional lack of focus. Overall, it's recommended for aviation enthusiasts and business readers interested in the commercial aircraft industry.
People Also Read
Glossary
commonalty
shared aircraft featuresCommonalty is the use of shared design features across a family of aircraft, especially similar cockpits and operating systems. Airlines value it because pilots, mechanics, and other staff can work across related models with less retraining and fewer separate procedures. Airbus used commonality across its aircraft families as a selling point and a way to reduce operating complexity.
launch aid
government aircraft-development financingLaunch aid is government financing for the development of a new aircraft program. In the arrangement described in the book, repayment depends on whether the airplane is produced and sells successfully, so some of the investment risk shifts from the manufacturer to public funders. Boeing and Airbus disputed whether this form of support gave Airbus an unfair advantage.
systems integrator
coordinator of complex suppliersA systems integrator coordinates components and systems made by multiple suppliers and combines them into a functioning product. Boeing used the term to describe its planned role on the 787, where outside partners designed and built major structures while Boeing coordinated the overall aircraft. The role requires enough technical knowledge to ensure that separate parts work together safely and meet performance requirements.
risk-sharing partner
supplier sharing program costsA risk-sharing partner contributes investment and takes responsibility for a substantial part of an aircraft program, rather than simply selling parts to the manufacturer. In return, the partner may receive an agreed share of revenue if the aircraft sells. Boeing used this model with major suppliers on the 787 to distribute development costs and financial risk.
learning curve
costs fall with production experienceThe learning curve describes how production becomes faster and less costly as workers and suppliers gain experience making a product. Early units may involve mistakes, delays, and expensive adjustments; repeated production improves skill and process reliability. The effect is especially important in aircraft manufacturing because each unit is costly and production volumes are relatively low.
program accounting
spreading aircraft costs over productionProgram accounting is an aircraft-industry method that allocates large development and production costs across an expected number of aircraft and years. It can make the financial results of an early production period look different from the immediate cash costs of building each plane. In the Boeing production crisis, critics argued that this flexibility could obscure overruns and weak cost estimates.
offset
sales tied to local industrial workAn offset is an arrangement in which an aircraft sale is linked to work or investment in the buyer’s country. A manufacturer may source components locally or involve domestic firms to support a large purchase. The book describes Boeing’s long-standing ties with Japanese suppliers and later Chinese production work as ways to support market access and local industrial participation.
Iron Triangle
defense contractor-government allianceThe Iron Triangle refers to the mutually reinforcing relationships among defense contractors, government agencies, and political actors. These relationships can facilitate procurement and support employment or industrial capacity, but they can also weaken independent oversight. The Boeing tanker controversy illustrates the danger when a contractor and government officials shape requirements and financing without adequate checks.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.