CO detector?

A pilot's Reddit post asking for a "second opinion" on a carbon monoxide detector reading—after being told by others that the alarm is "fine" and that such detectors "just aren't good"—captures a recurring and genuinely hazardous gray area in general aviation. The original post includes only an image link and no numerical readings or aircraft details in the text itself, but the underlying question is a familiar one in GA circles: when a CO detector, whether a panel-mounted unit, a plug-in electronic sensor, or a cheap spot-check card, shows an elevated reading, how much of that should be trusted versus dismissed as sensor noise or a false positive? The fact that the pilot felt compelled to seek outside validation, despite reassurance from peers, reflects a well-founded wariness that has developed around inconsistent CO detection technology in cockpits.

Carbon monoxide poisoning remains one of the more insidious risks in piston-engine aviation, particularly in older aircraft with exhaust systems, heater muffs, and firewall penetrations that degrade over time. CO is colorless, odorless, and produces symptoms—headache, drowsiness, impaired judgment—that mimic hypoxia or simple fatigue, making self-diagnosis in flight extremely difficult. The NTSB and AOPA Air Safety Institute have both flagged CO exposure as a contributing factor in a number of accidents, especially in aircraft using combustion heaters, prompting increased adoption of digital CO detectors like the Sensorcon, CO Guardian, and Aithre Shield, as well as cheap adhesive spot detectors that change color with prolonged exposure. However, not all detectors are created equal: low-cost colorimetric cards are known for slow response times and unreliable sensitivity thresholds, while electrochemical sensors in digital units can drift, suffer from calibration issues, or generate false alarms from unrelated cabin fumes, exhaust-adjacent ramp air, or even off-gassing from certain plastics and cleaning products. This variability is precisely why pilots on forums frequently split into camps—some dismissing alarms as "known to be flaky," others treating every reading as a potential emergency.

For working pilots, whether flying a Part 91 piston single, a 135 charter aircraft, or a business jet with a combustion heater, the practical takeaway is that CO detector ambiguity should never default to complacency. The professionally sound response to any elevated reading, regardless of a detector's reputation for false positives, is to treat it as valid until proven otherwise: crack a window or vent if able, turn off the heater and exhaust-fed systems, don oxygen if equipped, and land as soon as practical while monitoring for symptoms in all occupants. Dismissing a reading because "everyone says these things are junk" is a dangerous heuristic, since the cost of a false negative—actual CO buildup unaddressed—is incapacitation or death, while the cost of a false positive is merely a precautionary diversion. Maintenance-side, persistent elevated readings warrant a thorough inspection of the exhaust system, muffler, and cabin heat shroud rather than simply replacing or ignoring the detector.

This kind of crowdsourced safety question also reflects a broader trend in GA culture: pilots increasingly turn to online communities for real-time risk assessment, sometimes in place of, or in addition to, consulting a mechanic, CFI, or manufacturer's guidance. While peer input has value, especially for identifying common false-alarm patterns with specific detector models, it should supplement rather than replace grounded protocol and professional inspection. As CO detection technology becomes more standard equipment—and increasingly integrated into digital flight instruments and ADS-B-linked safety devices—operators and training providers would do well to reinforce clear, conservative response procedures for CO alerts, so that individual pilots aren't left weighing "is this sensor lying to me" against their own life safety in the moment.