Chapter 36: Wildlife, Environmental, and Forensic Engineering: When the Victim Isn't a Person

"The first principle is that you must not fool yourself — and you are the easiest person to fool." — Richard Feynman, Cargo Cult Science (Caltech commencement address, 1974). Feynman wrote it about science generally; it is, word for word, the discipline a forensic engineer brings to a collapsed building.

Overview

Everything in this book so far has had a human victim. A body in a burned cabin, a child who never came home, a man on death row. But the application of science to legal questions does not stop at the edge of the human body, and some of the most rigorous forensic work being done anywhere is done where the victim is an elephant, a river, a bridge, or the anonymous public who trusted that the walkway above the hotel lobby would hold. This chapter is about those cases — and about a quiet, important claim it will spend six sections proving: that the logic you have spent thirty-five chapters learning is not a set of rules about human bodies. It is a way of reasoning from physical evidence to a defensible conclusion, and it transfers, intact, to any domain where someone needs to know what happened and who is responsible.

Watch the machinery reappear. Wildlife forensics asks whether a seized tusk came from a protected species and where that animal lived — and answers with the same class-versus-individual distinction (Chapter 1) and the same DNA science (Chapter 7) that identifies a suspect. Environmental forensics asks whose oil is on the beach, and answers by chemically "fingerprinting" the spill against candidate sources, with the same honesty about consistent with versus proves that governs a fiber comparison. Forensic engineering and its core method, failure analysis, ask why a structure or a product failed, and reason from the wreckage back to a cause by forming hypotheses and testing them against the physical evidence — the scientific method of Chapter 5, applied to twisted steel. Accident reconstruction asks how a collision happened, and reads skid marks and crush damage the way a bloodstain analyst reads spatter (Chapter 10) — physics frozen into evidence. And fire-and-explosion engineering brings us full circle to the arson science of Chapter 22, where we will do something the cold case has been waiting for: independently rule out an accidental electrical cause of the Mill Creek fire.

We will be honest, as always, about where each method sits. Some of this work is as rigorous as anything in forensic science — species identification by DNA is genuinely strong; chemical source-attribution rests on real analytical chemistry. Some of it carries the same overstatement risks that have haunted the pattern disciplines, and the same need to say "the evidence is consistent with this, and here is what it cannot establish." The victim has changed. The discipline has not.

In this chapter, you will learn to:

• Define wildlife forensics and use species identification and geographic-origin DNA to answer "what animal, and from where" — at honest strength.
• Define environmental forensics and explain chemical source-attribution ("fingerprinting") and its limits.
• Define forensic engineering and failure analysis and reconstruct why a structure or product failed, using hypotheses tested against evidence.
• Define accident reconstruction and read physical evidence and physics to reconstruct a collision, stating what it can and cannot support.
• Connect fire-and-explosion engineering back to Chapter 22 and rule an accidental cause in or out.
• Place every method here on the validity spectrum and state what each can honestly carry into court.

Learning Paths

🔎 Investigator/CSI: These scenes look nothing like a homicide scene and are processed by exactly the same principles. Weight §36.1 (collecting a tusk or a carcass so the lab can do species work) and §36.4 (documenting a collision scene before the skid marks fade and the vehicles are towed). The first responder's job — preserve the evidence, document before you move anything — does not change because the victim is an animal or a road. 🧪 Lab analyst: Weight §36.1–36.2. Wildlife DNA (§36.1) is your STR and sequencing skills (Chapter 7) pointed at a non-human genome; environmental "fingerprinting" (§36.2) is your GC-MS (Chapter 23) pointed at a pollutant. The bench is familiar; the reference databases and the interpretation are what is new. ⚖️ Law/courtroom: Weight §36.3 and §36.5. Engineering testimony is Kumho Tire territory (Chapter 5) — non-scientific expert testimony that must still rest on reliable methodology. Learn how a failure analysis is attacked on cross, and how "the engineer's report" can overstate exactly the way a forensic examiner's can. 👥 General reader/juror: This chapter is the proof that forensic reasoning is a general skill, not a set of crime-lab tricks. §36.6 ties it together. If you can ask "class or individual? consistent-with or proves? what is the error rate?" of a bridge collapse, you have learned what this book set out to teach.

36.1 Wildlife forensics: poaching, trafficking, and species ID

Begin where the logic is clearest, because wildlife forensics is the most direct translation of the whole book into a new domain. A shipment is seized at a port: forty kilograms of carved ivory, declared on the manifest as "bone handicrafts." A hunter is stopped with a cooler of dressed meat he says is legally taken deer. A bag of dried sea-horse, a vial of powdered horn, a feather. In each case the law needs to know something the object will not volunteer: what species is this, is that species protected, and — increasingly — where did this individual animal come from? Those are scientific questions with legal consequences, which is the definition of forensic science from Chapter 1, and the science that answers them is largely the science of Part II, repurposed.

Wildlife forensics is the application of forensic science to crimes and legal questions involving wild animals and plants — poaching, illegal trade in protected species and their parts, and violations of conservation law — most centrally through identifying the species (and sometimes the population or individual) from biological evidence. The field has institutional weight behind it. In the United States, the U.S. Fish and Wildlife Service National Fish and Wildlife Forensic Laboratory in Ashland, Oregon — the only full-service laboratory in the world dedicated to wildlife crime, and the official crime lab for the international wildlife-trade treaty known as CITES (the Convention on International Trade in Endangered Species) — does for animal victims exactly what a state crime lab does for human ones: it examines evidence, identifies it, and produces analysts who testify to their findings. The treaty matters because it is the legal framework that makes "what species is this?" a question with teeth: CITES lists protected species, and proving an object came from a listed species is what converts a shipment of "handicrafts" into a federal crime.

The foundational task is species identification, and here the class-versus-individual logic from Chapter 1 (§1.3) reappears almost unchanged. Identifying that a sample is "elephant" rather than "cow" is a class determination — it places the evidence in a group (a species) the way a herringbone sole places a shoe in a manufacturing class. Several methods do this, arranged on a familiar ladder from gross examination to molecular confirmation:

