What to include in an aircraft photo brief.
An aircraft photo brief gives the operator, owner, crew, and creative team the same pre-shoot picture: mission objective, aircraft status, shot list, location constraints, FBO coordination, deadline, approvals, usage rights, and handoff expectations.
An aircraft photo brief is the work-before-the-work. It is the document that tells everyone why the aircraft is being photographed, who the images need to serve, what is approved, and what should not be solved at the aircraft.
The brief sits before the operating call sheet. It does not replace dispatch, FBO coordination, crew direction, or final visual QA. It gives those later steps a clear source: mission objective, aircraft status, shot list, location constraints, deadline, approvals, and expected handoff.
For a DOM, aviation manager, owner representative, or broker, the value is simple. The photo mission becomes less dependent on memory and more anchored to the aircraft's actual use, approved facts, and business need.
State the mission objective
Start with one mission objective. Is the aircraft being photographed for a fleet page, broker platform, resale package, owner deck, print piece, launch announcement, refresh, or internal archive?
The answer changes every decision after it. A broker upload may need current exterior, interior, and floor-plan views. A website rebuild may need hero options, fleet-card crops, and detail images. A resale package may need condition, document-adjacent details, and a more controlled owner-review path.
Keep the objective practical. The brief should say what success looks like in usable deliverables, not vague brand language. Example: update cabin sequence for broker and fleet-page use, capture baggage/lav/galley proof, and provide two approved exterior crops by the deadline.
Identify aircraft and status
The brief should identify the aircraft in the operator-approved way: aircraft type, model, cabin configuration, base or current location, Part 135 or Part 91 context, and whether any tail number or internal aircraft ID stays internal.
Aircraft status matters because a good photo request can still be wrong for the day. Note whether the aircraft is flying, between trips, in maintenance, waiting on cleaning, changing base, entering or leaving a certificate, listed for sale, or awaiting owner approval.
If the aircraft is represented for charter, the operator should confirm public claims against approved aircraft facts and the relevant certificate-holder path. FAA Part 135 resources support verifying operator and authorized aircraft status; the brief should point teams to the approved source rather than asking marketing to infer it.
Name audience and channels
Every aircraft photo brief should name the audience. A buyer, broker, charter client, owner, DOM, and internal sales team do not need the same proof in the same order.
List the channels before the shoot: fleet page, broker platform, PDF, deck, print piece, email, approved social post, owner packet, or archive folder. Avinode materials show that uploaded aircraft photos and aircraft information help brokers answer questions, so the brief should connect images to facts buyers will evaluate.
Channel clarity also protects scope. If the job is for a broker platform and a fleet page, say that. If it is not approved for social, print, or resale listing use, say that too.
Build the shot list around questions
A shot list should answer real selection questions. Start with exterior hero, exterior profile, entry, cabin overview, seating groups, tables, galley, lav, baggage, flight deck if approved, placards or amenities if approved, and any current upgrade or condition detail.
Then attach intent to each image. The cabin overview explains layout. The baggage image answers trip-fit questions. The lav and galley images reduce broker back-and-forth. Exterior angles confirm aircraft identity and present the airframe honestly.
The brief should also say what not to chase. If a detail is unapproved, misleading, owner-sensitive, condition-sensitive, or not useful for the mission objective, it does not belong on the required shot list.
List location constraints
Location constraints belong in the brief because they shape the creative plan before the operating call sheet is written. Note the FBO, airport, ramp or hangar preference, light direction if known, aircraft access limit, cleaning window, expected aircraft position, and any known neighboring-aircraft or background issues.
FAA ground-handling and vehicle guidance reinforces why this matters. Aircraft movement, ground support equipment, marshalling, fueling, servicing, and ramp traffic operate under local procedures and safety boundaries. The brief should not assume the aircraft can be moved or powered for a better frame.
This section should flag FBO coordination needs without owning them: tug request, GPU or battery cart, cabin power, escort or badge rules, hangar access, vehicle limits, and the operator contact who will approve the next step.
Set contacts and approvals
The brief should name decision owners, not expose private details. Include internal crew contacts, dispatch contact, owner representative, DOM, sales or broker lead, creative lead, and approval owner only in the controlled working document.
Separate who can answer a question from who can approve a change. A crew member may know aircraft state. Dispatch may know timing. An owner representative may approve public-use boundaries. A certificate-holder or operator leader may approve charter-related language.
Owner approval, public-use approval, and usage rights should be visible before the shoot. If an image can be used on a fleet page but not in a resale package, or in an owner deck but not on a broker platform, the brief should say that before files are made.
Define deadline and handoff
Deadline means more than shoot date. The brief should include shoot window, selection review date, first edit date, owner/operator review date, final export date, and the date assets need to reach the website, broker platform, PDF, deck, or print workflow.
Handoff should also be specific: expected crops, image count, file formats, captions if needed, alt text needs, descriptive filenames, version date, and which folder receives approved files. Google image guidance supports descriptive filenames and useful alt text near relevant page content; the brief is where those needs become part of the job.
A deadline without handoff detail creates pressure at the wrong end of the process. Decide in the brief what the finished folder needs to contain.
Add the stop and review notes
The brief should name reasons the work pauses before anyone is standing on the ramp: aircraft movement, passenger need, maintenance, owner direction, weather, airport/FBO restriction, safety concern, crew limit, or mismatch between approved facts and what the aircraft shows.
Review notes are not final visual QA. They are pre-shoot boundaries: avoid owner-sensitive objects, private documents, route clues, unapproved identifiers, cockpit screens if not cleared, maintenance details, and anything that could imply unavailable amenities or authorization.
The operating call sheet and final release checklist can carry more detail later. The brief's job is to make sure the mission begins with the right boundaries.
A good brief keeps creative ambition attached to aircraft reality.
Photo brief note
Brief the work before the ramp gets busy
An aircraft photo brief should be short enough to read and specific enough to guide the mission. It names the mission objective, aircraft status, audience, channels, shot list, location constraints, FBO coordination needs, crew contacts, deadline, approvals, usage rights, and handoff expectations.
That does not make the shoot rigid. It makes the right parts flexible. When the aircraft day changes, everyone can see what matters most and what needs operator approval before changing.
Airside builds photo missions from that kind of brief because aircraft media should respect the operation before it tries to represent it.
An aircraft photo brief should include the purpose of the shoot, aircraft type and status, audience, usage channels, required shots, location, schedule constraints, access rules, owner or operator restrictions, deadline, file handoff requirements, and approval contacts. The brief should be practical enough that the photographer, crew, FBO, and marketing team all understand the same mission.
