Rocket Lab completes analysis of Still Testing launch abort

Posted on 13 December 2017

Wednesday 13 December, 2017: Rocket Lab has completed analysis of the Electron test flight abort that occurred during the company’s ‘Still Testing’ launch attempt yesterday. 

The analysis determined the launch was aborted due to rising liquid oxygen (LOx) temperatures feeding into one of the Electron’s nine Rutherford engines on the vehicle’s first stage. Rocket Lab has implemented corrective actions ahead of the next launch attempt, which is currently targeted for no earlier than 2.30 pm, Thursday 14 December NZDT. 

The slight LOx temperature increase was a result of a LOx chilldown bleed schedule that was not compatible with the warm conditions of the day at Launch Complex-1. Rocket Lab has modified the bleed schedule to ensure components are sufficiently chilled ahead of a new launch attempt tomorrow. 

While the temperatures were within safe parameters for launch, Rocket Lab had set conservative parameters for the test flight campaign that led to the vehicle performing a safe auto-sequence abort at T-2 seconds prior to a lift-off. The abort caused no damage to the vehicle or launch pad infrastructure, with the vehicle performing exactly as expected in accordance with the launch criteria.

Rocket Lab CEO and founder Peter Beck said the rapid and safe abort was yet another advantage of Rocket Lab’s advanced electric-turbopump engine technology, which can shutdown significantly faster than traditional turbopump engines.  

“Electron performed as it should if it detects anything off-nominal during the auto-sequence and the electric turbopumps shut down in milliseconds. Our team developed very advanced systems to prevent launch if any one of thousands of factors isn’t perfectly aligned, and yesterday we proved those systems are performing well,” he said. 

“We quickly identified the cause, put corrective actions in place and are looking forward to another launch attempt soon.” 

For real-time updates from Rocket Lab, follow us on Twitter @RocketLab