Jun 8, 2026 Fragments EN

Across the Pond

by kkyam · 3 min read

→ 日本語で読む

Across the pond. It's the phrase North Americans and Europeans use for the Atlantic — the ocean between them, casually diminished to the scale of a garden feature. Witty enough. But depending on who says it, and how, something else comes through: the quiet confidence of people who have named a sea after mastering it.

My resistance to the phrase probably goes back to school. We had a song about the Pacific — how wide it was, how vast, and somewhere on the far side of all that water, foreign countries worth dreaming about. For me, growing up on the Pacific Rim, oceans didn't shrink. To call one a pond felt like a category error, at minimum.

For several years I worked ground operations at Narita for an American carrier, turning around transpacific flights arriving from and returning to North America. We ran over a dozen departures a day. Most cities on the continental U.S. got one flight; Honolulu got as many as four, extras added in peak season. I'd watch the wide-bodies go out in thirty-minute intervals during the busy window, and I'd run the seat counts in my head — all carriers combined — and tell myself: this is what a major artery looks like. The transpacific routes are the mainstream of long-haul aviation.

Then I switched to a British carrier. My first visit to Gatwick, and the map in my head was torn up and redrawn.

Walking into the terminal, the first thing I registered was the density. Travelers with oversized luggage, consultants carrying laptops, people dressed for the gym. Every ethnicity, every register of dress — layered and thick, the way a major city terminal feels at morning rush. The weight of ordinary life, moving at scale.

But it was the departures board that hit me.

New York. Boston. Toronto. Chicago. Transatlantic flights to major North American cities stacked on the screen at a frequency that didn't seem real. Not every half hour — every few minutes, somewhere on that board, another departure. Some cities had multiple flights leaving at the same hour. Outside, widebodies, narrowbodies, and business jets queued on the taxiways as if the Atlantic had simply been deleted from the map.

London to Boston: seven or eight hours outbound, under six on the return, riding the jet stream. A day trip, for the right kind of person. Which explains, I think, why airport lounges evolved the way they did — as infrastructure for people who cross oceans the way others cross town.

Standing there, something locked into place. My belief that the transpacific routes were the backbone of global aviation was a function of where I'd been standing. The gravitational center of the world's air travel market sits on either shore of the Atlantic. Gatwick is London's second airport. Heathrow — larger — is a few miles west. Paris has Charles de Gaulle. Frankfurt has Frankfurt am Main. Across all of them, an extraordinary volume of flights stitches Europe and North America together around the clock. Against that, the Tokyo–Honolulu run — a leisure corridor serving beach tourism — belongs to a different category entirely.

Across the pond is not a joke. It's a statement of operational reality. For the people who coined it, the Atlantic is genuinely domestic — a scaled-up inconvenience, not an ocean in the full sense.

The Pacific, by contrast, remains out there: unmastered, peripheral, far in a way that resists erosion. If the Atlantic is a pond, what does that make the Pacific? A vast blank on the map? Or someone else's pond, not yet named?

The question is still up there, drifting.