Rocket Lab schedules launches on an ongoing basis to deliver small satellites into precise orbital windows. Teams coordinate rideshare and dedicated missions across multiple launch sites to maximize flexibility and throughput.
Below is a structured overview of the program, highlighting mission IDs, payload types, launch pads, and target orbit profiles to help users quickly scan upcoming activity.
| Mission ID | Payload | Launch Pad | Target Orbit |
|---|---|---|---|
| Electron-411 | 36 Space Dots | Mahia LC-1A | 500 km Sun-synchronous |
| Electron-412 | ANIS and NEE-02 | Mahia LC-1B | 400 km inclined |
| Electron-413 | COMS 6U | Rocket Lab USA, LC-2 | 520 km retrograde |
| Electron-414 | Maritime Awareness Demo | Mahia LC-1A | Sun-synchronous phasing |
Rideshare Mission Cadence and Slot Planning
How rideshare launches are queued
Rocket Lab structures rideshare missions into sequential campaign windows that align with sun-synchronous dawn and dusk periods. Each slot targets a specific precess rate to keep lighting conditions consistent across imaging satellites. Load manifest activities begin months ahead, including integration, fit-checks, and compliance reviews.
Slot assignment follows priority tiers, with educational and early-stage payloads often placed in shared blocks to optimize cost. Real-time adjustments are possible when payloads require minor orbital tweaks, but major delays can shift entire sequences to preserve vehicle safety and regulatory coordination.
Operators publish a high-level cadence, yet exact timing may shift due to range availability, weather, and upstream processing. Customers receive detailed timelines during integration milestones, including encapsulation, transportation, and final countdown rehearsals.
Launch Site Operations and Range Availability
Mahia Peninsula and West Coast logistics
Operations at Mahia balance back-to-back campaigns with recovery and refurbishment cycles. Range teams coordinate with local authorities and maritime partners to maintain safe corridors, factoring in hazard zones and debris management plans. Integration facilities support both small and medium payloads, enabling rapid processing without long queue times.
On the West Coast, LC-2 focuses on national security and commercial payloads that require flexible launch azimuths. Site infrastructure supports vertical integration, wet dress rehearsals, and rapid rollback if contingencies arise. Coordination with airspace authorities and satellite operators ensures minimal conflicts during busy periods.
Across both regions, telemetry, tracking, and command systems are validated well before vehicle rollout. Real-time dashboards give stakeholders visibility into countdown phases, hold points, and successful completion of critical go/no-go gates.
Orbit Targeting and Mission Flexibility
Adjusting to changing customer needs
Rocket Lab designs missions to accommodate slight variations in altitude, inclination, and RAAN without major redesigns. Reaction control and kick stages provide additional delta-V for phasing maneuvers, enabling precise constellation layering. This flexibility is particularly valuable for Earth observation constellations that need gradual orbital spacing.
Planners model atmospheric conditions, propellant margins, and staging events to ensure each target orbit remains within verified performance envelopes. If customer requirements evolve late in processing, teams assess trade-offs between payload mass, orbital accuracy, and overall mission risk.
Every adjustment is documented and reviewed against flight heritage data to protect vehicle reliability. The result is a responsive schedule that can serve standardized payloads as well as bespoke orbital architectures.
Constellation Deployment and Specialized Campaigns
Bulk launches and precision deployments
For large constellation customers, Rocket Lab sequences clustered deployments across multiple vehicles or single Electron missions. Staggered release patterns reduce collision risk and allow satellites to drift into operational slots using onboard propulsion. Each manifest includes detailed deployment times and separation distances to satisfy regulatory filings.
Specialized campaigns such as polar and sun-synchronous passes are timed to meet mission-specific lighting and coverage requirements. These flights may involve custom avionics, tailored separation profiles, and coordination with ground stations for early acquisition. The schedule incorporates buffer periods to address anomaly recovery and replanning if needed.
Advanced planning tools forecast launch cadence against long-term demand, helping both internal teams and external partners align roadmaps. This integrated approach keeps Rocket Lab’s schedule responsive while maintaining clear visibility for customers and stakeholders.
Key Takeaways for Following Rocket Lab Launch Activity
- Monitor the official mission schedule and customer portals for real-time updates
- Understand that rideshare cadence can shift within designated deployment windows
- Coordinate orbit changes early to align with performance and regulatory limits
- Track range, weather, and processing milestones that influence on-time performance
FAQ
Reader questions
How can I find the exact date and time for my upcoming Rocket Lab mission?
Check the official Rocket Lab mission schedule page and your customer portal for the most current launch timeline, as times may shift due to range, weather, or priority changes.
What happens if a payload needs a different orbit than planned in the schedule?
Orbit change requests are reviewed during integration, and adjustments are approved based on vehicle performance margins, regulatory constraints, and impact on surrounding missions.
Can rideshare participants on a scheduled mission expect the same deployment order every time?
Deployment sequence follows the published plan, but minor timing shifts can occur to ensure separation safety and mission success; operators communicate updates through established channels.
How does weather at the launch site affect the published schedule?
Real-time weather reviews during count may trigger holds or 24-hour slips, and contingency opportunities are reserved in the cadence to preserve overall program flow.