Mrt 24 2016

Alarming testimony by Gilmore (DOT&E): F-35 problems continuing

Gepubliceerd door om 18:50 onder Global F35 News

Statement of the honorable J. Michael Gilmore, Director, Operational Test and Evaluation Office of the Secretary of Defense

Before the Tactical Air and Land Forces Subcommittee of the US House Armed Services Committee.

Summary of DOTE testimony:
- JSF Program is at a critical time
- Block 3i software fielded, however many unresolved significant deficiencies
- By overlap of production and testing many F-35s need costly and time consuming modifications and retrofits (300 aircraft involved; US$ 3 billion extra costs)
- Availability of effective mission load files may be a challenge
- Cybersecurity testing not completed and revealed important deficiencies
- Electro-Optical Targeting System (EOTS) on F-35 considered inferior by pilots to those currently on legacy system
- CAS capabilities in its childhood; a long way to go (fuel, targeting and weapons limitations)
- Alert launch test, with multiple aircraft involved, failed due to start-up problems
- High fuel burn rate (60% more than F-16); more tanker support necessary
- Heavy load of 931 open or unresolved (technical) deficiencies
- Ejection seat (escape system) immature and requires modifications and new testing
- Major findings continuing in the durability tests
- ALIS (logistics and maintenance) software not ready and problems in remote operations
- F-35 reliability/availabiloty improving but much too low
- New challenge is managing all different software and hardware versions
- Deployment sustainment tests show bad results (50-60% availability)

Text of Statement

Good afternoon, Mr. Chairman, Ranking Member Sanchez, my testimony today discusses the status of the F-35 program using my Fiscal Year (FY) 2015 Annual Report as the basis. There are a few updates since the report was released in January 2016, which I will highlight today.

Program at a critical time

Overall, the program is at a critical time. Although the Marine Corps has declared Initial Operational Capability (IOC) and the Air Force plans to do so later this calendar year (CY), the F-35 system remains immature and provides limited combat capability, with the officially planned start of Initial Operational Test and Evaluation (IOT&E) just over one year away. Over the past year, flight test teams continued to accomplish test flights at the planned rate, and a new version of software capability, Block 3i, was fielded. However, there are still many unresolved significant deficiencies, the program continues to fall behind the planned software block development and testing goals, and sustainment of the fielded aircraft is very burdensome. (The latter is not a surprise, since, as the Program Executive Officer has noted, F-35 remains under development notwithstanding the Services’ declarations of IOC.) The program is working to resolve the many issues it confronts, but my assessment is that the F-35 program will not be ready for IOT&E until CY18 at the soonest. Because aircraft continue to be produced in substantial quantities (all of which will require some level of modifications and retrofits before being used in combat), IOT&E must be conducted as soon as possible to evaluate F-35 combat effectiveness under the most realistic combat conditions that can be obtained. Over 300 aircraft are planned to be built by the end of FY17 when IOT&E is currently scheduled to begin.

Testing progress, despite severe problems

Test teams executed very closely to the planned sortie production rate throughout the year, as has been the case in previous years. It will be important to ensure the government flight test centers and the associated ranges and facilities at Edwards Air Force Base (AFB) and Patuxent River Naval Air Station (NAS) remain sufficiently resourced to overcome the remaining test challenges, which are significant. However, sortie production does not necessarily mean that planned test points were completed successfully, the system under test functioned as designed, the data collected were usable to sign off contract specification compliance, or that the system will actually be effective and suitable in combat.
In fact, the program did not accomplish the amount of test points planned in several flight test venues, and the program continued to add testing via “growth points” while deleting many mission systems test points as no-longer-required. Because of a change by the program in defining growth in test points, the amount of this re-defined growth was less during the last year than in previous years.
Regarding mission systems test progress over the past year, the program focused on culminating Block 2B development and testing in order to provide a fleet release enabling the Marine Corps F-35B Joint Strike Fighter (JSF) declaration of IOC, while transitioning development and flight test resources to Block 3i and Block 3F.
The program terminated Block 2B development in May 2015, and the Marine Corps declared IOC in July 2015, despite known deficiencies and with, as expected, limited combat capability. Block 3i developmental flight testing restarted for the third time in March 2015, after two earlier attempts in May and September 2014. As mentioned in my annual report, Block 3i began with re-hosting immature Block 2B software and capabilities into new avionics processors. Though the program originally intended that Block 3i would not introduce new capabilities and would not inherit technical problems from earlier blocks, both of these things occurred. Despite ongoing severe problems with avionics stability, sensor fusion, and other issues, the program terminated Block 3i developmental flight testing in October 2015, and released Block 3i software to the fielded units. This decision was made, despite the unresolved Block 3i deficiencies, in an attempt to meet the unrealistic current official schedule for completing development and flight testing of Block 3F mission systems.
The Air Force insisted on fixes for five of the most severe deficiencies inherited from Block 2B as a prerequisite to use the final Block 3i capability in the Air Force IOC aircraft; Air Force IOC is currently planned for August 2016 (objective) through December 2016 (threshold). However, as the program attempted to concurrently develop and test Block 3i and Block 3F software, the latter of which began flight testing in March 2015, the immaturity and instability of the Block 3i mission systems software continued to manifest problems in flight testing. In February 2016, when the latest version of Block 3F software – version 3FR5 – was delivered to flight test, it was so unstable that productive flight testing could not be accomplished. Consequently, the program elected to reload a previous version of Block 3F software – version 3FR4 – on the mission systems flight test aircraft, to allow limited testing to proceed. The program converted its developmental labs back to the Block 3i configuration in another attempt to address key unresolved software deficiencies, including the avionics instabilities troubling both Block 3i and Block 3F. This decision by the program to return to the Block 3i configuration and address the poor mission systems performance should be commended. It will likely cause some delays, but it is a necessary step to ensure the Air Force has adequate Block 3i software for IOC and that the additional full set of combat capabilities planned in Block 3F can be effectively tested with a stable baseline and eventually fielded to operational units. The extent to which the significant outstanding deficiencies are being addressed thus far is still to be determined; the program plans to begin flight testing of another version of Block 3i software, version 3iR6.21, in late March 2016.

