Exhibit A Property Analysis — Tool Guide

Coming Soon ARP SOP 3.00 · AC 150/5100-17 · ALL GUIDES

The Exhibit A Property Analysis tool supports the Exhibit ‘A’ Airport Property Inventory Map — the property exhibit that accompanies the ALP set and documents how each parcel of airport land was acquired and what federal obligations attach to it. You enter the runway configuration and a parcel inventory, and the tool overlays each parcel against the airfield design surfaces, cross-checks the deeded acreage, scores the submission against the FAA's own review checklist, and assembles the Exhibit ‘A’ parcel data table — so the data behind the map is checked before the FAA Airports Specialist checks it.

It replaces the usual workflow of assembling the parcel data table by hand, eyeballing which parcels the RPZ and other design surfaces cross, and reading ARP SOP 3.00 line by line to confirm nothing required is missing from the submission.

This tool is built and in pre-release. This guide documents the full workflow as it works today; the tool is gated “Coming Soon” in the catalog while the pre-release window runs.

Who It's For & When to Use It

Airport planners preparing or updating Exhibit ‘A’ property maps for ALP sets and grant compliance. Use it when assembling the parcel inventory for a new Exhibit ‘A’, when an ALP update or land acquisition changes the property picture, or when pre-checking a submission against the FAA review checklist before it goes to the ADO. The workspace runs against your existing runway configuration, so you bring the property data and the tool brings the surfaces and the checklist.

How to Use It

