Flight Deals from Indianapolis to Bangkok from $593

Flight times and distances come from our flight-schedule database, which combines published airline timetables, U.S. government schedule data from the Bureau of Transportation Statistics (BTS), and observed flight operations from the EUROCONTROL/OpenSky Open Performance Data Initiative (OPDI). The typical flight time is the median scheduled block time across all carriers on the route, computed the same way in both directions so the difference reflects prevailing winds rather than any change in method. Distance is the great-circle distance between the two airports, so the actual flown track is typically 2-5% longer.

Airlines and weekly frequencies are compiled from our flight-schedule database, which combines published airline timetables, U.S. government schedule data from the Bureau of Transportation Statistics (BTS), and observed flight operations from the EUROCONTROL/OpenSky Open Performance Data Initiative (OPDI). We count each operating carrier's scheduled weekly departures and the days it flies; where there is no nonstop service, connecting carriers are identified by linking scheduled nonstop segments through common hub airports. Where a median fare is shown for a carrier, it reflects the real fares Priceline users found on this route in the last 72 hours. Carrier service, flight times and distances for this route come from our flight-schedule database, which draws on published airline timetables, U.S. government schedule data, and observed operations from the EUROCONTROL/OpenSky Open Performance Data Initiative (OPDI). We report the days of the week and the departure times each carrier operates. The typical flight time is the median scheduled block time, given both per carrier and across all carriers on the route; where a schedule does not publish an elapsed time, it is derived from the scheduled departure and arrival times converted to UTC. Outbound and return times are computed by the same method, so the difference between them is directly comparable and reflects prevailing winds rather than any change in derivation. Distance is the great-circle distance between the two specific airports named, so an actual flown track is typically 2-5% longer. Where an aircraft type is shown, it also comes from this database: for U.S. routes it is grounded in the tail number that actually operated the flight, and elsewhere in the airline's filed equipment code. Where the source does not commit to a specific variant we name the aircraft family (for example "Airbus A320 family") rather than guess a member, and where no reliable type is on file the aircraft is simply omitted rather than estimated. Flights known only from the OPDI feed carry no aircraft type, because their flight numbers are synthetic and joining by flight number would attribute another flight's aircraft. Where shown, on-time departure and arrival rates and cancellation rates come from the U.S. Bureau of Transportation Statistics (BTS) Airline On-Time Performance dataset, which covers U.S. domestic routes only; where a typical fare is shown, it comes from the U.S. DOT Airline Origin and Destination Survey (DB1B), a quarterly 10% sample of tickets sold.

Red-eye flights are identified from scheduled local departure and arrival times and block times in our flight-schedule database — built from published airline timetables and official schedule data, including U.S. Department of Transportation records for domestic routes. A flight counts as a red-eye when it departs in the afternoon or evening (3 p.m. or later local time) or in the early hours before 4 a.m., and is in the air at some point between midnight and 4 a.m. local time at both its departure airport and its arrival airport. An evening flight that lands before midnight at its destination is never counted, nor is a morning departure or a daytime long-haul that reaches the next calendar date only because of time zones. Each red-eye is labelled with its timing (for example, overnight and landing the next morning, or late-night and landing after midnight). For connecting itineraries the same rule is applied to the longer leg, from one representative day's flight search.

Airlines and weekly frequencies come from our flight-schedule database, which combines published airline timetables, U.S. government schedule data from the Bureau of Transportation Statistics (BTS), and observed flight operations from the EUROCONTROL/OpenSky Open Performance Data Initiative (OPDI). We count each operating carrier's scheduled weekly departures and the days it flies; where there is no nonstop service, connecting carriers are identified by linking scheduled nonstop segments through common hub airports. Where a typical fare is shown for a carrier, it is the median of the real fares Priceline users found on this route in the last 72 hours.

Aircraft types come from our flight-schedule database, which combines published airline timetables, U.S. government schedule data from the Bureau of Transportation Statistics (BTS), and observed flight operations from the EUROCONTROL/OpenSky Open Performance Data Initiative (OPDI). For U.S. routes the type is grounded in the tail number that actually operated the flight; elsewhere it comes from the airline's filed equipment code. Where the source does not commit to a specific variant we name the aircraft family (for example Airbus A320 family) rather than guess, and where no reliable type is on file the aircraft is omitted rather than estimated. Types describe typical scheduled equipment and can vary with seasonal or day-of-week assignments and last-minute swaps.

Airlines and weekly frequencies are compiled from our flight-schedule database, which combines published airline timetables, U.S. government schedule data from the Bureau of Transportation Statistics (BTS), and observed flight operations from the EUROCONTROL/OpenSky Open Performance Data Initiative (OPDI). We count each operating carrier's scheduled weekly departures and the days it flies; where there is no nonstop service, connecting carriers are identified by linking scheduled nonstop segments through common hub airports. Where a median fare is shown for a carrier, it reflects the real fares Priceline users found on this route in the last 72 hours. Carrier service, flight times and distances for this route come from our flight-schedule database, which draws on published airline timetables, U.S. government schedule data, and observed operations from the EUROCONTROL/OpenSky Open Performance Data Initiative (OPDI). We report the days of the week and the departure times each carrier operates. The typical flight time is the median scheduled block time, given both per carrier and across all carriers on the route; where a schedule does not publish an elapsed time, it is derived from the scheduled departure and arrival times converted to UTC. Outbound and return times are computed by the same method, so the difference between them is directly comparable and reflects prevailing winds rather than any change in derivation. Distance is the great-circle distance between the two specific airports named, so an actual flown track is typically 2-5% longer. Where an aircraft type is shown, it also comes from this database: for U.S. routes it is grounded in the tail number that actually operated the flight, and elsewhere in the airline's filed equipment code. Where the source does not commit to a specific variant we name the aircraft family (for example "Airbus A320 family") rather than guess a member, and where no reliable type is on file the aircraft is simply omitted rather than estimated. Flights known only from the OPDI feed carry no aircraft type, because their flight numbers are synthetic and joining by flight number would attribute another flight's aircraft. Where shown, on-time departure and arrival rates and cancellation rates come from the U.S. Bureau of Transportation Statistics (BTS) Airline On-Time Performance dataset, which covers U.S. domestic routes only; where a typical fare is shown, it comes from the U.S. DOT Airline Origin and Destination Survey (DB1B), a quarterly 10% sample of tickets sold.