Block 3F presents significant challenges

Realizing the numerous new and advanced capabilities planned to be in Block 3F mission systems, which are specified in the program’s Operational Requirements Document (ORD), presents significant challenges for remaining development and flight test. Before the program’s decision to pause Block 3F developmental flight testing and rework Block 3i software, test progress was limited as flight testing had only accomplished approximately 17 percent of the Block 3F baseline test points by the end of February 2016. This is because many of the test points, including the more complex weapons delivery accuracy events, could not be flown until stable, functioning Block 3F software was available. After this next version of Block 3iR6.21 software has completed flight testing and the next iteration of the Block 3FR5 software is developed and tested in the lab, the program plans to release 3FR5 to the test centers and resume Block 3F flight testing. Because of the reworking of Block 3i software and the added capability being incorporated in the remaining Block 3F software, it is incorrect to assume that the difficult testing is behind the program. In fact, the most stressing missions systems testing remains to be completed, since the final Block 3F capabilities are both complex and important to the F-35’s viability. A recent example is an attempted four-ship Electronic Warfare “Super Scenario” mission with Block 3F software that resulted in only two aircraft arriving at the range because the other two aircraft ground aborted due to avionics stability problems during startup. Also, when the aircraft operated in a dense and realistic electromagnetic environment, the current avionics problems caused poor detection and fusion performance, which is exacerbated in multi-ship F-35 formations. Due to the large amount of difficult flight testing remaining, it is likely 6
there will be discoveries of additional significant deficiencies that will need to be rectified before IOT&E.

United States Reprogramming Laboratory (USRL)

Significant, correctable deficiencies exist in the U.S. Reprogramming Laboratory (USRL) that will preclude development and adequate testing of effective mission data loads for Block 3F. Despite a $45 Million budget provided to the Program Office in FY13, the required equipment was not ordered in time and the USRL is still not configured properly to build and optimize Block 3F Mission Data Files (MDFs). The program still has not designed, contracted for, and ordered all of the required equipment – a process that will take at least two years for some of the complex equipment – after which time for installation and check-out will be required. The estimate of earliest completion is 2019, which is after the planned IOT&E of Block 3F. As I explain in my annual report, the corrections to the USRL are needed to provide F-35s the ability to succeed against the modern threats that are the key rationale for pursuing this $400-Billion program. If the situation with the USRL is not rectified, U.S. F-35 forces will be at substantial risk of failure if used in combat against these threats. Further, I note that the laboratory being built to provide MDFs to the partner nations will be more capable than the USRL is when we are preparing for IOT&E. The full set of required upgrades for the USRL should be pursued immediately, without further delay.

Cybersecurity testing

The limited and incomplete F-35 cybersecurity testing accomplished to date has nonetheless revealed deficiencies that cannot be ignored. Multiple tests are scheduled for spring 2016; however, the JSF Program Office (JPO) and contractor are still reluctant to allow testing of the actual Autonomic Logistics Operating Unit (ALOU) including its many connections, fearing testing might disrupt its operations. Even though the program is providing alternate systems for ALOU testing in the near term, which is better than foregoing all testing, it must allow full cooperative and adversarial cyber tests on every level and component of the operational Autonomic Logistics Information System (ALIS), as well as the actual aircraft, as soon as possible. Cybersecurity testing on the next increment of ALIS – version 2.0.2 – is planned for this fall, but may need to be delayed because the program may not be able to resolve some key deficiencies and complete content development and fielding as scheduled.

IOT&E readiness and adequacy

IOT&E will be the first rigorous evaluation of the combat capability of the F-35. However, the current schedule to complete development and enter IOT&E by August 2017 is unrealistic. The problem is, and has been, the slow rate at which required combat capabilities are maturing; that is, becoming stable and viable enough to successfully complete testing. Based on the historical performance of the program and the large amount of testing that remains, my estimate for completion of developmental flight test is no earlier than January 2018. For these reasons, the test organizations’ capacity should be maintained at current levels, and not reduced in a counter-productive effort to meet unrealistic budget targets. Several other significant obstacles remain to be overcome before IOT&E can begin, including the following:

