{"id":20653,"date":"2024-02-21T23:38:52","date_gmt":"2024-02-21T15:38:52","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/software-glitch-doomed-firefly-aerospaces-rocket-mission-investigation-reveals\/"},"modified":"2024-02-21T23:38:52","modified_gmt":"2024-02-21T15:38:52","slug":"software-glitch-doomed-firefly-aerospaces-rocket-mission-investigation-reveals","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/software-glitch-doomed-firefly-aerospaces-rocket-mission-investigation-reveals\/","title":{"rendered":"Software Glitch Doomed Firefly Aerospace\u2019s Rocket Mission, Investigation Reveals"},"content":{"rendered":"<p>Firefly Aerospace disclosed on February 20th that a critical software malfunction sabotaged the upper stage of its Alpha rocket during a December launch, thwarting a planned second burn and stranding its payload in a low orbit.<\/p>\n<p>According to a statement issued by Firefly, an anomaly in the guidance, navigation, and control (GNC) software hindered the upper stage from executing the intended circularization burn during the company\u2019s \u201cFly the Lightning\u201d mission on December 22nd. Consequently, the upper stage, along with its cargo\u2014a Lockheed Martin technology demonstration satellite\u2014remained trapped in an orbit with a low perigee.<\/p>\n<p>An extensive investigation, led by Firefly\u2019s internal mishap team and complemented by an independent review, traced the glitch to an error in the GNC software algorithm. This flaw prevented the system from transmitting vital pulse commands to the Reaction Control System (RCS) thrusters prior to the stage two engine relight. Although Firefly did not delve into specifics, it is presumed that the RCS thrusters would have facilitated proper stage orientation and stabilized propellant flow to the engine.<\/p>\n<p>\u201cWe\u2019re proud of the combined team\u2019s ability to work together to achieve this positive outcome,\u201d remarked Bill Weber, Firefly\u2019s chief executive, expressing optimism regarding the investigation\u2019s findings. \u201cLooking ahead, the important long-term outcome is the rapid, thorough maturation of Alpha as the dependable one-metric-ton-class rocket the market is demanding.\u201d<\/p>\n<p>Firefly affirmed its commitment to rectifying the GNC software error while instituting procedural enhancements to enhance fault detection in future missions. Although the company refrained from specifying a precise timeline, it assured stakeholders that the Alpha rocket would be primed for its next launch in the \u201ccoming months.\u201d<\/p>\n<p>The mishap not only jeopardized Firefly\u2019s mission objectives but also imposed challenges on Lockheed Martin, whose satellite was ensnared in a perilously low orbit with an initial perigee of approximately 215 kilometers. Despite the setback, Lockheed expedited the satellite\u2019s antenna technology tests within a \u201cdramatically compressed mission timeline,\u201d achieving substantial milestones within weeks. The satellite met its fiery demise on February 10th, as reported by The Aerospace Corporation.<\/p>\n<p>While Firefly has yet to announce a definitive return-to-flight schedule for the Alpha rocket, Brett Alexander, the company\u2019s chief revenue officer, reiterated earlier projections of performing four Alpha launches this year. Addressing concerns at the SpaceCom conference on February 1st, Alexander emphasized Firefly\u2019s unwavering commitment to its launch manifest, undeterred by the recent setback.<\/p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Firefly Aerospace disclosed on February 20th that a critical software malfunction sabotaged the upper stage of its Alpha rocket during a December launch, thwarting a planned second burn and stranding its payload in a low orbit. According to a statement issued by Firefly, an anomaly in the guidance, navigation, and control (GNC) software hindered the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":20654,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[444,443,472,20,6045],"class_list":["post-20653","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-alpha","tag-firefly-aerospace","tag-lockheed-martin","tag-satellite","tag-software"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/20653"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=20653"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/20653\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/20654"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=20653"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=20653"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=20653"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}