Sputnik Digital Effects

American
Helicopter Charters

Eighty source pages. Every FAA heliport on one map. One hundred ninety-two indexed routes live.

helicoptercharters.us is an independent reference for people planning whole-aircraft helicopter charters in the United States. Sputnik Digital Effects migrated the complete content library into an Astro collection, built a distinct visual system around it, and then built the Heliport Atlas: the first and only public resource to put every operational heliport in the country on a searchable map with its FAA record, a public API, and an AI guide that reads it.

Open the live site Review the build
The American Helicopter Charters website displayed on a laptop at a beachside table
Live sitemap192 indexed routes
Content source80 Markdown pages
Heliport Atlas5,675 FAA heliports
Atlas pages55 states + 47 metros
Interface system20 Astro components
PresentationLight + dark themes
01The brief

Make deep reference material feel useful before the first paragraph.

The project already had a complete editorial map. The problem was presentation: dozens of substantial source pages needed one modern system without flattening every page into the same generic article template. The second problem arrived later: the question readers ask most, where a helicopter can actually land, had no complete public answer anywhere.

The rebuild gave the site a new American Helicopter Charters identity and a content model that understands category hubs, charter explainers, planning resources, and destination guides. The design moves between dark aviation photography and warm reading surfaces while the code keeps those page families on one shared rail.

  • Astro application architecture
  • Validated content collection
  • Full-site Markdown migration
  • Responsive design system
  • Heliport Atlas data pipeline and map
  • Public read-only heliport API
  • Huey AI guide integration
  • Search and analytics setup
PositioningIndependent charter reference
Public scopeUnited States
Publishing modelMarkdown and FAA data to static Astro routes
Commercial postureNothing on the site is for sale

The live Astro build across its homepage, Heliport Atlas, resource directory, long-form reading template, and destination system.

American Helicopter Charters The charter desk: A full-viewport opening establishes the independent reference position, national scope, and whole-aircraft subject immediately
The charter desk A full-viewport opening establishes the independent reference position, national scope, and whole-aircraft subject immediately
American Helicopter Charters The Heliport Atlas: Every operational United States heliport clusters on a brand-styled MapLibre basemap with search, near-me lookup, and category filters in the rail
The Heliport Atlas Every operational United States heliport clusters on a brand-styled MapLibre basemap with search, near-me lookup, and category filters in the rail
American Helicopter Charters An Atlas record card: A deep link by FAA identifier opens the facility card with pads, surface, elevation, ownership, and the owner contact a charter operator needs
An Atlas record card A deep link by FAA identifier opens the facility card with pads, surface, elevation, ownership, and the owner contact a charter operator needs
American Helicopter Charters The resource hub: Six planning references branch from a visual directory with concise descriptions and a dedicated editorial reading surface
The resource hub Six planning references branch from a visual directory with concise descriptions and a dedicated editorial reading surface
American Helicopter Charters Part 135 guide, light mode: The long-form template keeps dense regulatory guidance readable with a stable article column and a persistent contents rail
Part 135 guide, light mode The long-form template keeps dense regulatory guidance readable with a stable article column and a persistent contents rail
American Helicopter Charters Part 135 guide, dark mode: A first-party theme switch carries the same hierarchy into a low-light reading mode without splitting the content system
Part 135 guide, dark mode A first-party theme switch carries the same hierarchy into a low-light reading mode without splitting the content system
American Helicopter Charters Destination system: Market pages pair destination-specific hero art with the same reusable article shell and contextual navigation
Destination system Market pages pair destination-specific hero art with the same reusable article shell and contextual navigation

Systems review Astro production build + Heliport Atlas

One source for the content. One system for the experience.

The source remains readable Markdown and the FAA's own data file. Astro handles validation, templates, media, transitions, and the public route inventory around both. Editors can work on the subject without touching component code, a new FAA cycle refreshes the Atlas without anyone editing prose, and the interface can change without rewriting the library.

Sys 01

Content architecture

Eighty Markdown source pages enter one validated collection, then Astro turns that source and the Heliport Atlas data into the complete public route system.

  • One content collectionEvery page shares the same eleven-key front matter contract, with section and page type providing the distinctions
  • Zod validationTitles, slugs, publication state, related pages, and metadata are checked before the static build can finish
  • Dynamic routeOne Astro route renders the category, charter, resource, and destination page families without duplicating templates, and the Atlas adds its own data-driven routes beside them
  • Markdown transformsThe pipeline promotes hero media, rewrites cross-links, builds figures, and turns approved question blocks into accessible FAQ accordions
Sys 02

Design system

The interface uses an American chart-and-poster language that fits the subject without borrowing the look of another helicopter property.

  • Twenty shared componentsNavigation, reading rails, cards, CTAs, theme controls, identity pieces, and the Atlas map and nearby-heliport strips share one implementation
  • Content-aware templatesReference guides prioritize reading while category and destination pages give their hero imagery more room
  • Self-hosted typeArchivo carries the interface and Source Serif 4 is reserved for long-form article prose
  • Persistent themesThe light and dark presentations retain the visitor choice as Astro transitions between pages
Sys 03

Responsive media

