A pilot working for a small Part 135 operator recently posted a practical operations question on r/flying: how to get a flight-tracking display (FlightAware, FlightRadar24, or similar) running persistently on a break-room or ops-desk television. The setup constraints are common to small charter and fractional operations—no dedicated computer near the TV, only a Roku and a Fire Stick available as streaming hardware, and a desire for a simple "power on and it just works" solution rather than a manually managed browser session. While the question reads as a minor IT request, it touches on something increasingly central to small-operator situational awareness: cheap, reliable, always-on visibility into company aircraft movement without investing in a dedicated dispatch or flight-following system.
For small 135 operators, this kind of ambient tracking display serves a real operational function. Many charter and air-taxi operations lack the budget for enterprise flight-following software (ARINC, Honeywell GoDirect, FOS, or similar) and instead rely on a patchwork of ADS-B web tools, group texts, and phone calls to maintain awareness of where their aircraft are. A TV in the office or FBO lounge showing live positions of the fleet gives dispatchers, schedulers, maintenance, and even standby crews a shared, low-effort situational picture. It also matters for customer-facing purposes—clients and family members waiting on an inbound aircraft can glance at a screen rather than repeatedly calling ops. The fact that the poster is trying to solve this with consumer streaming hardware (Roku, Fire Stick) rather than a purpose-built avionics or dispatch solution underscores how thin the technology margins are at smaller operators compared to Part 121 carriers, which have dedicated operations control centers with redundant, professionally maintained tracking infrastructure.
The technical challenge is real: FlightAware and FR24 are designed as browser/app experiences with interactive maps, not as passive "kiosk mode" displays optimized for a TV that reboots or needs to auto-launch content without user input. Streaming boxes like Roku and Fire Stick are built around app stores and remote navigation, not persistent dashboard casting, so there's no clean native app for this use case. Workarounds that operators in similar situations have used include HDMI-connected Raspberry Pi or Amazon Fire TV Cube devices running a browser in kiosk mode pointed at a FlightAware/FR24 embed or a custom ADS-B Exchange map, digital signage software (like Xibo or a simple browser-refresh loop), or casting a browser tab from a dedicated always-on mini PC via Chromecast. Some operators build their own lightweight dashboard using ADS-B Exchange's free API or a Raspberry Pi ADS-B receiver (like a FlightAware PiAware kit) feeding a local display—bypassing the commercial trackers entirely and giving the operator full control over refresh rate, layout, and reliability.
More broadly, this thread reflects a recurring theme in small-operator and business aviation forums: the gap between the situational-awareness tools available to major airlines and fractional/charter operations and what's realistically achievable with consumer-grade budgets and lean IT support. As ADS-B data has become more accessible and affordable (via ADS-B Exchange, FlightAware's PiAware program, and low-cost SDR receivers), smaller flight departments and 135 operators increasingly build their own scrappy tracking solutions rather than paying for enterprise flight-following platforms. This DIY trend is likely to continue as more affordable single-board computers and open APIs make it easier for a two- or three-airplane operator to get airline-grade situational awareness on a budget, even if the "last mile" problem—getting a browser-based map to display cleanly and persistently on an office TV—remains a surprisingly common point of friction, as this thread illustrates.