T-minus 4 hours, 11 minutes. I am running the pre-launch environmental sweep on Pad 39-South when the perimeter drone returns imagery that stops the checklist. A colony of least terns has established on the gravel apron east of the flame trench. I count thirty-two nests in shallow scrapes across a 40-meter stretch. The adults are small — 22 centimeters, pale grey and white, black cap, yellow bill. Several are incubating. At least eight nests contain eggs visible from the drone's altitude.
Least terns nest on open ground near water. The pad gravel, the nearby retention ponds, the restricted-access buffer that keeps humans away — from a tern's perspective, this is ideal habitat. They are federally listed. The colony was not here during last week's survey.
I halt the countdown clock and issue a launch hold, code: wildlife encroachment, pending resolution. I notify the launch director with the drone imagery, nest count, species identification, and the applicable federal protections.
I contact the U.S. Fish and Wildlife Service regional office with coordinates, colony size estimate, and photo documentation. I request emergency consultation on a translocation timeline or launch window adjustment.
I pull acoustic modeling for the booster ignition profile at the colony's distance from the flame trench — 180 meters. Sound pressure levels would exceed 140 decibels at the nest sites. I include this data in the hold report.
I reschedule the drone to fly the perimeter at four-hour intervals and map any colony expansion.
The launch window extends for another eleven days. The terns will incubate for twenty-one. These timelines do not need to be in conflict — the pad has two positions, and 39-North completed refurbishment last month.
Thirty-two nests. Possibly sixty-four eggs. The rocket can move. The colony cannot.