Flight information is everywhere: airline apps, airport boards, search results, booking emails, and aviation trackers. Yet travelers still refresh several screens before leaving for the airport.
The problem is not a lack of data. It is turning changing data into a calm, useful signal.
A smaller promise
FlightDan does not try to book the flight, plan every part of a holiday, or replace the airline. Its promise is deliberately smaller:
- Find the flight that matters.
- Keep its latest reported state easy to read.
- Tell you when that state changes.
- Help the people around the traveler follow along.
That is why FlightDan works both as a web application and a Telegram bot. The web is better for reviewing detailed status and organizing trips. Telegram is already where many people expect timely messages.
Following instead of refreshing
A typical flight day contains long periods in which nothing important changes. Refreshing during those periods creates anxiety without adding information.
When you follow a flight, FlightDan checks it on an adaptive schedule. Flights far from departure need fewer checks. A flight close to departure or currently in the air deserves more frequent attention. After landing, it stays live for 90 minutes so travelers and the people meeting them can still see the latest arrival details at a glance.
The goal is not to send more notifications. The goal is to make each notification worth receiving.
Trips are social objects
Flight details rarely matter to only one person. Someone may be meeting the traveler, coordinating a connection, arranging transport, or simply waiting to know that they arrived.
Every followed flight is date-specific and appears in one timeline. A trip is an optional group around those same tracked flights, so organizing a journey does not create a second copy or hide its legs in another list. A trip can also produce a public read-only link; the recipient does not need to create an account just to see the plan.
Honest about uncertainty
Aviation data changes. Future schedules may not be fully published. Gates may be absent until close to departure. Live coverage varies between airports and providers.
FlightDan should make uncertainty visible rather than invent precision. A provisional future schedule is marked as provisional. Missing information stays missing. Critical travel decisions should still be confirmed with the operating airline or airport.
That combination—useful automation without false certainty—is the product we are building.