1 - Weapons integration. A significant amount of weapons integration developmental testing remains in order to integrate and qualify for operational use of the full suite of Block 3F weapons, including the gun. Since my annual report, nothing has changed my estimate that the program must complete weapons employment test events at a pace three times faster than it has previously been able to do. Eliminating some of the planned developmental weapons test events will only result in deferring them to be done later by the operational test squadrons, which will likely delay identification
and correction of significant new discoveries and, therefore, delay IOT&E. The developmental weapons test events are critical in preparing for IOT&E and the Block 3F weapons events are much more complex than previous testing for Block 2B and Block 3i. For example, critical air-to-air and air-to-ground gun accuracy testing still has not occurred because test aircraft have not received the required gun modifications, which are expected in summer 2016. Whether the F-35, the first modern fighter without a heads-up display, can accurately employ the gun in realistic situations with the Generation III Helmet Mounted Display System remains to be seen until this testing can be conducted.
2 - Modification of aircraft. One of numerous penalties associated with highly-concurrent F-35 development and production is that all the early operational aircraft now need many significant, time-consuming, and costly modifications. The 18 U.S. aircraft (6 each of F-35A/B/C) required for IOT&E need to be representative of the configuration of the weapons system that will be bought at full production rates, which is Lot 9 or Lot 10 and later; recall that the operational test aircraft were purchased in early production lots (Lot 3 through 5), when the program planned IOT&E to occur in 2013. The program and the Services need to decide whether to pursue all of the modifications needed to those early-lot aircraft prior to IOT&E, or to equip later production aircraft, requiring few or no modifications, with the necessary instrumentation for IOT&E. Nothing substantive has occurred since my annual report to change my estimate that if the former course is pursued, the aircraft designated for IOT&E will not be ready until April 2019. This is despite ongoing efforts by the program to accelerate the modification schedule. The program is also pursuing other options, including taking some of the new Block 3i processor sets from the production line to modify some of the IOT&E aircraft. The program and Services are also considering swapping new Block 3i processors from other delivered aircraft with the operational test aircraft that are currently configured with Block 2B hardware. The primary problem with staying on the course of completing modifications of the older aircraft is that the production line and the depots – where earlier lot aircraft are being modified – compete for the same materiel. Of course, this issue affects not only the IOT&E aircraft, but all of the aircraft produced before at least Lot 9 as well. A decision is needed now on the approach to be taken to provide production-representative aircraft for operational testing.
3 - Mission data. I already addressed earlier in my statement the problems with the USRL with respect to the need for upgrades in order to be able to produce mission data loads for Block 3F IOT&E. Again, this is a significant problem for the program and the processes involved in completing the Block 3F laboratory upgrades need to be accelerated, or IOT&E could be delayed well into 2019, with the combat capability of the F-35 remaining deficient. Besides programming the mission data loads, the laboratory is also used as a test venue for optimizing the performance of scan schedules within the data loads. These schedules command the time-sharing of the radar and the electronic support systems to ensure threat signals are detected, geo-located, and correctly identified for battlespace awareness. Such testing takes time in the laboratory and should be completed prior to, and refined after, testing on the open-air ranges.
4 - Sustainment. In my annual report I provided details on operational suitability. I highlight here, with respect to IOT&E readiness, that if the program is only able to achieve and sustain its goal of 60 percent aircraft availability, the length of IOT&E will increase significantly because a combat-ready availability of 80 percent is planned and needed to efficiently accomplish the open-air mission trials with the number of aircraft planned for IOT&E. Improvements in reliability and maintainability, along with significant improvements to the ALIS, are all needed. The program has worked and achieved better performance in these areas over the past two years, but progress is still too slow if the program is to be ready for IOT&E in less than two years. Of course, this is not only an issue for IOT&E execution, but also for the fielded operational units.
5 - Operator preparedness. In addition to having production representative aircraft, effective mission data, and improved sustainment, the units that will execute the operational test trials need viable tactics and enough time to become proficient by training to them. For example, the pilots will need time to adapt to and train with the new Generation III Helmet Mounted Display System that will begin testing later this year. The operational test team has always planned for this training to occur; however, the program continues to believe that this can be done concurrently with development. Concurrent development and training for test has been tried in other programs, and is fraught with difficulty and failure.
6 - Test range improvements. I have been working within the Office of the Secretary of Defense and with the Service staffs for the past five years to improve the test venues for operational testing of F-35 and other platforms, in particular the open-air
test resources. These efforts have resulted in putting improvements on track for F-35 IOT&E to be able to include already fielded advanced threats that previously were not going to be available for testing and training. However, resistance and bureaucratic delays to adequately integrating these assets continue despite the decision having been made by the Secretary of Defense to ensure a full and complete test capability that is no less than that available with older threat systems. I will continue to work to bring the needed level of integration to fruition, and appreciate the support provided so far.
7 - IOT&E plans. IOT&E will include trials in various mission areas, specifically Close Air Support (CAS), Surface Attack, Suppression/Destruction of Enemy Air Defenses (SEAD/DEAD), Air Warfare (both offensive and defensive), and Aerial Reconnaissance. The IOT&E will also include tests that compare the ability of the F-35 to accomplish CAS, Combat Search and Rescue and related missions – such as Forward Air Controller (Airborne) – with the A-10, plus SEAD/DEAD missions with that of the F-16, and Surface Attack missions with that of the F/A-18. These comparison test trials are essential to understanding the new capabilities expected from the F-35 program, relative to the legacy systems it is designed to replace. The trials will be designed to answer the question, “Is the new system as good as or better at accomplishing the mission than the legacy system under the same conditions and in the same environment?” Comparison testing is not new with the JSF. Of note, the F-22 completed comparison testing with the F-15 during its IOT&E. Typically, many variables are present during operational testing that cannot be controlled, especially in force-on-force exercises. Areas where commonality in the variables can be sought among trials to enable valid comparisons include: the type of mission; the size, organization, and capability of the enemy force; the terrain (or environment) where the test is conducted; the size, organization, and capability of the supporting blue forces; and time available to accomplish the mission. These comparison test trials will be designed as “matched pairs” where the F-35 aircraft will fly the mission trial and then the comparison aircraft will fly the same mission trial, under the same operational conditions, with pilots making best use of the differing capabilities and tactics for employing each aircraft.

Block 2B Capabilities Fielded