• Morphology. An expert examines physical features — the cross-hatched Schreger lines visible in a cut section of true elephant or mammoth ivory, the structure of a hair, the shape of a bone, the pattern of a feather — and assigns the specimen to a taxonomic group. This is class evidence by visual comparison, and like all such evidence (Chapter 16, Chapter 19) it is only as good as the reference knowledge behind it and the distinctiveness of the feature.
• DNA sequencing. The modern workhorse. Rather than the human STR markers of Chapter 7, species work typically reads a stretch of DNA — often a mitochondrial gene region used as a DNA barcode — and compares the sequence against a reference database of known species. The principle is the same as a database search (CODIS, AFIS): you generate a profile and look for what it matches. DNA can also work the individual end of the ladder — matching a specific tusk to a specific poached carcass, or to a population — using the same logic of increasingly rare shared features that takes a human comparison from "consistent with" toward "strongly associated."

🔬 At the Bench Species identification by DNA barcoding, in honest detail. The analyst extracts DNA from the evidence — a fragment of tusk, a sliver of meat, a single feather quill — which is often degraded or processed (boiled, dried, carved), so the same low-template and degraded-sample challenges from Chapter 8 apply. A target region is amplified by PCR (Chapter 7) and sequenced, and the sequence is compared against reference databases of known species. A close match to a reference sequence supports assigning the evidence to that species. The limits are real and must be stated: the reference database must actually contain the species in question (a gap in the database is a gap in the answer); closely related species can have very similar sequences, blurring the line; and a degraded sample may yield only a partial sequence that narrows the answer to a genus rather than a species. As always, the honest output is calibrated to what the data support — "the sequence is consistent with African elephant and excludes the domestic and common substitute species tested" is a different, more defensible claim than "this is definitely African elephant," and a good analyst knows which one their data earned.

The most striking advance in the field is geographic origin determination, and it is worth dwelling on because it shows the same scientific logic reaching a genuinely new and powerful conclusion. For some species — elephants are the celebrated example — researchers have built reference maps of how DNA varies across the geographic range of the species. Because populations in different regions carry different allele frequencies, a tusk's DNA can be compared against these maps to estimate where on the continent the elephant lived — narrowing a seized shipment's origin to a region, even a particular protected area. This is the same population-genetics reasoning that underlies the random match probability (Chapter 7): variation that is patterned and quantified can be read backward to a source. (A complementary approach uses stable-isotope analysis — the isotopic signature an animal acquires from the local water and food, previewed in Chapter 29 — to corroborate geographic origin, an entirely independent line of evidence pointing at the same question.) The forensic payoff is enormous: knowing that seized ivory traces to a specific region tells investigators where the poaching is actually happening, redirecting enforcement to the genuine hotspots rather than the ports where the ivory happens to surface.

⚖️ In the Courtroom Wildlife-DNA testimony is attacked, and defended, on exactly the grounds you would expect from the rest of this book. The defense probes the reference database (was the true source species even in it? how complete is the geographic map?), the possibility of a closely related species the test could not distinguish, contamination, and the chain of custody from a port seizure halfway around the world. The honest expert concedes what the data cannot do — a region-level origin is not a GPS coordinate; a species ID from a degraded carving may reach genus, not species — and testifies at the strength the sequence actually supports. Notice that geographic-origin evidence is, in the book's language, an association with a place-type — precisely the same kind of claim, and the same honest verb ("consistent with / supports"), as the pollen-on-the-floor-mat evidence in Chapter 13. The victim is an elephant; the evidentiary logic is identical.

Where does wildlife forensics sit on the validity spectrum? Its DNA-based species identification and geographic-origin work rest on the same rigorous, quantified molecular-biology and population-genetics foundation as human DNA (Chapter 7) — near the strong end, bounded mainly by database completeness rather than by any weakness in the method. Its morphological class identifications sit lower, in the company of other visual-comparison disciplines, strong when the feature is distinctive and the examiner well-referenced, weaker when neither holds. The field is, in miniature, the whole validity spectrum of this book — and it earns its strong end the same way DNA did: by quantification and validation, not by the confidence of its practitioners.

🔍 Check Your Understanding 1. Distinguish a species identification from an individual (or population) identification in wildlife forensics, and match each to the class-versus-individual distinction from Chapter 1. 2. Why is the completeness of the reference database the central limit on a DNA species identification — and what is the honest way to report a result for a species that may not be well represented in the database?

36.2 Environmental forensics: pollution and its source

Now the victim becomes a place — a river, an aquifer, a stretch of coastline, the air over a city. A pipeline leaks; an oil sheen spreads across a harbor; a plume of solvent turns up in the groundwater under a town with three factories that have used that solvent for forty years. The legal questions are immediate and expensive: who is responsible, and for how much? And the scientific question underneath them is one this book has asked in a dozen forms: can we connect this contamination to that source? That is a source-attribution problem, and it is solved with chemistry that should feel familiar from Chapters 23 and 24.

Environmental forensics is the application of scientific methods to determine the source, age, and responsible party of environmental contamination — identifying what a pollutant is, where it came from, and when it was released — in support of regulatory enforcement, litigation, and cleanup-cost allocation. It exists because environmental law assigns liability, and liability requires proof of causation and source: it is not enough to show a town's water is contaminated; someone must show whose contamination it is. That is forensic science — science for the forum — applied to an ecosystem.

The core technique is chemical fingerprinting, and the name is a deliberate (and slightly dangerous) borrowing. A complex pollutant — crude oil, a fuel, a mixture of industrial chemicals — is not a single compound but a characteristic mixture of many, in characteristic proportions, often carrying trace components specific to its origin. Analyzed by the instrumental methods of Chapter 23 — above all gas chromatography–mass spectrometry (GC-MS), which separates a mixture into its components and identifies them — a pollutant yields a detailed chemical pattern. That pattern can be compared against the patterns of candidate sources: the oil from suspect ship A versus suspect ship B, the solvent signature of factory X versus factory Y. A close correspondence supports attribution to that source; a clear difference can exclude it.

