Labeling photos correctly: registration, type, location and date for platforms

The photo is sharp, the light is right, the aircraft fills the frame – and still the email with “Bad Info” arrives. On photo platforms and fleet databases, it is not only what is visible in the picture that counts but also what you write about it. If you label aircraft photos correctly, you have four details under control: registration, aircraft type, location and date. This guide shows you how to determine each of them reliably, avoid typical mistakes and write the details into the metadata so that they are ready for every upload and for your own archive.

The technical side – what EXIF, IPTC and XMP actually are and how keyword hierarchies work – is explained in the article Metadata for aircraft photos. Here it is about practice: which detail goes where, and how you get it right.

Labeling photos: the short answer

A well-labeled aircraft photo clearly answers four questions: which aircraft (registration), which type (type with variant), where (airport or place, ideally as a code) and when (date, ideally with the correct time). Almost always on top of that come the operator at the time of capture and – automatically added on many platforms – the serial number.

The order of work matters more than the tool: first correct the camera time, then read off and verify the registration, then take all other details from a reliable database and finally write them into the metadata. If you reverse this order, you label mistakes right along with everything else.

The registration: read, verify, enter

The registration is the most important entry, because all the other details hang on it. Platforms and databases assign your picture to the right aircraft via the registration. A transposed digit lands your photo with a completely different aircraft – or with one that doesn’t exist at all.

Reading is the first step. Zoom to 100 percent in your image viewer and read the registration on the fuselage, the vertical stabilizer or the underside of the wing. Where it has to appear is explained in the article Where the registration has to appear on an aircraft. Watch out for typical mix-ups: 0 and O, 1 and I, 8 and B look similar at a great distance or in heat shimmer.

Verifying is the second step, and many skip it. Enter the registration you read into a fleet database and compare:

• Does the type stored there match what you see in the picture?
• Does the livery match the stored operator or known photos of the same aircraft?
• Was the aircraft registered under this registration on the capture date at all? After a re-registration, the same letter sequence can later be attached to a different aircraft.

How to look up registrations, history and operators with Planespotters.net is shown in the guide Using Planespotters.net as a fleet database. An overview of further sources is provided by the fleet databases at a glance.

Entering it finally always in the original format with a hyphen, as it appears in the registers: D-AIXA, not DAIXA or d-aixa. For countries without a hyphen in the registration – such as the USA with N-numbers – it is omitted accordingly. How the prefixes are structured is explained in Understanding aircraft registrations.

The aircraft type: family, variant, customer code

For the type there are three levels of precision, and platforms usually expect the most precise one:

Level	Example	What it is good for
Family	Boeing 737, Airbus A320 family	rough classification, usually too imprecise for uploads
Model series	Boeing 737-800, Airbus A320neo	good basis for archive and keywords
Variant with customer or engine code	Boeing 737-8AS, Airbus A320-214	what databases and many platforms show in the type field

At Boeing, the full designation has for decades contained a two-character customer code that identifies the original buyer. A 737-800 ordered by Ryanair is called 737-8AS; the codes of Lufthansa and Condor end in 30, for example on the 747-430. The code stays with the aircraft even if it later changes owners – a used 737-8AS at another airline is still called that. Boeing let the system fade out in the mid-2010s; newer types such as the 737 MAX are listed by the manufacturer without a customer code.

At Airbus, the digit sequence after the hyphen describes the build version and engine. An A320-214 has CFM56-5B engines, an A320-232 IAE V2500. For the spotter that means: you generally don’t read the variant off the picture but take it from the database – at most the engine shape gives a clue.

For keywords and search fields, the ICAO type designator is added: B738 for the 737-800, B38M for the 737 MAX 8, A20N for the A320neo, A359 for the A350-900. These four-character codes are unambiguous and short, explained in detail in ICAO type designators explained. Our profiles of the Boeing 737-800, the Airbus A320neo and the Airbus A350-900 also show you how to tell the types apart in the picture.

Serial number and operator

The serial number – called MSN or CN depending on the manufacturer – is an aircraft’s permanent identity. Unlike the registration, it never changes. Many upload forms fill it in automatically as soon as the registration is recognized. Still, don’t leave the field unchecked: if a registration is reissued, autocomplete can suggest the wrong aircraft. What distinguishes MSN, CN and line number is explained in MSN, serial number and line number.

For the operator, the rule is: enter whoever operates the aircraft at the time of capture – not the lessor and not necessarily the airline whose colors are on the fuselage. If an aircraft is flying on a wet lease, in a hybrid livery or still in the previous owner’s colors, a short sentence in the comments field helps. According to the upload guide, private aircraft go under “Private” at JetPhotos.

For your own archive it is worth saving the operator as plain text and code, for example Lufthansa with DLH or Ryanair with RYR. The difference between IATA and ICAO codes is explained in the guide IATA and ICAO codes.

