Identifying an unreadable registration: combining timestamps, flight history and databases

The Airbus came in low and fast, the burst is sharp – only the registration on the tail has melted to mush in the heat haze. Or in the evening twilight you caught a silhouette where you can tell the type but not a single letter. That leaves your logbook missing exactly the detail that spotting is all about. The good news: in most cases you can identify the registration from the photo anyway. You only need three ingredients that you combine cleanly: a reliable timestamp, the airport’s flight history and a fleet database to cross-check.

Identifying a registration: the short answer

You identify an unreadable registration by matching the exact capture time from the photo against the airport’s flight history and confirming the result via features in the picture. The history shows you which aircraft departed or landed on your runway at that minute – including type, airline and registration. If type, livery and time fit only one candidate, you have your registration.

The procedure is always the same: first secure the time, then search in the matching window, then cross-check. Most failures happen in the first step, not the second.

Step 1: What your photo still reveals

Before you search online, look at the picture closely. Even without a readable registration, it holds a lot of information that drastically reduces the number of candidates.

• Type and variant: An A320neo differs from the classic A320 mainly in the clearly larger engine nacelles – Sharklets alone are no proof, since many older A320s carry them too. You recognize a Boeing 737 MAX by the serrated trailing edges of the engine cowling; split winglets, by contrast, also exist on retrofitted 737s of the previous generation. The more precisely you determine the variant, the shorter the list becomes.
• Airline and livery: New or old paint scheme, special livery, alliance livery – such details often clearly separate aircraft of the same fleet.
• Partial registration: Often two or three characters are still recognizable, such as the country prefix or the last letter. How registrations are structured is explained in the guide Understanding aircraft registrations.
• Other titles: Many airlines carry christening names on the nose, some fleets short fleet numbers on the nose gear or the tail. The registration can also be in another place, such as under the wing – exactly where depends on national regulations, more under Where the registration has to be on an aircraft.
• The neighboring pictures: Go through the whole series. A photo shortly before touchdown is often blurry, but one during rollout suddenly shows the registration readable.

If heat shimmer over the asphalt is your main problem, take a look at Avoiding heat haze – that way the registration stays readable from the start next time.

Step 2: Securing the timestamp

The capture time is the key to the whole search. It is in the EXIF metadata of your image file: the field DateTimeOriginal contains date and time of the shot, SubSecTimeOriginal the fractions of a second for bursts, and newer cameras additionally write the time zone with OffsetTimeOriginal. Every photo manager shows you these values; a detailed overview of the fields is in the article Metadata for aircraft photos.

The EXIF time is only as good as the camera clock, though. Three errors occur constantly:

• The clock drifts. Camera clocks drift by minutes over months. At an airport with dense traffic, five minutes of deviation is already two or three other aircraft.
• Daylight saving time is missing. Many cameras do not switch automatically. Then the EXIF time is an hour off from the end of March.
• The time zone is wrong. After a spotting trip abroad, the camera is often still on home time.

The simplest safeguard: at the start of each spotting day, photograph your smartphone display with the current time. The difference between the clock in the picture and the EXIF time of this photo is your correction for the whole day. If you shoot with a smartphone, you hardly have this problem – the phone gets its time from the network.

Converting local time to UTC

Many flight tracker histories and especially the ADS-B replays work in Coordinated Universal Time (UTC). Germany is one hour ahead of UTC in winter (CET) and two hours ahead in summer (CEST). A photo at 14:20 local time in July therefore corresponds to 12:20 UTC.

Step 3: Searching the flight history

With secured time, airport and aircraft type, you go into the history. Two paths lead to the goal.

The airport’s arrival and departure list. The big flight tracker services show a list of past arrivals and departures for every airport, often with type and registration. How to read such boards is described in Arrival and departure schedules for your spotting day. Watch whether the list shows scheduled or actual times: the landing time in the list can differ by a few minutes from your photo time, depending on whether it describes touchdown or arrival at the parking position.

Replay of the live map. Many services offer a playback that replays the situation at the airport for a specific point in time. With ADS-B Exchange, you choose a day in UTC for an aircraft and play the track back at several times the speed. This is especially useful if you photographed from a spot under the approach: you see exactly which aircraft was above your location at your minute. How far back the history goes depends on the service and often on the subscription – free versions usually cover only a short period. So do not wait weeks before evaluating. More on the options is in the guide Looking up an aircraft’s past flights.

If no registration is in the list

Sometimes the history shows only a hex address. This is the ICAO 24-bit address that every Mode S aircraft transmits and that is assigned at registration. Each state has its own address block for this, and the address normally stays with the aircraft as long as it remains in the same register. With the address you find the matching registration in a fleet database or a public register. Background is in ICAO 24-bit address (hex code) and Transponder Mode A, C and S explained.

