Media plan for a new charter base or fleet addition.

Start with approved operating facts

The launch should begin with the facts a Director of Operations would want checked before the first public line is written. Is the aircraft approved for charter? Is the base airport public? Who can approve owner-use limits? What can sales say about availability, positioning, baggage, Wi-Fi, pets, catering, and international use?

Create one master launch sheet before photography, design, email, or social work begins. It should list aircraft type, approved identifier, base airport, operating entity, charter status, cabin configuration, amenity notes, owner approvals, internal contacts, sign-off owner, and the first day the material may be used.

This keeps marketing from getting ahead of the operation. A polished launch that creates calls to dispatch for basic clarification is not a launch. It is another source of friction.

Build a launch timeline, not a post

A useful launch timeline has phases: pre-arrival facts, photo window, website update, broker packet, internal sales materials, announcement, and follow-up QA. Each phase should have an owner and a deadline.

Pre-arrival work can start before the aircraft reaches the base or before the market is announced. Draft the aircraft page, base page, one-pager, broker email, sales deck slide, and internal FAQ early. Leave placeholders for final photos, but do not wait on photography to define the message.

The announcement should be late in the sequence. It should point toward completed assets: live aircraft page, current broker files, clear quote contact, approved photos, and sales material that matches what the public sees.

Protect the photo window

Aircraft media work has to respect the aircraft schedule. A fleet addition shoot may need exterior light, cabin reset, galley prep, lav presentation, baggage access, aircraft power, crew coordination, and FBO ramp approval. None of that should be solved casually during a turn.

Separate the exterior and cabin priorities. Exterior work needs clean ramp positioning, permission for the background, and enough room for web, broker, deck, and print crops. Cabin work needs time for detailing, seat alignment, tables, lighting, galley, lav, baggage, and approved cockpit access if that belongs in the package.

The shot list should match the launch assets, not the photographer's favorite frames. Capture hero exterior, three-quarter exterior, base-context exterior, entry, cabin wide, primary seating, tables, galley, lav, baggage, detail views, and any aircraft-specific proof needed for brokers.

Publish the website update before the announcement

A fleet addition needs more than a news post. It needs a live aircraft page or fleet card that lets a broker or direct buyer qualify the aircraft quickly: category, aircraft type, base airport, seating, cabin layout, baggage guidance, galley and lav notes, Wi-Fi or connectivity context, images, and inquiry path.

A new charter base needs a location or base page with real local proof. Name the base airport, explain the service area with restraint, show relevant aircraft availability, provide the correct contact path, and include proof of presence only when it is true: local team, recurring aircraft presence, FBO coordination, hangar access, maintenance support, or a defined operating footprint.

Avoid thin local pages built only around city keywords. They may read like SEO, but they do not help sales if they fail to explain what the operator can actually support in the market.

Make the broker packet usable on day one

Broker-facing material should be ready when the aircraft or base is commercially usable. The broker packet should include approved photos, aircraft one-pager, cabin layout where available, amenity list, baggage notes, base airport, quote contact, operational caveats, and any company material approved for broker use.

Update broker platforms, aircraft marketplace profiles, scheduling integrations, and internal quote tools from the same source of truth. If photos, amenities, base, or availability are split across separate systems, assign one person to verify them against the master launch sheet.

The broker should not need to ask whether the aircraft page, PDF, and marketplace profile refer to the same current aircraft. If that question appears, the launch packet is not finished.

Launch day should remove questions from sales, not hand new ones to dispatch.

Operator launch note

Update sales material before the first outreach

Internal material is part of the media plan. Update the sales deck, one-pager, email templates, CRM snippets, phone notes, quote language, broker follow-up, and internal FAQ before the announcement goes out.

The internal FAQ should answer the questions the website will not carry in full: owner limits, preferred missions, repositioning notes, operating caveats, who approves exceptions, what not to say publicly, and where the current assets live.

Sales language should stay useful and restrained. Say what the aircraft or base helps with. Do not promise routes, pricing, response times, nonstop missions, or broad availability unless operations has approved that language for normal use.

Use announcement channels as distribution

Email, social, PR, and news posts should distribute the launch, not carry the whole launch. A good announcement points people to an aircraft page, base page, broker packet, or sales contact that already answers practical questions.

The message can stay simple: what changed, where it is based, what aircraft or market it affects, who it helps, and how to inquire. If the post needs a long explanation to make the launch useful, the underlying assets are probably incomplete.

Send targeted broker outreach after the public announcement. Ask what is missing. If multiple brokers ask the same question about baggage, Wi-Fi, owner approval, repositioning, or base support, update the public and internal materials.

Keep the fleet page from going stale

Many operators handle launch day well and let the page decay afterward. The aircraft leaves the certificate, changes base, gets new soft goods, adds connectivity, receives owner-use limits, or gets a new photo set, while the site and PDF keep telling the old story.

Put review dates in the launch plan. At 30 days, update FAQs based on real inquiries. At 60 days, remove 'new' language if it no longer helps. At 90 days, check website copy, broker-platform data, aircraft photos, one-pagers, sales deck slides, and quote templates against the current operation.

Keep a current folder and an archive. The launch is not complete when the announcement posts. It is complete when the materials keep helping sales and brokers after the first wave of attention passes.

Run a 30-day rollout

Days 1-5: confirm operating facts with operations, sales, dispatch, owner services, and marketing. Build the master launch sheet, approval list, asset list, and stop words for claims that are not approved.

Days 6-10: draft the aircraft page, base page, broker packet, one-pager, sales deck slide, email announcement, internal FAQ, and shot list. Coordinate FBO access, line crew support, aircraft power, detailing, and pull-out timing.

Days 11-20: capture and finish media, publish website updates, update broker profiles, sync internal materials, and verify the inquiry path. Days 21-30: announce, follow up with brokers, review inquiry quality, and patch missing answers in the packet, page, and sales scripts.