As mentioned in my annual report, if used in combat, the Block 2B F-35 will need support from command and control elements to avoid threats, assist in target acquisition, and control weapon employment for the limited weapons carriage available (i.e., two bombs and two air-to-air missiles). Block 2B deficiencies in fusion, Electronic Warfare, and weapons employment result in ambiguous threat displays, limited ability to respond to threats, and a requirement for off-board sources to provide accurate coordinates for precision attack. Since Block 2B F-35 aircraft are limited to two air-to-air missiles, they will require other support if operations are contested by enemy fighter aircraft. The program deferred deficiencies and weapons delivery accuracy test events from Block 2B to Block 3i and Block 3F, a necessary move in order to transition the testing enterprise to support Block 3i flight testing and Block 3F development, both of which began later than planned in the program’s integrated master schedule. The program fielded new software for the ALIS during 2015. These versions included new functions, improved interfaces, and fixes for some of the deficiencies in the earlier ALIS versions. The program also fielded a new version of the Standard Operating Unit (SOU) which is more modular and easier to deploy. However, many critical deficiencies remain which require 13
maintenance personnel to use workarounds to address the unresolved problems. For example, training systems for ALIS are immature and require maintenance personnel to learn ALIS processes in the fielded locations. Also, data within ALIS modules referring to aircraft parts are often inaccurate and need to be manually corrected. In addition, the process for creating and receiving action requests, needed for resolving maintenance issues when technical data are insufficient or not clear, is lengthy and burdensome.
The Marine Corps conducted a deployment demonstration to the USS WASP in May 2015, which provided lessons learned and highlighted limitations for conducting ship-borne operations. The Marines also conducted a deployment demonstration to the Strategic Expeditionary Landing Field near Marine Corps Air Station (MCAS) Twentynine Palms, California, in December 2015. Both deployments required extensive time to transfer data to the deployed ALIS and ensure files were formatted correctly to support operations. In addition, low aircraft availability rates resulted in less than planned sortie generation rates.
The Air Force also conducted deployment demonstrations – one as a “cross-ramp” deployment of three F-35A aircraft across the ramp at Edwards AFB, California, in April and May 2015 and another with six F-35A aircraft to Mountain Home AFB, Idaho, in February 2016. Like the Marine Corps demonstrations, the cross-ramp deployment required extensive time to get ALIS set up and data files transferred from the operational unit. ALIS set up and data transfer during the Mountain Home deployment was more efficient than in other demonstration, being completed within four hours for each of the six aircraft. The Air Force attempted two alert launch procedures during the Mountain Home deployment, where multiple F-35A aircraft were preflighted and prepared for a rapid launch, but all failed to accomplish the alert launch successfully due to start-up problems requiring system or aircraft shut-downs and restarts.

CAS capabilities very restricted

There are several issues affecting the F-35’s CAS capabilities, as mentioned in my annual report. Both the Air Force, with the F-35A, and the Marine Corps, with the F-35B, have flown simulated CAS missions during training or in support of training exercises, with the aircraft in the Block 2B configuration. These training missions have shown that the Block 2B aircraft will need to make substantial use of voice communications to receive target information and clearance to conduct an attack. This is because of the combined effects of digital communications deficiencies, lack of infrared pointer capability, limited ability to detect infrared pointer indications by a controller (which may be improved in the Generation III Helmet Mounted Display System), and inability to confirm coordinates loaded to GPS-aided weapons. Many pilots consider the Electro-Optical Targeting System (EOTS) on the F-35 to be inferior to those currently on legacy systems, in terms of providing the pilot with an ability to discern target features and identify targets at tactical ranges, along with maintaining target identification and laser designation throughout the attack. Environmental effects, such as high humidity, often forced pilots to fly closer to the target than desired in order to discern target features and then engage for weapon employment, much closer than needed with legacy systems, potentially exposing them to threats around the target area or requiring delays to regain adequate spacing to set up an attack. When F-35 aircraft are employed at night in combat, pilots with the currently-fielded Generation II helmet will have no night vision capability from the helmet, due to the restriction on using the current limited night vision camera (due to poor performance, unless a waiver is granted for combat), which is planned to be subsequently upgraded after aircraft are retrofitted with Block 3i and pilots are equipped with the Generation III helmet, which is still in development and testing. In general, using Block 2B F-35 aircraft, pilots would operate much like early fourth generation aircraft using cockpit panel displays, with the Distributed Aperture 15
System providing limited situational awareness of the horizon, and heads-up display symbology produced on the helmet.
Fuel and weapons limitations also affect F-35 CAS performance. For example, an F-35B, assuming a 250-nautical mile ingress to a CAS area contact point, would have only approximately 20 – 30 minutes to coordinate with the controller, assess the tactical situation and execute an attack using its two air-to-surface weapons before needing to depart for fuel. By comparison, an Air Force A-10 would have approximately one and one half hours of time in the CAS area under the same conditions, but would be able to autonomously acquire and identify targets, while using datalink to receive and/or pass target and situational awareness information. Also, an A-10 would be able to employ at least four air-to-surface weapons, including a mixed load of ordnance and its internal gun, which provides flexibility in the CAS role. Although F-35 loiter time can be extended by air refueling, operational planners would have to provide sufficient tankers to make this happen.

High fuel burn rate

The F-35 fuel burn rate is very high compared to legacy strike fighters, at least 60 percent higher than the F-16C, and 180 percent higher than the A-10. This creates a burden on the air refueling resources if used to increase F-35 time on station. Of course, the F-35 is designed to do more missions than CAS, which is the primary mission for which the A-10 was designed. Also, the F-35 is designed to do these missions in a high-threat area. Furthermore, F-35 development is still not complete. If the capabilities stated in the ORD are realized, Block 3F aircraft will have the ability to carry additional weapons externally, for an increased payload, as well as a gun. For example, a Block 3F F-35A aircraft could carry six Guided Bomb Unit (GBU)-12 laser-guided bombs (vice two in Block 2B) along with four air-to-air missiles (two Air Intercept Missile (AIM)-120C and two AIM-9X). The gun capabilities of the F-35 and A-10 are significantly different. The F-35 has a lightweight, 25-millimeter cannon, 16
internally mounted on the F-35A with 182 rounds, and in an external pod with 220 rounds for the F-35B and F-35C, while the A-10 has a 30-millimeter cannon with 1,150 rounds. Even though the A-10 gun has a higher rate of fire, the A-10 gun can fire for over 17 seconds versus approximately 4 seconds for the F-35, providing the capability for many more gun attacks. Also, while both guns have a similar muzzle velocity, the rounds fired by the A-10 are twice as heavy, providing twice the impact energy on the target. The F-35’s fusion of information from onboard sensors and data from off-board sources (i.e., F-35 aircraft in formation via the Multi-function Advanced Data Link (MADL) and other aircraft via Link 16), along with all-weather ground-moving target and synthetic aperture radar capability, are planned to be more capable in Block 3F and should provide better battlespace awareness than that being fielded with Block 2B and better capability in these aspects than an A-10. The extent that these capabilities improve combat capability over legacy systems will be evaluated during IOT&E.
Mission planning time and the debriefing times for the F-35 with the current version of ALIS – which must account for the long download process for cockpit video – are much longer than those of legacy platforms and will affect operations when the F-35 unit is a member of composite air and surface forces, since planning timelines will have to be adjusted.

