Flight Ops HQ

Company

Editorial Policy

How Flight Ops HQ researches, writes, and maintains its estimates and guides. Last updated July 2026.

Why we publish

Flight Ops HQ exists so people can understand private aviation costs before they talk to an operator or broker. The why is people-first: help trip planners, assistants, and first-time charter buyers set realistic expectations—not chase search rankings with thin pages or fabricated quotes.

Flight Ops HQ is not a Part 135 operator, broker, or aircraft seller. We publish planning estimates and charter-buyer literacy—not quotes or operational advice.

Who creates the content

Guides, route notes, calculators, and industry stories are researched and reviewed by the Flight Ops HQ editorial team. We are charter buyers' advocates in prose form: we explain how operators and brokers price trips, not how to sell you one.

We are not certificated pilots, dispatchers, or Part 135 operators. When a page touches regulation or safety, we point to primary sources (FAA, IRS, industry associations) and keep claims verifiable. See about for scope and limits.

How we build estimates

Calculators: Built from category hourly bands in our aviation data, estimated block time from distance and cruise speed, and stated fee allowances. Outputs are ranges, not live market prices.

Routes: Distance comes from great-circle nautical miles between representative origin and destination airports, verified with our distance script. Cost ranges use the same calculator math as the charter cost tool. Corridor notes name real airports and seasonal drivers; flagship pages include sourced research blocks where we deepen coverage. Distances are checked against great-circle miles between representative airports (see our route verification script in the repository).

Guides: Written for charter buyers and trip planners. We avoid invented prices; cost statements stay qualitative or tied to on-page calculators. New guides must exceed 1,200 words, cite verifiable regulatory or airport facts, and avoid templated cross-sell bullets.

Industry stories: Summaries are drawn only from the cited news article. Analysis sections are labeled editorial and do not add facts beyond the source.

Automation: Drafting may use AI-assisted tools. A human reviews every page before publish: airport codes, distances, regulatory references, and the rule that estimates are not quotes. We strip templated filler phrases at render time on route pages and block new content that reuses them in CI.

  • We state assumptions on each calculator and methodology page.
  • We use ranges rather than single numbers where the market is a range.
  • We pair every estimate with a disclaimer that it is not a quote.
  • We update dateModified on a page only when content substantively changes—not site-wide for appearance of freshness.

What we will not do

  • We do not publish invented statistics or fake savings claims.
  • We do not show live aircraft availability, which we cannot verify.
  • We do not present estimates as guaranteed prices or offers.
  • We do not publish templated bullet lists reused across dozens of pages (for example generic “guide pairs with” cross-sells or identical Part 135 reminders in every pricing section).
  • We do not index thin secondary route pages until they receive a flagship editorial pass (they remain reachable from the routes hub).
  • We do not let calculator inputs be prefilled through links, so a result always reflects what you entered.

Sources and assumptions

Aircraft categories, speeds, and ranges reflect widely published general characteristics for each class of aircraft. Hourly ranges are broad planning figures that we review and adjust over time. When assumptions change, we update the affected pages and their review dates individually.

Quality bar for new pages

Every new route, guide, glossary entry, or industry story must add corridor-specific or topic-specific value—not keyword variants of an existing template. Before publish we check great-circle distances, airport identifiers, and that pricing bullets name real drivers (season, permits, crew duty, repositioning) instead of boilerplate.

  • Flagship routes need at least six distinct pricing-context bullets after review, named airports, and FAQ answers a real planner would ask.
  • Guides need 1,200+ words, structured checklists where appropriate, and internal links to calculators and peer guides—not repeated “pairs with” sentences in body copy.
  • Stories draw facts only from the cited article; our analysis is labeled editorial.
  • We run npm run verify:content in the repository to catch templated phrasing on new batches and thin flagship pages.

Accuracy and corrections

We review content periodically and welcome corrections. If you find an assumption or figure that looks wrong, tell us through the contact page and we will review it.

Independence

Our explanations are written to inform planning, not to push a specific operator, broker, or program. If we add advertising or partnerships in the future, we will disclose them clearly.

Updates

This policy reflects how we actually work as of July 2026. We update it when our process changes.