Subjects and lessons to explore.

Law

Engineering Fundamentals · Engineering Practice

Engineering Ethics

13 min read 5 practice questions
8 key termsSourcesReport an error
Want it in plain words first? Jump to Eli explains — the same idea, no jargon.
On this page 9 sections
  1. In 30 seconds
  2. Why this matters
  3. The college version
  4. Eli explains
  5. Worked example
  6. Key takeaway
  7. Quick check
  8. Study tools
  9. Sources & references

In 30 seconds

Engineering codes of ethics are built on one ordering: the safety, health, and welfare of the public comes before your obligations to your client and your employer. Around that sit duties of competence, truthful reporting, disclosed conflicts, bounded confidentiality, and sustainability. The rule is easy to state. The difficulty is acting on it when the pressure to stay quiet is coming from inside your own organization, on a schedule, from people who sign your reviews.

Why this matters

Every engineering course you take assumes someone will act responsibly with the result. Ethics is where that assumption gets examined. Academically, it is the frame that connects design decisions to consequences, and it is examined content on the professional licensing path. Practically, engineers are the people who see a problem first and often the only people who understand it, which is why codes give them an affirmative duty rather than permission to stay silent. Looking forward, the cases keep arriving in new forms — emissions software, autonomous systems, models nobody can fully inspect — and the question is always the same one: what do you do when what you know collides with what the organization wants to hear?

The college version

The ordering that organizes everything else

The NSPE Code of Ethics for Engineers opens its Fundamental Canons by directing engineers to "hold paramount" the safety, health, and welfare of the public. A later canon directs them to act for each employer or client as "faithful agents or trustees." Both duties are real and usually point the same way; the code's ordering settles what happens when they do not. The ASCE code makes the same move more explicitly: it sorts an engineer's responsibilities under five stakeholders — society, the natural and built environment, the profession, clients and employers, and peers — states that in a conflict between ethical responsibilities the stakeholders are listed in order of priority, and singles out the duty to protect the public's health, safety, and welfare as taking precedence over every other responsibility in the code. Notice what this ordering is not. It is not a claim that clients do not matter, and it is not a license to obstruct a project you dislike. It is a tie-breaker for a narrow, serious situation: when doing what the client wants would leave the public exposed to a hazard you understand and they do not. That situation is rare across a career and decisive when it arrives. This is the , and every other duty in the codes is arranged around it.

The standing duties

Four duties surround the public-safety principle and do most of the work of keeping the collision from arising. Competence: both codes limit engineers to work they are qualified for by education or experience, and the NSPE code separately forbids signing or sealing documents in subject matter you lack competence in. This is a public-safety rule wearing ordinary clothes — most bad engineering is not malicious, it is someone out of their depth who did not say so. Truthfulness: engineers are to be objective and truthful in professional reports, statements, and testimony, and to include all relevant and pertinent information in them. The obligation is affirmative, which matters: a report can be composed entirely of true sentences and still violate it by omission. Conflicts of interest: known or potential conflicts that could influence, or appear to influence, your judgment are to be disclosed. The remedy is disclosure rather than prohibition — a conflict everyone can see is one everyone can price. Confidentiality: you do not reveal a client's or employer's confidential business affairs or technical processes without consent — but the NSPE rule carves out disclosure authorized or required by law or by the code itself, and a separate rule directs engineers who know of an alleged code violation to report it to appropriate professional bodies and, when relevant, to public authorities. ASCE likewise directs reporting misconduct where necessary to protect the public. Confidentiality is real and it is bounded; it was never designed to be the reason a hazard stays hidden. Sustainability now sits alongside these with different force in different codes: NSPE encourages adherence to the principles of sustainable development, defined in a footnote around meeting human needs while conserving environmental quality, whereas ASCE makes the natural and built environment its second-ranked stakeholder.

Ethics, law, and liability are three different things

Students routinely collapse these three, which produces bad reasoning in both directions. Legality is what a statute or regulation requires. Liability is whether a court will make you pay for harm, which usually turns on whether you met the — what a reasonably prudent engineer in the same field and circumstances would have done. Ethics is what the profession's conduct rules require of you. They overlap heavily and they are not the same set: something can be legal and unethical, and something can be ethical and still leave you liable. The ASCE code is unusually candid about this, carrying a footnote saying that the code does not establish a standard of care and should not be interpreted as one. Enforcement follows the same split. Courts award damages. Professional societies can discipline or expel a member, which affects standing but not the right to work. The body that can end an engineer's right to practice is the state licensing board — NCEES, whose members are the 69 engineering and surveying licensing boards of the states and territories, describes licensure as existing to ensure practice that protects public health, safety, and welfare, and the NSPE code itself records that state registration board rules of professional conduct remain in full force and effect. Board discipline is not theoretical. After the Hyatt Regency collapse the Missouri Board for Architects, Professional Engineers and Land Surveyors filed a complaint in February 1984; the Board revoked the certificates of the project engineer, the supervising engineer, and the firm, and the Missouri Court of Appeals affirmed in 1988. Carry the commission's working definition of gross negligence in that licensing context: an act or course of conduct demonstrating conscious indifference to a professional duty — different in kind from ordinary negligence, not merely worse in degree.

