ARMS and CAFRS to airline applications: keep every total defensible

An ARMS or CAFRS total usually isn't the number an airline application or an FAA form is asking for. That doesn't make your military record wrong; the two are organizing the same flying history under different definitions. The way through is to leave the official record alone, write down every adjustment you make, and build each application view from the same reviewed flights.

Know which layer of the record you are looking at

Military aviation records arrive in layers. A line-by-line export carries the detail, a career summary carries the official cross-check, and source or training forms explain the activity behind both. Treat all three as flight time and you have built yourself a duplicate problem in an afternoon.

• Flight-level history: ARMS, ARTEMIS, Envision, or CAFRS rows that represent individual flights or events.
• Source records: records such as AFTO Form 781 or DA Form 2408-12 that document the crew, mission, conditions, and time for a flight.
• Career summaries: ARMS Flying History pages and the DA 759 family that preserve official cumulative totals.
• Qualification records: evaluations, training completions, and milestone dates that explain when a duty position or qualification changed.

Keep the layers separate. Summaries are for reconciling the detailed record, not for stacking more flights on top of it.

Preserve the military categories before converting anything

Store the original duty, condition, mission, aircraft, and time values first, and derive civilian PIC, SIC, cross-country, and airline presentation from those. Change a conversion preference after that and the historical flight never has to be rewritten.

This is what saves you when an airline wants a different presentation than the FAA or the last employer who asked. You can show the official military total, the exact conversion method, and the resulting application total without keeping three competing copies of the same logbook.

Expect explainable differences between totals

A difference isn't automatically an error. It becomes one the moment you can't explain where it came from. The usual culprits:

• Simulator sessions included in a military summary but excluded from flight totals.
• RPA or UAV time retained in the service record but separated from manned flying.
• Non-pilot crew duties that should not enter civilian PIC or SIC columns.
• Overlapping exports or source forms that restate the same flight.
• Flights present in an official summary but missing from the detailed export.
• Airline-specific additions or presentation rules applied outside the raw logbook.

Build a totals bridge that starts at the official military number and itemizes every exclusion and adjustment. The civilian number at the end is the result of that walk. It does not replace the military total, and it should never be presented as though it did.

Reconcile before choosing an application convention

1. Import the most detailed flight history available.
2. Resolve duplicate or overlapping rows.
3. Compare the remaining flights with the official career summary.
4. Document any summary-only baseline needed to represent missing historical detail.
5. Confirm simulator, RPA, non-pilot, and opted-out time separately.
6. Only then select the civilian or airline presentation you need.

If you create a baseline for an unexplained historical difference, label it clearly with the source summary and covered date. Do not invent individual flights to make a grand total match.

Build the airline and FAA views separately

Airline applications commonly ask for aircraft experience, PIC and SIC treatment, flight counts, recency, and milestone dates. The live portal and hiring airline control the current instructions, so confirm them when you apply. Keep the underlying military flights unchanged while shaping the requested view.

The FAA 8710-1 uses a different category-and-class grid. Use the current form published by the FAA and keep airline-specific presentation rules out of that view. One reviewed logbook can support both outputs without forcing the two totals to look identical.

Prepare the explanation an interviewer can follow

Before an interview, export a package that contains:

• A clean flight ledger with page and period totals, and the export ID printed on it.
• The official ARMS or DA 759 summary used for reconciliation.
• A short conversion-methodology statement.
• A totals bridge showing every material difference.
• The original source files, organized and available if a reviewer asks.

You are not trying to make the differences disappear. You are trying to make every number traceable and every adjustment repeatable, so the conversation is about method instead of arithmetic. If a reviewer wants to confirm the ledger file itself, see how to verify a logbook export.

A repeatable workflow

1. Archive the untouched ARMS, CAFRS, source-form, and summary files.
2. Import detailed flights and review flagged fields.
3. Resolve duplicates before comparing totals.
4. Reconcile against the official career summary.
5. Set the conversion convention for the destination you are preparing.
6. Generate separate airline, FAA, and portable-logbook outputs.
7. Save a dated export before every application or interview cycle.

Continue with the broader military-records-to-airline-applications field guide, or check the current supported record formats.