Aircraft Counting

B

How to identify aircraft type from satellite imagery

Overhead view of a widebody jet's tail and wingspan on an airport apron, with other aircraft and terminal buildings beyond.

If you've ever squinted at a ramp image trying to work out whether that's an A320 or a 777 sitting on stand 14, you already know the problem. From directly overhead, an aircraft loses most of the cues a spotter on the ground relies on. No nose profile, no engine cowling detail, no livery close enough to read. What's left is a shape, a shadow, and whatever context the apron gives you.

Here's what actually holds up when you're working from VHR (very high resolution) imagery, the 0.3-0.5 m per pixel range where most commercial satellite and aerial programs sit today.

The measurements that carry the most weight

Wingspan. This is the single most reliable number you can pull from a top-down image, because it barely changes with camera angle the way length does. A regional jet runs under 30 m tip to tip. A narrowbody like the A320 or 737 family sits in the 34-36 m range. Widebodies start around 50 m and climb past 60 m for the larger 777 and A350 variants. If you can get a clean pixel measurement across the wingtips and you know your GSD, you've got a number you can sanity-check against a type chart.

Fuselage length relative to width. Narrowbodies read as a long, thin cylinder from above, usually six or seven times longer than they are wide. Widebodies look stockier in the same ratio because the fuselage diameter jumps even as length doesn't always track proportionally. This is a softer cue than wingspan, but it's useful for telling apart two aircraft with similar spans.

Shadow length, if the sun angle is low enough. Tail height doesn't show up directly in a straight-down image, but a shadow cast across the apron at a shallow sun angle will trace the vertical stabilizer and sometimes the fuselage outline. This is weather- and time-of-day-dependent, so treat it as a confirming detail rather than a primary one.

Engine count and position. Four-engine aircraft (747, A340, some older 767 derivatives you'll still see on cargo ramps) are the easiest positive ID in the set, because nothing else on a civil apron carries four pylons. Twin-engine widebodies versus twin-engine narrowbodies come down to where the engines sit relative to the wing root and how far out along the span they're mounted, which takes a decent amount of resolution to read confidently.

Widebody vs narrowbody from above: the quick version

If you're trying to sort a ramp fast rather than pin an exact type, wingspan and fuselage width do almost all the work:

  • Span under ~36 m, thin fuselage: narrowbody.
  • Span over ~50 m, visibly wider fuselage cross-section even foreshortened: widebody.
  • Everything in between (regional jets, turboprops) tends to show a shorter fuselage and smaller span together, which keeps it from being confused with either category.

What you generally can't get reliably from satellite imagery alone is the sub-variant. An A320 versus an A321, or a 777-200 versus a 777-300, comes down to a few meters of fuselage stretch that's genuinely hard to separate from measurement noise at 0.3-0.5 m resolution. For fleet tracking purposes, most of what you need is the broad type bucket (narrowbody, widebody, regional, freighter-configured) rather than the exact subtype, and that's the level most apron counts are built to deliver.

Where this gets tedious fast

None of the above is hard to do for one aircraft on one image. It gets tedious when you're trying to do it for every outside base on a daily cadence, across a watchlist of airports, pulling fresh imagery each time and re-measuring by eye. That's the part that doesn't scale with a human looking at tiles.

If you're tracking parked-fleet counts across several fields and don't want to build that measuring habit from scratch every morning, Aircraft Counting turns daily VHR imagery into a dated table of aircraft counts by broad type for the apron you're watching. Worth a look if base activity is something you're already checking by hand.

Start a project

← Back to the blog