The Reddit thread in question centers on a video posted from inside an Airbus A220-300 cabin, capturing a persistent buzzing noise tied precisely to flap configuration rather than flap motor operation. The original poster notes the sound begins during takeoff roll and continues until flaps are fully retracted, then reappears on approach from the initial flap-1 selection through to full retraction after landing rollout. That correlation pattern is the most technically interesting detail: because the noise persists continuously across a range of flap settings rather than only during the brief interval when the flap surfaces are actually moving, it rules out the flap drive motor or transmission as the source. Instead, the pattern points toward something whose state changes with flap handle position but which then runs continuously in that configuration — a strong candidate being aerodynamic-induced vibration from flap track fairings, slat/flap gap seals, or fairing panels exposed to disturbed airflow whenever the high-lift devices are extended, or alternatively a bleed-air or hydraulic valve that cycles open based on flap-position logic (such as those tied to wing anti-ice scheduling or system pressurization logic that changes with configuration).
For working pilots, this kind of crowd-sourced troubleshooting thread illustrates a broader and increasingly common phenomenon: passengers and crew now routinely capture and share cabin audio/video, and online aviation communities attempt real-time diagnosis of noises that would otherwise generate a routine maintenance discrepancy entry. The precision in this report — noise present at flaps 1 through flaps up, absent when flaps are fully retracted, occurring identically on both departure and arrival — is exactly the kind of configuration-correlated detail that maintenance control and reliability engineers want in a write-up. Vague "heard a weird noise" reports are difficult to chase; noises tied cleanly to a specific system state are far more actionable, whether the eventual finding is a benign aerodynamic buzz, a loose fairing fastener, or a valve requiring adjustment per an OEM service bulletin. Flight crews are trained to note phase-of-flight and configuration when logging cabin or flight deck anomalies for exactly this reason, and this thread is effectively a passenger doing informal fault isolation.
The A220 program, still relatively young compared to the A320 or 737 families, has seen its share of in-service squawks surface publicly as the fleet has scaled at Delta, airBaltic, Air France, JetBlue, Breeze, and other operators. Newer types tend to generate more of these viral "what is this noise" threads simply because the type is less familiar to the flying public and even to line pilots transitioning from other fleets, and because any airframe-specific quirk — a fairing resonance, a valve chatter, a systems logic idiosyncrasy — hasn't yet been normalized through years of collective type experience. Manufacturers and airlines do monitor this kind of social chatter informally, since a noise that alarms passengers or gets flagged repeatedly across a fleet can eventually prompt an engineering bulletin or inspection campaign even if it poses no safety-of-flight concern. It mirrors similar public discussions that have surrounded other types, from A320neo "gear whine" threads to 737 MAX rattle complaints, where benign but noticeable sounds become widely discussed before airlines or OEMs formally characterize and, if warranted, address them.
For dispatchers, maintenance controllers, and check airmen, the practical takeaway is less about this specific clip and more about reinforcing good discrepancy-reporting discipline among line crews: configuration, phase of flight, duration, and whether the sound is continuous or cyclical are the details that separate an easily-diagnosed squawk from a recurring "cannot duplicate" write-up. As the A220 fleet continues to grow and accumulate operating hours across diverse climates and route structures, expect more of these configuration-specific noise reports to surface, some of which will resolve into known-issue service bulletins and others that will simply become accepted characteristics of the type — the kind of institutional knowledge that experienced A220 pilots eventually pass along informally to new hires transitioning onto the aircraft.