The location: code, name, spot

For the capture location there are three sensible levels, and a good label uses all three:

• Airport as a code: The four-letter ICAO code is unambiguous – EDDF stands for Frankfurt Airport, EDDM for Munich Airport, EDDH for Hamburg Airport. JetPhotos expects this code in the airport field and rejects entries with an IATA code or special characters.
• Airport as plain text: For captions and social media, “Munich Airport” reads better than EDDM. In the archive it does no harm to save both.
• The spot: Exactly where you stood rarely interests platforms, but it interests you a lot – for example “visitors’ hill” or “Affenfelsen” (Monkey Rock). That way you later find all pictures from the Munich visitors’ hill or from the Hamburg Affenfelsen with one click.

The location is most precise with coordinates. How to add GPS data to photos afterward and what to watch out for when sharing is in the guide Geotagging photos. Special cases such as photos from the aircraft window or from sensitive places are handled differently by the platforms; JetPhotos has its own entries for this, such as “Inflight” or an undisclosed location.

Date and time: the underestimated source of error

The date seems to be the simplest entry, because the camera writes it along anyway. That is exactly the problem: the camera writes what its clock shows – and it is wrong more often than you think.

The capture time is in the EXIF field DateTimeOriginal, in the format year:month:day hour:minute:second – without a time zone. Newer cameras additionally write the time zone into the field OffsetTimeOriginal, for example +02:00 for Central European Summer Time. Older models don’t. Then later nobody knows whether 23:40 was local time, home time or UTC.

Typical sources of error:

• Forgotten time change: The camera is still on winter time in summer or vice versa – all pictures are shifted by an hour.
• Traveling to other time zones: If you spot in Asia or America and leave the camera on German time, evening pictures quickly end up with the next day’s or the previous day’s date in the metadata.
• Clock drift: Camera clocks drift by a few minutes over months. Uncritical for the date, but relevant for geotagging and for matching against flight tracking data.
• Dead battery: After a long failure of the backup battery, some cameras jump back to a factory date.

Correct the time, don’t manipulate it

The correction belongs at the start, before you label anything. In Lightroom Classic there is a function for editing the capture time, with which you shift a whole selection by a fixed amount. With the free command-line tool ExifTool it works by command: exiftool -alldates+=1 folder shifts the capture, creation and modification date of all images in the folder by one hour, and with -= it goes back. The addition -P preserves the file’s modification date. Test such commands on copies first.

The limit is important: you are correcting a technical error of the camera. Deliberately changing a date, for example to pass off an older picture as current, is something completely different. According to its guidelines, JetPhotos treats an altered capture date as manipulation; for sensitive locations the platform in some cases accepts month and year instead of the exact day, but only with an explanation to the screeners.

From raw image to fully labeled photo

With the four details, labeling becomes routine. This is how it goes after every session:

An example of a finished caption: Ryanair Boeing 737-8AS EI-xxx on takeoff, Hamburg Airport (EDDH), October 12, 2026. The “EI-xxx” is only a placeholder here – your caption naturally contains the verified registration. How to set up such templates and keywords in Lightroom is shown in the Lightroom workflow for aircraft photos. How to file the labeled pictures afterward is described in the article Archiving aircraft photos.

Which details which platform wants

You need the four core details everywhere; the specifics differ. Before every upload, check the current rules of the site in question – they are adjusted regularly.

You will find the details for the individual platforms in the respective guides: Uploading photos to JetPhotos, Airliners.net: upload tips, Flickr for aircraft photographers and Instagram for plane spotters. What else leads to rejection is summarized in Common rejection reasons in photo screening.

Common labeling mistakes

• Family instead of variant: “Airbus A320” is too coarse for a database when A320-214 or A320neo is asked for.
• Owner instead of operator: Leasing companies appear in the registers; on platforms the operator belongs in the airline field.
• IATA code in the ICAO field: FRA instead of EDDF leads to a query or rejection on platforms with fixed codes.
• Registration without hyphen or with a space: Search does not find “D AIXA” under D-AIXA.
• Uncorrected camera time: An evening picture from another time zone gets the wrong date – and then no longer matches flight tracking.
• Copy-and-paste errors: If you carry details over from the previous photo, you quickly label the next aircraft with the old registration. Re-check after every aircraft.
• Special livery not marked: Platforms have their own categories for it, the archive its own keyword. How to document liveries cleanly is explained in Collecting and documenting special liveries.

Conclusion

Good labeling is less a question of software than of order: first the time, then the registration, then everything else from a reliable source. If you verify the registration rather than just reading it, take the type down to the variant, save the airport as an ICAO code and correct the date before labeling, you have the right details ready for every platform. With a metadata template and a fixed caption scheme, this becomes a routine that takes only a few minutes after every session.