Software Block 3 – more instability, more reboots

As I explained above, Block 3i was intended to be a simple re-hosting of Block 2B mission systems software on new hardware and processors. However, Block 3i content also includes attempted fixes for five significant functional deficiencies related to mission systems identified by the Air Force as necessary for its IOC declaration. Four additional discoveries in Block 3i have since been identified as deficiencies in need of fixes. Unfortunately, as explained earlier in my statement, Block 3i software is still not stable; in fact, it is much less stable than Block 2B. The final version of Block 2B, version 2BS5.2, had 32.5 hours between stability events during flight testing, versus only 4.3 hours for Block 3iR6. Because Block 3i is the basis for the final new and challenging Block 3F capabilities, the program has rightly determined to focus on Block 3i problems in lieu of further Block 3F development. The program is developing another version of Block 3i software – version 3iR6.21 – which it plans to release to flight test in late March 2016. Unfortunately, further development of the software had been on hold, due to the expiration of the Authority to Operate of the software testing labs at the contractor lab facilities, but has now recently re-started. The Block 3i software instabilities, unresolved deficiencies, lab delays, and the potential for additional discoveries are adversely affecting Block 3i tactics development and the IOC Readiness Assessment, currently underway at Nellis AFB, and are likely to affect Air Force IOC. Nevertheless, the program continues to deliver Block 3i aircraft configured with the available software to fielded units and will continue to do so this year and next year.
Success of Block 3F mission systems depends on the program resolving the problems with Block 3i. 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. The program recently announced a commitment to shift to capability-based software releases, rather than schedule-driven and overlapping releases. While this may cause further short-term delays to the program, I agree with the program’s decision to shift to a serial process of testing and fixing software in the lab before releasing the next software version. If a workable version of 3FR5 is released later this spring or early this summer, mission systems testing and weapons releases can potentially resume in earnest. If this software has better stability and functionality, the test point completion rate may increase, which will be essential given the significant amount of testing that remains.

Heavy load of 931 open and unresolved deficiencies

The program continues to carry a heavy load of technical debt in open and unresolved deficiencies. As of the end of January 2016, the program had 931 open, documented deficiencies, 158 of which were Category 1, defined as deficiencies which may cause death, severe injury, or severe illness; may cause loss of or major damage to a weapon system; critically restricts the combat readiness capabilities of the using organization; or result in a production line stoppage. Of the 158 Category 1 deficiencies, 135 were associated with the air vehicle and the remaining 23 were associated with the ALIS or support equipment. Furthermore, 100 of the 158 open Category 1 deficiencies were categorized as “high severity” by the program or Services. Specific to mission systems, the program was carrying 17 open Category 1 deficiencies for Block 2B capabilities that were characterized as having “high” impact and 35 open Category 1 deficiencies for Block 3F with “high” impact. The Program Office, in cooperation with representatives from the Services, developmental test and operational test organizations, recently led a detailed review of the open deficiencies. This effort, which I applaud, assessed the effect of each deficiency with respect to both combat capability and IOT&E. The resulting list of critical deficiencies should be the top priority fixes for the program prior to finalizing Block 3F and conducting IOT&E.

Mission Data

The problems in the USRL described earlier will not only adversely affect Block 3F combat capability; they are crippling the ability to produce effective mission data loads for today’s fielded aircraft. The current tools and software in the lab are very difficult to work with, resulting in a lengthy, inefficient process to produce and test the mission data. Along with the decision to delay moving the lab equipment from the contractor facilities in Fort Worth, Texas, these inefficiencies created sufficient schedule pressure that the program and the Marine Corps directed the lab to truncate the planned testing of the Block 2B mission data so that an 19
immature version could be fielded in mid-2015 to “support” Marine Corps IOC. The lab provided a Block 2B mission data load, but the risks of operating with these mission data are not understood, and will not be characterized until the full set of planned testing, including operational test flights with the mission data, are conducted later this year. Because the hardware in aircraft equipped with Block 3i cannot operate with the Block 2B mission data, Block 3i mission data must be developed and tested independently of, but concurrently with, the mission data for Block 2B. This creates an additional significant strain on the lab, which is already burdened with inefficient reprogramming tools. Block 3i mission data will likely incur the same fate as Block 2B mission data, as inevitable schedule pressure to field immature mission data will drive product delivery despite incomplete optimization and testing. In any case, the risks in combat associated with operating with these early mission data versions will remain unknown until the planned lab and flight testing are complete.

Escape System – immature, modifications required

The F-35’s pilot escape system is immature; it requires modifications and additional testing if the Services are to be reasonably confident the system is safe for their intended pilot populations. The failures during sled tests last summer simulating controlled, low-speed ejections caused the program and Services to restrict pilots below 136 pounds bodyweight from flying the aircraft. Also, the risk to pilots weighing up to 165 pounds, while lower than the risk to lightweight pilots, is still considered “serious” by the program. Last year the program assessed the risk for this 136 to 165 pound weight class, which accounts for approximately 27 percent of the pilot population. The program assessed the probability of death during an ejection in these conditions to be 23 percent and the probability of some level of injury resulting from neck extension to be 100 percent. However, the program and the Services decided to accept that risk and not restrict pilots in this weight category from flying. Subsequently, the program 20
conducted “proof of concept” tests last fall for modifications to the escape system including a “lightweight pilot” switch on the seat and a fabric head support panel between the parachute risers behind the pilot’s head, intended to restrict the severe backward neck extension. The tests apparently showed that the lightweight pilot switch and head support panel prevented a neck load exceedance after parachute deployment and opening shock. However, these changes do not prevent the high loads on the pilot’s neck earlier in the ejection sequence due to the rocket firing and wind blast. Full testing of these fixes using the new lightweight Generation III helmet and full range of mannequin weights across different airspeeds is expected to extend through this summer with flight clearance this fall and modification kits in 2017. Additional testing and analyses are also needed to determine the risk of pilots being harmed by pieces of the transparency from the canopy removal system during ejections (the canopy must be explosively shattered during ejection) in other than stable conditions (such as after battle damage or if out-of-control), referred to as “off nominal” conditions.