When obligation meets organizational pressure

The codes anticipate the collision and give a sequence. NSPE directs that if engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate; that they shall approve only engineering documents in conformity with applicable standards; and that they shall not complete, sign, or seal plans or specifications that do not conform to applicable engineering standards — and if the client or employer insists, shall notify the proper authorities and withdraw from the project. ASCE directs engineers to present clearly and promptly the consequences to clients and employers when engineering judgment is overruled where public health, safety, and welfare may be endangered. As a practical sequence: escalate inside the organization first, in writing; state the technical concern and its consequence rather than your discomfort; do not attach your seal to work you believe does not conform; and if the organization insists, escalate outward and step off the project. Documentation is the load-bearing element and the one most often skipped. A dated memorandum stating what you found, what you recommended, and what you were told turns a contested memory into a record — and it changes the organization's position too, which is exactly why writing it is uncomfortable. Dissent inside an organization is not disloyalty; the faithful-agent duty runs to the client's genuine interests, and no client's genuine interest includes a hazard nobody told them about. Two limits. The codes ask for escalation over resignation: quitting quietly protects your conscience and leaves the hazard in place. And none of this is advice about any particular situation — real cases turn on employment law, contracts, and jurisdiction-specific duties, and need a lawyer and your own licensing board, not a lesson.

Whistleblowing, honestly

External reporting is the end of the sequence, not the start of it, and it should be described without romance. The codes contemplate it — the NSPE confidentiality rule carves out disclosure required by law or by the code, and both codes direct reporting to appropriate authorities where public safety requires it. What the codes cannot do is protect you: U.S. legal protection for someone who reports a safety problem is a patchwork, not a general shield. OSHA's Whistleblower Protection Program administers the anti-retaliation provisions of a list of separate federal statutes — 25 as listed on the program's statutes page in August 2026 — each tied to a particular industry or subject: aviation, rail, pipelines, nuclear energy, motor vehicles, food safety, consumer products, environmental media, securities. If your concern does not land inside one of those subject areas, that list does nothing for you. The general workplace provision, section 11(c) of the Occupational Safety and Health Act, is narrow and fast-expiring: an employee who believes they were discharged or discriminated against may file a complaint with the Secretary of Labor within thirty days of the violation, and it is then the Secretary — not the employee — who brings any action in federal district court. OSHA's regulation adds that later complaints are ordinarily presumed untimely and that a pending grievance-arbitration proceeding or a filing with another agency does not stop the clock. Meanwhile the personal cost is borne up front and in full: the career damage, the legal expense, and the years of it arrive long before any vindication, and vindication is not guaranteed. Stating this plainly is not discouragement — it is why the earlier steps matter. Escalating early and in writing is not the timid version of ethics; it is what most often works, and what leaves a record when it does not.

Challenger and Hyatt Regency, read against the investigations

These cases are taught everywhere and several are mis-taught, so take them from the investigations. Challenger: the Rogers Commission concluded the cause was failure of the pressure seal in the aft field joint of the right Solid Rocket Motor, due to a faulty design unacceptably sensitive to temperature, dimensions, materials, reusability, processing, and dynamic loading. Ambient temperature at launch was 36 degrees Fahrenheit (about 2 degrees Celsius), 15 Fahrenheit degrees below the next coldest previous launch, and the coldest point on the joint was estimated at 28 plus or minus 5 degrees Fahrenheit (about minus 2 degrees Celsius). Roger Boisjoly had written to Thiokol's Vice President of Engineering on 31 July 1985 warning that a field-joint failure would be a catastrophe of the highest order involving loss of human life. On the night of 27 January 1986 Thiokol engineers recommended against flying outside their data base, whose low point was 53 degrees Fahrenheit (about 12 degrees Celsius); Thiokol then caucused off the loop and reversed its own recommendation. The Commission found a serious flaw in the decision process, found that waiving launch constraints appears to have been at the expense of flight safety, found that Thiokol management reversed its position at the urging of Marshall and contrary to the views of its engineers to accommodate a major customer, and found that senior NASA managers did not know of the constraint or its six waivers. The failure was in the reporting chain as much as in the joint. Hyatt Regency: NBS found the most probable cause was insufficient load capacity of the box beam-hanger rod connections, with two contributing factors — an inadequate original connection design and a construction change from one continuous rod set to two that essentially doubled the load on the fourth-floor connections. The change is what people remember; the finding that matters professionally is that the original design was already only about 60 percent of code-expected capacity. The Missouri board located the professional failure precisely: a structural drawing prepared without the required work, shop drawings not reviewed, a connection called safe by an engineer who had not calculated it, and a seal applied to a drawing its sealing engineer had never reviewed.

