The Disappearance of D. B. Cooper

Disappearance Source Collection

Evidence Dossier

Legacy category: Disappearance

Evidence Dossier: A record proves that a statement, transfer, examination, or result was documented. It does not automatically prove the anomalous interpretation attached to it.

Overview Evidence Timeline Analysis Sources

Date(s) 1971-11-24, 1980, 2016-07-08, 2016-07-12

Location(s) Portland, Oregon, Seattle, Washington, flight corridor between Seattle and Reno

Investigative Scepticism (Scully Score) 7/10

Anomalous Plausibility (Mulder Score) 5/10

Reported Claim The hijacker known as D. B. Cooper disappeared after parachuting from Flight 305 on 24 November 1971, and no definitive identification or fate has been established.

Evidence Evaluation Strength Very strong for the hijacking sequence, ransom, jump, later money recovery, archival record, and official unresolved disposition. Weak for survival claims and named-suspect identifications.

Investigative Assessments

AGENT MULDER ASSESSMENT

"The reported claim remains worth testing against the record: The hijacker known as D. B. Cooper disappeared after parachuting from Flight 305 on 24 November 1971, and no definitive identification or fate has been established. The strongest documented reasons to keep the file open are: D.B. Cooper Hijacking: FBI history page: The alias Dan Cooper, Flight 305 sequence, $200,000 demand, parachute jump, physical tie, ransom-money recovery, and continued uncertainty; 2016 update on the NORJAK investigation: FBI Seattle: The FBI redirected active resources in July 2016 after 45 years and stated that no tip had definitively identified the hijacker. Key unresolved lead: Did Cooper survive the nighttime jump?"

AGENT SCULLY ASSESSMENT

"Evidentiary limitations: Very strong for the hijacking sequence, ransom, jump, later money recovery, archival record, and official unresolved disposition. Weak for survival claims and named-suspect identifications. Note that: D.B. Cooper Hijacking: FBI history page fails to support: It is a modern institutional summary, not the complete investigative file, and its survival discussion is a theory rather than a finding; 2016 update on the NORJAK investigation: FBI Seattle fails to support: The administrative decision does not prove that Cooper died, escaped, or was any named suspect. Documented contradiction: The public name D. B. Cooper became canonical even though the FBI says the hijacker used Dan Cooper and the initials were a press-created myth. Leading conventional hypothesis: Cooper died during or shortly after the jump."

Case Summary

On 24 November 1971, a man using the name Dan Cooper hijacked Northwest Orient Flight 305 after boarding in Portland. He demanded $200,000 and four parachutes, released the passengers in Seattle, and later jumped from the rear of the aircraft at night. The FBI never definitively identified him. In 1980, $5,800 matching the ransom serial numbers was recovered, but the find did not establish his fate. The FBI redirected active investigative resources in 2016 while preserving the evidence.

Evidence Locker

6 inspectable evidence items. Claims and source findings are kept separate.

Complete rendered-text derivative of an official page Local copy hash-verified Complete source

D.B. Cooper Hijacking: FBI history page

Analyst rating: Strong official synthesis of the hijacking, physical evidence, investigation, and unresolved status

“Money recovered in 1980 that matched the ransom money serial numbers.”

Record locationRendered page body, paragraphs 1–12.

Evidence classOfficial investigative-agency synthesis

Relationship to claimProvides the best concise official narrative and labels the ultimate fate a mystery.

Authenticity assessmentThe staged text identifies the FBI canonical URL; intermediary acquisition is disclosed rather than presented as direct-origin custody.

What this supportsThe alias Dan Cooper, Flight 305 sequence, $200,000 demand, parachute jump, physical tie, ransom-money recovery, and continued uncertainty.

What it does not supportIt is a modern institutional summary, not the complete investigative file, and its survival discussion is a theory rather than a finding.

ProvenanceFederal Bureau of Investigation official history page, captured as complete rendered Markdown text.

Chain of custodyThe complete rendered page text was acquired through r.jina.ai because the official origin rejected automated retrieval; canonical and acquisition URLs, response headers, bytes, and SHA-256 are recorded.

Source completenessComplete. The staged text contains the complete rendered article body returned for the official FBI page.
Known gaps: Page layout, scripts, and image binaries are not embedded.; The artifact is an intermediary-rendered derivative, not a byte-for-byte FBI HTML response.

Open Complete Source (Local TXT Document) Download Copy Canonical Agency Record

Complete rendered-text derivative of an official press release Local copy hash-verified Complete source

2016 update on the NORJAK investigation: FBI Seattle

Analyst rating: Strong official source for investigative disposition and the absence of a definitive identification

“none to date have resulted in a definitive identification of the hijacker.”

Record locationSecond paragraph of the official release.

Evidence classOfficial investigative disposition

Relationship to claimDirectly constrains later identification claims and records the end of active resource allocation.

Authenticity assessmentThe staged derivative preserves the official release text and URL; the acquisition intermediary is disclosed.

