HN Showcase
Back to browse
PreflightAPI – US airports, weather, NOTAMs and more via one API

PreflightAPI – US airports, weather, NOTAMs and more via one API

by bberisford·Mar 4, 2026·2 points·4 comments
Visit ProjectView on HN

AI Analysis

●●●BangerSolve My ProblemDark Horse

Solves aviation's most painful data problem: FAA's fragmented, slow, locked-down feeds.

Strengths
  • •Unifies six fragmented FAA/AWC data sources (NASR, DOF, ADDS, NMS, d-TPPs, d-CS) behind one normalized REST API.
  • •Real-time NOTAM updates every 3 minutes + daily obstacle patches eliminate stale data risk.
  • •Author is a real domain expert (pilot + engineer); infrastructure built for actual flight planning use case, not generic.
Weaknesses
  • •Free tier (5K calls/mo) is tight for active apps; pricing unclear and may be high relative to hobbyist market.
  • •Adoption risk: niche aviation market; success hinges on builders choosing this over custom FAA scraping.
Category
SaaS
Target Audience

Pilots, aviation app developers, flight planning tool builders

Similar To

Aviation Weather Center API · FlightRadar24 API · CheckWX (weather aggregator)

Post Description

I'm a private pilot and software engineer. I set out to build a 3D VFR flight planning tool — something that would let you visually plan a cross-country flight with real weather, airspace, and terrain.

Before I could build any of that, I had to build an entire data infrastructure first.

FAA airport data comes as fixed-width text files from the NASR subscription, updated on a 28-day cycle. Obstacles are a separate 56-day file with daily patches. NOTAMs require a formal application to the FAA's NMS system — staging approval, then production approval, OAuth2 token management. Weather data from aviationweather.gov comes as bulk XML cache files they'd prefer you download rather than polling their API. Airspace boundaries live behind ArcGIS REST endpoints you have to paginate through with a 10-minute timeout.

I did eventually build the flight planning app — it's fully functional. But it caused problems with a previous employer who considered it competitive, and I lost my job over it. To avoid further legal headaches, I shelved the app and pivoted to the infrastructure underneath it.

That became PreflightAPI. Everything is synced into PostgreSQL with PostGIS by Azure Functions cron jobs — no external API calls happen at request time. The API just serves from the database, so latency stays low and you're not dependent on the FAA's uptime.

What you get with one API key:

- 19,600+ US airports with runways, frequencies, and terminal procedures - Real-time METARs, TAFs, PIREPs, SIGMETs, G-AIRMETs - NOTAMs with spatial queries (by airport, radius, or route corridor) - Airspace boundaries as GeoJSON (Class B/C/D/E, restricted, MOAs, etc.) - 625k+ obstacles from FAA's Digital Obstacle file. - E6B utilities (crosswind, density altitude, wind correction, pressure altitude, TAS) - VFR navlog generation with automatic TOC/TOD waypoints, winds aloft interpolation, and fuel tracking - A composite briefing endpoint — one request returns all weather, NOTAMs, and hazards along a route

I just launched and have one paying customer. Free tier is 5,000 calls/month. Docs: https://preflightapi.io/docs

I'd appreciate feedback on the API design or what's missing or if this is something you'd find useful or interesting :)

Similar Projects