Are the arrival times consistent with departure and duration?

Yes. The tool picks a departure time and a flight duration, then computes arrival as departure plus duration plus a layover allowance for connecting flights. The displayed arrival always matches departure plus the stated duration.

Do the airport codes look real?

They use the three-letter IATA format and are drawn from a pool of well-known codes, but no real schedule, availability, or pricing is implied. It is mock data for UI work, not a booking source.

How are stops and layovers handled?

Each flight is randomly direct or has one or two stops. Stops add layover time to the total duration, and the number of stops is shown so your UI can render direct versus connecting clearly.

Is the price realistic?

Price scales with duration and a per-airline base fare, with a small random spread, so longer flights cost more on average. It is plausible for mockups but should never be treated as a real fare.

What does the output contain?

A JSON array of flight objects with airline, flight number, origin, destination, departure, arrival, duration, stops, and price. It drops directly into a flight-results list or a test fixture.

Flight Data Generator

Travel-search interfaces need a list of plausible flights to design against before any GDS or airline feed is connected. This generator builds fake flight records where the times add up — arrival equals departure plus duration plus any layovers — and prices scale sensibly with flight length.

How it works

For each flight the tool picks an airline (with a flight number), a departure time, and a base duration, then adds layover time for any stops. Arrival is computed from those values so the itinerary is internally consistent. Price is derived from duration and a per-airline fare floor with a little random spread:

arrival   = departure + duration + sum(layovers)
duration  = baseLeg × (stops + 1) + layovers
price     = round(fareFloor + durationHours × ratePerHour ± spread)

Origin and destination use three-letter IATA-format codes from a known pool, and the two are always different.

Example and tips

A generated row might read Skyline Air SL842 — LHR → JFK, dep 09:15, arr 12:40 (7h 25m), direct, 410, while a connecting option shows one or two stops with a longer duration and a different price. Leave the route fields blank to get random city pairs for stress-testing your list, or fix origin and destination to mock a specific search. All data is fictional and safe for public marketing screenshots.