#686 2006 · NASA · Aerospace / government contracting
NASA stopped paying contractors for their costs and started paying them only for what actually worked
the problem
Cost-plus contracts pay a spacecraft developer for overruns, not for success
background
Since the Shuttle era, NASA had developed vehicles mostly through traditional cost-plus contracts: the government pays a contractor's costs plus a guaranteed margin, whether or not the vehicle flies on time or on budget. That structure removes the contractor's own financial stake in staying on budget, and it shows in NASA's own numbers — its historical cost model, built entirely from decades of cost-plus programs, predicted $1.7 to $4 billion just to develop a rocket in the Falcon 9 class. After the 2003 Columbia disaster and the decision to retire the Shuttle, NASA needed to get cargo, and eventually crew, to the space station without either flying aging hardware indefinitely or committing to another decade-long, multibillion-dollar traditional program for every new vehicle.
The obvious fix — a normal Federal Acquisition Regulation contract with tighter cost controls and better contractor selection — leaves the underlying problem untouched: a cost-plus contractor is still paid the same whether it comes in on budget or triples it, and the FAR's own compliance and reporting requirements add real cost independent of how hard the actual engineering problem is.
what everyone would do
The standard fix for a contractor blowing through budget and schedule is tighter management — more oversight, more reporting, harsher penalty clauses bolted onto the same cost-plus structure. NASA had this entire toolkit already, and its own historical cost model, built from decades of cost-plus programs, still predicted $1.7 to $4 billion just to develop one new rocket, because none of those fixes touch the part of the contract that removes a contractor's own financial stake in staying on budget.
what they saw
The problem was never that NASA needed better visibility into a contractor's costs — it was that paying for costs at all removes the contractor's incentive to control them. Using a decades-old legal authority, the 1958 Space Act's power to enter "other transactions" outside the Federal Acquisition Regulation, that had mostly sat unused for this purpose, NASA stopped funding the WORK and started funding the RESULT: pay only when an objectively verifiable milestone is hit, and let the company itself absorb whatever it actually costs to get there.
the move
Using authority Congress had granted NASA back in the 1958 Space Act to enter into "other transactions" outside the FAR, NASA structured its 2006 Commercial Orbital Transportation Services (COTS) program around funded Space Act Agreements: fixed-price, milestone-based payments, where a company — SpaceX, and later Orbital Sciences — was paid a pre-agreed sum only when it hit a specific, objectively verifiable technical milestone, such as a successful engine test or demonstration flight. NASA supplied technical expertise and data but did not manage the contractor's internal costs or process, and each company bore any cost overrun itself.
why it works
A milestone-based Space Act Agreement gives a contractor exactly the outcome NASA wants and none of the outcomes it doesn't: hit the milestone and collect a fixed sum regardless of how cheaply you got there, keeping any underrun as profit; miss it and absorb the overrun yourself. That is what pushes a contractor to optimize for actual cost control instead of defensible cost reporting. NASA's own cost-assessment data shows the scale of the effect: SpaceX's real Falcon 9 development cost roughly $300 million against NASA's own cost-plus-based model predicting $1.7 to $4 billion for an equivalent vehicle, and the full COTS cargo program landed at roughly a tenth the estimated cost of the traditional-contract equivalent.
the payoff
NASA's own cost-assessment data (Edgar Zapata, NASA Kennedy Space Center, 2017) puts SpaceX's actual Falcon 9 development cost at roughly $300 million, against NASA's own cost-plus-based model predicting $1.7 to $4 billion for an equivalent vehicle developed the traditional way. Across the full COTS cargo program, NASA's total investment of roughly $953 million delivered two new launch vehicles and two cargo spacecraft, versus an estimated $3,977 million for the traditional-contract equivalent — about a tenth of the cost.
where it breaks
Fixed-price milestones only work when the funder can define a milestone that is genuinely objective and hard to satisfy on paper without the underlying capability actually existing — GAO's own review of NASA's funded Space Act agreements found the basic controls generally sufficient but flagged specific gaps worth strengthening. The structure also depends on the partner having enough of its own capital or investor backing to absorb a real overrun; a company without that cushion can't safely take on cost risk the funder has fully shifted onto it, which is why NASA paid out in stages tied to a sequence of milestones rather than the full sum at the very end.
what came after
COTS became the template for NASA's Commercial Crew Program, which carried NASA astronauts to the space station on a SpaceX vehicle, and more broadly established fixed-price milestone Space Act Agreements as NASA's standard tool for stimulating a competitive commercial launch industry rather than owning and operating vehicles itself. A 2011 GAO review of NASA's funded Space Act agreements found the agency's basic controls for managing them generally sufficient, while flagging specific gaps worth strengthening and clarifying.
references
- [1]An Assessment of Cost Improvements in the NASA COTS/CRS Program and Implications for Future NASA MissionsNASA (Edgar Zapata, Kennedy Space Center) / AIAA Space 2017 Forum, 2017ntrs.nasa.gov
- [2]GAO-12-230R: Key Controls NASA Employs to Guide Use and Management of Funded Space Act Agreements Are Generally Sufficient, but Some Could Be Strengthened and ClarifiedU.S. Government Accountability Office, 2011gao.gov