A Reddit user flying with Bose A30 headsets has surfaced a potentially serious safety issue: an incoming phone call via Bluetooth is overriding the intercom, blocking communication with the other pilot, ATC transmissions, and even the pilot's own transmitted voice until the call is manually declined. This directly contradicts the A30 manual's stated design philosophy that "radio/intercom overrides all other audio" — a priority scheme that exists precisely because flight crews cannot afford to lose situational awareness to a phone call, text notification, or streaming audio at a critical moment. The pilot reports the behavior is new (occurring after connecting an iPhone 17 Pro), has tried the BT/Aux priority switch behind the battery compartment, and attempted iOS Focus modes to suppress calls from WhatsApp, Messenger, and Phone — none of which resolved the problem, since ANC headsets pair via Bluetooth to the phone's OS-level call-handling stack, which sits outside the headset's own audio-mixing firmware.
For working pilots, this matters more than it might first appear. Bluetooth-enabled ANR headsets like the A30 and its predecessor the A20 have become standard equipment across GA, corporate, and even some Part 135 cockpits, largely because they allow pilots to stream ATIS, music, or take calls during ground operations without swapping devices. But the entire value proposition rests on the assumption that intercom and radio audio will always take priority when the aircraft is moving or the engine is running. If a firmware update, iOS update, or headset/phone pairing quirk can silently invert that priority — burying ATC and CRM communication under a personal phone call — it represents a single point of failure that pilots may not discover until it happens in flight, exactly as occurred here. The user's plan to escalate directly to Bose customer support, rather than trust a workaround, is the right instinct: this is a hardware/firmware behavior issue, not a training or procedure issue, and it likely needs a vendor-side fix or documented setting change communicated to the fleet of A30 owners.
This incident also reflects a broader pattern in aviation electronics: as consumer smartphone ecosystems (iOS updates, Bluetooth stack changes, Focus mode logic) increasingly intersect with certified or semi-certified pilot equipment, unexpected interactions between phone OS behavior and headset firmware can emerge without warning, often triggered by an iPhone update the pilot didn't associate with the headset at all. Similar issues have surfaced historically with ANR headset firmware updates changing default mix levels, Bluetooth auto-reconnect behavior, and squelch/VOX settings after manufacturer app updates. Pilots relying on BT-paired headsets should treat any consumer-side software update (iOS, Android, or the headset's companion app) as a potential trigger for behavior changes and verify intercom/radio priority on the ground before every flight, particularly after any update to phone or headset firmware.
More broadly, this thread is a reminder that personal electronic device (PED) integration into the cockpit audio chain — while convenient — introduces failure modes that didn't exist with purely analog intercom systems. Operators and flight departments that permit or standardize on Bluetooth ANR headsets should consider adding a line item to preflight or currency checks confirming that intercom/radio-priority behavior is functioning as designed, and should discourage leaving phones in a state where incoming calls are enabled during flight regardless of headset behavior, given that a firmware quirk, not pilot error, could otherwise silently mute critical communications at the worst possible time.