Large aviation photography reaches the browser through an image pipeline built around the viewport instead of one oversized source file.

  • Responsive source setsAstro emits multiple widths for each hero and card image so small screens do not inherit desktop payloads
  • Modern formats firstAVIF leads the picture source, with WebP and JPEG fallbacks for broad browser coverage
  • Stable dimensionsGenerated width and height attributes reserve the media box before an image arrives, protecting the page from layout shift
  • Poster-first videoThe homepage is useful before its optional hero motion loads, and the video never blocks the first view
Sys 04

Motion system

Movement is progressive enhancement. The content remains complete without JavaScript and motion preferences are honored.

  • Astro view transitionsInternal navigation can change pages without the visual reset of a traditional full reload
  • CSS-first revealsNative scroll-driven animation handles the common reveal path where the browser supports it
  • Focused GSAP useGSAP is reserved for continuous parallax and numeric interpolation rather than owning every transition
  • Reduced-motion pathVisitors who request less motion receive finished content states with no parallax choreography
Sys 05

Discovery

Every public page leaves the build with the technical signals a reference site needs to be found and understood.

  • Generated sitemapThe live sitemap currently carries 192 indexed routes, 104 of them Heliport Atlas pages, and excludes the internal style guide
  • Shared head componentCanonical URLs, descriptions, social cards, and first-party font preloads stay consistent across the site
  • Structured public factsOrganization and page-level schema identify the publisher and subject, and the Atlas publishes Dataset schema with its FAA source, license, and cycle date
  • Measurement installedGoogle Analytics and Search Console verification are deployed without changing the independent editorial position
Sys 06

Heliport Atlas

Every operational heliport in the United States, taken from the FAA source file and served through a searchable map, crawlable state and metro pages, a public API, and the Huey AI guide.

  • FAA NASR data buildA Python pipeline reads the FAA 28-day APT_CSV cycle, keeps the 5,675 operational heliports, classifies each one, and emits the schema, CSV, SQLite build, and cycle date in one run
  • MapLibre GL mapClustered GeoJSON over a brand-colored vector basemap generated from VersaTiles, with search, near-me geolocation, category and heavy-lift filters, and exact record links by FAA ID
  • Read-only public APIA PHP endpoint over PDO serves points, record detail, ranked search, and nearest-facility queries from MySQL in production and SQLite in development, cached per FAA cycle
  • Crawlable index pagesFifty-five state and territory pages, 47 curated metro pages, a public-use list with CSV download, and a hospital helipad study are built as real HTML from the same dataset
  • Huey integrationThe AI guide resolves a ZIP or city, calls the same public API, and adds nearby non-emergency records as planning leads with the access and landing-permission caveat intact
02The Heliport Atlas

Every heliport in the country, on one map, with the record behind it.

The FAA registers 5,675 operational heliports in the current cycle. Only 56 are open to the public. Before the Heliport Atlas, no public resource showed all of them in one place with the facts a charter planner needs. Now one does. It is the first and only resource of its kind.

The data pipeline reads the FAA's 28-day NASR cycle directly, so a refresh is a download and one command rather than a hand-built workbook. The result feeds three surfaces at once: a MapLibre map that clusters every pad over a brand-colored vector basemap, a read-only public API for points, detail, search, and nearest-facility queries, and crawlable state, metro, public-use, and hospital pages rendered as real HTML from the same dataset. Each record opens by FAA identifier, carries pads, surface, lighting, elevation, ownership, and the owner contact, and repeats the planning caveat that landing permission comes from the owner, never from a map.

Huey, the site's AI guide on the shared Sputnik chat platform, reads the same API. Give it a ZIP or a city and it adds nearby non-emergency records to a charter referral as planning leads with exact Atlas links. A competitive gap analysis the owner ran with Google Gemini in September 2026 found Google already citing helicoptercharters.us in AI overviews for high-intent queries such as landing permissions on private property, golf resort charters, and FBO tarmac transfers, alongside legacy private jet brokers, on the strength of its operator-informed, non-salesy authority. The Atlas is that authority made inspectable.

Coverage5,675 operational heliports, 56 public use
SourceFAA NASR, refreshed every 28 days
Map engineMapLibre GL over VersaTiles vector tiles
Data servicePHP read-only API, MySQL with SQLite fallback
Crawlable pages55 states, 47 metros, public-use CSV
03The portfolio lineage

Related expertise. A separate product.

The subject benefits from years of helicopter-industry work, but the site was built for its own reader and its own editorial job.

American Heavy Lift Helicopters explains industrial external-load operations through a steel-and-field visual language. SKYNET proves the studio can operate charter search systems at network scale. American Helicopter Charters takes neither template. It is a national planning reference with an Astro publishing architecture shaped around long-form reading, and the Heliport Atlas gives it a data product no competitor publishes.

That separation matters. A content system should carry the subject and audience, not advertise the framework that produced it. The same principle guides Sputnik's broader website design and development work.

Industry contextHelicopter charter planning
New architectureAstro content collections
Original systemDedicated identity + components
Original data productThe Heliport Atlas

Have a content library that needs a real publishing system?

Bring the source material and the business goal. Sputnik Digital Effects can turn both into a fast, maintainable site that is ready to grow.

Open project channel