CONFIGURATION INDEX
| Item | Configuration |
|---|---|
| Document | airportfinder.html |
| Markdown source / build | airportfinder_R02.md / B261109 |
| File revision / build | R004 / B261109 |
| Content revision / build | R001 / B261013 |
| Date | 2026-11-09 |
| Approved source application | SPOTMAP v0.9.9R01 FIX1 |
| Standalone application | n/a |
| Source display / package build | B261013 / 2026101303 |
| Standalone package build | n/a |
| Status | Prepared for project-owner review; not uploaded. |
Generic information
- The offline app help stays available even when not connected to internet.
- The online web help requires an internet connection.
- This is a reference tool only and not a substitute for knowledge, experience or approved operational data; always strictly use, adhere, follow and verify with approved operational data.
- If you do not have a FULL understanding of the tool, do not use it!
How to use the help section
🔴Disclaimer: A disclaimer is a legal statement designed to limit a company's liability or specify the boundaries of a product's warranty. It informs the user about what the product or company is not responsible for, or clarifies that certain information (like third-party software updates) is outside of the company's control. Impact: Legal/Financial. It protects the organization from lawsuits and sets realistic expectations for the product's performance or usage.
⚠️Warning: A warning alerts the user to potential hazards that could result in personal injury, death, severe data loss, or permanent damage to equipment. It is the most critical type of callout and must clearly explain the hazard, the consequences of ignoring it, and how to avoid it. Impact: High. Ignoring a warning can lead to physical harm or catastrophic system failure, or both.
🔼 Note: A note provides helpful, non-critical information to the user. It emphasizes points, clarifies steps, or offers background context that is not essential to completing the main task but improves the user's understanding. Impact: Low. Ignoring a note will not cause harm, damage, or data loss.
INTRODUCTION
AIRPORT FINDER searches a local airport/runway database by distance, direction, surface, and runway length. It also builds an ordered route as you select successive departure airports.
BASIC USAGE
Open TOOLS → AIRPORT FINDER. Airport searches and calculations use local databases (no internet needed, as long as the databases have been downloaded prior use). Apple Maps background imagery needs a network unless suitable tiles are already cached; cached coverage is not guaranteed, but the background imagery is not needed to do airport searches and calculations using the local databases.
1. Import the databases
Tap IMPORT DATABASES on an empty screen, or DATABASE in the controls. Import both files generated as a compatible pair by the SPOTMAP FAA PR/D Builder:
| File | Purpose |
|---|---|
SPOTMAP_US_YYYY-MM-DD_r00X.prddb |
Airport/facility records. |
SPOTMAP_AIRPORTS_YYYY-MM-DD_r00X.afdb |
Airport Finder runway records. |
Use IMPORT .PRDDB and IMPORT .AFDB in either order. The pair becomes active only after validation. Check effective/next-cycle dates and any compatibility message. A newer facilities revision can share the same runway file when the FAA source content and cycle match.
RESTORE LAST WORKING PAIR restores the retained working pair after an import problem. Original Files items remain unchanged. Airport Finder stores its database copies separately from PR/D.
2. Select A, then B
Tap A to select the departure airport and B to select the direction/arrival reference. Type letters within an identifier; prefix matches are placed first. Select the intended airport after checking its name/location. ICAO identifiers are displayed when present; otherwise the FAA identifier is retained.
- A = B selects a circular search around A.
- A ≠ B uses the initial true direction from A toward B for a directional search.
Manually changing A after route history exists asks for confirmation because it starts a new route. Changing B keeps the intermediate route history.
Only US airports (CONUS and OCONUS) are used. Airports from Canada and Mexico are not used in the computation.
3. RADIUS / NM
Tap RADIUS / NM to open the keypad. Enter the distance and tap DONE to apply it. The range is 1–2,000 NM.
For a circular search, this is the maximum distance from A. For a directional search, it sets the target step distance, limited by the A-to-B distance as explained below.
4. TOLERANCES
For A ≠ B, open TOLERANCES to set distance tolerance (0–2,000 NM) and initial-bearing tolerance (0–180°). The normal initial values are ±10 NM and ±10°; check your retained values before searching.
The distance window is centered on the smaller of the selected radius and the A-to-B distance. Bearings are measured from A around the initial A-to-B direction.
For example, with a 200 NM radius, B 80 NM from A, and ±10 NM / ±10° tolerances, the search covers approximately 70–90 NM from A, within 10° on either side of the initial direction toward B. It does not mean a 10 NM corridor along the entire route.
When A = B, tolerances are shown as N/A and are ignored.
For example, A = B would be used to find all the airports that are inside a radius, to define if it is a cross country flight (50NM or more) or not.
5. Runway length, HARD, and SOFT
Choose a runway-length band:
- ANY LENGTH,
- UNDER 1,000 FT,
- 1,000 TO <2,000 FT,
- 2,000 TO <3,000 FT,
- 3,000 TO <4,000 FT,
- 4,000 TO <5,000 FT,
- or 5,000 FT AND ABOVE.
Length bands include their lower endpoint and exclude the upper endpoint. An unknown runway length passes only ANY LENGTH.
- HARD accepts the database's asphalt/concrete/paved classification.
- SOFT accepts the supported turf/grass/gravel/dirt/sand/caliche/coral classification.
- Both may be selected at once. Both off prevents a search.
- Mixed, other, and unknown surface classifications are excluded.
At least one individual runway must satisfy both the selected surface and length rules. One runway passing surface and a different runway passing length does not satisfy that requirement.
6. SEARCH and results list
Tap SEARCH after setting the criteria. Use the adjacent list/count button to open all matching airports, or tap a green airport on the map for details.
In circular mode, every qualifying airport within the radius can be returned, including A itself if it qualifies. In directional mode, B is returned only if it also meets the runway and search criteria. Public and private open airports can be included.
⚠️Warning: A search match is not a determination of airport access, runway availability, aircraft performance, obstacle clearance, or landing suitability. Those checks require applicable current operational information.
⚠️Warning: An airport search match does not guarantee a safe or compliant route. The flight crew remains responsible for verifying and adjusting the route to ensure terrain and obstacle clearance and compliance with airspace restrictions, border-crossing requirements, and all applicable regulations.
7. Read and adjust the map
- Red — selected radius.
- Blue — target arc, tolerance boundaries, and shaded search region.
- Magenta — route and A-to-B direction.
- Green airport icons — matches.
- Gray airport icons — other database airports.
Use STREET or SATELLITE for the background, the fit icon for the search area, and FIT RESULTS for current matches. At wide zoom, nearby icons can cluster and neutral airports can be sampled; the results list remains the place to inspect every match.
The upper-right menu also provides Database Information, Fit Search Area, Fit Entire Route, Show Database Airports, and help. Map lines are split at the date line; the map display cannot represent the poles.
8. USE AS NEXT DEPARTURE and route management
Choose an eligible match and tap USE AS NEXT DEPARTURE. It is appended to the route, becomes the new A, and triggers a new search. B and the filters stay the same. A qualifying airport that is already the current departure cannot be selected again as its own next departure.
Route airports remain visible as magenta dots, with current A and final B labels. Changing search criteria clears/recomputes results but retains route history.
In the menu, Undo Last Next Departure reverses the last route step. Start New Route asks for confirmation before replacing route history. Export first if you need a copy.
9. ROUTE export
The bottom ROUTE control creates KML and TXT together and opens one Files dialog for both. Copies are also retained under AirportFinderRoutes in the app's Documents folder. The TXT lists successive-leg distances and initial true headings; the total uses unrounded leg distances.
The KML contains ordered route geometry, magenta waypoint dots, and a thin dashed magenta line. The symbols/dashes are geometry and require no external icon file. Their apparent size changes with zoom. This control does not offer a KMZ route output.
10. Close, reopen, and check
Tap the top-right X to return to SPOTMAP. The database pair, settings, and chronological route are retained across launches; waypoint coordinates are saved when selected. Search results are recomputed.
RUN ENGINE CHECKS in help runs the tool's diagnostic checks. Its output is not proof that an airport is suitable or that database information is current. Airport Finder does not modify the flight recorder or PR/D's separate database.
ABBREVIATION
- FAA — Federal Aviation Administration.
- FT / ft — Feet.
- ICAO — International Civil Aviation Organization.
- KML — Keyhole Markup Language.
- KMZ — A ZIP archive containing KML and any packaged resources.
- N/A — Not Applicable.
- NM — Nautical Miles.
- PR/D — Point Radial / Distance.
- RWY — Runway.
- TXT — Plain-text file.
- WGS84 — World Geodetic System 1984.
DEFINITION
- Circular search — A runway-filtered search inside a radius around A when A and B are the same airport.
- Directional search — A runway-filtered search inside a distance/bearing window oriented from A toward B.
- Tolerance — The allowed amount on either side of a target distance or bearing.
- Match — An airport meeting the current database search rules.
- Route leg — One segment between successive airports in the ordered route.
- Compatible database pair — Facilities and runway files whose source content/cycle pass the app's validation.
- True heading/bearing — The calculated direction referenced to geographic north; it is not wind-corrected aircraft heading.