When the data became valuable.
ACARSd began as a free Linux radio-decoding project. A few years later, the same live aircraft data had become useful far beyond plane spotting — for identifying flights, reconstructing aircraft movements and, eventually, supporting passenger-rights claims.
The problem: one flight, several identities.
Operational aviation identifiers were not always the public flight numbers a passenger would recognise. An ACARS message could contain a cryptic operational callsign rather than something simple such as LH601. Turning that identifier into a route and public flight number was one of the hardest enrichment problems in the early ACARSd database.
According to KjM's recollection, a supporter eventually pointed him to a Dutch website that maintained exactly such translations. The programmer's response was immediate: automate it. A script fetched the data four times a day.
This anecdote is preserved as a first-person memory. The surviving ACARSd source independently confirms that flight-number translation tables and automated database updates became an important part of the system.
The letter from the Netherlands.
Then came a letter from the people behind the Dutch data source. They invited KjM to Amsterdam — explicitly to talk before involving lawyers. At that point, he did not know that the people he was about to meet were behind EUclaim. The first meeting took place in a small, smoke-filled office. The message was clear: repeatedly harvesting their data was not acceptable.
KjM did not travel alone. His long-time friend Jürgen H. accompanied him to Amsterdam. Jürgen H. spoke excellent English and had often joined him on trips. With only one year of English at school, KjM was perfectly capable of discussing the technical side, but having a trusted friend there was invaluable whenever a phrase or nuance became difficult.
The meeting did not end with a cease-and-desist. It ended with an exchange — still without the full identity and business behind the Dutch operation being apparent.
Translation data for a live ACARS stream.
Instead of scraping the translation table, ACARSd would receive updated data directly after changes. In return, the Dutch partner received the live aircraft-message stream gathered by the ACARSd infrastructure.
Three months later: the name EUclaim appears.
KjM remembers being invited back only a few months later. This time the setting was completely different: instead of the small, smoke-filled office, they entered a large, modern operation. Only at this second meeting did it become clear that the company behind the cooperation was EUclaim, working with passenger-rights claims.
Jürgen H. was with KjM again for the second visit. When the scale of the operation — and the identity of EUclaim — finally became apparent, Jürgen summed up the situation rather more bluntly:
“Meyer, they really fucked you.”
KjM just laughed. His answer was simple:
“I’m happy. They’re happy. Everything is fine.”
And that was genuinely how he saw it. ACARSd received the flight-number translation data it needed without scraping. EUclaim received an independent live stream of aircraft messages. ACARSd was a hobby project, not a business venture; the fact that the data had become commercially valuable did not make the exchange feel unfair to its author.
The reason for the interest in ACARSd data now made sense. Independent aircraft movement data could help establish what had actually happened to a delayed flight. Data gathered by hobby receivers had acquired legal and commercial value. Looking back, keeping EUclaim's identity out of the first meeting also seems rather clever: first resolve the data dispute and establish whether a mutually useful exchange was possible; reveal the larger business context later.
The data had become gold — or, more accurately, money.
The Martinair case: a remarkable match in the public record.
A surviving Dutch court judgment documents a case between EUclaim B.V. and Martinair Holland N.V. concerning flight MP 815. The flight was scheduled for 5 July 2007 from Amsterdam to Calgary, onward to Edmonton and back to Amsterdam, using a Boeing 767. It was actually operated on 6 July — every sector more than 24 hours late.
That is strikingly close to KjM's independent recollection of an early documented EUclaim case: Martinair, Canada and roughly one day of delay. Contemporary reporting from February 2008 likewise describes EUclaim pursuing Martinair over an Amsterdam–Calgary flight delayed by more than 24 hours.
The court record proves the EUclaim/Martinair MP815 case and its 24+ hour delay. It does not identify ACARSd as the evidence source, nor does the published judgment establish KjM's remembered detail that ACARS data disproved an aircraft defect and exposed a planning failure. Until an original EUclaim communication, data extract or case exhibit is recovered, that connection remains a strong but unproven historical match.
An independent 2010 source confirms EUclaim used ACARS/ADS-B data.
A 2010 European Commission study on air-passenger rights describes EUclaim's evidence system in unusually specific terms. It states that EUclaim combined timetable, aviation-authority, airport and weather information with aircraft ADS-B/ACARS transmissions to reconstruct what happened to a particular flight or aircraft.
This does not name ACARSd. It does, however, independently confirm the exact business use that KjM remembers: flight-claim analysis built partly on received aircraft transmissions.
Why this belongs in the museum.
The episode marks a transition. ACARSd was still a hobby project and remained free, but its distributed receiver network had created something that organisations could not easily obtain elsewhere: independent observations of real aircraft movements. The value was no longer only in decoding the radio message. It was in the network, history, enrichment and ability to correlate events across time and geography.