LWC → NRTLawrence to Tokyo

live

Direct flights from Lawrence (LWC) to Tokyo (NRT) run nonstop between the two airports. The nonstop covers 9,933 km, an estimated 13 hours 14 minutes in the air.

LWC Lawrence tracking

NRT Tokyo smooth · +0

9,933 km · ~13h 14m est.

Running clean · 0 airlines · nonstop

100 / 100

route health from live LWC and NRT delay boards

Flight time~13h 14mestimated from route distance

Airports right now

live boards

LWCLawrence tracking Full LWC delay board →

NRTTokyo +0 min smooth 🌤 mostly cloudy · NE 8 kt Full NRT delay board →

How the Lawrence to Tokyo route actually runs

Pro Flight Search records official board updates for nonstop LWC to NRT flights through the day: schedules, estimates, gate pushes and actual departures. The verdict above comes from operated flights, so it reflects what this route does rather than what the timetable promises.

Planning around a delay? Live airport delays · Weather delay risk map · Will a delayed flight be cancelled? · Do planes make up time in the air? · How we measure

Cite this data

Journalists, bloggers, and researchers may cite this page with attribution and a link to Pro Flight Search.

Suggested citation

Pro Flight Search: Lawrence (LWC) to Tokyo (NRT) route reliability, measured from operated flights on official airport boards.

Canonical URL

https://proflightsearch.com/search-flights/LWC-NRT

How we measure this →

LWC to NRT questions

Is LWC–NRT running on time right now?

Smooth skies ahead. Both endpoints currently score the same, route health score 100/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from LWC to NRT?

Great-circle distance is 9,933 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 731–881 min gate-to-gate on this route.

What does the route health score measure?

A blend of departure-side delay at LWC and arrival-side delay at NRT, computed from rolling delay windows (refreshed every 40 minutes) with a daily-rollup fallback. Current MVFR, IFR, or LIFR endpoint weather caps the score when flight rules can limit throughput. Higher is healthier: 100 means operations are clean at both ends.