The same runway section had failed twice in four weeks
For the second time in less than a month, LaGuardia Airport has closed one of its two primary runways after inspectors found a two-inch depression in the pavement — the same stretch that buckled during the Memorial Day rush. In a city where infrastructure and urgency are perpetual companions, the recurring failure raises a quieter, more unsettling question: whether what lies beneath the surface has been truly understood, or merely patched. Thousands of travelers absorbed the disruption Wednesday evening while repair crews worked through the night, holding open the possibility that by Thursday morning, the wound would be dressed — if not yet healed.
- A two-inch pavement depression on Runway 4/22 triggered LaGuardia's second emergency closure in under four weeks, halting operations on one of New York City's busiest airport corridors.
- With only one primary runway absorbing the full weight of the schedule, delays cascaded quickly — 174 flights affected and an average 48-minute wait grinding through the afternoon and evening.
- The repetition is what unsettles: the same runway section failed near Memorial Day, was repaired, and has now failed again, suggesting the original fix may not have reached the root of the problem.
- Overnight crews raced to assess, stabilize, and restore the runway before Thursday morning's travel wave, but the outcome hinged on what the pavement revealed beneath the surface.
- Airport officials urged passengers to contact their airlines directly, a quiet acknowledgment that the posted schedule had become unreliable and the situation remained fluid.
On Wednesday afternoon, LaGuardia Airport closed Runway 4/22 after inspectors found a roughly two-inch depression in the pavement running alongside the strip. Officials described the move as precautionary, stressing no immediate safety threat — but the discovery demanded action. By 5 p.m., all operations had shifted to the airport's single remaining primary runway, 13/31, while repair crews began an overnight assessment to determine the cause and perform whatever stabilization work was needed. The target: restore the runway before Thursday morning.
The human toll was immediate. Flight-tracking data showed arrivals delayed an average of 48 minutes, with 174 delays already logged before the formal closure. Thousands of passengers waited, phones in hand, as the airport advised travelers to check directly with their airlines rather than rely on posted schedules.
What gave the closure its weight was its familiarity. The same runway section had forced emergency work around Memorial Day, when a sinkhole formed in nearly the same location. Two significant pavement failures in less than four weeks on one of New York's most trafficked airports pointed toward something more than routine wear — raising questions about the integrity of the underlying structure and whether a single overnight repair could hold.
LaGuardia's two-runway design leaves little margin for error. When one closes, the other must carry everything, and the bottlenecks form fast. As crews worked through the night, the deeper question remained open: whether the pavement would yield a straightforward fix by morning, or whether it would reveal a problem that no overnight crew could fully resolve.
On Wednesday afternoon, LaGuardia Airport shut down Runway 4/22 after inspectors discovered a depression in the pavement roughly two inches deep running adjacent to the strip. It was the second time in less than a month that the same runway section had forced an emergency closure, a pattern that began to suggest something deeper than routine wear.
The airport framed the decision as precautionary. Officials stressed there was no immediate safety threat, but the discovery warranted action. The closure took effect at 5 p.m., shifting all operations to LaGuardia's single remaining primary runway, 13/31, while repair crews worked through the night to assess the damage, determine what caused it, and perform whatever stabilization work proved necessary. The goal was to have the runway operational again by Thursday morning.
The timing hit hard. By mid-afternoon, flight-tracking data showed arrivals backed up by an average of 48 minutes. Earlier in the day, before the official closure, 174 delays had accumulated across the airport's schedule. Thousands of passengers found themselves waiting, checking their phones, calling airlines for updates. The airport urged travelers to contact their carriers directly for current flight status rather than relying on posted schedules.
What made this closure noteworthy was its repetition. The previous incident had occurred around Memorial Day, when a sinkhole had formed in roughly the same location, forcing similar emergency work. Two major pavement failures in four weeks on one of New York City's busiest airports suggested the problem might not be a one-time event. The recurring nature of the damage raised questions about what lay beneath the surface—whether the underlying structure was sound, whether the original repairs had held, or whether there was a systemic issue that a single overnight fix could not address.
LaGuardia operates with just two primary runways, making either one critical to the airport's capacity. When one closes, the other must absorb the full load, creating immediate bottlenecks. The airport's statement acknowledged the disruption but emphasized the commitment to completing repairs safely and restoring normal operations as quickly as possible. Whether that would happen by Thursday morning, or whether the pavement would reveal deeper structural problems requiring more extensive work, remained to be seen as the repair crews began their overnight assessment.
Citações Notáveis
Our goal is to complete the assessment and any necessary repair work overnight and return the runway to service as soon as it is safe to do so— LaGuardia Airport officials
A Conversa do Hearth Outra perspectiva sobre a história
Why does a two-inch depression in pavement warrant closing an entire runway? Isn't that being overly cautious?
A runway is engineered to precise specifications. Even small deviations can affect how aircraft land and take off—weight distribution, braking distance, structural stress. Two inches might sound minor, but at scale it matters.
But they said there's no immediate safety concern. So why not just warn pilots and keep flying?
That's the question, isn't it. The fact they closed it suggests they weren't entirely confident in that assessment. And the fact it happened in the same spot a month earlier—that changes the calculus. You start wondering if the ground underneath is stable.
What does a sinkhole in May have to do with a depression in June?
Same location. Same runway section. If the ground shifted once, it might shift again. Or maybe the first repair didn't take. Either way, it signals something's wrong below the surface, not just on top of it.
So this could happen again?
That's what the overnight assessment will try to answer. If they find the underlying structure is compromised, a quick patch won't solve it. They might need to do something much more extensive.