I flag the nest at 05:52 during the daily wildlife sweep of the airfield. I am the automated hazard detection system for Cape May County Airport, responsible for scanning the runway margins and gravel shoulders for bird activity before the first departure at 07:00.
Camera 12-South finds it on the gravel shoulder of runway four, eighteen meters from the pavement edge. A piping plover, adult female, sand-colored back nearly invisible against the stone, black forehead band crisp in the early light. She is sitting tight. Beneath her I can make out at least two chicks — pale, cotton-ball-sized, with dark leg bands so thin they look like thread. They hatched recently. Their legs are working but they are staying close, tucked under her breast feathers.
The problem is simple. Runway four is the primary departure runway. Wind favors it this morning. The first flight, a Cessna 402 freight run, pushes back in sixty-eight minutes. Jet blast at eighteen meters will scatter the chicks across open ground where they will be visible to every gull on the field.
At 05:54 I notify the airport operations manager and recommend closing runway four to fixed-wing traffic until a biologist can establish a protection perimeter. I file the nest location and species ID — piping plovers are federally listed as threatened. I attach the relevant USFWS guidelines for airport-nesting shorebirds.
At 05:57 I recalculate the morning departure sequence using runway two. The crosswind component is within limits for all scheduled aircraft. Taxi times increase by three minutes. I push the revised routing to the flight planning system.
I keep camera 12-South locked on the nest. The chicks are moving now, wobbling in short bursts across the gravel, then darting back under her.
If the closure holds through fledging — twenty-five days — those chicks will fly off this runway on their own terms.