A pilot flying with a Stratus 2S ADS-B receiver paired to the Stratus Insight app has reported a recurring and operationally significant glitch: traffic targets disappear roughly 15 minutes after power-on, only to reappear if the unit is power-cycled, with the pattern repeating on a consistent ~14-minute interval. GPS position and other data reportedly continue functioning normally, isolating the fault to the traffic (1090ES/UAT) reception or processing chain rather than a wholesale receiver failure. The user has already ruled out several common culprits—installing a new battery, updating firmware, and updating the app—yet the issue persists, and Sporty's (the manufacturer) customer support has offered little beyond a recommendation to send the unit in for service. The thread, posted to r/flying, is essentially a crowd-sourced troubleshooting request to see if this is a known or widespread firmware/hardware issue rather than an isolated unit defect.
For working pilots, particularly those flying VFR or IFR in busy terminal airspace, GA traffic, or mixed-use environments, ADS-B traffic display is a core layer of the see-and-avoid and TCAS-lite safety net that portable receivers like the Stratus line were designed to provide. A traffic display that silently drops targets mid-flight—especially without an obvious alert distinguishing "no traffic present" from "traffic feed has failed"—creates a dangerous false sense of security. Pilots accustomed to glancing at an iPad or panel-mounted display for conflict awareness may not immediately recognize that the picture has gone stale, particularly in high-workload phases of flight. This is a known hazard class with portable ADS-B: unlike certified, panel-integrated traffic systems with built-in self-test and failure annunciation, portable receivers and their companion apps vary widely in how (or whether) they alert users to a degraded or lost data feed. Operators relying on Stratus, Sentry, SkyEcho, or similar devices should build a habit of periodically cross-checking traffic display currency (e.g., watching for expected known traffic, verifying own-ship position updates, or noting timestamp/status indicators in the app) rather than assuming continuous, uninterrupted service.
This complaint also reflects a broader and recurring theme in the portable ADS-B/EFB ecosystem: intermittent, hard-to-diagnose faults that manufacturers often address by defaulting to "send it in" rather than engaging in real root-cause troubleshooting with the customer. For an aircraft owner or renter pilot, this is more than an inconvenience—it can mean flying without full electronic traffic advisory capability for days or weeks while a unit is in for repair, during which the pilot must revert to more conservative visual scanning and ATC traffic calls. It also underscores the value of redundancy: pilots who rely heavily on portable ADS-B for traffic awareness, especially in the pattern or in Mode C veil airspace, benefit from having a backup awareness strategy (transponder-based TIS-B/TAS options, ATC flight following, or a second independent receiver) rather than treating any single portable unit as an infallible safety layer.
Looking at the bigger picture, this incident is a small but telling data point in the ongoing maturation of the ADS-B In ecosystem a decade after the FAA's ADS-B Out mandate reshaped GA equipage. As more pilots depend on affordable portable traffic and weather receivers rather than certified panel systems, software-driven failure modes—firmware bugs, app-side data parsing errors, or receiver overheating/timeout issues—are increasingly likely to surface as the primary reliability concern, displacing purely hardware failures. Manufacturers' support responsiveness and transparency around known issues (including publishing service bulletins or firmware changelogs that address symptoms like this) will matter more as fleets of these devices age and as pilots' operational reliance on them grows. For now, this thread stands as a useful reminder to the pilot community: intermittent traffic dropouts on portable ADS-B units are a real-world hazard worth actively monitoring for, documenting, and reporting—both to manufacturers and to fellow pilots—rather than assuming the system is working simply because it worked on the ramp.