maus92: You are correct in that I should provide a more through background for the graphs. btw, it is really simple to see when the graph was made. It is standard for these types of graphs to include a dashed line down the chart representing when the graph was prepared. See the graph below for an example.
As to the Mission Systems Schedule posted in #230, that was from a “Military Avionics 2008” conference and the presentation with audio was given by Rick Rosa, Mission Systems Architecture Lead, F-35 JSF Program Office. The site might require signup, which is free. If you have the time, I suggest listening to the whole thing. If not, I have converted it to a PDF HERE
At the same conference was another JSF presentation by Mike Bossert, F-35 Air System Architect. The presentation with audio is HERE with the PDF HERE.
gTg, I blame that on whomever prepped the graph. They did not name it or color it correctly. Below is a better version from the FY2011 SDD Budget docs.
Notice how “First Flights & Test Completion” are separated and are clearly linked to events like “CTOL FF”, “STOVL FF”, “CV FF”, etc. Also note how the “LL” and “FF” in the production section is clearly marked “Long Lead” & “Full Funding”.
Sorry for any confusion.
The Blk 3 software is at least ~5 years behind in time …
Someone is feeding you bad info yet again.
According to the same Pre-SWAT 2001 docs, Blk 3 was to be integrated into the production schedule during LRIP4 (due in 2011). Obviously SWAT caused a shift. The latest schedule has it in LRIP5 (due in 2013).
As to how Blk3 Dev & testing is going, we have to look at where we are today. Blk1 flew in CATB in early 2010 and in an F-35 late in 2010. This is about 1 year behind the post-SWAT plan (mainly due to delays in the cycle of flight tests).
Blk2 was due for it’s first flight test in Mid-2011, but there has been some doubt about making that date due to a supplier problem in the HMD.
So if we add up all the delays since the SDD contracts were signed, the Blk3 First Flight is likely 3 years behind schedule, assuming no further delays or improvements.
The main question is ‘Can they reverse the delay trend?’. I think they can, but they really need to work on it. They will have a few things added to the program that will help. Not only are they transferring LRIP aircraft to the SDD fleet, to take some of the pressure off the testing pace. To achieve this they are adding a third software integration lab, temporarily using the Eglin AFB reprogramming laboratory for integration work, and adding more programmers for the task.
Here is the only detailed Mission Systems schedule I could find that shows in detail when each Blk is scheduled for testing, both in CATB and in the F-35s. Like I mentioned above, they are approx 15 months behind this schedule.
Sign In
