HMD Aviation Start a brief
Start a brief

Sector · Municipal airports

A public and administrative layer for municipal airports

Make airport information easier to navigate and organize the non-critical workflows that connect tenants, visitors, vendors and municipal teams.

Prepare a project brief Explore every sector
Four light aircraft parked in front of an airfield hangar
Licensed illustrative photography. No client or operator relationship is implied.
Primary conversationAirport manager, municipal administrator or economic-development lead

Buyer guide

Municipal airport website design for visitors, tenants and the public owner.

A municipal airport website serves several distinct audiences: people researching the facility, current tenants, prospective businesses and community members. Each needs an identifiable information owner and a clear next step. The project should connect approved airport content with the municipality's existing processes while making the boundary between public information and operational instructions easy to understand.

Decisions to make before commissioning

  • Separate airport-owned information from services provided by tenants or an FBO. Make the responsible organization visible wherever a visitor could otherwise contact the wrong team.
  • Map public enquiries to the municipality's approved channels. Establish who handles noise questions, facility requests and records enquiries without implying that the website itself determines an official response.
  • Agree accessibility, content review, retention and procurement requirements with the municipal owner. Confirm the source of public documents before selecting a publishing or intake platform.

Public layer · website first

What clients and stakeholders need to see.

  • Visitor, tenant and business-development information
  • Approved facilities, access and community content
  • Noise, records or general enquiry routing
Explore aviation websites

Proposed administrative tools

What the team needs to control.

These are possible build scopes to review against your existing systems. Operational decisions remain with authorized people and authoritative records.

  • Tenant and vendor administration
  • Facility request and document workflows
  • Public-enquiry triage
  • Reporting assembled from approved municipal systems
Explore operating systems

Intake and delivery

A process shaped around Municipal airports.

The initial discussion uses public material and redacted examples. Access to live systems follows an agreed scope, responsible reviewers and an explicit test plan.

  1. 01

    Inventory public information

    Review current facility, tenant and community pages with the airport and municipal content owners. Identify conflicting or outdated material.

  2. 02

    Design the routing map

    Specify visitor, tenant and business-development journeys, including the existing municipal process each one must reach.

  3. 03

    Test public tasks

    Verify mobile navigation, accessible document links and synthetic requests that need redirection or a municipal reviewer.

Authority boundary

Human and operational authority stays where it belongs.

HMD does not provide air traffic control, emergency response, airport operational control or safety-management determinations.

Possible starting points

Choose the intervention the evidence supports.

01Website or revampPublic clarity and qualified enquiry02Operational diagnosticCurrent state and test plan03Bespoke system buildAdministrative workflow and evidence04Ongoing supportWork and terms to be agreed in writing

Questions before a project

Municipal airports: frequently asked questions.

Can the airport site connect to municipal systems?

A link or integration can be scoped with the municipality's technology and records owners. The review must establish approved interfaces, access, data retention and the system that holds the official record. Existing municipal processes need not be replaced.

Can the website publish operational airport information?

Only approved material should be published, with its source and update responsibility established. HMD does not provide air traffic control, airport operational control or safety-management determinations. Public content cannot substitute for authoritative operational sources.

How should airport and FBO pages differ?

Airport pages explain the facility, tenants, public-owner processes and community information. FBO pages describe that provider's approved commercial services. Clear cross-links help visitors reach the right organization without merging their responsibilities.

Related decisions

Follow the handoff across sectors.

U.S.-first commercial work, with international engagements available where the operating context and content can be reviewed. Read the localization standard for market-specific work.

FBO website design

Give a commercial handling provider its own service and enquiry journey within the airport ecosystem.

For the broader method, read how HMD scopes and tests a project and the human-authority and data boundaries before sharing project material.

Start with context

Describe the operation, the present handoff and the result you need.

Do not send credentials, passenger information, maintenance records or confidential operational data in the initial brief.

Discuss Municipal airports