Documenting sightings: from notebook to digital logbook

The ballpoint pen jams, the wind flips the pages, and while you are still scribbling the registration of the last landing, the next aircraft is already rolling past. That is how almost every spotter collection begins. If you want to document sightings, sooner or later you run into the question of how to turn full notebooks into a logbook you can search, sort and analyze. This guide shows you which details a sighting really needs, where the typical pitfalls are and how to bring old notes into the digital world without losing data.

Documenting sightings: the short answer

A good spotter logbook records every observation as its own entry with the same fields every time: when, where, which aircraft, which type, which airline. Whether that happens on paper, in a spreadsheet or in an app is secondary. What matters is the structure. A notebook full of running text reminds you of good days, while a logbook with fixed fields answers questions like “Which Lufthansa A350s am I still missing?” or “At which spot do I see the most new registrations?”.

The most important rule is simple: one line per observation. If you see the same aircraft landing in the morning and departing in the afternoon, that is two entries. Only then can you count later how often you have encountered an aircraft.

Why the registration is the core of every sighting

With aircraft you have a big advantage: every civil aircraft carries its identity clearly visible on the fuselage. The registration – for example following the pattern D-A… on large German airliners – identifies exactly one aircraft. How the prefix and the registration mark are constructed is explained in detail in the guide Understanding aircraft registrations, and you will find the prefixes of all countries under Aircraft country codes.

For your logbook that means: type and airline describe a group, the registration the individual aircraft. You see a Boeing 737-800 of Ryanair several times an hour at many airports – it only gets interesting for your collection once you know which of the many aircraft is already in your logbook.

Four identifiers are easily confused. Keep them in separate fields or leave them out deliberately:

Identifier	Example form	Refers to	In the logbook?
Registration	D-A… on the fuselage	the individual aircraft on the current register	yes, required field
Flight number / callsign	Airline code plus number	the route or the radio call	optional, as context
Hex code	six characters, e.g. on flight tracker maps	the 24-bit transponder address	optional, for cross-checking
Manufacturer serial number	Serial number from the manufacturer	the airframe over its whole life	optional, helpful for registration changes

The difference between flight number and callsign is explained in the article Callsign and flight number. The hex code is the transponder’s address, which appears on flight tracker maps as a six-character string. It is assigned at registration and normally stays the same – helpful for confirming a sighting after the fact via flight tracking with ADS-B.

When registrations move around

An aircraft may only be registered in one state at a time. If it is sold or moves to a group subsidiary in another country, it gets a new registration. Some registers also reissue freed-up registrations to a different aircraft later. For your collection that means two things: the same aircraft can appear under two registrations in your logbook, and the same registration can refer to two different aircraft over the decades.

The clean solution: always enter the registration you actually saw, and never correct it to a newer one afterward. If you learn of a change, add the manufacturer serial number in the note. This pays off especially in large groups such as the Lufthansa Group, whose aircraft can move between companies.

The data model: which fields you need

The temptation is big to create twenty columns right away. In practice most of them stay empty. Start lean and only add what you have missed twice.

Field	Required	Example	What you need it for
Date	yes	2026-10-15	Sorting, year and season comparison
Time + time reference	yes	14:32 LT or 12:32Z	Daily patterns, cross-checking with flight data
Airport	yes	Frankfurt	Collection per airport
Spot	yes	Zeppelinheim viewing platform	Hit rate per location
Registration	yes	as read on the fuselage	Identity of the aircraft
Aircraft type	yes	A20N or “Airbus A320neo”	Type coverage, wish list
Airline	yes	Lufthansa	Fleet comparison
Movement	no	landing, takeoff, taxiing, parked	Analysis by runway direction in use
Photo reference	no	file name	Proof, quick retrieval
Confidence	no	certain / uncertain	Reliable statistics
Note	no	special livery, first visit to the airport	Context and search terms

Consistent spellings are everything

Most logbooks fail not because of missing data but because of synonyms. If the same type is “A320neo” once, “A320 Neo” another time and “320N” a third time, your numbers fall apart into three piles. A proven solution is the ICAO type designators from ICAO Doc 8643, which are also used in flight plans: A20N for the Airbus A320neo, B738 for the 737-800, A359 for the Airbus A350-900, B77W for the Boeing 777-300ER, A388 for the Airbus A380. You will find more in the guide IATA and ICAO codes explained.

