ALP Data Tables — Tool Guide

Who It's For & When to Use It

Airport planners assembling or updating an Airport Layout Plan sheet set. Use it when an ALP update needs its data tables rebuilt against the current NASR cycle, when a new ALP needs the full Appendix A.3 table set stood up from scratch, or when a planning study needs a defensible, citation-backed snapshot of airport, runway, and design-standards data in tabular form.

It is built for speed over hand-holding: a planner who already knows the runway design codes can produce the full package in under a minute, with every value carrying its source for the citation trail.

How to Use It

The workspace runs as three numbered steps top to bottom, with an optional Save Project / Load Project… bar above Step 1 (state also autosaves as you work).

1. Step 1 — Source mode. Choose a tab:
   • Auto (NASR) — type an airport identifier (FAA LID or ICAO, e.g. KDEN) into the Airport Identity Bar and press Look Up. On a hit, the bar shows the airport name, ident, elevation, runway count, and a data-source badge. This mode is NASR-only: if the airport is not in the current cycle, you get “not found in NASR — switch to Manual runways,” and if the lookup resolves to non-authoritative OurAirports data, the tool surfaces a warning and refuses it (ALP tables require NASR declared distances and per-end data). Use Manual for those airports.
   • Manual runways — build the runway table by hand with + Add runway (up to 12). Each row takes LE ident, HE ident, Length (ft), Width (ft), Surface, and LE / HE elevation. Enter the field Airport elevation (ft MSL) below the table; length and width must be positive for every runway.
2. Step 2 — Runway design codes. Add one or more rows with + Add design code. Each row carries a Runway id (leave blank to apply to all runways, or name one, e.g. 17/35 or 17) and the design code: AAC, ADG, Visibility (Visual, ≥1 mile, ≥3/4 mile, <3/4 mile), Approach type (— auto, Visual, Non-Precision / IFR Circling, APV, Precision), and a Small aircraft checkbox. These drive the Design Standards rows (via the RDSM) and the Part 77 Approach Surfaces classification.
3. Step 3 — Generate package. Pick a Format (XLSX styled workbook or DXF CAD table block), set a Project name, and review the Package contents preview (Airport Data, Runway Data, Declared Distances, Design Standards, Approach Surfaces, Modifications). Press Generate & download to download the file. The page then renders a provenance echo — result line, controlling standard, design codes applied, assumptions, and the data vintage (FAA NASR cycle date in auto mode plus the AC 13B Chg 1 date) for the citation trail.

Key Features

The tool builds the six ALP data tables required by FAA ARP SOP 2.00 Appendix A.3:

• Airport Data Table — airport identification, ARP, elevation, magnetic variation, and NPIAS role.
• Runway Data Table — per-runway and per-end data (designation, length, width, surface, lighting, marking).
• Declared Distances Table — TORA, TODA, ASDA, and LDA per runway end.
• Design Standards Table — RDSM dimensions selected by each runway's design code (AAC / ADG / visibility).
• Approach Surfaces Table — 14 CFR Part 77 imaginary-surface classification per runway end.
• Modification to Standards Table — emitted as a structure, defaulting to “None Required” for the planner to complete.

Beyond the table set:

• Two source modes — NASR auto by airport identifier, or manual runway entry for facilities outside NASR; the manual fields mirror the NASR data shape so the tables come out identical in structure.
• Per-runway design codes — assignable to one runway or all, driving both the Design Standards and Approach Surfaces tables.
• Two export formats — a styled XLSX workbook or a CAD-ready DXF table block for placement on the ALP sheet.
• Decision-Engine provenance echo — an on-page result block stamping the controlling standard, applied design codes, assumptions, and the data vintage (NASR cycle date, AC edition) after each generate.
• Save / Load projects — named projects plus debounced autosave, so a configuration can be reopened and regenerated against a fresh NASR cycle.

Rows that no data pipeline can supply — critical aircraft / ARC, mean maximum temperature, NPIAS service level, wind coverage, pavement strength — are still emitted with placeholder values, because Appendix A.3 requires those rows to exist on the sheet. The generator surfaces them for the planner to complete rather than silently dropping them.

FAA References

• FAA ARP SOP 2.00, Appendix A.3 — the ALP data-table set: defines the required tables and rows the package builds.
• AC 150/5300-13B (Chg 1, 8/16/2024), Airport Design — the RDSM design standards (App G) selected per runway design code, plus Runway Design Code components and declared distances (App H).
• 14 CFR Part 77 — civil airport imaginary surfaces (§77.19) for the per-end approach-surface classification rows.
• FAA NASR 28-day subscription — authoritative source for airport and runway facts in auto mode, with the cycle date carried on the output for the citation trail.

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. Verify all table contents against current FAA publications and airport records before placing them on an Airport Layout Plan or including them in a submittal.

• NASR auto mode covers airports in the current FAA NASR cycle only (US facilities). It is NASR-only — it does not fall back to OurAirports, which lacks declared distances and per-end data; non-NASR airports use manual entry.
• Several required rows (critical aircraft, mean maximum temperature, NPIAS service level, wind coverage, pavement strength) are emitted as placeholders for the planner to complete — they are not auto-populated.
• The Modification to Standards table is generated as a structure (defaulting to “None Required”); documenting approved modifications remains the planner's responsibility.
• Design Standards and Approach Surfaces rows are only as correct as the design codes you enter in Step 2 — confirm AAC / ADG / visibility before generating.

Tips & Best Practices

• Start in Auto. Look the airport up in NASR first — it stamps the cycle date onto your citation trail and fills the airport/runway facts so you only have to add design codes.
• Apply codes broadly, then override. Leave the Runway id blank on a design-code row to apply it to every runway, then add per-runway rows (e.g. 17/35) only where the code differs.
• Set the approach type deliberately. Leaving it on “— (auto)” defers the Part 77 classification to the engine; pick Visual / NPI / APV / Precision when you know the published approach.
• XLSX for review, DXF for the sheet. Generate XLSX while iterating, then re-run as DXF for the CAD-ready table block once the values are settled.
• Read the provenance echo. After each generate, check the result block's design codes, assumptions, and data vintage — that is your citation trail; transcribe the NASR cycle date and AC edition into the ALP narrative.
• Save the project. Save a named project so the same configuration can be regenerated against the next NASR cycle without re-entry.

Related Tools

• Runway Linework Generator — draws the runway environment (RSA, ROFA, RPZ, Part 77) as CAD-ready linework to pair with the table block (guide).
• Declared Distances — work through TORA/TODA/ASDA/LDA scenarios for a single runway before committing them to the table (guide).
• Exhibit A — the companion property-inventory side of the ALP package.