Date: 201902
Local time of day: 0001-0600
Location: EDDK.Airport, FO
Flight conditions: VMC
Weather elements / visibility: 5
Light: Night
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Aircraft component: ACARS
Component problem: Malfunctioning
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction; Communication Breakdown; Human-Machine Interface; Troubleshooting
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Airport
Primary problem: Airport

Narrative: We were preparing to operate Flight X from CGN to ZZZZ. On the ground in CGN; the ACARS (Automatic Communications Addressing and Reporting System) would not initialize. We had an intermittent 'no comm' message. We notified Maintenance who cycled the circuit breaker and even powered down the airplane completely; all to no avail. The Mechanic then told us that three other airplanes on the ground in CGN were having the same problem. I had seen this problem before in CGN more than once. The ACARS won't initialize; but shortly after liftoff; it gets a better signal; and everything works fine. The problem is CLEARLY on the ground in CGN. We wrote up and deferred the inoperative ACARS anyway; entered the initialization data manually; used the TLR (Takeoff/Landing Report) for our takeoff data and did our best to get the flight out on time. We were busy; but took only a six minute delay.


Second narrative: We were preparing to operate Flight X from CGN to ZZZZ. On the ground in CGN; the ACARS (Automatic Communications Addressing and Reporting System) would not initialize. We had an intermittent 'no comm' message. We notified Maintenance who cycled the circuit breaker and even powered down the airplane completely; all to no avail. The Mechanic then told us that three other airplanes on the ground in CGN were having the same problem. I had seen this problem before in CGN more than once. The ACARS won't initialize; but shortly after liftoff; it gets a better signal; and everything works fine. The problem is CLEARLY on the ground in CGN. We wrote up and deferred the inoperative ACARS anyway; entered the initialization data manually; used the TLR (Takeoff/Landing Report) for our takeoff data and did our best to get the flight out on time. We were busy; but took only a six minute delay.The first officer suggested we get an [Amended Release]; but I didn't think it was necessary; and again; was struggling to get the flight out on time. I knew this problem was going to resolve itself shortly after liftoff (which it did); and if [Operations] Control needed to get in touch with me; I have a SAT phone. I also planned on calling [Operations] Control once airborne to make sure they were aware of our deferred ACARS. As expected; the ACARS functioned normally shortly after liftoff. However; I was realized later that; in fact; an [Amended Release] was necessary before block out. I'll remember that in the future.


Synopsis: Air carrier flight crew reported poor ACARS reception on the ground in Cologne; Germany.