What this supportsThe FBI redirected active resources in July 2016 after 45 years and stated that no tip had definitively identified the hijacker.

What it does not supportThe administrative decision does not prove that Cooper died, escaped, or was any named suspect.

ProvenanceFederal Bureau of Investigation Seattle Field Office press release dated 12 July 2016.

Chain of custodyComplete rendered text acquired through r.jina.ai, with canonical official URL and intermediary response provenance retained.

Source completenessComplete. The entire rendered press-release body is staged.
Known gaps: The artifact is not a byte-for-byte FBI HTML response.

Open Complete Source (Local TXT Document) Download Copy Canonical Agency Record

Complete rendered-text derivative of an official document-viewer page Local copy hash-verified Complete source

D.B. Cooper Part 01: FBI Vault viewer record

Analyst rating: Official metadata and custody context for one FBI FOIA file, but not the underlying PDF

“The best representation of the files contained within the FOIA Library are provided for viewing purposes.”

Record locationFBI Vault disclaimer and download metadata.

Evidence classOfficial archival metadata page

Relationship to claimDocuments the official FBI archival context and explains why differently sized recovered PDFs were excluded.

Authenticity assessmentCanonical viewer URL and download URL are visible in the staged text; no claim is made that the underlying PDF was acquired.

What this supportsThe FBI Vault identifies a 4,167,160-byte Part 01 PDF and warns that scan quality reflects the originals and scanning efforts.

What it does not supportThe staged viewer page is not the underlying 35-page FBI Vault PDF and does not validate any recovered PDF with a different byte count.

ProvenanceFBI Vault document viewer for D.B. Cooper Part 01.

Chain of custodyComplete rendered viewer text acquired through r.jina.ai after the official origin presented bot protection; the viewer's direct official PDF URL and stated byte count are preserved in the text.

Source completenessComplete. The complete rendered viewer record is staged.
Known gaps: The underlying FBI Part 01 PDF was not acquired because automated access was blocked by the official origin.

Open Complete Source (Local TXT Document) Download Copy Canonical Agency Record

Complete official HTML response Local copy hash-verified Complete source

D.B. Cooper U.S. Attorney case-file highlight: National Archives

Analyst rating: Strong official archive description tying the case to U.S. Attorney file CR-0451 and its digitized records

“The investigative case file contains photographs and the initial sketch of the suspect.”

Record locationOfficial article body.

Evidence classOfficial archive description

Relationship to claimConnects the staged NARA PDFs to the U.S. Attorney case-file series and provides institutional context.

Authenticity assessmentAcquired directly from the National Archives official HTTPS origin.

What this supportsThe archive identifies Case CR-0451, summarizes the hijacking, and describes photographs, a suspect sketch, and FBI/USAF experiments in the case file.

What it does not supportThe modern highlight is descriptive metadata, not proof of any suspect identity or of Cooper's fate.

ProvenanceNational Archives at Seattle official highlights page.

Chain of custodyDirect HTTPS acquisition from archives.gov, retained byte-for-byte as returned, with response headers, bytes, and SHA-256 recorded.

Source completenessComplete. The complete HTML response body returned by archives.gov is staged.
Known gaps: External scripts, styles, and linked image binaries are not embedded.

Open Complete Source (Local HTML Media) Download Copy Canonical Agency Record

Complete image-only official PDF Local copy hash-verified Complete source

CR 72-0451 Cooper, Dan aka D.B.: Significant Case File 1 of 5

Analyst rating: Central primary-document file from the National Archives Significant Case Files series

“Image-only record; use page images as the controlling source.”

Record locationPDF pages 1–110.

Evidence classPrimary official case-file scan

Relationship to claimProvides central primary documentation beyond modern agency summaries.

Authenticity assessmentThe PDF was acquired from the National Archives official media endpoint and passes signature and page-count checks.

What this supportsA complete digitized file unit of contemporaneous investigative and prosecutorial records associated with CR 72-0451.

What it does not supportThe PDF is image-only, has no reliable embedded OCR, and is only one of five file units; individual claims require page-level human review before publication.

ProvenanceNational Archives Catalog medialz object 573478-001-001, Record Group 118.

Chain of custodyDirect HTTPS acquisition from catalog.archives.gov; PDF signature, 110-page count, byte count, response headers, and SHA-256 are independently recorded.

Source completenessComplete. The complete 110-page PDF returned by the official NARA media URL is staged.
Known gaps: It is file 1 of 5, not the complete five-file case series.; No authoritative OCR accompanies the staged PDF.

Open Complete Source (Local PDF Document) Download Copy Canonical Agency Record

Complete image-only official PDF Local copy hash-verified Complete source

CR 72-0451 Cooper, Dan aka D.B.: Significant Case File 2 of 5

Analyst rating: Second central primary-document file from the National Archives Significant Case Files series

“Image-only record; use page images as the controlling source.”

Record locationPDF pages 1–21.

Evidence classPrimary official case-file scan

