Stop paging through archive tiles to find out what changed on the apron.
Airfield Activity counts aircraft by type on the apron and in the revetments of a named airfield, and flags new runway and shelter work, from VHR imagery on a daily cadence. You get a dated running log and a T0/T1 clip for each change.
- GSD
- ≤0.5 m VHR
- Cadence
- Daily
- Platform
- VHR satellite / aerial
- Spectral
- RGB
The morning check
You open the airfield in the globe or the archive viewer, step back through dated tiles until you find the last usable pass, and count what is parked. Then you do it again for the pass before, to see whether the number moved. The tally goes into your own spreadsheet.
A new hardstand or a lengthened shelter line only registers if you remember what the tile looked like last time. When a colleague asks what changed since yesterday, you are rebuilding the answer from screenshots and hoping the dates line up.
The same watch, run two ways
01Finding the latest pass
- Archive tiles
- Open the viewer, page through dates, work out which tile is the newest usable one for that airfield.
- With Airfield Activity
- Each day's log entry carries the date of the pass it was built from. If there was no usable pass, the entry says so.
02Counting what's parked
- Archive tiles
- Count aircraft on the apron and in the revetments by eye, and type them from memory or from a reference sheet.
- With Airfield Activity
- A tail count by type for apron and revetments, one line per pass in the running log.
- Still yours
- Deciding what an unusual type or number means for your assessment.
03Spotting new construction
- Archive tiles
- Flip between two dates and try to catch a new shelter, a lengthened runway or a fresh hardstand.
- With Airfield Activity
- Runway and shelter construction is flagged day over day, with a T0/T1 clip of the ground before and after.
04Keeping a citable record
- Archive tiles
- Screenshots and a spreadsheet you built yourself, with dates you hope you noted.
- With Airfield Activity
- A running CSV with the date, the count and the change type for every entry. Each row points to its pass.
05Choosing where to look harder
- Archive tiles
- Whichever airfield you had time for, or whichever one somebody asked about.
- With Airfield Activity
- The change flags show which days on which airfield deserve a closer look before you task anything.
- Still yours
- Reading the imagery yourself, and the tasking request itself.
What arrives with each pass
Everything is tied to a named airfield, and each item is dated to the imagery pass behind it.
- Log entry
Daily tail count
Aircraft by type on the apron and in the revetments, for that day's pass. It replaces the hand count and it is the line you cite in order-of-battle tracking.
Counting what's parked - Log entry
Change log
Runway and shelter construction flagged day over day. Each flag names the change type and the date it first showed.
Spotting new construction - T0/T1 clip
Split-view imagery
For every flagged change, the earlier and later imagery side by side, so you can check the flag against your own eyes in seconds.
Choosing where to look harder - CSV
Running CSV
Date, count and change type for each entry, cumulative from the day you start. It opens in a spreadsheet or loads into your own tracker.
Keeping a citable record
From a named airfield to a daily log
You name the site once. After that the log grows each day there is a usable pass.
- Once
Name the airfield
Give us the airfield, or a boundary around it if you want the dispersal areas and outlying shelters in scope.
- Every day
Daily pass, cloud permitting
A VHR optical pass over the site. If cloud or a revisit gap leaves no usable pass, that day is logged as a gap.
Counts and change detection
Aircraft are detected and counted by type. Compared with the previous usable pass, new runway or shelter construction is flagged.
Log and clips delivered
The day's entry goes into the running log and CSV, with a T0/T1 clip for each flag. You review it at the start of your cycle.
What the archive viewer still does better
Read these before you build a briefing on the log.

Daily depends on the sky
Cadence is a daily target. Cloud cover or a gap in revisits can skip a day, and the log shows that day as a gap rather than repeating the last count.
Type is a class, not a tail number
Detection is by aircraft type. It doesn't identify individual airframes or read tail numbers. At 0.5 m or finer, larger aircraft can be counted and sorted by type. A small drone may be missed. Close variants of one type are the sort of call your analysts still make by eye.
Presence, not intent
A count shows what is parked. It doesn't tell you why, and it doesn't replace your own reading of the imagery. The log gives you counts and flags, not verdicts.
Not live
Data follows imagery delivery and processing. It is a daily log, not a live or continuous feed, and we don't promise an hour it will land.
Only what's under the frame
Aircraft inside closed shelters or under cover can't be counted. Construction under way is flagged when it shows on the surface.
Switch if
- You watch a short list of named airfields and the daily tile-paging eats your morning.
- You keep a running tally for order-of-battle tracking and want each count dated and tied to its pass.
- You want change flags to tell you where to point your closer analysis first.
Stick with the archive viewer if
- You need tail-number-level identification of individual aircraft.
- You need live or sub-daily coverage.
- You expect a verdict on intent. This is a log of counts and flags.
Before you switch
Is this daily, every day?
Daily is the target. It needs a usable, cloud-free pass, and cloud or revisit gaps can skip a day. The log marks a skipped day plainly.
What counts as "by type"?
Aircraft type as classified from VHR imagery, sorted into the types your desk cares about. It isn't tail-number identification.
Does it replace our imagery analysts?
No. It is a first look that shows where to spend analyst time. The T0/T1 clips let your team check every flag.
How do we check it against our own counts?
Run it alongside your hand tally for the first weeks. Where a count differs from yours, send us the date and we'll go through that pass with you.
How soon after capture is the log updated?
It follows imagery delivery and processing. It isn't instantaneous, and we won't give a delivery hour on this page.
Can we watch more than one airfield?
Yes. Each airfield is tracked and logged separately.
Can it feed our tracker or GIS?
The running log comes as a CSV, and the clips as imagery. There is no direct integration with a tracker; CSV loads into most.
Who owns the outputs, and what about the imagery licence?
Your list of airfields stays yours. Rights to the outputs and the licence on the imagery behind them are written into the project agreement before the first day runs.
How is it priced?
It depends on how many airfields you watch and for how long, so we quote once we know the list. There's no price list on this page.

Name the airfield and we'll scope the daily log.
Send the airfield, or a few of them, and how you track them today. We'll come back with what a daily log for that site would look like.