The Pinto, Volkswagen, and the shape of the pattern

Ford Pinto: NHTSA campaign 78V143000, received 19 June 1978, records a fuel-system defect in which a rear impact could disconnect the filler pipe or puncture the tank. In Grimshaw the court recited evidence of 9 or 10 inches of crush space behind the rear axle, tank puncture and filler-neck separation in 21-mile-per-hour (34 km/h) crash tests, and fixes costing roughly $2 to $10 per car — and stated that a prototype failing the fuel system integrity test triggered an industry standard of care requiring redesign and retest. But the famous "Pinto memo," the Grush-Saunby Report, was excluded from evidence; the jury never saw it. What it did see was a different internal document recommending that a flak suit or bladder be delayed to 1976 for a stated design cost saving of $10.9 million. The real case is more interesting than the myth and less convenient as a slogan. Volkswagen: EPA's notices of violation of 18 September and 2 November 2015 describe software that detected when a vehicle was undergoing emissions testing and enabled full emissions controls only during the test, with on-road nitrogen oxide emissions reaching up to 40 times the standard on the 2.0 liter cars. In January 2017 Volkswagen AG agreed to plead guilty to three criminal felony counts and pay a $2.8 billion criminal penalty, alongside $1.5 billion in civil resolutions; individuals were prosecuted in the same federal case, including a Volkswagen engineer. Software is engineering, and writing code whose purpose is to defeat a test is a professional act with professional consequences. Across all four cases the shape repeats: a documented technical concern traveling upward through a structure whose incentives were not technical. This lesson is educational material — not legal advice, not professional or engineering advice, not design guidance — and it takes no position on any current controversy or investigation.

Eli, the EliExplains learning guide

Eli explains

The same idea, in plain words

Explain it like I’m 10

Imagine you are the only person in a building who can read the sign that says the floor will not hold everyone. Your boss wants to open the doors, the owner has already sold tickets, and you are the one who has to say something. Engineering ethics is the set of rules the profession wrote for exactly that moment. The first rule is the ordering: keeping people safe comes before keeping your client happy. The rest of the rules mostly exist so that moment does not sneak up on you — only take work you actually know how to do, tell the whole truth in your reports rather than only the true parts that are convenient, say out loud when you have a reason to be biased, and remember that keeping a company's secrets never covered hiding a danger. And there is a sequence for what to do: say it clearly, say it in writing, do not put your name on the drawing, and if nobody listens, go over their heads.

Picture it like this

It works like a lifeguard's whistle. A lifeguard is employed by the pool, but the whistle answers to the swimmers. If the manager wants the pool kept open during lightning because a party has been booked, the lifeguard is not being disloyal by clearing the water — that is precisely the job the pool hired them to do, and the whole reason anyone trusts the pool enough to swim in it.

Where the picture stops working

The analogy breaks in two places. A lifeguard sees the danger in real time and can act alone in seconds; an engineer usually sees it months in advance, in a calculation nobody else can check, and can only act by persuading other people. And a lifeguard who blows the whistle is backed by the rules of the facility, while an engineer who escalates may be arguing against their own management with very little protecting their job.

Worked example

