CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Birgenair Flight 301

1996 aviation accident in the Atlantic Ocean

Architectural plans, a scale model, maps and brass measuring instruments
Places and architectureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 14, 2026
Entity authoritySource title only
Source-derived summary

Birgenair Flight 301 was a chartered flight by Turkish-managed Birgenair partner Alas Nacionales from Puerto Plata in the Dominican Republic to Frankfurt, Germany, via Gander, Canada, and Berlin, Germany. On 6 February 1996, the Boeing 757 operating the route crashed shortly after take-off from Puerto Plata's Gregorio Luperón International Airport, killing all 189 people on board. The cause was pilot error after receiving incorrect airspeed information from one of the pitot tubes, which investigators believe was blocked by a wasp nest built inside it. The aircraft had been sitting unused for 20 days, and without pitot tube covers in place for the two days preceding the crash.

Editorial summary

The public source identifies “Birgenair Flight 301” as 1996 aviation accident in the Atlantic Ocean. This brief keeps that definition visible, then builds a research path around Birgenair, Flight and aviation.

Editorial reviewMost useful as a place-based finding aid connecting the present description to earlier jurisdictions, maps and built evidence. The current lead gives the account dated anchors—1996—that can be checked directly. The selected authority fields contribute no independent date. Its value is orientation rather than verdict, with Birgenair, Flight and aviation providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “Birgenair Flight 301”, the useful work is to connect “1996 aviation accident in the Atlantic Ocean” to the records capable of establishing context and consequence.

Evidence profile

Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Sep 14, 2026. The first chronological checks are 1996.

Critical limits

Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.

Best used for
  • Historic place names
  • Jurisdictional context
  • Routes into maps and plans
Verify next

Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.

Three-step research path

  1. Establish the record: confirm the title “Birgenair Flight 301”, its source revision and the description used here.
  2. Expand the search: follow Birgenair Flight 301 primary sources, Birgenair Flight 301 archive and Birgenair research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Birgenair Flight 301”?
  2. What physical evidence or contemporary plan supports the description?
  3. Which earlier names or jurisdictions may reveal additional records?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Birgenair Flight 301” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.