Rocket Launch Windows: NET and Your Local Time

Identify the schedule label first

NET means no earlier than. As an explicitly historical example, NASA's January 31, 2024 Crew-8 post paired NET in its title with a February 22 target in the text. That illustrates the label; it supplies no current launch date. If your schedule gives only a NET date, keep it as a provisional date rather than inventing an alarm time.

A launch window is the interval in which launch can satisfy mission and safety constraints. Read its stated opening and closing times together. A published target liftoff time identifies the time to plan around, but keep any accompanying NET label or window attached to it. Do not assume the opening is a confirmed liftoff or that every mission has the same window duration.

Convert the date as well as the clock

Record the year, month, day, clock time and stated source zone before converting. Check whether daylight saving or standard time applies on that date in the places involved. NIST explains that local-zone and daylight-saving corrections are handled by your computer's operating system; check its settings and updates before trusting the displayed conversion.

Convert both endpoints if a window is supplied, and retain any change of calendar day. If the source omits its zone or leaves the daylight-saving setting unclear, seek clarification in the mission's schedule information before setting an alarm. Avoid choosing an offset from memory or treating the launch site's clock as your own.

Worked example: a hypothetical midnight crossing

Hypothetical example only: a fictional schedule lists July 15, 2026, with a window from 00:30 to 01:30 UTC. Suppose your viewing clock is explicitly set to UTC minus four hours, with its daylight-saving correction already included. Subtracting four hours gives July 14, 2026, from 20:30 to 21:30 locally. These invented times illustrate conversion, not a real mission or a standard window length.

If that fictional notice separately gives a target of 00:45 UTC, record July 14 at 20:45 locally as the target within the converted window. Do not add another daylight-saving hour to an offset that already includes it. The practical gain is choosing the correct evening to watch rather than setting an alarm for July 15.

Before setting an alarm

Check these items in order: the latest mission schedule; whether the entry is NET, a window or a target; the complete source date and zone; the converted local date and daylight-saving setting; and both window endpoints, if supplied. If any item is missing, resolve it before committing the alarm. Keep the original schedule beside your conversion so you can compare later updates.

Then check the viewing direction and predicted appearance for your location. LookToSpace models when a rocket clears your horizon after liftoff, so the target launch time and your first possible sighting need not coincide. An open horizon matters, and terrain, weather and trajectory differences limit predictions. Correct timing helps you be looking in the right direction when the rocket may become visible.

Sources and further reading

• NASA: historical example of NET meaning no earlier than
• NASA: launch and flight fundamentals
• NIST: local time, UTC and daylight saving
• LookToSpace: visibility model and limitations