🔬 At the Bench Oil-spill fingerprinting is the textbook case, so make it concrete. Crude and refined oils contain thousands of compounds, including families of biomarkers — compounds whose relative abundances reflect the geological source and refining history of that particular oil, and which are relatively resistant to weathering. An analyst characterizes a spill sample and the candidate-source samples by GC-MS, focusing on ratios of these stable components, and compares the patterns. Because the ratios survive weathering better than the lighter, more volatile compounds (which evaporate and degrade once the oil hits the environment), they allow a spill that has sat on the water for days to still be matched to its source. The honest analyst accounts for weathering explicitly — comparing weathering-resistant features and modeling how the sample has changed — and reports the comparison at its true strength. As in all comparison work, exclusion is cleaner than inclusion: a source whose pattern clearly differs from the spill can be ruled out with confidence, while attributing the spill to a particular source is a probabilistic statement about how distinctive the matching pattern is and how many other sources could share it.

This last point deserves the full weight of the book's first theme, because environmental forensics is exactly as vulnerable to overstatement as any pattern discipline. The strength of a source attribution depends entirely on the distinctiveness of the chemical signature and the completeness of the candidate set — the same two factors that govern a pollen match (Chapter 13) or a soil comparison (Chapter 24). If a contaminant's signature is common — a generic diesel that a hundred sources could have produced — then matching it to one suspect source proves very little, however precise the chemistry. If the signature is unusual, or carries a rare marker, the attribution is stronger. And if there is an unsampled fourth factory upgradient that no one tested, the "match" to factory X may simply mean factory X used the same common solvent as the real culprit. The chemistry that identifies the compound is strong, validated analytical science (Chapter 23); the inference that attributes it to a specific source is a comparison, with all the honesty about "consistent with" versus "proves" that comparisons demand.

⚠️ Junk-Science Alert Beware the word "fingerprint" doing more work than the science supports. A chemical "fingerprint" is not a human fingerprint, and the metaphor smuggles in a false promise of uniqueness. A pollutant's chemical pattern is a class characteristic — shared by all the product of that type, that batch, that process — not an individualizing mark unique to one source in all the world. Attributing contamination to a source is therefore a probabilistic, exclusion-and-distinctiveness argument, exactly like soil or glass (Chapter 24), and it must account for the alternative sources that were never sampled. An expert who testifies that "the chemical fingerprint proves this spill came from this defendant's tank, and no other" has made the same overreach as a bite-mark examiner claiming a unique match — dressed up in the genuine prestige of analytical chemistry. The instrument's precision about what the compound is is not precision about whose it is.

There is a second, equally interesting question environmental forensics tackles: when was the contamination released? Dating a release matters enormously for liability — a company is responsible only for its own tenure on a site, so whether a plume of solvent dates from the 1970s or the 2000s can decide which of a property's successive owners pays. Analysts estimate release timing using lines of evidence such as the degradation state of the contaminant (many compounds break down on a roughly known schedule, so the ratio of parent compound to breakdown products acts as a rough clock — conceptually like reading decomposition state), the depth and extent of a plume's migration through soil and groundwater (modeled against how fast such plumes move), and historical records of what was used when. Each of these is an estimate with real uncertainty, and the honest report is, once again, a range with stated assumptions rather than a date — the same discipline the entomologist brings to a postmortem interval (Chapter 13).

🔍 Check Your Understanding 1. Why is excluding a candidate source of pollution generally a cleaner, more confident statement than attributing the pollution to a particular source? (Connect to the exclusion-over-proof asymmetry from Chapter 1, §1.6.) 2. Two factories used the same common solvent; a third, unsampled factory upgradient also used it. Explain how an attribution to one of the sampled factories could be wrong, and which two factors most control the real strength of a chemical source attribution.

36.3 Forensic engineering and failure analysis

Change the victim again. Now it is a structure, a machine, or a product — and behind it, often, the people the failure killed or injured, or the company facing ruin over who is to blame. A crane topples. A gas line explodes. A medical device fails in a patient. A car's accelerator sticks. Each is a question of the form why did this fail, and was the failure due to a design flaw, a manufacturing defect, improper use, inadequate maintenance, or simply the end of the thing's natural life? Answering it is the province of forensic engineering, and its central method is one this book has been teaching since Chapter 5.

Forensic engineering is the application of engineering principles and methods to investigate the causes of failures — of structures, materials, components, vehicles, and products — typically when those failures cause injury, death, or significant loss, and when the cause must be established for legal proceedings. Its core activity is failure analysis: the systematic process of determining how and why a structure, component, or system failed, by examining the physical evidence of the failure and reasoning backward to its cause. Read those two definitions against Chapter 5 and you will see they describe the scientific method applied to wreckage: observe the failed object, gather data, form hypotheses about the cause, and test each hypothesis against all the physical evidence, discarding those the evidence refutes, until one survives. It is origin-and-cause determination (Chapter 22) for things instead of fires — and it shares fire investigation's central discipline: the honest answer is sometimes "the evidence does not allow a determination."

The forensic engineer reads physical evidence the way every analyst in this book reads it — as the frozen record of a physical process. The clues are different but the grammar is the same:

• Fracture surfaces. When metal or another material breaks, the surface of the break records how it failed. A ductile failure (the material stretched and tore, like pulling apart taffy) looks different from a brittle failure (it snapped cleanly, like glass). Most revealing of all is fatigue: a component subjected to repeated cycles of stress can develop a crack that grows a tiny amount with each cycle, leaving characteristic progression marks ("beach marks") on the fracture surface that record the crack's slow advance, followed by a final sudden rupture when the remaining material could no longer bear the load. An engineer reading those marks can often tell that a part failed by fatigue, roughly how long the crack grew, and where it started — frequently at a stress concentration, a flaw, or a design feature that focused the load.
• Deformation and load paths. The way a structure bent, buckled, or collapsed records the forces that acted on it and the order in which things gave way — letting the engineer reconstruct the sequence of failure and find the first element to fail, the "initiating" failure that started the cascade.
• Materials testing. Samples of the failed material can be tested to determine whether they met specification — whether the steel was as strong as the design required, whether a weld was sound, whether a polymer had degraded. A part that failed because the material was below spec points to manufacturing; a part that met spec but failed anyway points to design or loading.

