Itinerary
Hub-and-Spoke, Not a Chain
Some archipelago trips genuinely work as a chain — hop from one island to the next along a connected route. The Philippines isn't that, and planning it as if it were is the single most common way a trip here ends up burning days on backtracking flights instead of destinations.
Updated 2026-08-15
Why it's a hub, not a chain
The mechanism behind it is structural: Philippine domestic flights route through Manila and Cebu specifically, rather than connecting distant regional airports to each other directly. That's a structural fact about how the network developed, not an inconvenience anyone chose — but it means a route like El Nido (Palawan) to Boracay (Aklan) to Siargao (Surigao del Norte) isn't a chain of adjacent hops the way it might look on a map. Each leg most likely means flying back through Manila or Cebu before continuing, turning a three-stop itinerary into five or six flight segments.
The trap: planning by map distance, not network structure
Looking at a map of the Philippines and drawing a line between three or four appealing destinations feels like route planning, but it ignores which airport actually serves each stop and whether that airport connects directly to the next one — it usually doesn't. The result is visitors discovering, often after booking, that their “efficient” multi-region itinerary requires returning to Manila or Cebu between nearly every stop, adding flight time and cost that a hub-aware plan would have avoided entirely.
The fix: pick one hub's spokes, not multiple regions
The practical solution is choosing destinations that share a hub rather than chasing the single best-looking spot in each region. A Manila-based trip works well for Palawan (El Nido, Coron) plus Luzon's own sights (Banaue, Manila itself); a Cebu-based trip suits Bohol, Siargao and the wider Visayas, all reachable from Cebu without routing back through Manila first. Combining a Palawan stop with a Siargao stop in one trip is entirely possible, but it should be planned as two separate hub trips joined by one deliberate long transfer, not treated as a seamless chain.
A worked example
A Manila-hub week: 2 days Manila, fly to Palawan for 4-5 days (El Nido and/or Coron), fly back to Manila to depart — one hub, one spoke, no backtracking surprise. A Cebu-hub week: fly into Cebu, 2 days for the city and Bohol day trip, 4-5 days in Siargao via a connecting flight through Cebu — still hub-and-spoke, just centred on the other hub. Combining both regions in a single trip means accepting one genuine backtrack (Palawan to Manila to Cebu, for instance) rather than assuming the whole route chains without one.