Structural testing – major findings are continuing

Major findings are continuing in the durability test articles, particularly in the titanium bulkhead in the F-35C test article. Significant limitations to the life of the fielded F-35C aircraft can only be addressed with intrusive structural modifications prior to the expected full service life, and show again the high cost of concurrent production and development. In the past year, discoveries of unpredicted cracks continued to occur, and in some cases required pauses in testing to determine root causes and fixes. This occurred in all three variants. Currently, only the F-35A structural test article can be tested; it is about to begin the third lifetime test phase, or the third series of 8,000 equivalent flight hours of testing. The F-35B test article is still down for repairs needed to complete the second lifetime. The F-35C test article restarted testing in mid-February but stopped three days later when strain gauges indicated cracking in a titanium bulkhead; it has not yet restarted.
ALIS – not ready, difficulties in remote operations

The program has developed a new version of the ALIS hardware, termed Standard Operating Unit version 2 (SOU v2), which possesses all of the functional capabilities included in the original version – SOU v1 – but in a modularized, more deployable form. As I described earlier in my statement, in recent months, both the F-35A and F-35B have conducted deployment demonstrations in an effort to learn how to forward deploy with, and conduct flying operations using, the SOU v2. The Marine Corps and Air Force needed several days to successfully establish a new network in an austere expeditionary environment or to integrate ALIS into an existing network at a non-F-35 military installation before ALIS was able to support flying operations. Although the hardware for the SOU v2 was much more manageable to move and set up, the processes for connecting to the main Autonomic Logistics Operating Unit (ALOU) at Lockheed Martin facilities in Fort Worth took time, as did ensuring the data from home station units was transferred correctly to the deployed unit.
These two Service-led deployment demonstrations showed that ALIS operations will require significant additional time to initiate beyond setting up hardware modules, since the details of a network configuration and data file structure vary among base operating locations. ALIS requires a secure facility to house hardware, including SOU modules, mission planning workstations, and receptacles for transferring data to and from aircraft storage devices, which must be connected to power and external communications and integrated into a network with data exchanges occurring at multiple levels of security. It is difficult to establish and configure a network in the precise manner that ALIS requires, so network personnel and ALIS administrators have needed several days to troubleshoot and implement workarounds to prepare ALIS for operations. Although Lockheed Martin has provided several techniques for transferring aircraft data from a main operating location SOU to a deployed SOU, data transfers have proven time consuming and have required high levels of support from Lockheed Martin. Also, relatively minor deviations in file structures relative to ALIS’ specifications can cause the process to fail.
The program plans to release another increment of ALIS software this year – version 2.0.2, with added capabilities to support Air Force IOC declaration. However, it is struggling to meet the schedule currently required to deliver the planned content. Recent Program Office schedule assessments show delays from six weeks to five months, neither of which align with the planned objective date for Air Force IOC of August 2016. Cybersecurity testing of ALIS 2.0.2 is planned for this fall, but may need to slip if the program cannot deliver the planned increment of additional capability on time, adding associated risk to fielding systems and declaring IOC because adequate cybersecurity testing will not have been completed.
Delays in completing development and fielding of ALIS 2.0.2 will compound the delay already realized for ALIS 3.0, the last planned increment of ALIS, which is needed for IOT&E but is currently not scheduled to be released until April 2018. Although the program is considering deferring content and capabilities to make up schedule, the full set of capabilities for ALIS 3.0 will be needed to comply with the program’s requirements and therefore are required for IOT&E.

Aircraft Reliability, Maintainability, and Availability