FAILURE-ANALYSIS FAULT TREE  —  "Why did this load-bearing connection fail?"   [constructed teaching example]

                         ┌───────────────────────────────────┐
                         │   TOP EVENT: connection failed,    │
                         │   structure collapsed              │
                         └──────────────────┬────────────────┘
                                            │  (which cause is supported by the evidence?)
        ┌───────────────────────┬───────────┴───────────┬───────────────────────┐
        │                       │                       │                       │
 ┌──────┴───────┐       ┌───────┴────────┐      ┌───────┴────────┐     ┌────────┴────────┐
 │ DESIGN flaw  │       │ MANUFACTURING/ │      │ OVERLOAD /      │     │ DETERIORATION / │
 │ (under-rated │       │ FABRICATION    │      │ MISUSE          │     │ MAINTENANCE     │
 │  for load)   │       │ defect (bad    │      │ (load exceeded  │     │ (corrosion,     │
 │              │       │  weld, wrong   │      │  the design,    │     │  fatigue from   │
 │              │       │  part)         │      │  improper use)  │     │  age/neglect)   │
 └──────┬───────┘       └───────┬────────┘      └───────┬────────┘     └────────┬────────┘
        │                       │                       │                       │
   test vs.                test vs.                test vs.                test vs.
   the loads,              fracture surface,       actual loads at         corrosion products,
   the calculations,       weld quality,           failure, use            crack progression
   the as-built drawings   materials spec          history, witnesses      marks (fatigue)

  Legend: each branch is a HYPOTHESIS. The engineer tests every branch against the physical
          evidence and ELIMINATES the ones the evidence refutes. A branch is supported only by
          AFFIRMATIVE evidence — never by "we couldn't find anything else" (cf. negative corpus, Ch.22).

Walk the fault tree, because it is the whole method in one diagram. The top event is what you are trying to explain: the connection failed and the structure came down. Beneath it hang the candidate causes — design, manufacturing, overload or misuse, and deterioration or maintenance — and these are hypotheses, not conclusions. The engineer's job is to test each branch against the physical evidence: the design hypothesis against the load calculations and as-built drawings; the manufacturing hypothesis against the fracture surfaces and weld quality; the overload hypothesis against the actual loads present at failure and the use history; the deterioration hypothesis against corrosion products and fatigue marks. Branches the evidence refutes are pruned. A branch survives, and earns a finding, only on affirmative evidence — and here the diagram carries a warning lifted straight from Chapter 22: a cause must never be concluded merely because the engineer "couldn't find anything else." That is the negative corpus fallacy (Chapter 22, §22.4) wearing a hard hat. Eliminating other causes can support a hypothesis, but the surviving branch still needs positive evidence of its own — a fatigue crack you can see and measure, a calculation showing the design was under-rated, a weld demonstrably defective.

🧠 Cognitive-Bias Watch Forensic engineers are vulnerable to the same contextual bias (Chapter 31) that contaminates a fingerprint examiner, and the mechanism is identical. The engineer is very often retained by one side — the injured plaintiff or the defendant manufacturer — and is told, before examining anything, what conclusion would help. That expectation can steer which hypotheses get serious testing and which get waved away, which fracture features get emphasized, how an ambiguous calculation gets resolved. The safeguards are the same ones the whole book preaches: form and test all the hypotheses, including the one that hurts the retaining party; ground every conclusion in affirmative physical evidence that another engineer could examine and replicate; and document the reasoning so the work can be checked. An engineering conclusion reached by testing only the hypothesis the client wanted is worth exactly as little as a print "match" made by an examiner who knew which suspect the detective liked.