If an aircraft appears only as an MLAT position, it does not transmit full ADS-B but is located by several receivers via time-difference calculations. Even then the hex address is usually known. How that works is explained in MLAT/multilateration.

Step 4: Cross-checking with databases

A hit in the history is a candidate, not yet proof. For confirmation you combine three kinds of databases.

Fleet databases such as Planespotters.net list every aircraft of an airline with registration, serial number, variant, engines and often with photos. There you check whether your candidate really has the variant, cabin configuration or paint scheme that you see in the picture. You will find a comparison of the offerings under Fleet databases at a glance, and the operation in detail under Using Planespotters.net as a fleet database.

Official registers confirm owner, type and serial number. Some are freely searchable, such as the FAA registry in the US or G-INFO of the British aviation authority – more in British G registrations and the G-INFO register. Other registers release their data only to a limited extent.

Photo archives are the strongest cross-check. If you search there for your candidate, you often find pictures by other spotters from the same day and airport. If livery, antennas, stickers or wear marks match, the matter is clear.

Clue	Source	Reliability
Capture time	EXIF data, corrected for camera deviation and time zone	high if the clock is checked
Airport, runway, type of movement	own notes, GPS data in the photo	high
Type and variant	picture: engines, winglets, fuselage length	medium to high
Candidate registration	arrival/departure history, ADS-B replay	high in light traffic, medium in dense traffic
Hex address	flight tracker raw data, MLAT	high, can be matched via registers
Livery and details	fleet database, photo archives	very high as confirmation
Partial registration	picture	decisive with several candidates

The most convenient way to record the location is directly in the image file – how that works is shown in Geotagging aircraft photos.

Typical pitfalls

Even with a clean method, investigations sometimes go wrong. You should know these situations:

• Aircraft swap: Airlines swap aircraft at short notice. A flight number that according to the schedule should have a particular aircraft may have been flown with a completely different registration. Always rely on the aircraft actually flown in the history, not on planning data.
• Wet lease and foreign aircraft: A flight under an airline’s number may be operated by another company in its livery. Then the livery in your photo does not fit the flight number – a valuable clue, not an error.
• Re-registrations: If an aircraft moves to another country, it gets a new registration and usually a new hex address. Older data sets then list it under the old registration. Background is under Re-registrations.
• Gaps in the data: Not every movement ends up in every history. Military flights, some business jets and flights with blocked data are partly missing or appear without a registration.
• Two identical candidates: If two A320s of the same airline land in the same minute on parallel runways, only the runway, the livery or a partial registration helps. If it stays undecidable, leave it open.

If you regularly compare sightings with live and log data, you recognize such traps faster. The guide Matching sightings against ADS-B logs shows how to do this systematically.

How reliable is your result?

Not every investigation ends in certainty. Classify your result honestly – that protects your logbook from errors that are hard to find later.

Documenting identified registrations properly

Once you have found the registration, enter it – but with a note on its origin. Many spotters keep a separate column or an abbreviation in their logbook for “identified instead of seen” and note the source: history, database, comparison photo. Whether you count such entries in your statistics is your decision; there is no binding rule. All that matters is that you still know in a year how you arrived at it. How to build your logbook overall is described in Documenting sightings: logbook and statistics.

Also write the registration into the image file’s metadata. Then you can find the photo again later with a simple search, and the information is right there when you share it. A practical system for this is shown in Labeling photos properly.

If you want to upload a photo with an identified registration to photo databases or forums, check their rules first. And be transparent: a brief note that the registration comes from the flight history is good manners in the community.

How to keep the registration readable next time

The best investigation is the one you do not need at all. A few habits at the spot save you a lot of follow-up work:

• Shoot the whole series: Do not photograph only the moment of touchdown, but also the rollout or liftoff. Some picture usually shows the registration head-on.
• Jot it down: A keyword with the time on your phone – “A320 new livery, 14:20, runway 26” – makes the later search trivial. Tips for quick notes are under Logging sightings quickly at the spot.
• Read along live: If you have flight tracking open at the spot, you see the registration on approach already. How that works with ADS-B is explained in Flight tracking with ADS-B for spotters.
• Maintain the camera clock: Reset the clock at every switch between summer and winter time and before every trip.

Conclusion

An unreadable registration is a puzzle with few pieces. The most important is time: if camera clock and time zone are right, the airport’s flight history usually leads you straight to a handful of candidates. Type, variant, livery and partial letters in your picture shrink the list further, and fleet databases and comparison photos provide the confirmation. Where two aircraft fit equally well, “open” is the more honest answer than a guessed registration.