One catch: ICAO codes only distinguish what matters to air traffic control. Passenger and freighter versions often share a code – for the Boeing 747-8, for example, B748 stands for both. If you want to collect such things separately, add a variant field or write the version in the note. The same goes for places: decide once what your home spot is called and use exactly that spelling.

Date and time: the underestimated source of errors

Write dates in the format YYYY-MM-DD according to ISO 8601, so 2026-10-15 instead of 10/15/26. Because the entry runs from year to day, alphabetical sorting automatically matches chronological sorting – in every spreadsheet and every file system. You can name photo files this way, too.

With the time of day you have to decide. Aviation works in UTC, and flight plans, weather reports and a lot of tracking data use it. If you append a “Z”, the time is clearly marked as UTC. Local time is more convenient in everyday life, but in Germany and many other countries it shifts twice a year because of daylight saving time. Both are fine – just don’t mix them without labeling.

Be careful with photos: the Exif data stores the time set in the camera. If you did not adjust the camera after the clock change or after a long-distance trip, every timestamp is off. A quick look at the camera clock before the outing saves you a lot of guesswork later. And one more note on privacy: cameras and smartphones with GPS often write the capture location into the file as well. That is practical for your logbook, but when you share images online, this data can go along with them.

Notebook, spreadsheet or app?

All three options can represent the same data model. They differ in speed, convenience and analyzability.

Criterion	Notebook	Spreadsheet	Spotter app
Capture at the fence	very fast	cumbersome	fast, with selection fields
Works without battery	yes	no	no
Consistent spellings	pure discipline	discipline plus filters	via selection lists
Search and filter	not possible	good	built in directly
Photo for the sighting	separate	as a file reference	linked directly
Sharing with others	hardly	send the file	community features

The notebook has an advantage no app beats: it works in cold, rain and with an empty battery. Especially for plane spotting in winter that is no minor argument. Many spotters therefore work in two stages – a quick note outside, a clean transfer in the evening. The article Plane spotting apps compared compares what apps are available for capturing sightings.

Digitizing old notebooks

The switch is the moment when collections most often get damaged – not because data is missing, but because things get “tidied up” during the transfer. Stick to a fixed order.

How long this takes depends mainly on the volume and your handwriting. Work it out quickly:

What a clean logbook gives back to you

Once the structure is in place, your logbook answers questions you could only guess at without it:

• Fleet coverage: How many aircraft of an airline have you already seen? With fleets that have many identical types, such as the Airbus A320neo at Lufthansa or the Embraer E190 in regional service, this quickly becomes a collecting goal.
• Spot balance: Which location gives you the most new registrations per hour? Whether Düsseldorf observation deck or Munich Airport visitors’ hill – the logbook tells you.
• Runway direction and light: With the “movement” field you see at which runway direction in use your spot works. If you also note when the light was right, your personal light catalog grows on the side, as described in the guide to the sun position at the photo spot.
• Special sightings: Special liveries, rare visitors and first visits can be found again through the note field. The article Finding special liveries shows where to track down such aircraft.

One side effect surprises almost everyone: the logbook corrects your own memory. Types you felt you saw “all the time” show up only a handful of times, and years slip in your head more easily than you would think.

Common mistakes when documenting

• Lump entries instead of individual entries. “Morning Frankfurt, lots of widebodies” can never be broken down into individual aircraft again.
• “Updating” registrations afterward. Anyone who rewrites old entries to a new registration falsifies the history of the sighting.
• Entering the type by gut feeling. If you are unsure whether it was an A320 or A321, flag the entry or check the type with the guides Recognizing aircraft types and Telling Airbus and Boeing apart.
• Mixing your own and other people’s data. Anything you only saw on a map or in a group gets a source note.
• Managing photos and logbook separately. A uniform file naming scheme with ISO date and registration connects the two. How to edit images afterward is covered in Editing aircraft photos.
• No backup. Notebooks get lost, and so do phones.

Conclusion

Documenting sightings is not drudgery but the step from watching to collecting. A few fixed fields, the registration as the key, ISO date and a clear time reference are enough to keep your logbook usable for years. Whether you work with a notebook, a spreadsheet or an app is a matter of taste – what matters is that you record registrations the way you saw them and leave uncertain things as uncertain. If you are just starting out, the guide Plane spotting for beginners helps you with your first outings.