Although measurements of aircraft reliability, maintainability, and availability have shown some improvement over the last two years, sustainment relies heavily on contractor support, intense supply support to arrange the flow of spare parts, and workarounds by maintenance and operational personnel that will not be acceptable in combat. Measures of reliability and maintainability that have ORD requirement 23
thresholds have improved since last year, but six of nine measures are still below program target values for the current stage of development; two are within 5 percent of their interim goal, and one – F-35B mean flight hours between maintenance events (unscheduled) – is above its target value. Aircraft availability improved slightly in CY15, reaching a fleet-wide average of 51 percent by the end of the year, but the trend was flat in the last few months and was well short of the program’s goal of 60 percent availability that it had established for the end of CY14. It is also important to understand that the program’s metric goals are modest, particularly in aircraft availability, and do not represent the demands on the weapons system that will occur in combat. Making spare parts available more quickly than in the past to replace failed parts has been a significant factor in the improvement from 30 to 40 percent availability experienced two years ago. However, F-35 aircraft spent 21 percent more time than intended down for maintenance in the last year, and waited for parts from supply 51 percent longer than the program targeted. At any given time, 10 to 20 percent of the aircraft were in a depot facility or depot status for major re-work or planned upgrades, and of the fleet that remained in the field, on average, only half were able to fly all missions of the limited capabilities provided by Block 2B and Block 3i configuration.
The program showed improvement in 11 of 12 reliability metrics by May 2015; however, as I depicted in my annual report, 8 of the metrics are still below the program interim goals for this point in development, and it is not clear that the program can achieve the necessary growth to reach the reliability requirements for the mature system, at 200,000 total fleet flight hours. Many components have demonstrated reliability much lower than predicted by the contractor, such as fiber channel switches, main and nose-wheel landing gear tires, the display management computer for the helmet, and signal processors. These low-reliability components drive down the overall system reliability and lead to long wait times for re-supply, which negatively affects aircraft availability.
Maintainability metrics indicate flight line maintenance personnel are working extremely hard to keep up with the demands of unscheduled maintenance (e.g. trouble-shooting and fixing failures) and scheduled maintenance (e.g. inspections). Small improvements in maintainability metrics occurred in the past year, but the measures for all variants are far from the operational requirements. There are a few individual causes for long down times that may be addressed by the program, such as long cure times for low observable repairs, but many must be accepted as facts of life for the time being. Maintenance manuals and technical information must continue to be produced, verified, and validated for use by the military maintenance personnel so that they can learn how to generate combat missions in the most efficient manner. The current process requiring “action requests” to fill gaps in technical information, while improved, will not be acceptable for combat. F-35 maintainers must also dedicate a significant amount of time to scheduled maintenance, in addition to repairs. This accounts for over half of all maintenance time in the last year (from June 2014 through July 2015), a result of fielding an aircraft with an immature structural design that must be inspected for evidence of wear and cracking, such as that which has been found in the structural static test articles.
I also want to point out that the fielded units, and the overall program, have a new challenge with managing multiple software and hardware configurations as aircraft emerge from depot and local modification processes. Modified aircraft include new parts and this should improve reliability metrics. However, managing multiple configurations requires continual, intense focus to ensure correct procedures and parts are used based on aircraft configuration and data elements tracked within ALIS. 25
Deployment sustainment results. As I outlined earlier in my statement, Service-led deployments over the past year have revealed challenges to adequate suitability performance, and provided useful lessons for future operations. More detail is provided below.
During the Cross Ramp Deployment Demonstration flying period at Edwards AFB during May 4 – 8, 2015, the operational test squadron flew 20 of 22 planned missions. The squadron originally intended to deploy four F-35A aircraft and planned most fly-days with two aircraft flying two sorties apiece, but could only make three aircraft available to participate in the exercise. The ALIS data transfer problems forced the detachment to operate in an ALIS-offline mode until the morning of May 7, which restricted aircraft maintenance to minimal, simple activities. The detachment was able to achieve a relatively high completion rate of planned sorties in spite of this largely because no mission systems were required for the flights, so failures in these components were left un-repaired. By the end of the deployment, one of three aircraft had to be towed back to the test squadron hangar because it was down for a flight system discrepancy that the detachment could not fix in time. The detachment also exposed problems with retaining spare part requisitions against aircraft when they are transferred between SOUs, and issues with keeping maintenance records intact when returning from ALIS-offline operations.

USS Wasp deployment demonstration

The shipboard flying period of the USS WASP deployment demonstration from May 18 – 28, 2015, excluding the return flights from the ship to home base on May 29, was not intended to maximize aircraft utilization rates, but showed difficulties in achieving adequate availability to support planned flight schedules. The six deployed F-35B aircraft were mission capable for flight operations approximately 55 percent of the time, which led to the detachment flying 61 of 78 planned missions. The Marine Corps reports a higher number of sorties than missions, since each vertical landing constituted a sortie, while each post-flight engine shut down constituted a mission. Several missions were canceled for weather, or other operational reasons, but 13 missions were canceled, apparently due to a lack of available aircraft. In order to consistently generate tactically relevant four-aircraft mission packages day after day, out of the normal complement of six F-35B aircraft onboard an L-class amphibious ship, the F-35B would likely have to achieve availability rates closer to 80 percent; although during the deployment demonstration, the detachment did generate a four-aircraft mission on one day. Fuel system reliability was particularly poor. This is more burdensome in the shipboard environment than at land bases, as fuel system maintenance in the hangar bay can restrict the ability to perform maintenance on other aircraft in the bay. Due to a fuel system problem that would have required an engine to be pulled, one aircraft was transferred on a one-time flight back to shore and swapped with an alternate aircraft, an option that would not exist in forward-deployed combat conditions. Aircraft availability and utilization varied widely among the seven different aircraft used in total on the deployment, with the top performing aircraft flying 20 missions, and the least performing aircraft flying only 2 missions, not including a one-time ferry flight to shore to be swapped. The ALIS data transfers also relied on combat-unacceptable workarounds, including using commercial Wi-Fi access to download aircraft files. Several factors limited the ability to draw more conclusions about shipboard integration of the F-35B from this deployment demonstration. These included the lack of the rest of the Air Combat Element (ACE) aircraft onboard ship except for the required Search and Rescue (SAR) helicopters; the use of developmental Support Equipment (SE), vice the production-representative SE the Marine operational squadron is now equipped with; and no employment of ordnance.

USMC austere site test

The Marine Corps conducted an assessment of F-35B austere site deployed operations at Twentynine Palms, California, from December 8 – 16, 2015, with eight F-35B aircraft assigned. The Marines intended to fly four aircraft a day from an expeditionary landing field made of aluminum matting and with minimal permanent infrastructure, representing the type of temporary airfield that can be quickly built near the forward line of troops. The demonstration included the use of inert ordnance and production representative support equipment. Aircraft availability for this detachment was again in the 55 to 60 percent range, which led to a significant number of missed flights on the planned flight schedule. The detachment flew 41 out of 79 planned missions; however, 22 of the 38 missions not flown were due to high crosswinds which made landing and taking off from the aluminum matting too risky. Overall, 16 missions were lost due to either lack of aircraft availability, difficulties in transferring and accepting aircraft data into the deployed ALIS, or ground aborts. Propulsion system maintenance was particularly burdensome. Two F-35B aircraft received foreign object damage to their engine fan stages, a result from operating in rugged conditions with jet wash likely blowing small rocks into aircraft intakes. This prevented those aircraft from further participation in flying activities until repairs were completed just prior to the ferry flights home. A contractor technician was called in from the East Coast and was able to repair the engine damage on site, as opposed to having to perform a full engine swap. A further engine system discrepancy required an aircraft swap around mid-way through the detachment. Routine flight operations, such as aircraft start-up and basic troubleshooting, also relied heavily on contractor maintenance.

