Writing a spotting report: structure, log list and photos for your trip report

The spotting day was great: runway direction just right, light behind you, plus a special livery you’d been waiting weeks for. Two weeks later, all that’s left is a folder with 600 photos and a scrap of paper with three registrations. A spotting report captures a day like that, for you and for other spotters. This guide shows you how to build a report or trip report, what a clean log list looks like and how to pick the ten pictures out of hundreds that really show the day.

Writing a spotting report: the short answer

A good spotting report consists of three parts: key facts, narrative and log list, complemented by a small photo selection. The key facts say when and where you were and under what conditions. The narrative explains how the day went and what made it special. The log list soberly documents which aircraft you saw. The photos show the highlights and the atmosphere.

The most common mistake is mixing these layers. If registrations are buried in the middle of long paragraphs, nobody will find them again. And a list with no context at all reads like a database dump. If you separate the parts, every reader can pull out what they need: one just wants to know whether the spot is worth it, another is looking for a specific registration.

Spotting report or trip report?

Both terms are often used interchangeably but mean different formats. Before you start, you should know what you’re writing, because the structure depends on it.

Feature	Spotting report	Trip report
Period	one day or one session	several days, a whole trip
Places	usually one airport, one to three spots	several airports or cities
Focus	traffic, light, highlights at the spot	course of the trip, spots, logistics, often your own flights
Log list	one list for the day	one list per day or airport
Typical length	compact	detailed, with subheadings
Value to readers	spot check, current info	trip planning, inspiration

A trip report is basically a series of spotting reports with a frame around them: travel, accommodation, costs, conclusion. If you’re still planning a trip, the guide Planning a spotting trip helps with preparation. How to save money doing so is covered in Planning spotting trips on a budget.

Structure: how to organize your report

Most successful reports follow a similar pattern. You don’t have to stick to it slavishly, but the order has a reason: readers decide in the first few lines whether the report is relevant to them.

The key facts block in detail

This block is the part experienced spotters read first. Without it, your observations are hard to place. If someone reads that only short-haul traffic came on a given day, they want to know whether you were there in the morning or evening and which runway was in use. A simple template:

Field	Example	Why it matters
Date	Saturday, October 12	The day of the week affects the schedule
Airport	Hamburg	Basis for everything else
Spot(s)	Affenfelsen, later observation deck	Readers can retrace the location
Time window	9:30 a.m. to 3:00 p.m. local time	Puts traffic and light in context
Runway direction	Takeoffs on runway 33 toward the north	Determines what was visible from which spot
Weather	clear, wind from the northwest, cumulus clouds building from noon	Explains image quality and changes in light
Gear	camera, 100–400 mm	Helps judge distances

Give times consistently in one time zone and say which. Flight tracker histories and air traffic control data are often given in UTC, while your camera usually stores local time. If you mix the two, you won’t be able to find movements again later. How runway direction and runway numbers relate is explained in the article Understanding runway direction at airports.

The log list: the backbone of your report

The log list is the part that stays useful the longest. Narratives fade, but a clean list still answers questions years later: When did you first see this registration? Which airline flew which type on this route back then? For the list to do that, it needs a fixed structure.

Column	Required	Example	Note
Time	yes	10:42	always the same time zone
Registration	yes	D-ABCD (example)	capital letters, with the hyphen as on the aircraft
Type	yes	A320neo	fixed spelling or ICAO type designator
Airline	yes	name of the airline	operator, not codeshare partner
Movement	yes	Landing 23	landing/takeoff, with runway if known
Flight number	no	from flight tracker history	only if matched with certainty
Origin/destination	no	IATA code	makes routes traceable
Marker	no	first sighting, special livery	highlights at a glance
Certainty	no	certain / uncertain	separates what was seen from what was assumed

Three rules make the difference between a usable and a chaotic list.

• One line per movement. If an aircraft lands and takes off again two hours later, that’s two lines. Otherwise you can’t say later when you saw what.
• Consistent spellings. Decide on “A320neo” or “A20N” and stick with it. How the short codes are built is covered in the article ICAO type designators explained. For telling similar variants apart, the guide A320neo or ceo? helps.
• Operator rather than marketer. The airline column should list the company that actually operates the aircraft. With codeshares and wet leases, that often differs from the flight number. The difference between callsign and flight number is explained in Callsign or flight number?.

Complete or abridged?

For your own archive, a complete list is almost always the better choice, even if at a big airport it quickly grows to a hundred lines. Only a complete list lets you run analyses later, such as hit rate per spot or the frequency of individual types. What can be gained from such data is described in Analyzing your own spotting statistics.

For the published report you may abridge, for instance to highlights, first sightings and anything that isn’t everyday traffic. But then say explicitly that the list is not complete. Otherwise readers conclude from the absence of a type that it wasn’t there that day.

Staying honest about gaps

Every spotter misses movements: a takeoff behind the hangar, a landing while you were changing the battery. That’s normal. It only becomes a problem when you fill the gaps in afterward from flight tracker data without labeling it. A separate “source” column or a note like “looked up afterward” solves that cleanly. How to compare your notes with ADS-B histories without distorting them is covered in Matching sightings against ADS-B logs.

Capturing properly at the spot

