CACrown ArchivesThe cinema collection
EN/FR
Search
Menu
Research dossier · Places & Architecture

Palcasa Airport

airport in Nicaragua

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 revisionJul 7, 2026
Entity authorityQ25037236 ↗
Source-derived summary

Palcasa Airport (ICAO: MNPA) is an airport serving the town of El Castillo in Río San Juan Department, Nicaragua. The airport is 5.5 kilometres (3.4 mi) north of El Castillo, midway between the small towns of La Palma and Las Colinas. It is surrounded by and supports the palm oil plantations of Palmares del Castillo S.A. (PALCASA).

The Bluefields VOR-DME (Ident: BLU) is located 67.0 nautical miles (124 km) northeast of the airport. The El Coco VOR-DME (Ident: TIO) is located 65.5 nautical miles (121 km) south of the airport.

Editorial summary

Begin with the source’s own compact description: “Palcasa Airport” is airport in Nicaragua. The dossier treats that line as a proposition to test through Palcasa, Airport and airport, not as a finished interpretation.

Editorial reviewA valuable geographic starting point for tracing changing names, boundaries, uses and administrative responsibility. The current 90-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. For this dossier, Palcasa, Airport and airport is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “airport in Nicaragua” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

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 Jul 7, 2026. The linked authority identifier is Q25037236. Authority coordinates are 11.067, -84.410. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.

Critical limits

A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. 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 “Palcasa Airport”, its source revision and the description used here.
  2. Expand the search: follow Palcasa Airport primary sources, Palcasa Airport archive and Palcasa 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 “Palcasa Airport”?
  2. Which authority defined the place, boundary or structure at the relevant date?
  3. What physical evidence or contemporary plan supports the description?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Palcasa Airport” 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.