Airport-pair calculatorAirport-specific, not city substitution.

Los Angeles to Tokyo Flight Time

Convert an LAX–HND planning duration into Tokyo local arrival time while handling the international date line and time-zone rules.

Route assumptionsLAX → HNDThis pilot uses LAX and Haneda. Narita is a separate airport with different ground transfer and schedule considerations.
Route scope

What this calculation includes.

This pilot uses LAX and Haneda. Narita is a separate airport with different ground transfer and schedule considerations.

Crossing the international date line changes the local calendar date. The calculator resolves the instant first, then formats Tokyo local time.

Use the current airline itinerary for the scheduled duration. Great-circle mode remains an estimate and never becomes an “actual flight time” claim.

Reference calculation

Enter your details.

Calculated locally in your browser. Nothing is uploaded to CalcSpan.

Section 1

Core details

Start with the information that defines this calculation.

Origin airport Search by IATA code, city or airport name.
Origin airport

20 options

Destination airport Choose an airport, not only a city.
Destination airport

20 options

Fri, Aug 28, 2026
Section 2

Review and confirm

Check the remaining facts before calculating.

Plain-date semantics · start date is not counted unless the result explicitly says inclusive.

Your result
Local arrival: Saturday, Aug 29, 2026, 10:15 PM GMT+9

LAX to HND spans 11 hours 45 minutes in this user-entered itinerary scenario.

Airport pairLAX Los Angeles → HND TokyoAmerica/Los_Angeles → Asia/Tokyo
DepartureFriday, Aug 28, 2026, 6:30 PM PDT
Scheduled duration input11 hours 45 minutesCopy from the current itinerary
Local arrivalSaturday, Aug 29, 2026, 10:15 PM GMT+9Date line and DST resolved from the two IANA zones
Destination clock at departure16 hours aheadOffset can change before arrival if a DST transition occurs
Great-circle distance8,813 km · 5,476 miNot an operational route distance
Aug 28, 2026Depart LAX · 18:30 local
Aug 29, 2026Arrive HND · 10:15 PM GMT+9
Calendar options

Add to calendar

Choose a calendar service, then confirm the event. Downloading an .ics file does not add it until you open or import it.

Read before relying

Context matters.

  • The duration is the value you entered from an itinerary; airline schedule updates control.
  • Airport records are explicit so metro-area airport substitutions do not silently change the result. Time-zone conversion uses the browser's IANA data.
Rule set 1.1.0

Sources & scope

Source & calculation QA reviewed

The calculation guide and this source trail show what the result means, where the rule came from and when it was last reviewed. This is source-and-calculation QA, not a claim of medical, legal, tax or other professional review; time-sensitive decisions still belong with the linked authority.

JurisdictionGlobal airport-pair and IANA time-zone planning — scheduled itinerary controls; great-circle mode is explicitly an estimate
Last reviewed2026-08-23
Next review due2027-02-23
Review scopeCalcSpan source & calculation QA
PrivacyNo input upload
How this calculation works

A visible path from input to answer.

Convert an airport-specific itinerary duration into local arrival time, or label a great-circle duration clearly as a planning estimate. The page keeps the calculation scope and its limits beside the result so the output can be checked, copied or revisited.

Calculation flow
  1. Read the record. The calculator uses Origin airport, Destination airport, Local departure date, Local departure time and Duration source and 4 additional fields supplied in the form.
  2. Apply the scope. It applies the Global airport-pair and IANA time-zone planning — scheduled itinerary controls; great-circle mode is explicitly an estimate reference and the explicit date, unit and counting conventions shown in the result.
  3. Expose the checkpoints. Intermediate rows, warnings and timeline events stay visible; the emphasized row identifies the primary checkpoint when one exists.
Illustrative default example Local arrival: Saturday, Aug 29, 2026, 6:30 AM GMT+1

JFK to LHR spans 7 hours in this user-entered itinerary scenario.

  • Scheduled duration input7 hours
  • Local arrivalSaturday, Aug 29, 2026, 6:30 AM GMT+1
Defaults are an illustration only. Replace them with the record that applies to your situation.
Assumptions and scope

Calculation purpose: Convert an airport-specific itinerary duration into local arrival time, or label a great-circle duration clearly as a planning estimate. This is a high-sensitivity reference output; the linked authority or qualified professional controls the final decision.

Boundary behavior

Calendar inputs use plain year-month-day semantics. Leap days, month ends, date-pair order and unsupported dates are checked before the result is shown.

Rule trail

Rule set 1.1.0 · Last reviewed 2026-08-23 · Next review due 2027-02-23. The source panel below contains the linked evidence.