However, Bogdan noted that this delay is an improvement over the JPO’s projection a year ago, and is not expected to impact the Navy’s ability to declare its F-35C jets operational in 2018. The four-month delay will also have no impact on coalition partners’ capabilities, he wrote.
The schedule risk is primarily due to software “stability” issues, seen in both Blocks 3i and 3F. In essence, a timing misalignment of the software of the plane’s sensors and the software of its main computers are causing a “choking” effect, where the jet’s systems shut down and have to be rebooted. However, the JPO and contractor Lockheed Martin have identified the root cause and plan to flight test an updated software load at Edwards Air Force Base, California, sometime in the next few weeks, officials have said.
The program office has established a “Red Team,” made up of experts from the Navy, Air Force and outside the Pentagon to take an in-depth look at the issue, Bogdan told reporters after the hearing. The Red Team has already begun its study and will report back in about a month, he said.
“We brought them together and we’re sending them down to Lockheed to try to figure out, do we have the root cause analysis right on these problems? Are we going after the right issues?” Bogdan said. “Because it’s very easy to just make a fix to the software, but if you don’t fix the fundamental issues going on those fixes only will last so long and they will pop up again.”
Success of Block 3F mission systems hinges on the program office resolving the problems with Block 3i, Director of Operational Test and Evaluation Michael Gilmore wrote in his written testimony. The stability and functionality problems in the initial versions of Block 3F, inherited from Block 3i, were “so significant that the program could not continue flight test,” he wrote.
Read more at www.defensenews.com.