US Air Force simulated combat deployment

The Air Force sent a detachment of six F-35A operational test aircraft from Edwards AFB to Mountain Home AFB from February 8 to March 2, 2016, to simulate a combat deployment of this variant in preparation for Air Force IOC later this year. This demonstration employed both inert and live ordnance in the CAS and Aerial Interdiction roles, in conjunction with legacy platforms. Results from this demonstration are still too preliminary to report on in full, although some early observations were made. The detachment discovered a major discrepancy in the technical data for loading free fall ordnance after a released bomb hit the weapons bay door and then impacted and gouged the horizontal stabilizer. The aircraft returned to base safely and was eventually repaired on station, and the detachment coordinated with Lockheed Martin to correct the appropriate ordnance loading instructions. The deployment also successfully transferred aircraft data files within the autonomic logistics infrastructure (i.e., using ALIS, the Central Point of Entry, and the ALOU); however, there were some difficulties in establishing ALIS on the host Air Force network on Mountain Home AFB. Finally, the relatively frequent requirement to shut-down and restart an aircraft on start-up before flying due to software instabilities in vehicle and mission systems hampered the detachment’s ability to conduct alert launches.

Test range capability improvements required for IOT&E

Key test range capability improvements are required for IOT&E, on which we have been working with the Office of the Secretary of Defense and Service staff for several years. In particular, these include the Air-to-Air Range Infrastructure-2 (AARI2) system, the instrumentation that allows the many engagements during complex test trials to be accurately assessed and shaped in real time; and the integration of the Electronic Warfare Infrastructure Improvement Program (EWIIP) emitters, that will simulate current, advanced threats on the range. For an adequate IOT&E, the integration of AARI2 with the F-35 should allow the F-35 Embedded Training modes to realistically emulate and display weapons employment data and threat indications to the pilot, and include the shot validation method that is being developed for this purpose. The planned schedule for AARI2 integration, however, does not align with the current plans for IOT&E and does not include these features. Therefore, the product will either be inadequate or late to need. The new EWIIP emitters, that will simulate current, advanced threats on the range start arriving in fall of this year. However, Air Force integration plans fall short of what is needed for an adequate IOT&E, both in how the emitters are integrated with the range infrastructure and the degree of incorporation with the AARI2 battle-shaping instrumentation. We continue to work with the Air Force in an attempt to correct these problems, and ensure we get the most of the investment made in these emitters. There is no alternative to correcting these problems if IOT&E is to provide a representative threat environment – an environment that has been in existence, and robustly so, in the real world for several years. Not incorporating these assets will result in a test of the F-35 only against decades-old threats, which do not represent the intended operational environment for this fifth generation system. I assess the technical challenges to the integration requirements I mention here as relatively minor; this test concept is not new. Unfortunately, the issues seem to stem primarily from cultural resistance to change and to the adoption of modern technology.
Of all the issues mentioned earlier that threaten IOT&E spin-up and start, the most significant are the modifications needed for operational test aircraft, Block 3F completion (including flight test, weapons deliveries, and envelope release), and completion of ALIS 3.0. The program has an executable plan to pull completion of the modifications back from 2019 to 2018; however, the Services must commit to executing that plan, which has not yet occurred. The Block 3F schedule, even with significant improvements in software stability, deficiency resolution, and flight test rates, still appears to extend into 2018 before the capabilities will be ready and certified for IOT&E. Inadequately tested mission data and failure to provide the Verification Simulation will likely not delay the start of IOT&E, but will affect the results and adequacy of the test, respectively, and the former will likely limit significantly the ability of the F-35 to be used in combat against existing, modern, stressing threats. Therefore, a mid-2018 start for IOT&E appears to be the earliest viable date based on when the mods, Block 3F and ALIS 3.0 will be ready. Based on the issues above that will not likely be resolved or ready until 2018 or later, I am concerned that the program may not have adequate resources to complete the required System Development and Demonstration activities prior to IOT&E.

Block Buy

In my annual report, I raised several questions regarding the program’s proposed “block buy” to combine three production lots comprising as many as 270 U.S. aircraft purchases to gain near-term savings. My understanding is that the program and the Services have decided to delay the consideration of the block buy for at least another year, possibly starting in FY18. Nonetheless, in that case, all of the questions I pose in my annual report remain valid, since IOT&E will not start until FY18, at the earliest, and will not be complete until later that year

Follow-on Modernization

The program’s proposed “F-35 Modernization Planning Schedule” is overly optimistic and does not properly align with their current software development schedule, which is also unrealistic. There is a four-year gap between the final planned Block 3F software release in 2016 and fielding of the first proposed modernization increment, labeled Block 4.1, in late 2020. The proposed schedule also does not depict any incremental software releases to correct open Block 3F deficiencies and new discoveries, likely to be found during IOT&E, prior to adding the proposed new Block 4.1 modernization capabilities. Such a schedule greatly increases risk to development and testing of Block 4. Despite the significant ongoing challenges with F-35 development, including the certainty of additional discovery, the proposed modernization schedule is very aggressive; it finalizes the content of Blocks 4.1 and 4.2 in early 2016. Then, before or during IOT&E, the program would award contracts to start simultaneous development of Blocks 4.1 and 4.2 in 2018, well prior to completion of IOT&E and having a full understanding of the inevitable problems it will reveal. Also, the proposed Block 4 modernization plan and schedule does not clearly depict acquisition milestones, despite the large amount of capabilities and funding required. Finally, the follow-on modernization plan and schedule still do not allocate schedule and resources for operational test and evaluation of each increment consistent with the approach being used for F-22 follow-on development.

Source: Source: U.S. Department of Defense; 23-Mar-2016

Comments RSS

Reageer ook

Je moet ingelogd zijn om een reactie te kunnen plaatsen.