How good your report turns out isn’t decided at the desk but at the fence. If you take clean notes there, you write in half an hour in the evening. If you only photograph, you spend the weekend searching 600 images for registrations.

A proven middle path: at the spot you briefly record time, registration and a keyword note for anything special. You match the photos later by capture time. For that, set the camera clock to the correct time before the spotting day; it saves a lot of guesswork. Tips for quick capture are in Logging sightings quickly at the spot, and the basics of the logbook in the article Documenting sightings. Whether notebook, spreadsheet or app suits you is compared in Notebook, spreadsheet or app.

Choosing photos: story over quantity

Most reports fail at picture selection – not because of bad photos but because of too many. Twenty nearly identical side views of short-haul jets tire any reader. A good report shows a selection that tells the day.

Picture type	Number	What it shows
Spot overview	1	what the location looks like, fence, direction of view
Highlights	3–6	the reason the day was special
Atmosphere	1–3	light, weather, backlight, evening mood
Detail or something unusual	1–2	engine, landing gear, taxi maneuver, ground operations
Comparison	0–2	two types or liveries side by side

The spot overview is often forgotten but is the most useful picture for other spotters: it shows how high the fence is, whether you need a ladder and how far away the runway is. At the Affenfelsen in Hamburg or on the visitors’ hill in Munich, such a picture says more than any description.

Preparing images

• Edit consistently. Similar cropping and similar color rendering make the report feel calm. You’ll find tips on cropping in Cropping aircraft photos properly, and a complete workflow in the Lightroom workflow for aircraft photos.
• Captions with data. Every picture should have registration, type and airline beneath it, and for highlights ideally a sentence of context. That way the picture works even when someone sees it detached from the text.
• Maintain metadata. Registration and type in the image metadata make your archive searchable. How to do it is explained in Captioning photos properly and Metadata for aircraft photos.
• Suitable export size. Forums, blogs and social networks have different requirements. The details are in Export settings for Instagram, forums and websites.

People and rights

Spotter photos inevitably include people: other spotters at the fence, ground staff, passengers on the stairs. In Germany, the Kunsturhebergesetz (Art Copyright Act) sets out when pictures of people may be published without consent. One of the exceptions covers people who appear only as incidental to a location. If a person is clearly the focus, though, you should ask beforehand or blur the face. More in the article People in spotter photos. What’s generally allowed around the fence is summarized in Is plane spotting allowed?.

Writing style: factual, concrete, honest

A spotting report is not a novel, but it isn’t a form either. The best reports read like a conversation among spotters: concrete, with personal impressions and without exaggeration.

• Concrete rather than general. “Backlight on the west side from 2 p.m.” helps more than “the light was bad in the afternoon.”
• Show your own assessment. What was the high point for you? Readers care why something excited you, not just that it was there.
• Admit mistakes. A missed long-haul jet because of the wrong runway direction is instructive for others. Experiences like that make reports credible.
• Use jargon sparingly. Not every reader knows every abbreviation. The plane spotting glossary helps if you’re unsure whether a term should be explained.
• No rumors as facts. If you only heard about an upcoming special flight, say so. How to judge whether a sighting was really rare is shown in How rare is my sighting?.

Where to publish your report

Every platform requires a slightly different format. The core stays the same, but you adapt length, number of pictures and list format.

German-language places to start are presented in the overview German-language aviation forums. For photo series, Instagram for plane spotters is worth a look, and if you want to collect your reports permanently in one place, you’ll find ideas in Creating your own website for aircraft photos. You can connect with other spotters through Finding the plane spotter community.

Template: a framework for your next report

Copy this framework and fill it in after your next spotting day. Over time you’ll develop your own variant.

Section	Content	Scope
Title	airport, date, a highlight	one line
Key facts	date, spots, time window, runway direction, weather, gear	five to eight lines
Introduction	goal and expectation	two to three sentences
Course of the day	chronological or by spot, with photos	three to six paragraphs
Highlights	first sightings, special items	short list
Spot info	directions, parking, fence, light, notes	one paragraph or list
Log list	time, registration, type, airline, movement	as long as needed
Conclusion	assessment and lessons	two to four sentences

Common mistakes in a spotting report

• Key facts missing. Without runway direction and time window, nobody can place your observations.
• Registrations hidden in running text. Anyone looking for a particular aircraft wants a list, not a text search.
• Time zones mixed. UTC from the flight tracker history and local time from the camera in the same column create phantom movements.
• Too many similar photos. Every picture should show something new.
• Highlights exaggerated. Not every long-haul jet is a rarity. If you make every aircraft a highlight, you end up with none.
• Spot notes forgotten. Info on directions and parking in particular is valuable to other visitors. What applies to parking at spotting locations is covered in Parking at spotting locations.

If you’re just starting out, a short report on your first day is a good beginning. How such a day goes is described in Your first spotting day, and Plane spotting for beginners bundles the basics.

Conclusion

A spotting report turns a good day into a memory that helps others too. The formula is simple: key facts at the start, a readable narrative in the middle, a clean log list at the end and a handful of photos that carry the story of the day. The real work happens at the spot. If you note time and registration there, you’re left with almost nothing but writing in the evening.