CTS → OKASapporo to Naha

live

Direct flights from Sapporo (CTS) to Naha (OKA): 7 nonstop departures observed each week across 1 airline. 89% of the last 9 operated flights arrived within 15 minutes of schedule. The median arrival is 3 minutes late. No cancellations were recorded across the 9 tracked flights. The nonstop covers 2,242 km, an estimated 3 hours 22 minutes in the air. Measured by Pro Flight Search from live flight boards at Sapporo and Naha. Updated 17 August 2026 at 06:14 UTC.

CTS Sapporo smooth · +5
OKA Naha smooth · +2
2,242 km · ~3h 22m est.
departs 15:057x weekly
Runs reliable · 1 airline · 7x weekly · nonstop
89% on time

of the last 9 operated CTS → OKA flights arrived within 15 minutes

Median arrival delay is +3 min. 0 of 9 tracked legs cancelled in the sample. Will a delayed flight be cancelled? →

Search live fares for this route →
Median arrival+3 minacross the last 9 operated legs
Flight time~3h 22mestimated from route distance
Weekly departures7x1 direct airline on the leg

Current nonstop fares

CTS → OKA · one way · economy · 1 adult

loading
TodayChecking…Direct airline fares
TomorrowChecking…Direct airline fares
In one weekChecking…Direct airline fares

The week

scheduled departures · origin local time
06121824
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Malta MedAir

Each mark is a scheduled departure at its origin-local time, observed operating in the last 7 days. Today is highlighted.

Who flies it

observed on the boards · 7 days
Malta MedAirMM86% on time

Flights MM273 15:05 daily

History

operated legs · board outcomes
08-17APJ273departed+7
08-16APJ273departed+11
08-16MM273arrived+6
08-15MM273arrived+16
08-14MM273arrived+3
08-13MM273arrived−22
08-12MM273arrived−6
08-11MM273arrived+2
08-10MM273arrived−16

Actual board outcomes rather than schedules, paired departure and arrival per flight and day.

Full board history, day by day →

Airports right now

live boards
CTSSapporo +5 min smooth 🌤 mostly cloudy · SSE 14 kt Full CTS delay board →
OKANaha +2 min smooth 🌤 few clouds · E 11 kt Full OKA delay board →

Weather lens

Current conditions put the pressure at OKA: 44% odds of a 15+ minute delay and around +13 min expected when it bites, measured from this route's own weather-matched delay history. See live delays → · Weather risk by airport →

How the Sapporo to Naha route actually runs

Pro Flight Search tracks every published board update for nonstop CTS to OKA flights: 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. Fares link straight to the operating airline with no markups.

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 — Sapporo (CTS) to Naha (OKA) route reliability, measured from operated flights on official airport boards.

Canonical URL
https://proflightsearch.com/search-flights/CTS-OKA
How we measure this →

CTS to OKA questions

Is CTS–OKA running on time right now?

Smooth skies ahead. The departure side at CTS is the weaker end, route health score 95/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from CTS to OKA?

Great-circle distance is 2,242 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 188–222 min gate-to-gate on this route.

How often does CTS–OKA fly?

Malta MedAir runs the route with about 7 flights a week (daily). Since one carrier owns the route, a single disruption tends to ripple through the day.

What does the route health score measure?

A blend of departure-side delay at CTS and arrival-side delay at OKA, 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.