Relationship to claimAdds an independently acquired, complete supporting primary file to the dossier.

Authenticity assessmentThe PDF was acquired from the National Archives official media endpoint and passes signature and page-count checks.

What this supportsA second complete digitized file unit in the CR 72-0451 record set.

What it does not supportIt does not complete the five-file series and its image-only pages require visual inspection for claim-level use.

ProvenanceNational Archives Catalog medialz object 573478-001-002; catalog NAID 325594129 identifies it as file unit 2 of 5.

Chain of custodyDirect HTTPS acquisition from catalog.archives.gov; PDF signature, 21-page count, byte count, response headers, and SHA-256 are independently recorded.

Source completenessComplete. The complete 21-page PDF returned by the official NARA media URL is staged.
Known gaps: It is file 2 of 5, not the complete five-file case series.; No authoritative OCR accompanies the staged PDF.

Open Complete Source (Local PDF Document) Download Copy Canonical Agency Record

Documented Timeline

1971-11-24: A man using the name Dan Cooper boarded Flight 305 in Portland, demanded $200,000 and four parachutes, released the passengers in Seattle, and jumped after the aircraft departed again.
1980: A young boy found $5,800 whose serial numbers matched the ransom money.
2016-07-08: The FBI redirected resources away from active NORJAK investigation work.
2016-07-12: FBI Seattle publicly announced the decision and said no tip had produced a definitive identification.

Named Participants and Roles

Flight attendants aboard Flight 305, Direct witnesses to the hijacker before the jump. Account basis: Contemporaneous. Witness quality: High. The FBI history page says two attendants supplied nearly identical physical descriptions, but their full statements are not staged here. Evidence: dbc_fbi_history

Contradictions and Record Conflicts

The public name D. B. Cooper became canonical even though the FBI says the hijacker used Dan Cooper and the initials were a press-created myth.
The dangerous jump conditions support a fatal-jump hypothesis, but no staged record proves that Cooper died.
Recovery of $5,800 confirms part of the ransom's later location but does not identify Cooper or establish where the rest went.
Many named suspects have been promoted publicly, while the FBI's 2016 update says no definitive identification resulted.

Conventional Explanations

Cooper died during or shortly after the jump.
Evidence for: The FBI notes a non-steerable parachute, unsuitable clothing and footwear, wooded terrain, darkness, and no evidence that Cooper was an experienced parachutist.
Limits: No body or parachute is staged as recovered, and the FBI presents death as a possibility rather than a conclusion.
Evidence: dbc_fbi_history
Cooper survived and avoided identification.
Evidence for: No definitive identification or remains are reported in the staged official summaries.
Limits: Absence of identification is not affirmative proof of survival, and the recovered ransom fragment does not establish his later movements.
Evidence: dbc_fbi_history, dbc_fbi_2016_update

Evidence Stance Matrix

Hypothesis	Stance	Rationale	Evidence IDs
Cooper died during or shortly after the hazardous nighttime parachute jump.	Supports	The FBI lists multiple conditions that made the jump hazardous, but does not state death as a finding.	dbc_fbi_history
Cooper survived the jump and concealed his identity and most of the ransom money.	Inconclusive	No definitive identification is reported, but that absence does not demonstrate survival.	dbc_fbi_history, dbc_fbi_2016_update
A named later suspect was Cooper, despite the FBI's 2016 statement that no definitive identification had been established.	Challenges	The FBI's 2016 disposition states that no tip had resulted in definitive identification; McCoy is specifically described as ruled out in the history page.	dbc_fbi_history, dbc_fbi_2016_update

Missing Evidence

Verified remains, parachute, or personal effects tied to the jump
Such evidence could establish survival or death and narrow the landing area.
A definitive identity supported to criminal-proof standards
The FBI expressly said no tip had yielded the necessary proof.
Most of the $200,000 ransom
Only $5,800 is identified as recovered in the staged official summary.
NARA Significant Case Files 3 through 5
The bundle stages two complete file units, not the entire five-file series.
Underlying FBI Vault Part 01 PDF
The official viewer metadata is staged, but automated acquisition of the PDF was blocked by the FBI origin.

What Remains Unresolved

Cooper's identity
The FBI reported in 2016 that no tip or technique had produced a definitive identification.
Cooper's survival after the jump
The official history discusses hazardous conditions but reports no conclusive remains or recovery.
Meaning of the recovered ransom fragment
Matching serial numbers establish provenance of the bills, not how they arrived there or what happened to Cooper.

Investigative Hypotheses

Cooper died during or shortly after the hazardous nighttime parachute jump.
Cooper survived the jump and concealed his identity and most of the ransom money.
A named later suspect was Cooper, despite the FBI's 2016 statement that no definitive identification had been established.

Open Questions

Did Cooper survive the nighttime jump?
How did the recovered $5,800 reach its discovery location?
Would the remaining three NARA file units materially change the evidentiary picture?
Can any future physical evidence establish identity to a criminal-proof standard?