The view nobody has

An aircraft lands at a small airfield. If there is a tower, someone writes it in the log. If there is an apron crew, someone writes it on the sheet, and in the office someone types the invoice from both. At a smaller strip there is no tower and no sheet, and the landing is a line in a notebook, a memory, or nothing. The aircraft that has sat on the grass for a month is in the security guard's book, if it is anywhere. Either way the airport hears about it tomorrow, if it hears at all. The region never hears about it.

That last sentence is the one I want to write about. We have spent years on the first, on the airport's own record, and the airport is where the work still begins. But in the last few months I have been asked the same question by people who sit a long way above any one airfield: a planner, an association, a provincial transport executive, the head of operations at an airport group. What is actually happening across our airports? And the honest answer, almost everywhere, is that nobody knows what happened last month on a Wednesday, let alone yesterday.

The number underneath is a guess

Most medium and smaller airports, globally, run on paper and spreadsheets. They have no statistics and no history, because a spreadsheet does not keep history, it keeps whatever was last typed into it. So when a province, a ministry or an industry body wants to know how many movements its airports handled last year, by what kind of flying, in which months, the figure comes from a survey. Someone at each airport fills it in from memory. Someone else adds the surveys up.

Everything downstream is built on that number. Transport planning: which airports are growing, which are quiet, what would be displaced if one closed. Economic development: the case for investing in a field, or the funding application for its runway, argued on activity nobody counted. The climate baseline and the maintenance plan: emissions modelled and runway work scheduled from an estimate of movements rather than counted from recorded landings by aircraft type. Flight training: a school's circuits touch down fifty times in an afternoon, and a count of flights shows one.

None of this is the airport's fault. A field with four staff is not going to run a statistics office. It is a planner's problem, and planners have tried to solve it from the top.

Why the top-down systems failed

Many countries have tried a national system. Report your movements here, every month, in this format. They fail at exactly the airports they were meant to reach, for two reasons that do not go away.

The first is time. Nobody at a small airport has an hour a month to re-key the log into a government form, so the form is filled from memory, late, or not at all. The system then holds a cleaner-looking version of the same guess.

The second is trust, and the airports are right about it. An airport's record is its business. Who lands there, who is based there, what it charges, what it earns. Hand that to an authority or an association and it becomes a comparison table, and then a lever. Airports resist feeding systems like that, and they are right to.

Consent, not command

The way through is the other way round. Do not build the national view and ask the airports to feed it. Give each airport its own record first, because that is the thing it actually wants, and let the view above be assembled from records the airports already keep, by their consent.

The record has become cheap. A phone that reads a registration with its camera and works without signal. A small camera on the apron, or on a pole beside the strip, that counts the aircraft nobody wrote down. A receiver on the roof that hears every transponder. Where there is a tower, its paper strips stay, and each movement is captured digitally beside them. Where there is none, the camera and the receiver do the watching. Pilots declare their own arrivals on a portal before they leave home. Each source feeds one pipeline, and each aircraft becomes one verified movement, counted once.

Then the sharing. An airport joins a region, or an association, or a national picture, only when its own administrator agrees, and it can withdraw that agreement at any time. What travels upward is a pattern, not a figure: how many movements, of what kind of flying, when. Never one airport's numbers beside another's. The region sees itself. The country sees itself. No airport is exposed to its neighbour, and no authority holds a lever it was not given.

That is the view nobody has had. It is not a national database. It is a thousand small records, each owned where it was made, agreeing to be seen together.

What a region learns when it can see

The first thing is how wrong the estimates were, in both directions. Quiet fields that turn out to carry medevac and firefighting traffic every week. Busy fields whose movements were mostly circuits, which the survey counted as flights.

Then the planning gets real. Movements by month and by kind of flying, by airport, with a trend from the first day the record began. An emissions baseline counted from landings by aircraft type and weight band, and the shift as the fleet changes, year on year. The evidence behind a funding case taken from the record rather than from a letter. And for the airport itself, every landing as a wear event: which runway end takes the load, which stands carry the heavy aircraft, when a surface will reach its threshold, so the work is planned into a quiet window rather than found by failure.

Whose country the record lives in

A word on where all this sits, because every planner asks. The record stays in the country it describes. Hosted there, backed up there, under that country's privacy law, and never routed through a commercial flight-tracking service that sends every receiver's data abroad and sells it back. A country that is finally able to see its own airports should not have to ask a foreign company for the picture.