The workspace is a single column with three numbered steps on the left and the live SOP 3.00 Appendix B checklist docked in the right rail. The checklist loads first — its interest types, easement types, parcel statuses, and the 14 review items all come from the API, so they populate the form before you start.

  1. Identify the airport (optional). In the Airport Identity Bar at the top, type an FAA LID or ICAO identifier (e.g. KDEN) and press Look Up. AvPlot pulls the facility name, ident, and elevation from FAA NASR and lists the runways. If NASR doesn't cover the field, a non-authoritative OurAirports fallback banner appears — choose Continue with OurAirports data or Stop and enter runway data by hand. This step is optional; you can skip straight to manual runway entry.
  2. Set up the runway (Step 1). If you looked up an airport, pick a runway from Prefill from airport runway — AvPlot detects the State Plane zone from the ARP, converts the NASR lat/lon thresholds to northing/easting, and fills both ends. Otherwise fill the Low end and High end fields directly: designation, threshold elevation, northing/easting (or lat/lon), runway width, classification (large vs. small aircraft), and the AAC / ADG / TDG / approach type / visibility-minimums design codes that drive the surface dimensions. Set Include Part 77 approach surface to Yes or No, and choose the Parcel coordinate system — Northing/Easting or Latitude/Longitude. When parcels are lat/lon, a State Plane zone field appears and must be filled (it's required for the overlay math).
  3. Enter parcels (Step 2). Each parcel card carries a Parcel ID, a status (current, proposed, released, or disposed), and a ground elevation. Build the boundary in the Boundary vertices grid — add rows one at a time with + Vertex, or paste a block of coordinates (one Y, X pair per line) and click Add pasted. The grid column headers switch between Northing/Easting and Latitude/Longitude to match the coordinate system you chose. Fill the Inventory (ARP SOP 3.00 App B) fields — grantor (5a), interest acquired (5b), deeded acreage (5c), conveyance type (5d), recording reference (5e), easement type (6d), and purpose (7) — and expand Federal obligation & legal data for grant/PFC numbers, federal agreement, release/disposal actions, public-land reference, encumbrances, the legal description, and notes. Add as many as 100 parcels (3–200 vertices each) with + Add parcel.
  4. Analyze (Step 3). Click Analyze parcels. The tool validates that each parcel has at least three vertices and that lat/lon parcels carry a zone, then posts the runway, zone, parcels, and Part 77 flag to the analysis engine and renders the results below.
  5. Read the results. A summary band reports parcel count, parcels on an airfield surface, parcels in an RPZ, easement candidates, acreage-review count, and total computed acres. A Decision-Engine result block follows with the controlling standard, assumptions, warnings, and the data vintage, plus an advisory note on the property-interest indications. Each parcel then gets its own card — the advisory recommended interest with rationale, a deeded-vs-computed acreage check (flagged REVIEW when out of tolerance), a table of every design surface that overlaps the parcel (overlap acres, percent of parcel, surface height above the parcel, and citation), and a list of any missing inventory fields. The right-rail checklist re-renders with each item's pass / needs-attention / manual status.
  6. Export. Once results render, the Exhibit ‘A’ parcel data table (the deliverable) appears at the bottom, and the Copy parcel table and Export parcel table CSV buttons turn on. Both run entirely client-side — copy drops a tab-separated table onto the clipboard for pasting into a sheet, and CSV downloads exhibit_a_parcel_table.csv. Signed-in users can also Save Project and reload named projects; the workspace autosaves as you type.

Key Features

  • Airport Identity Bar with NASR prefill. One lookup pulls facility facts and runway ends from FAA NASR, detects the State Plane zone from the ARP, and converts the threshold coordinates — or falls back to OurAirports behind a blocking, non-authoritative banner.
  • Design-surface overlay analysis. Each parcel polygon is overlaid with the AC 150/5300-13B footprints the SOP 3.00 checklist requires — approach and departure RPZ, RSA, ROFA, runway pavement, and optionally the Part 77 approach surface (anchored 200 ft beyond the threshold per 14 CFR 77.19(d)) — using the same geometry engine as the runway linework, so footprints match the DXF output. Per surface it reports overlap acres, percent of parcel, surface height above the parcel, and the citation.
  • Advisory property-interest indications. Each parcel carries a recommended interest with a rationale and alternatives, drawn from AC 150/5300-13B ¶3.13 and Appendix I. These are advisory only — the determination rests with the sponsor in coordination with the FAA ADO.
  • SOP 3.00 Appendix B checklist. A structured version of the 14-item FAA review checklist runs in the right rail, with data items evaluated automatically (pass / needs-attention) and plan-sheet drafting items flagged for manual review. Items backed by an AC 150/5100-17 content standard carry their citation.
  • Acreage cross-check. The computed polygon acreage is compared against the deeded acreage per parcel and flagged REVIEW when the delta exceeds tolerance.
  • Parcel data table deliverable. The Exhibit ‘A’ parcel data table is assembled from the SOP Appendix B fields, with per-parcel data gaps surfaced, and exported by client-side copy or CSV.
  • Decision-Engine output. Every analysis returns a defensible trail — Result, controlling Standard, Assumptions, Logic/rationale, Warnings, and the dated Vintage (ARP SOP 3.00 · AC 150/5300-13B Chg 1 · AC 150/5100-17 Chg 7 · 14 CFR 77.19).

FAA References

  • FAA ARP SOP 3.00 — FAA Review of Exhibit ‘A’ Airport Property Inventory Maps; Appendix B is the review checklist this tool encodes.
  • AC 150/5100-17 Chg 7, Land Acquisition and Relocation Assistance — Exhibit ‘A’ development and content standards (§1.1.6–1.1.7 and Figure 1-1; SOP 3.00 cites the figure as Figure 1-2 under pre-Chg-7 numbering).
  • AC 150/5300-13B Chg 1, Airport Design — design-surface dimensions used in the overlay analysis (RSA, ROFA, RPZ per §3.2 and ¶3.10–3.12) and the property-interest guidance (¶3.13 / Appendix I) behind the advisory indications.
  • 14 CFR Part 77, §77.19(d) — the Part 77 approach surface footprint overlaid when that option is enabled (inner edge anchored 200 ft beyond the threshold).

Limitations & Disclaimers

AvPlot is technical planning production support — accurate enough for design reports, planning studies, and ALP narratives. It is not a replacement for stamped engineering or construction documents.

  • This tool is not a title search, survey, or legal property determination. Parcel boundaries, interests, and recording references are planner-supplied and echoed into the analysis — never independently verified.
  • Property-interest indications are advisory, drawn from AC 150/5300-13B guidance; the controlling determination rests with the sponsor and the FAA.
  • Exhibit ‘A’ drafting standards (sheet layout, legend, graphics per AC 150/5100-17 Figure 1-1) are checklist items for manual review, not validated by the analysis.
  • Verify all results against current FAA publications and the sponsor's property records before use in official submittals.

Related Tools

  • ALP Data Tables — the data tables that accompany the same ALP set, generated per ARP SOP 2.00.
  • Runway Linework Generator — draws the RPZ, RSA, ROFA, and Part 77 surfaces this analysis overlays, as CAD-ready linework (guide).
  • State Plane Zone Lookup — confirm the SPCS83 zone when your parcels are in latitude/longitude.
  • ARP Lookup — the same FAA Airport Reference Point lookup that backs the Airport Identity Bar.

Tips & Best Practices

  • Look up the airport first. A NASR lookup wires the runway ends and the State Plane zone for you, so prefilling beats typing thresholds by hand — and it keeps the coordinate basis consistent with the surface math.
  • Match the coordinate system to your source data. Set Parcel coordinate system before you paste vertices — the grid headers and the required zone field follow it. Lat/lon parcels will not analyze without a State Plane zone code.
  • Paste vertices in bulk. For surveyed boundaries, paste one Y, X pair per line into the parcel's paste box rather than adding rows one at a time.
  • Treat the OurAirports banner as a stop sign. If the fallback banner appears, the airport facts are community-sourced and non-authoritative — verify the runway data independently before continuing.
  • Resolve every acreage REVIEW flag. A delta between computed and deeded acreage usually means a boundary digitizing error or a stale deed figure — reconcile it before the table goes to the ADO.
  • Clear the missing-field flags. Each parcel lists the SOP Appendix B fields it's missing; fill them so the checklist and the deliverable table are complete before submittal.
  • Remember the indications are advisory. The recommended interest is a planning aid under AC 150/5300-13B ¶3.13 / Appendix I, not a determination — the sponsor and FAA ADO own the call.