Airframe Engine Lock-In

Airframe engine lock-in is the aviation-system dependency in Vol.268 两个劳斯莱斯 where an aircraft and engine become so tightly co-designed that replacing one supplier is not a simple procurement change. The source’s case is [[LockheedL1011TriStar|Lockheed L-1011 TriStar]] and [[RollsRoyceRB211|RB211]].

The episode argues that [[LockheedCorporation|Lockheed]] could not cleanly switch from RB211 to another engine after delays emerged because the TriStar’s design, performance promise, and certification path had already been built around that engine. Contract penalties therefore did not fully protect Lockheed: the aircraft maker and engine maker were commercially separate but technically bound.

Key Claims

• In aircraft programs, a subsystem supplier can become part of the product architecture rather than a replaceable vendor.
• Contract language can allocate liability, but it cannot instantly decouple engineering work already embedded in the airframe.
• Lock-in can make an upstream supplier crisis become a downstream market-entry crisis.
• The source’s lesson is system-level: technical integration changes bargaining power after the contract is signed.

Connections

• [[LockheedL1011TriStar|L-1011 TriStar]], [[RollsRoyceRB211|RB211]], [[LockheedCorporation|Lockheed]], and [[RollsRoyce|Rolls-Royce]] - source case.
• Fixed Price Engineering Risk - contract risk intensified by technical dependency.
• [[McDonnellDouglasDC10|McDonnell Douglas DC-10]] and Boeing - competitive context where delays mattered.
• Constraint Driven Engineering Strategy - adjacent concept for how engineering constraints can reshape strategy.