A Smarter Homepage and a Friendlier Empty State
Three small things, big difference. A live flight count above the fold, an honest pitch about why this tool exists, and an empty-state screen that tells you exactly which filter is hiding your results.
✨ What changed
- A pulsing red dot under the hero with the real number of flights currently covered by live VATSIM ATC
- A “what makes findsim.flights different” section listing the five things we actually do that other route finders don't
- When a search returns zero flights, we tell you which filter is most likely hiding routes from you and offer a one-click return to the form
A real live flight count above the fold
For ages the first homepage stat card said the literal text “Live” — which is fine as a placeholder but undersells what we actually do. Now there's a real number under the hero subhead: “247 flights with live ATC at 18 airports right now” (those numbers change every minute).
The count is computed server-side from the current VATSIM controllers feed (cached for 60 seconds), joined against our flights table excluding anything community-flagged as potentially inaccurate. The pulsing red dot is just a CSS animation — no extra JS, no live-updating overhead. The number refreshes when you reload, which is good enough for a homepage stat.
If for some reason the VATSIM feed is unreachable, the banner quietly doesn't render and the stat card falls back to its old placeholder text. Homepage never breaks.
What makes findsim.flights different
We added a section between the hero and the stats cards that names five things this tool actually does that a typical static route-finder doesn't:
- Live VATSIM ATC matching — routes are scored by who's actually controlling right now, not a list someone curated last quarter
- Real-time weather scoring — visibility, wind, ceiling, time-of-day all factor in
- Knows what you can fly — point us at your MSFS community folder and we match flights to aircraft you actually own
- One-click SimBrief dispatch — no copy-pasting route strings
- Community-corrected data — real pilots can flag and suggest fixes for wrong flights
The header strapline does the contrast subtly without naming any competitor: “Most route finders show you a static list. We show you flights where ATC is on duty right now.”
Empty-state that helps instead of shrugs
The old “no flights found” screen told you to “try adjusting your filters” — which is technically true and totally unhelpful. The new screen looks at your actual filters and surfaces specific suggestions:
- You set an aircraft filter? “Clear the aircraft type filter — many real routes have no aircraft data, so any filter hides them.”
- Both origin and destination whitelisted? “Clear either origin or destination — locking both ends down rules out a lot of valid pairings.”
- Your duration range is under 2 hours wide? “Widen the duration range — a tight window skips most routes.”
- ATC requirement set (e.g. Tower or better)? “Drop the minimum departure ATC requirement (currently TWR)” — and the suggestion about Skip VATSIM scoring shows up for the Beyond ATC / PilotEdge crowd.
There's also an obvious “Edit your search” button that takes you back to the homepage form. The point is to give users a concrete next action instead of a generic apology.
We also added an aircraft tip directly under the aircraft-types input in the search form: “Tip: many real routes have no aircraft data — leave empty to see far more flights.” Highlighted in amber so people actually read it. It's the single most common reason a search returns less than expected, and now we tell you up front.
None of this is rocket science
Just a few hours of focused product polish that nobody had got around to. The kind of stuff that doesn't show up in a changelog one line at a time but adds up to “this tool feels like it cares whether I find what I'm looking for.” If you've been bouncing off findsim.flights because it felt like it shrugged at empty searches — try it again.