On November 24, 1971, a man calling himself Dan Cooper boarded Northwest Orient Airlines Flight 305 in Portland, Oregon, paid cash with cheap tickets, and shortly after takeoff hijacked the plane. He passed a note to a flight attendant demanding $200,000 and four parachutes, ordered the crew forward after landing in Seattle, and then jumped into the night over the Pacific Northwest with his loot. Despite one of the most extensive manhunts in FBI history and decades of later speculation, the case remains officially unsolved. This overview draws on the publicly available D.B. Cooper FBI files to outline what is documented, what is not, and why the investigation and its legacy continue to matter.
Key Facts of the D.B. Cooper Hijacking
The core sequence is well established through flight manifests, ransom notes, and law enforcement records. After the midair jump, Cooper disappeared, the money was never recovered, and physical evidence was limited. The table below captures the most verifiable elements and their documented status.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Hijacker identity | Unknown; alias D.B. Cooper used on ticket | Flight manifest, FBI investigation |
| Date | November 24, 1971 | Flight and FBI logs |
| Aircraft | Boeing 727, registration N467US | FBI files, Northwest Orient records |
| Ransom amount | $200,000 in sequentially marked bills | FBI evidence logs |
| Parachutes | Four parachutes obtained; use unclear | FBI interviews, supplier records |
| Landing location | d>Seattle-Tacoma International Airport | Air traffic control and FBI reports |
| Coordinates of likely jump zone | Approximate; calculations vary by source | FBI analysis, expert reconstructions |
The FBI Investigation Overview
Within hours, the FBI took the lead, treating the case as both a kidnapping and aircraft crime. Agents interviewed crew and passengers, tracked the ransom money, and searched the likely drop zone. Initial leads focused on military personnel and aviation workers with relevant skills. Despite thorough canvassing and underwater searches in Lake Washington and the Columbia River, no Cooper was identified with a credible connection to the events. The case file grew with theories, simulated jumps, and speculative profiles, yet no definitive match emerged.
Investigation Steps and Outcomes
The investigation progressed through several phases, from immediate response to long-term review. Early efforts concentrated on the airport, airline staff, and passengers; later years saw the examination of ex-military parachutists, known criminals, and geographic searches. Modern reviews revisited weather data, known aliases, and potential grave or cache discoveries, consistently falling short of conclusive proof.
- Initial response: passenger and crew interviews, document collection
- Ransom tracking: monitoring marked bills and reported sightings
- Search operations: lake and river dives, fugitive sweeps
- Later reviews: re-analysis of radar, weather, and suspect backgrounds
Notable Persons of Interest
Several individuals were scrutinized because of background, skills, or conduct, but none were formally charged. Cooper is believed by many analysts to have had familiarity with aviation or military operations, which shaped suspect selection. Because the FBI file reflects ongoing reviews of multiple names, the list below highlights figures commonly referenced without asserting involvement.
| Name | Relation Noted | Source Type |
|---|---|---|
| Robert Rackstraw | Former Army officer, skydiver; suspect theory | Media reports, FBI summaries |
| Dwight Weiner | Criminal associate; questioned by investigators | Law enforcement records |
| Richard Floyd McCoy | Similar airborne hijacking; comparison case | FBI cross-reference |
The Evidence Landscape
Evidence in the Cooper case is sparse by design. Only a small number of objects were ever recovered, and most documentation is constrained by privacy, ongoing interest, and periodic re-release. The following categories summarize what the FBI file principally contains.
- Ransom money: serial numbers recorded, no confirmed recovery
- Parachutes and gear: manufacturer leads, no final link to Cooper
- Physical traces: minimal from the aircraft and landing sites
- Witness statements: consistent on key actions, limited on identity
- Analytic reports: suspect profiles, flight simulations, geographic models
Why the Case Remains Open
The file stays active because no conclusive identity, recovery, or admission has resolved the central questions. Investigators note that absent a suspect in custody or recoverable money, the case retains provisional status. Public interest and new technology periodically renew review, but the fundamental evidentiary thresholds for an official closure have not been met. As long as meaningful leads or credible confidences emerge, the D.B. Cooper FBI files are likely to be revisited.
Key Takeaways and Practical Context
For researchers, journalists, and enthusiasts, the D.B. Cooper story illustrates how incomplete evidence, high public attention, and technical uncertainty can sustain a long-term investigation. The files offer a structured record of what was done, what was found, and why questions remain. Understanding the distinction between documented facts, investigative steps, and speculative theories helps frame ongoing discussions and future reviews.
- Fact: A hijacking occurred with defined demands and a disappeared suspect
- Fact: The FBI conducted a broad investigation with few definitive leads
- Interpretation: Gaps in evidence enable continued speculation without confirming hypotheses
- Outlook: The case will likely remain open unless new, verifiable information surfaces
In sum, the D.B. Cooper FBI files present a detailed but inconclusive record of a singular airborne mystery. They capture the methods used, the people reviewed, and the limits of available proof. For anyone studying the case, the files provide a durable foundation for analysis while clearly signaling where uncertainty persists.