⚖️ In the Courtroom Forensic-engineering testimony lives under a specific legal rule you met in Chapter 5: Kumho Tire Co. v. Carmichael (1999), which extended the Daubert reliability gate to non-scientist expert testimony — including engineers. (The Kumho case itself, fittingly, concerned an engineer's testimony about why a tire failed.) The consequence is that an engineer cannot testify to a cause on the strength of experience and authority alone; the methodology must be reliable — hypotheses tested against evidence, calculations that can be checked, principles that are established. A failure analysis built on the systematic elimination-and-affirmation method survives that scrutiny. One built on an expert's say-so — ipse dixit, the "he himself said it" problem from Chapter 1 — is exactly what Kumho empowers a court to exclude. On cross, the attack mirrors the rest of the book: which hypotheses did you not test, what evidence did you discount, what is the uncertainty in your calculation, and were you told the answer before you began?

Where does forensic engineering sit on the validity spectrum? Generally toward the strong end, for a principled reason: it rests on the established, quantitative, testable sciences of mechanics, materials, and physics, and its conclusions are often checkable by independent calculation and replicable examination of the same evidence — the hallmarks PCAST (Chapter 6) demands. But it is not automatically strong, and the same author can produce strong and weak work. A fatigue fracture identified from clear, measurable progression marks is a robust finding; a confident reconstruction of a complex, partially destroyed failure with several plausible causes and an engineer retained to reach one of them is far softer. As everywhere in this book, the discipline lies not in the field's reputation but in whether this conclusion was reached by testing hypotheses against affirmative evidence — or backed into.

36.4 Accident reconstruction

Stay with physical evidence and physics, and narrow to the single most common forensic-engineering task: figuring out how a collision happened. Two cars meet at an intersection and each driver swears the other ran the light. A pedestrian is struck and the question is how fast the car was going. A truck rolls over and the question is whether speed, the road, the load, or a mechanical failure caused it. These are reconstructable events, because a collision is a physics problem that leaves its working scattered across the scene — and reading that working is the discipline of accident reconstruction.

Accident reconstruction is the application of physics and engineering to determine how a collision or other accident occurred — the speeds, paths, positions, and sequence of events — by analyzing the physical evidence it left behind. The reconstructionist is, quite literally, a bloodstain-pattern analyst for vehicles: where the BPA expert reads the geometry and distribution of spatter to reconstruct the events that produced it (Chapter 10), the reconstructionist reads the geometry and distribution of skid marks, gouges, debris fields, and vehicle damage to reconstruct the events that produced them. The same caution applies to both, and for the same reason: reconstructing past events from their physical residue is powerful but inferential, and it is strongest when grounded in hard physics and weakest when it drifts into narrative.

The physical evidence a reconstructionist reads includes:

• Tire marks. Skid marks, scuff marks, and yaw marks record braking, steering, and loss of control. Their length and character, combined with the road's friction, allow an estimate of speed — because the energy a vehicle sheds in a skid is related, by well-established physics, to how far it skidded and how grippy the surface was. (This is the most genuinely quantitative part of the discipline, resting on conservation of energy and momentum — real, testable mechanics.)
• Crush damage. How much a vehicle's structure deformed relates to the energy absorbed in the impact, allowing estimates of impact speed from the depth and pattern of the crush.
• Final rest positions and debris. Where the vehicles and their shed debris ended up, combined with conservation of momentum, constrains the speeds and directions at impact.
• Event data recorders (EDRs). Most modern vehicles carry a "black box" that records speed, braking, throttle, and other parameters in the seconds before a crash — a digital witness (Chapter 25) that can confirm or refute the physical reconstruction with recorded data. Where it exists, the EDR is often the strongest single piece of evidence, and a physical reconstruction that contradicts a reliable EDR record is a reconstruction in trouble.

🔬 Read the Evidence

```text FIGURE 36.1 — "Reading speed from the road" [constructed teaching example] THE ITEM At an intersection: a pair of straight, dark skid marks ~24 meters long leading to Vehicle A's point of impact; a debris field (glass, plastic) clustered just past the impact point; Vehicle A's front-end crush; both vehicles' final rest positions. N ↑ ════════════════════════════════ (road edge) A ──────────skid──────────►× ← impact point ░░░ debris \ \ B's path ════════════════════════════════ [A] Vehicle A [B] Vehicle B × impact ░ debris field → travel measurements ILLUSTRATIVE, not to scale; a real scene carries surveyed distances.

THE CONTEXT Daylight, dry asphalt of known friction; scene surveyed and photographed before the vehicles were moved; Vehicle A's event data recorder downloaded with a write-blocked tool (Ch. 25) and chain of custody intact. THE INFERENCE The 24 m of skid on a dry surface of known friction is CONSISTENT WITH a pre-braking speed in a calculable range (by the energy-and-friction relationship). The crush and the debris field's position are consistent with that range. If the EDR independently records a speed in the same range, the lines of evidence CONVERGE. WHAT IT SHOWS That Vehicle A was braking hard before impact and traveling, at minimum, fast enough to lay 24 m of skid on that surface — a defensible, physics-based speed range. WHAT IT DOESN'T It does NOT, from the marks alone, establish who had the right of way, who entered the intersection first, or intent. Skid length gives a MINIMUM speed (the vehicle was going at least fast enough to skid that far); it does not capture speed lost before the wheels locked. A range, not a single number. THE LESSON Physics turns a skid mark into a speed RANGE, not a speedometer reading. The marks answer "how fast, roughly, and in what sequence" — not "whose fault." Like spatter (Ch. 10), the geometry constrains the event; it does not narrate intent. ```

Read the figure against the bloodstain chapter and the parallel is exact. In both, geometry and physics constrain what physically happened — a speed range, an area of origin — at a strength the evidence genuinely supports, and in both, the danger is the same overreach: sliding from the defensible physical reconstruction ("the vehicle was braking and traveling in this speed range") into the unsupported narrative ("the defendant was driving recklessly and ran the light"). The first is physics; the second is a story that the physics, by itself, has not earned. Skid-mark speed estimation in particular carries an honest asymmetry worth naming: because a skid captures only the speed bled off after the wheels locked, it yields a minimum speed, not the full speed — the same floor-not-verdict logic as the entomologist's minimum postmortem interval (Chapter 13). And the friction value that feeds the calculation is itself an estimate, so the output is a range, reported with its assumptions, never a single authoritative number.

🧠 Cognitive-Bias Watch Reconstruction is as exposed to expectation as any method in this book. A reconstructionist who is told, before measuring anything, that "the other driver was clearly speeding and drunk" may unconsciously select the friction value, read the ambiguous marks, and frame the range toward that conclusion. The fix is the book's standing fix (Chapter 31): build the physical reconstruction from the physics first, on the surveyed measurements and the EDR data, before letting the narrative of fault and blame into the analysis — then compare. And where an event data recorder exists, it is a partial antidote to bias precisely because it is a record, not an interpretation: it is much harder to read your expectation into a logged speed than into a smear of rubber on the road.

On the validity spectrum, accident reconstruction — like fire investigation (Chapter 22) and like forensic engineering generally — spans it. Its core speed-from-skid and momentum calculations rest on genuine, testable, quantitative physics and sit near the strong end when the inputs (friction, measurements) are well established. Its softer reaches — reconstructing a complex multi-vehicle event with degraded evidence, attributing fault, inferring driver intent — drift toward the contested middle, where assumptions multiply and the answer becomes as much narrative as calculation. Which one you have depends, as always, on the rigor of the inputs and the honesty about uncertainty, not on the confidence of the expert.

36.5 Fire and explosion engineering (callback Chapter 22)

We now return to fire — but from the engineer's side of the table, and with a specific job to do for the cold case. Chapter 22 taught fire investigation as the origin-and-cause discipline: where did the fire start, and what started it, established by the scientific method and by affirmative evidence, with the Willingham catastrophe as the standing warning against folklore and the negative-corpus fallacy. Fire-and-explosion engineering is the deeply related discipline that applies engineering analysis to the mechanism of a fire or explosion — and one of its most important contributions is to rigorously evaluate, and often eliminate, candidate accidental causes, above all the electrical system. This is a callback, not a redefinition: the terms of fire science — origin and cause, accelerant, flashover, ignitable-liquid residue, negative corpus — were all defined in Chapter 22, and we use them here as established. (Re-read Chapter 22 if any feels unfamiliar; we will not re-derive them.)

The engineer's distinctive role is the rigorous, affirmative analysis of accidental ignition hypotheses — and this is exactly where forensic engineering complements the fire investigator. Recall the danger Chapter 22 named: an investigator who cannot find an accidental cause and therefore assumes arson commits the negative-corpus fallacy, because the accidental cause may simply have been destroyed by the fire, or never properly investigated. The forensic engineer's contribution is to attack the accidental hypotheses affirmatively and competently, so that a conclusion about them rests on evidence rather than on failure-to-find. The most common — and the one that matters for Mill Creek — is the electrical system.

🔬 At the Bench Electrical failure analysis in a fire, in honest detail, because it is a discipline with a famous trap. When investigators find melted, beaded, or damaged wiring at a fire scene, the tempting inference is that the electrical fault caused the fire. But fire science draws a careful, evidence-based distinction between two superficially similar things. Cause arcing is electrical activity that ignited the fire — a fault that produced enough heat to start combustion. Victim arcing (often discussed as arc-through-char or simply fire-caused electrical damage) is electrical damage produced by the fire — the fire's heat destroyed the insulation and caused arcing or melting in wiring that was a victim of the fire, not its cause. The two can look alike to the untrained eye, and confusing them is a classic error: reading fire-caused electrical damage as the fire's cause is, in structure, the same mistake as reading a post-flashover "pour pattern" as proof of accelerant (Chapter 22, §22.3). The competent analysis examines the whole electrical system against the physics — was the circuit energized at the relevant time and location? does the pattern and location of the electrical damage fit an ignition source at the established origin, or does it fit damage inflicted by an already-burning fire? is there a competent ignition mechanism (a real fault capable of igniting nearby fuel), or only fire-victim damage? — and it reaches a conclusion on affirmative evidence about which kind of arcing is present and where, not on the mere presence of melted wire.

The forensic payoff of this analysis is double-edged, and both edges are honest. It can sometimes establish an accidental electrical cause — a genuine fault, at the origin, with a competent ignition mechanism and a circuit that was energized, that affirmatively explains the fire. Or it can do the opposite, which is what concerns the cold case: it can rule out the electrical system as an accidental cause — by showing that the electrical damage present is fire-caused (victim) rather than fire-causing, that the circuits at the origin were not energized or carried no competent ignition mechanism, and that there is no affirmative evidence of an electrical fault capable of starting the fire. Ruling out an accidental cause is itself a finding — and, in the book's recurring grammar, it is an exclusion, the strongest and cleanest kind of statement forensic science makes (Chapter 1, §1.6). Critically, this is the affirmative closing of an accidental hypothesis that Chapter 22 demanded as the antidote to negative corpus: instead of "we didn't find an accidental cause, so it must be arson," the engineer can say "we examined the electrical system and affirmatively determined it did not cause this fire" — a far stronger and more honest statement, and one that complements an independent incendiary finding without committing the Willingham error.

The same engineering logic governs explosions, which is why the discipline pairs them with fire. An explosion is a sudden release of energy producing a pressure wave, and forensic engineering reconstructs it from the physical evidence the pressure left: the direction and magnitude of structural damage (which point back toward the blast's center and intensity), the fragmentation pattern, and the nature of the energy source — a fuel-air explosion (e.g., leaked natural gas reaching an ignitable concentration in a confined space) versus a condensed-phase explosive, distinguished by their characteristic damage signatures and residues. As with fire, the analysis is origin-and-cause reasoning — where did it originate, what was the mechanism — conducted by testing hypotheses against the physical evidence, with the same prohibition on backing into a conclusion by elimination alone.

⚠️ Junk-Science Alert The presence of damaged electrical wiring at a fire scene is not, by itself, evidence that the electrical system caused the fire — and treating it as such is a real and recurring error. Because virtually every structure fire damages the building's wiring (the fire melts insulation and beads conductors regardless of what started it), "melted wires near the origin" is a finding present at nearly every fire, which makes it almost worthless as a cause indicator on its own — the same ubiquity problem that made "crazed glass" worthless for arson (Chapter 22, §22.3). Establishing an electrical cause requires affirmatively distinguishing cause arcing from victim arcing and demonstrating a competent ignition mechanism at the origin. Symmetrically, ruling out an electrical cause requires affirmatively showing the damage is fire-caused and no competent electrical ignition source existed — not merely asserting it. In both directions, the conclusion must rest on affirmative, evidence-based analysis of which kind of electrical damage is present, never on its mere presence or absence.

Where does this sit on the validity spectrum? With the rest of fire science (Chapter 22), it spans it. Engineering analysis grounded in electrical theory, materials science, and the documented physics of arcing and combustion — examining the whole system, distinguishing cause from victim arcing on affirmative evidence — is solid, testable, and near the strong end. Eyeball conclusions from the mere presence of melted wire, or from failure-to-find, are the same discredited folklore that executed Cameron Todd Willingham, in a new costume. The reform of fire investigation that Chapter 22 chronicled applies in full force here: the discipline earned its higher standing by getting tested and by learning to reason from affirmative evidence, and the engineer who closes out an accidental cause must meet that same standard.

36.6 The same logic, new domains

Step back and look at what these five domains have in common, because the commonality is the point of the chapter and, in a real sense, the point of the book. We have examined cases where the victim was an elephant, a river, a structure, a road, and a building's electrical system. The objects could not be more different. The reasoning was, in every case, the same — and recognizing that sameness is the deepest thing this book has to teach, because it means forensic science is not a bag of crime-lab techniques but a disciplined way of getting from physical evidence to a defensible, honestly-bounded conclusion, wherever the evidence is found.

Watch the four themes of this book (Chapter 1, §1.7) reappear in domains that have nothing to do with homicide:

• Forensic science excludes more reliably than it proves (Theme 1). Wildlife DNA excludes the wrong species cleanly while attributing origin only probabilistically. Environmental fingerprinting rules out a source confidently while attributing a spill with stated uncertainty. The failure analyst eliminates refuted hypotheses and the fire engineer rules out the electrical cause — both exclusions, both clean. Across every domain, the cleanest, strongest statement is not this one, exactly as Chapter 1 promised, and the homicide lab has no monopoly on that asymmetry.
• Not all methods are equally valid (Theme 2). Every domain spans the validity spectrum. Wildlife DNA is strong; morphological eyeballing is weaker. The compound identification in environmental chemistry is strong; the source attribution is a softer comparison. A fatigue fracture read from clear progression marks is strong; a confident reconstruction of a destroyed, ambiguous failure is soft. The yardstick — is the core claim tested, with a known error rate? — applies identically whether the claim is about a tusk, a tank, or a truck.
• Cognitive bias is the chief threat (Theme 3). The retained engineer told what conclusion the client needs, the reconstructionist told the other driver was drunk, the spill analyst told which company is the target — each is the fingerprint examiner who knew which suspect the detective liked (Chapter 31), and each needs the same safeguard: reason from the evidence first, test the hypothesis that hurts, document so others can check.
• The CSI effect cuts both ways (Theme 4). A jury that overtrusts a confident "chemical fingerprint proves it" is the jury that overtrusted a confident bite-mark match; a jury that dismisses a careful, hedged engineering range because it wanted television certainty is the jury that acquitted because "there was no DNA." Communicating honest uncertainty is a forensic skill in every domain, not a homicide-courtroom afterthought.

And beneath the themes, the deepest grammar of all — the class-versus-individual distinction from the very first chapter (§1.3) — governs everything here. "This is elephant ivory" is a class statement; "this tusk came from this poached carcass" reaches toward the individual. "This is diesel" is a class statement; "this is this tank's diesel" is a probabilistic reach toward a source. "This steel met spec" is class; "this fracture started at this specific flaw" is individual. In every domain, the analyst's discipline is to know how far along the class-to-individual arrow the evidence honestly travels, and to refuse to claim more — the identical discipline that separates honest DNA testimony from a bite-mark examiner's overreach.

🔍 Check Your Understanding 1. Pick any two domains from this chapter and show how each instantiates the exclusion-over-proof asymmetry: name the clean exclusion it can make and the softer, probabilistic attribution it must hedge. 2. The "chemical fingerprint" (§36.2) and the "bite-mark match" (Chapter 16, previewed) both borrow a metaphor of uniqueness. Explain why the environmental chemist's claim can still be more defensible than the bite-mark examiner's, even though both metaphors overpromise — and what each must do to claim honestly.

This is why the chapter sits where it does, near the end of the book. By now the reasoning should feel portable. When you read, in a newspaper, that an engineer has "proven" why a building collapsed, or that a "chemical fingerprint" has "identified" the polluter, or that ivory has been "traced" to a poacher, you now reach automatically for the questions this book has drilled: Class or individual? Consistent-with or proves? What is the error rate, and how do we know? Was the analyst told the answer before they began? Those questions do not care whether the victim is a person, an ecosystem, or a structure. They are the questions forensic science is. The victim changes; the discipline does not.

🗂️ The Case File

Carrow County — closing the accidental door. By the time the forensic engineer is brought into the Mill Creek case, the picture is already firm on two fronts. The autopsy (Chapter 11) established that Marcus Diallo was dead before the fire — no soot in the airways — and the fire investigation (Chapter 22) reached a finding of incendiary cause on affirmative grounds: multiple, separate, unconnected points of origin plus an ignitable-liquid (gasoline) distribution pattern, later confirmed instrumentally by GC-MS (Chapter 23). That finding was built honestly — explicitly not on the debunked indicators that executed Cameron Todd Willingham. But an honest incendiary finding invites an honest challenge, the very one a competent defense will raise: could the fire have had an accidental cause that the investigation simply overlooked or that the fire destroyed? Above all — could it have been electrical? Answering that question affirmatively, rather than by failure-to-find, is the forensic engineer's job, and it is the entry this chapter adds.

What the failure analysis establishes — affirmatively. A forensic-engineering failure analysis of the cabin's electrical system rules it out as an accidental cause of the fire. The analysis does this the way §36.5 requires: not by failing to find an accidental cause (that would be the negative-corpus error of Chapter 22), but by affirmatively examining the wiring and circuits and determining that the electrical damage present is fire-caused (victim arcing) rather than fire-causing (cause arcing) — that the circuitry at the points of origin carried no competent ignition mechanism capable of starting the fire, consistent with a system that was a victim of the fire, not its source. In the book's grammar this is an exclusion: not the electrical system — the cleanest and strongest kind of statement forensic science makes (Chapter 1, §1.6). It independently complements the Chapter 22 incendiary finding from the opposite direction: Chapter 22 affirmatively established that the fire was deliberately set; this chapter affirmatively closes the most plausible accidental alternative.

What this does — and only this. Be precise, as the chapter demands. Ruling out the electrical system closes an accidental-cause alternative; it does not, by itself, identify who set the fire, and it adds no name to the file. It strengthens the staged-homicide picture by removing an innocent explanation for the fire — the accidental-electrical-fire hypothesis is affirmatively eliminated, so the incendiary finding no longer has that competing explanation to contend with — but "the fire was not an electrical accident" is a statement about the fire, not about a person, exactly as "the fire was incendiary" (Chapter 22) was a statement about the fire and not a hand that lit it. No single piece of this case names a suspect; the convergence is still being assembled, brick by brick, toward the capstone (Chapter 39).

Running status. Honest status after this chapter: accidental-cause alternatives closed. Combined with the prior findings, the staged-homicide reading is now firmly supported from multiple independent directions — dead before the fire (Chapter 11), incendiary on affirmative grounds (Chapter 22), accelerant confirmed (Chapter 23), and now the leading accidental cause affirmatively excluded (this chapter). What remains unestablished from this evidence alone: who. Log it in the workbook (Appendix I) as: electrical system affirmatively ruled out as an accidental cause (victim arcing, no competent ignition mechanism at origin); an exclusion that complements — but does not duplicate — the Chapter 22 incendiary finding; no person identified. The accidental door is closed. The hand that lit the fire is still a question for the convergence of the whole file.

Conclusion

The victim is not always a person, and the application of science to legal questions does not stop at the human body. We saw the book's entire logic transfer, intact, into five new domains. Wildlife forensics identifies species and even geographic origin with the same class-versus-individual reasoning and the same DNA science as the homicide lab — strong at its quantified molecular core, bounded mainly by the completeness of its reference databases, and honest in calling a region-of-origin finding an association with a place-type, not a coordinate. Environmental forensics attributes pollution to a source by chemical "fingerprinting," strong in identifying what a compound is and properly cautious in attributing whose it is — a probabilistic comparison governed, like soil and pollen, by distinctiveness and the completeness of the candidate set, and dangerous only when the "fingerprint" metaphor is allowed to promise a uniqueness it cannot deliver. Forensic engineering and failure analysis reason from a failed structure back to its cause by testing hypotheses against physical evidence — origin-and-cause reasoning for things, governed by Kumho Tire, strong when grounded in checkable calculation and affirmative evidence, and subject to the same negative-corpus prohibition and contextual bias as fire investigation. Accident reconstruction reads skid marks and crush damage the way bloodstain analysis reads spatter — genuine physics that yields a speed range, not a speedometer reading, and that constrains what happened without narrating whose fault. And fire-and-explosion engineering brought us back to Chapter 22, where the engineer's affirmative analysis of the electrical system — distinguishing fire-causing cause arcing from fire-caused victim arcing — lets a destroyed scene yield a real conclusion rather than a negative-corpus guess.

In the cold case, that last discipline did the work the file had been waiting for: a forensic-engineering failure analysis ruled out the cabin's electrical system as an accidental cause, affirmatively — not by failing to find a cause, but by demonstrating the electrical damage was the fire's victim, not its origin. That is an exclusion, the cleanest statement in forensic science, and it complements the Chapter 22 incendiary finding from the opposite direction: the fire was deliberately set, and it was not an electrical accident. The accidental-cause alternatives are closed. What no single piece of this — not the autopsy, not the arson finding, not the engineering exclusion — establishes is who. The chapter advanced the book's themes one more time, in domains far from the morgue: exclusion over proof, the validity spectrum, the chief threat of bias, and the two-edged CSI effect, all governing a tusk, a tank, and a truck exactly as they govern a body. The reasoning is portable because it was never about the body in the first place. In Chapter 37 we turn to the forensic science of the living victim — forensic nursing and the evidence collected from those who survive — where the principles you now hold meet a domain that demands they be applied with particular care and humanity.

Key Terms

• Wildlife forensics — the application of forensic science to crimes and legal questions involving wild animals and plants (poaching, illegal trade in protected species, conservation-law violations), centrally through identifying species — and sometimes population or individual, or geographic origin — from biological evidence.
• Environmental forensics — the application of scientific methods to determine the source, age, and responsible party of environmental contamination (what a pollutant is, where it came from, and when it was released), in support of regulatory enforcement, litigation, and cleanup-cost allocation.
• Forensic engineering — the application of engineering principles and methods to investigate the causes of failures of structures, materials, components, vehicles, and products, when those failures cause injury, death, or significant loss and the cause must be established for legal proceedings.
• Failure analysis — the systematic process of determining how and why a structure, component, or system failed, by examining the physical evidence of the failure (fracture surfaces, deformation, materials testing) and reasoning backward to a cause through hypotheses tested against the evidence.
• Accident reconstruction — the application of physics and engineering to determine how a collision or other accident occurred — speeds, paths, positions, and sequence — by analyzing the physical evidence (tire marks, crush damage, rest positions, event-data-recorder data) it left behind.

Spaced Review

1. Explain why a forensic-engineering failure analysis must reach a cause by affirmative evidence rather than by eliminating other causes alone, and name the fire-investigation fallacy (Chapter 22) it would otherwise commit. (§36.3, §36.5; Chapter 22)
2. In the cold case, the fire was found incendiary on affirmative grounds in Chapter 22. How does this chapter's finding — the electrical system ruled out as an accidental cause — complement that finding from the opposite direction without duplicating it, and why is "not the electrical system" an exclusion rather than an inclusion? (Case File; Chapter 1 §1.6; Chapter 22)
3. Recall Locard's exchange principle and the pollen-on-the-floor-mat evidence (Chapters 3 and 13). Explain how wildlife geographic-origin DNA (§36.1) is the same kind of association with a place-type claim, and give the honest verb both should use. (§36.1; Chapters 3, 13)
4. Validity-spectrum question. Environmental forensics is said to be strong at identifying a compound but only probabilistic at attributing it to a source. Place each of those two claims on the NAS 2009 / PCAST 2016 spectrum, and explain why the instrument's precision about what a pollutant is does not transfer to certainty about whose it is. (§36.2; and the spectrum from Chapter 6)
5. Recall Kumho Tire from Chapter 5. Why does a forensic engineer's testimony fall under the Daubert reliability gate even though engineering is not a "science" in the narrow sense, and what feature of a failure analysis is what actually makes the methodology reliable enough to admit? (§36.3; Chapter 5)