How Leaded Gas Became a Known Poison on Its First Day and What It Teaches Modern Tech

In early 1921 General Motors engineers mixed tetraethyl lead (TEL) into gasoline to solve engine knocking, and the additive was marketed as “Ethyl” gas. Within weeks the first tank of leaded gasoline was sold, even though a Du Pont executive had described TEL in 1922 as a “very poisonous” liquid that could cause immediate lead poisoning through skin contact. By 1924 a series of workplace disasters at GM and DuPont plants exposed workers to lethal doses, resulting in dozens of severe illnesses and multiple deaths. The industry downplayed the hazards for profit, and the poison lingered in the air, soil, and water for a generation. Understanding this timeline matters for any builder who balances innovation with public safety.

What happened

The breakthrough came on December 9, 1921, when Thomas Midgley Jr. and his GM team demonstrated that TEL raised octane and eliminated engine knock. The same day, a Du Pont executive warned that the compound was “very poisonous if absorbed through the skin.” Despite the warning, GM rushed the additive to market, branding the fuel “Ethyl.”

In February 1923 the first public filling station sold leaded gasoline, while Midgley himself was already suffering from lead exposure. Within a year, public backlash grew as reports of worker illnesses surfaced. In October 1924, a refinery in Bayway, New Jersey, saw two dozen employees develop severe lead poisoning, six of whom died, and similar incidents occurred at other plants.

The industry’s response was defensive. Standard Oil’s spokesperson claimed ignorance and advised the press that “nothing ought to be said about this matter in the public interest.” It would take decades of epidemiological research before the full health toll—cognitive deficits, cardiovascular disease, and environmental contamination—was acknowledged.

Why it matters

The leaded‑gas saga illustrates how technical solutions can mask long‑term public‑health costs when profit incentives dominate. Modern developers and builders face analogous dilemmas with data privacy, AI bias, and hardware sustainability. Ignoring early warnings can embed systemic risks that persist for generations, eroding trust and creating costly remediation later. The story also shows the power of whistleblowers, journalists, and regulators in surfacing hidden harms.

How to think about it

When evaluating a new technology, map out three layers: immediate functional benefit, known hazards (even if they seem minor), and long‑term systemic impact. Require independent safety reviews before scaling, and embed transparent reporting mechanisms for any adverse effects. Treat early dissenting voices as data points, not noise, and build contingency plans that can be activated if hidden risks emerge.

FAQ