Filed under RAF Squadrons and Operations Records: A Method Guide
Where should you start looking?
Published histories are useful orientation, but they are secondary sources written after the event. Use them to find dates and questions, then check the claims that matter against the operations record book or the service record.
If the first search returns a crowd of same-name results, narrow by dates before you narrow by anything else: dates cut a crowd faster than spellings do. Do not trust a result because it is the only result. A single result with one matching filter is a lead that needs a second record, not a conclusion. Keep the question narrow. A search for everything about a person returns nothing usable, while a search for one dated fact returns something testable.
Working through it in order
Treat each step as a test with a possible negative result. A step that can only confirm is not a test, and a research plan made of confirmations is a story, not a timeline. Do the unglamorous steps first. Fixing names, numbers and dates feels slow, and it is what makes every later step possible. If a step produces nothing, record that nothing. A documented negative result is part of the research, and it stops the same step being repeated blindly. Write the reference down before you read the record, not after. A reference noted after reading is a reference half remembered.
- Take the posting dates from the personal file before opening any unit record.
- Open the operations record book for those dates only, and note its reference.
- Check names, ranks and roles in crew or personnel lists against the personal file.
- Use station records and published histories only after the unit record for those dates has been read.
How do you read what you find?
An entry that gives a town but no county, or a camp but no town, is deliberately vague or locally obvious. Local knowledge, not a global search, usually settles it. If an entry puzzles you, date it first and interpret it second. Most misreadings here come from carrying a later meaning backwards.
Where an entry is routine, say so in your notes. Routine entries matter precisely because they are routine: they show where a person actually was, not where a story puts them. If a word is illegible, look at the same word elsewhere in the file. Clerks repeat words, and a clear instance elsewhere can unlock an unclear one.
Dead ends to expect here
A photograph, a medal, or a story that points to a unit the records do not support is a prompt for one more check, not evidence that the records are wrong. Note dead ends in the timeline itself, with dates. A timeline that shows where the trail went cold is more honest, and more useful, than one that jumps the gap.
- A squadron disbanded or renumbered, breaking a simple number trail.
- An operations book that is thin or missing for the exact dates.
- A crew list that gives initials rather than full names.
- A published history that fills gaps without saying so.
What to open after this one
Cross-check, rather than collect. One record confirmed by a second, independent record is worth more than five records that all repeat the same source. The strongest timelines are short and referenced. Resist the urge to add unreferenced detail at the end of a session, when checking discipline is weakest.
The next record in the chain is usually the one for the same dates in a different record set, not the next date in the same record set. Let each dated entry earn its place before the timeline grows.
Primary sources for this guide
This guide keeps its claims general and points to the official holders, so the holder itself is the place to check the current position. It is general educational information only, not personal professional advice, and it offers no record lookup service and no determination of any individual's service.