B
Reconciling a satellite apron count against a fleet status report

When the apron count from an image doesn't match what's sitting in the fleet status report, the first instinct is to assume one of them is wrong. Usually neither is. They're counting different things, on different clocks, and the gap between them is where the actual reconciliation work happens.
What the two documents are actually counting
A lessor's fleet status report is a position statement built from operator notifications, maintenance records, and whatever the asset management team has logged by MSN. It tells you who's supposed to be holding the aircraft, what status it's carrying (active, parked, stored, AOG), and when that status was last confirmed. It's accurate as of the last update someone made to it, which on a quiet tail could be weeks old.
A satellite apron read is a count of airframes physically present on the ramp on a given day, sorted by broad type (narrowbody, widebody, regional jet, and so on). It gives you type and position at the moment the image was taken, nothing about MSNs, lease terms, or why a given aircraft is sitting where it is.
So right away you've got a report built on reported status reconciled against a count built on physical presence. They'll agree most of the time. The interesting cases are when they don't, because that's usually where a status change hasn't been logged yet, or where an aircraft is parked somewhere nobody expected.
A workflow that actually closes the gap
Start with the status report, not the image. Pull everything the report shows as parked or stored at the base you're checking, group it by broad type, and get a count: how many narrowbodies the report says should be sitting there, how many widebodies, and so on.
Then line that up against the apron read for the same date, or the closest date to it. If the counts match by type, you're done for that base. If they don't, work the difference one of two ways:
If the apron count is higher than the status report, something landed or was repositioned that hasn't made it into the report yet. Ferry flights, early redeliveries, and sub-lease moves all show up on the ramp before they show up in the paperwork. Flag the type and date, and check it against any pending transition you know is in progress.
If the apron count is lower, look for the usual reasons an airframe drops out of an imagery read: it's inside a hangar, it's been towed to a maintenance stand off the main apron, or the image was taken during a brief window when the aircraft was mid-taxi. These are read-timing gaps, not disappearances.
A satellite read sorts by broad airframe type rather than by registration, so tail-level matching stays out of reach and the reconciliation holds at the type-and-base level: "the report says four widebodies parked at this base, the apron shows three." That's a prompt to check which one is unaccounted for, not a conclusion on its own.
When to call the operator instead of re-checking the image
A single off day usually just means a hangar door was shut, cloud cover blocked the read, or the image crop clipped the edge of the ramp. A mismatch that shows up in several daily reads in a row points to something else: a status in the report that's gone stale. At that point the fastest fix is a call or email to the operator or the lease management desk, and running the same imagery again just burns a day.
Where this earns its keep is on the aircraft nobody's actively watching. A fleet with forty active leases doesn't need daily apron checks on the ones flying revenue routes. It needs eyes on the tails parked somewhere between leases, in storage, or coming up for redelivery, where a status report alone leaves you guessing at how long an airframe has actually been sitting. A daily, dated count of what's on the ramp gives you something to check the report against without putting a person at the fence line.
If base-by-base reconciliation is eating more of your week than it should, it might be worth seeing what a standing daily apron count looks like for your watch list.