D
docm
Guest
<blockquote><font class="small">In reply to:</font><hr /><p><b>NASA's hopes of manned flights before 2014 are dashed as Orion programme hits first hold-up</b><br /><br />By Rob Coppinger<br /><br />NASA internal planning, official's comments and contractor expectations suggest much touted goal of manned flights of new crew vehicle Orion before 2014 are unrealistic<br /><br />NASA will fail to meet its goal of flying manned Orion missions before 2014, as the first delay emerges for the new spaceship's development timetable just a week after its prime contractor, Lockheed Martin Space Systems, was selected.<br /><br />NASA administrator Michael Griffin had wanted Orion's development accelerated because the four-year gap between the Space Shuttle's 2010 retirement and the new spacecraft's planned 2014 operational debut was deemed unacceptable. The prime contractor selection process was even adjusted for changes introduced by NASA to accelerate Orion.<br /><br />However NASA internal planning documents obtained by Flight International, and recent comments by Constellation and Lockheed Martin programme officials, reveal that this goal is unrealistic.<br /><br />In an interview with Flight International last week, Lockheed Project Orion business development manager Patrick McKenzie said that the "requirements review (SRR) should slip into the first quarter of next year". NASA's plan had been for Orion's SRR to occur in the fourth quarter of 2006.<br /><br />While McKenzie was sure his company could deliver the Orion for a 2012 manned flight, at the 31 August contractor selection announcement Project Orion office manager Caris Hatfeld said "a full and final" Ares I test was unlikely before 2012 in order to complete the launcher's upper stage and its Pratt & Whitney Rocketdyne J-2X engine. That 2012 test flight will not be manned.<br /><br />The leaked documents and corroborating NASA sources describe a timetable where the Ares I-1 test would occur in 2009, followed by the 2012 flight, w</p></blockquote> <div class="Discussion_UserSignature"> </div>