Work the Hyatt Regency numbers as a consistency check, then locate the professional duty. NBS reported that a fourth-floor box beam-hanger rod connection as built carried a maximum load equal to only 31 percent of the ultimate capacity expected of a connection designed under the Kansas City Building Code, and that without the construction change from one continuous rod set to two the figure would have been approximately 60 percent. Does that hang together? The change essentially doubled the load on the fourth-floor connections. Halving 60 percent gives 30 percent, against the 31 percent NBS reported — a one-percentage-point difference, consistent with rounding and with the measured weights and occupancy the investigators used. Both numbers are below 100 percent, so the original design was already deficient before anyone changed anything; the change left the walkways, in the investigators' words, with only minimal capacity to carry their own weight and virtually none for the loads people would add. Now the professional question, which is not a design question. Who owed a duty here? The Missouri board's answer was: the structural engineer, throughout. Connection design is an engineering function because it requires calculations. Responsibility for connection adequacy stays with the structural engineer even where a fabricator does the detailing, because the drawings communicate who designed what. The failures the board found were procedural and professional — a drawing prepared without the required work, shop drawings not reviewed, a connection called safe by someone who had not calculated it, a seal applied to an unreviewed drawing. Every one of those is a step someone could have taken on an ordinary Tuesday. Note carefully: these figures are reported as investigation findings for study. Nothing here is design guidance, and real structural design requires a licensed engineer working to the governing code.

Key takeaway

Engineering codes put public safety, health, and welfare above the engineer's duty to client and employer, and the whole apparatus of competence limits, truthful reporting, disclosed conflicts, and bounded confidentiality exists to make that ordering operable. The rule is easy; the moment is not, which is why the codes describe a sequence — escalate, document, refuse to seal, and go outside only as a last resort.

Quick check

3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.

Question 1 of 3foundational

In the NSPE and ASCE codes of ethics, which obligation is ranked above an engineer's duty to a client or employer?

Choose an answer, then check it.
Question 2 of 3intermediate

What did the Rogers Commission conclude about how the recommendation to launch Challenger came to be reversed on the night of 27 January 1986?

Choose an answer, then check it.
Question 3 of 3intermediate

A structural engineer concludes that a proposed change to a connection detail leaves the assembly below the governing code's requirements. The client instructs the engineer to seal the drawings anyway so the schedule holds. Which response best matches what the codes direct?

Choose an answer, then check it.
Practice all 5

Keep learning

Ready to build on this? Continue to the next lesson.

Practice this lesson
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related

You’ll learn to

  • Define the paramountcy principle and explain where it sits relative to an engineer's obligations to client and employer.
  • Distinguish ethical obligation from legal requirement and from civil liability, and identify who actually enforces professional-conduct rules.
  • Explain the standing duties that surround the public-safety principle: competence, truthfulness, conflict disclosure, bounded confidentiality, and sustainability.
  • Apply the codes' escalation sequence to a situation in which engineering judgment is overruled, and describe the role of contemporaneous documentation.
  • Analyze the canonical cases — Challenger, Hyatt Regency, the Ford Pinto, Volkswagen — against what the investigations actually established, and separate that from the versions in general circulation.
  • Evaluate whistleblowing honestly as a last resort, including its personal cost and the narrowness of U.S. legal protection.

Common mistakes

  • Treating the Ford "Pinto memo" as the proven document in which Ford priced lives and decided against a fix.

    The Grimshaw opinion states that the Grush-Saunby Report was excluded from evidence, so the jury that returned the punitive award never saw it. What was in evidence was a different internal Ford document recommending that a flak suit or bladder be delayed to 1976 for a stated design cost saving of $10.9 million. Cost-based deferral of a safety fix is established; the specific famous memo is not the thing that established it.

  • Saying that NASA overruled Roger Boisjoly and launched anyway.

    The Rogers Commission found that Thiokol management reversed its own engineering recommendation, at the urging of Marshall and contrary to the views of its engineers, in order to accommodate a major customer — and separately found that the launch constraint and its six waivers were not known to the senior NASA managers in the readiness process. The failure ran through the contractor's management and the reporting chain, which is a harder and more useful lesson than a simple override.

  • Blaming the Hyatt Regency collapse entirely on the fabricator's change to the hanger rod arrangement.

    NBS found two contributing factors, and the first was that the original connection design was already inadequate — approximately 60 percent of code-expected capacity even before the change. The construction change roughly doubled the connection load and made a deficient design catastrophic, but it did not spoil a sound one, and the licensing board's findings were about the engineers' review and sealing duties.

  • Assuming that if something is legal it is ethical, or that meeting a code of ethics protects you from liability.

    These are three separate systems. Statutes set legality, courts assess liability against a standard of care, and professional bodies assess conduct against a code — and the ASCE code states in a footnote that it does not establish a standard of care. An engineer can satisfy one and fail another, and only a state licensing board can end the right to practice.

  • Assuming that an engineer who reports a safety problem is legally protected.

    There is no general federal statute protecting engineers who report safety problems. OSHA administers anti-retaliation provisions under a list of industry-specific statutes — 25 as listed in August 2026 — and the general OSH Act provision gives the employee thirty days to complain to the Secretary of Labor, who then decides whether to sue. Protection depends entirely on which statute, if any, your concern falls under.

