F-GZCP
A DIGITAL TRAIL
For years it was simply one Air France A330 among thousands of aircraft appearing in the worldwide ACARSd reports. After 1 June 2009, the registration F-GZCP acquired a very different meaning.
The surviving extraction supplied to the museum contains 1,392 report lines for F-GZCP, beginning in January 2006 and ending on 31 December 2008. It is a historical trail assembled from ACARSd World Reports — not a complete operational history of the aircraft and not the final ACARS transmission of AF447.
Before the registration became famous
The archive reads like the working life of a long-haul aircraft: Detroit, Philadelphia, Tehran, Tokyo, São Paulo, Cairo, Bangalore, Dubai, Rio de Janeiro and many other destinations. The same registration reappears day after day, received by stations in different countries.
One entry is especially personal to this museum. On 2 February 2006, F-GZCP was logged on Air France flight AF0508 from Paris to Cairo with the receiver location recorded as “Hungary, near lake Balaton”. Days later the receiver label becomes “acarsd.org home - Balatonfoeldvar”. The worldwide archive therefore contains receptions of this aircraft made by the project’s own home station.
Long before the accident, the World Reports also show F-GZCP repeatedly operating the Rio de Janeiro route: AF0444 Paris → Rio and AF0447 Rio → Paris. Examples survive from December 2007 and repeatedly in late 2008.
Selected lines from the archive
ACARS_Report_20060103.txt: F-GZCP (A332 AF) 1146 20060103 AF0374 (CDG-DTW) ACARS_Report_20060202.txt: F-GZCP (A330 AF) 1530 20060202 AF0508 (CDG-CAI) [Hungary, near lake Balaton] ACARS_Report_20060214.txt: F-GZCP (A330 AF) 0813 20060214 AF0191 (VOBG-LFPG) [acarsd.org home - Balatonfoeldvar] ACARS_Report_20071031.txt: F-GZCP (A330 AF) 0915 20071031 AF0503 (CAI-CDG) [near Zuerich] ACARS_Report_20071213.txt: F-GZCP (A330 AF) 0950 20071213 AF0447 (GIG-CDG) [somewhere] ACARS_Report_20081127.txt: F-GZCP (A332 AF) 1209 20081127 AF0444 (CDG-GIG) [Portugal North] ACARS_Report_20081128.txt: F-GZCP (A332 AF) 0747 20081128 AF0447 (GIG-CDG) [Canico] ACARS_Report_20081202.txt: F-GZCP (A332 AF) 1212 20081202 AF0444 (CDG-GIG) [somewhere] ACARS_Report_20081203.txt: F-GZCP (A332 AF) 0917 20081203 AF0447 (GIG-CDG) [Paço de Arcos, Portugal] ACARS_Report_20081220.txt: F-GZCP (A332 AF) 2124 20081220 AF0444 (CDG-GIG) [Belo Horizonte, Brazil] ACARS_Report_20081221.txt: F-GZCP (A332 AF) 0745 20081221 AF0447 (GIG-CDG) [Funchal Madeira] ACARS_Report_20081231.txt: F-GZCP (A332 AF) 0757 20081231 AF0373 (DTW-CDG) [Exmoor SW England]
The spelling and receiver descriptions reflect the historical report data. Some old reports used A330, others A332, for the aircraft type.
1 June 2009 — the archive suddenly mattered
Air France flight AF447, operated by F-GZCP, was lost over the Atlantic while flying from Rio de Janeiro to Paris. KjM remembers receiving a call from an organisation involved in research surrounding the accident, asking whether ACARSd held historical messages from this particular aircraft.
The reason the request could be answered was simple: ACARSd had not only decoded traffic in real time. The project had accumulated history. A registration could be followed backwards through years of independently received data.
Among the older material KjM remembers messages concerning oil-pressure issues. In the uncertainty immediately after the loss, previous technical anomalies naturally attracted attention. They were ultimately unrelated to the cause of AF447. The surviving World Report extraction on this page documents the aircraft sightings and routes; it does not itself contain those full maintenance-message texts.
Nothing in these historical World Report lines should be presented as a warning of the accident. Their significance is archival: they demonstrate that an enthusiast-built worldwide receiver network had preserved a long digital trail of the aircraft before anyone knew that trail might one day be requested.
What was later established
The official investigation established that AF447 transmitted automated ACARS maintenance information during the final minutes of the flight. The eventual accident explanation centred on temporary inconsistency in measured airspeeds after obstruction of the Pitot probes by ice crystals, the crew’s subsequent loss of control and a sustained stall. The older oil-pressure material remembered from the ACARSd archive was not the cause.
Why this belongs in the museum
Most lines in an ACARS log are mundane. That is precisely what makes an archive valuable. The data was collected before anyone knew which aircraft, route or message might later become historically significant.
A live decoder is useful for seconds. An archive can become useful years later, for reasons nobody imagined when the signal was first received.
F-GZCP is perhaps the clearest example in the ACARSd story: an ordinary registration moving through a worldwide hobby network, repeatedly heard even at the project’s home station near Lake Balaton — and years later a registration somebody urgently wanted to search backwards through time.