Easily confused

Ethical obligation under a code vs. Legal requirement under a statute or regulation

A code is written and enforced by a profession and reaches conduct no statute mentions; a statute is written by a legislature and enforced by the state. Conduct can satisfy one and violate the other in either direction.

Professional society discipline vs. State licensing board discipline

A society can sanction or expel a member, which affects standing and reputation. A licensing board can suspend or revoke the license itself, ending the right to practice — which is what happened to the engineers of record after the Hyatt Regency collapse.

Internal dissent vs. Whistleblowing

Internal dissent means escalating a documented technical concern through the organization's own chain; whistleblowing means going outside it to a regulator, a board, or the public. The codes ask for the first and reserve the second for when the first has failed.

Confidentiality vs. Concealment

Confidentiality protects a client's business affairs and technical processes and is bounded by carve-outs for disclosure required by law or by the code itself, plus an affirmative duty to report code violations to appropriate bodies. Once information is being withheld to keep a hazard from the people it endangers, the confidentiality rule has stopped applying.

Key vocabulary

Paramountcy principle
The ordering written into engineering codes of ethics under which the safety, health, and welfare of the public outranks every other professional obligation, including the duty owed to a paying client or an employer.
Fundamental canon
One of the short numbered statements at the head of a code of ethics that names a governing duty; the detailed rules of practice and professional obligations that follow are elaborations of those numbered duties.
Engineer's seal
The stamp or seal a licensed engineer applies to drawings and specifications. Applying it is a formal assumption of professional responsibility for the work, and in some jurisdictions that responsibility is imposed by statute rather than merely implied.
Conflict of interest
Any interest, financial or otherwise, that could influence or appear to influence a professional's judgment on a matter. Codes generally require disclosure of known or potential ones rather than banning every situation that produces them.
Standard of care
The legal yardstick for professional negligence: what a reasonably prudent practitioner in the same field and circumstances would have done. It is set by courts and expert testimony, and at least one major code states that it is not established by that code.
Gross negligence (licensing context)
In a professional-discipline proceeding, an act or course of conduct demonstrating conscious indifference to a professional duty. A Missouri hearing commission and appellate court treated it as different in kind from ordinary carelessness rather than simply a worse grade of it.
Whistleblowing
Reporting a hazard or wrongdoing to someone outside the organization's own chain of command — a regulator, a licensing board, or the public. Codes treat it as a last resort after internal escalation has failed.
Defeat device
A design element, in hardware or software, whose function is to make a product behave differently under test conditions than in normal use so that it passes a regulatory test it would otherwise fail.

Sources & references

  1. NSPE Code of Ethics for Engineers — National Society of Professional Engineers
  2. Code of Ethics — American Society of Civil Engineers
  3. Report of the Presidential Commission on the Space Shuttle Challenger Accident, Volume 1 — NASA History Division
  4. Investigation of the Kansas City Hyatt Regency Walkways Collapse (NBS Building Science Series 143) — National Bureau of Standards (now NIST)
  5. Duncan v. Missouri Board for Architects, Professional Engineers and Land Surveyors, 744 S.W.2d 524 (Mo. Ct. App. 1988) — Missouri Court of Appeals, Eastern District (via CourtListener)
  6. Grimshaw v. Ford Motor Co., 119 Cal. App. 3d 757 (Cal. Ct. App. 1981) — California Court of Appeal, Fourth Appellate District (via CourtListener)
  7. NHTSA Recalls by Vehicle: Ford Pinto (campaign 78V143000) — National Highway Traffic Safety Administration
  8. Learn About Volkswagen Violations — U.S. Environmental Protection Agency
  9. Volkswagen Agrees to Plead Guilty, Pay $4.3 Billion in Criminal and Civil Penalties (EPA news release, 11 January 2017) — U.S. Environmental Protection Agency (January 2017 web snapshot)
  10. United States v. Liang, No. 2:16-cr-20394 (E.D. Mich.) — docket — U.S. District Court for the Eastern District of Michigan (via CourtListener RECAP)
  11. Statutes | Whistleblower Protection Program — Occupational Safety and Health Administration, U.S. Department of Labor
  12. 29 U.S.C. 660(c) — Discharge or discrimination against employee for exercise of rights — Office of the Law Revision Counsel, U.S. House of Representatives
  13. 29 CFR 1977.15 — Filing of complaint for discrimination — Electronic Code of Federal Regulations (National Archives / GPO)
  14. Licensure — National Council of Examiners for Engineering and Surveying (NCEES)

EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.

Researched 2026-08-19

Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.