November 2, 2018 | International, Aerospace
By: Burak Ege Bekdil
ANKARA, Turkey — Turkey's aerospace authorities have chosen General Electric's F110 family of engines to power the prototype and an initial batch of what will become Turkey's first indigenous fighter jet, the TF-X.
A senior procurement official confirmed the choice, saying that the twin-engine TF-X will be powered by the F110-GE-129 or the F110-GE-132 engine.
“This is a stopgap solution until we have built our indigenous engine for the TF-X,” the official said.
Under the deal, the first prototype of the TF-X and an unknown number of initial batches would be powered by the F110 engine.
Turkey then plans to switch to an engine to be developed by TRMotor, a national engine consortium.
But some aerospace sources say the F110 may not be the ideal engine for a fifth=generation fighter. “If the Turks go for the GE option, they will have to compromise on the stealth capabilities of the TF-X,” a Paris-based defense specialist said.
Earlier this year, Turkey and Rolls-Royce came close to a strategic cooperation deal for the development and co-production of an engine for the TF-X. The British company and the Turkish government signed a letter of intent to finalize negotiations on the engine program by July 31, but the plan did not come to fruition.
Turkish officials say the idea behind the GE deal is to rely on foreign technology to eventually in the long term build an indigenous engine to power the TF-X.
Turkey wants to build the TF-X with know-how from BAE Systems. In January 2017, Britain and Turkey signed a deal worth more than £100 million (U.S. $128 million) to develop the Turkish fighter jet.
Turkey hopes to have the first test flights of the aircraft in 2023.
November 4, 2024 | International, Land, C4ISR
This week, we're diving into the chaos as hackers ramp up attacks, including North Korean ransomware collaboration and evasive password spraying tacti
December 10, 2018 | International, Aerospace
By: Stephen Losey Nearly two months after Hurricane Michael devastated Tyndall Air Force Base in Northern Florida, the Air Force on Friday said it wants to rebuild the installation — so it can station three squadrons of F-35 fighters there. But the change in plans, if approved, would mean operational F-22 Raptors from the 95th Fighter Squadron would not return to Tyndall. The Air Force is asking Congress for supplemental funding to repair Tyndall's damage, the service said in a release. Air Force spokeswoman Ann Stefanek said the amount of money is still being decided. A preliminary evaluation showed Tyndall could accommodate up to three F-35 squadrons, the Air Force said. If Congress grants the supplemental repair funds and the F-35 basing is approved, F-35s could be based there beginning in 2023. The move would mean operational F-22s that were formerly at Tyndall would be permanently moved to squadrons at other bases that are now temporarily housing them: Joint Base Langley-Eustis in Virginia, Joint Base Elmendorf-Richardson in Alaska and Joint Base Pearl Harbor-Hickam in Hawaii. Those F-22 squadrons would grow from 21 to 24 fighters apiece to permanently accommodate the Tyndall aircraft. “We have recommended that the best path forward to increase readiness and use money wisely is to consolidate the operational F-22s formerly at Tyndall in Alaska, Hawaii and Virginia, and make the decision now to put the next three squadrons of F-35s, beyond those for which we have already made decisions, at Tyndall,” Air Force Secretary Heather Wilson said. “We are talking with congressional leaders about this plan and will need their help with the supplemental funding needed to restore the base." This decision will allow the Air Force to tailor the new construction at Tyndall to the best fit for F-35s, the Air Force said. The 325th Fighter Wing, which was comprised of two F-22 squadrons, was located at Tyndall before the Oct. 10 storm. Most Tyndall aircraft evacuated before the storm hit, but 17 Raptors could not be flown and stayed behind, sustaining varying levels of damage that is now being repaired. Nearly a month after the storm, Wilson said that F-22 training with the 43rd Fighter Squadron would be temporarily moved to nearby Eglin Air Force Base. The Air Force said it will conduct a formal process to decide what will be the best location for the 43rd and its training mission. The 95th has 21 F-22s and 36 active-duty airmen, the Air Force said last month, and its associated maintenance units have about 500 airmen. F-35 basing decisions in Alabama, Alaska, Arizona, Florida, Texas, Utah, Vermont and Wisconsin, which have already been announced, will not be changed. https://www.militarytimes.com/news/your-air-force/2018/12/07/air-force-wants-to-house-three-f-35-squadrons-at-rebuilt-tyndall-move-raptors-permanently
August 13, 2020 | International, Aerospace
Lee Hudson August 12, 2020 The Pentagon is in the early stages of replacing the troubled Lockheed Martin F-35's autonomous logistics system with a new, cloud-based network, and hopes to get it up and running by the end of 2022. The Operational Data Integrated Network (ODIN) is intended to reduce workload and increase F-35 mission readiness rates by using a smaller, deployable, commercial and cloud-native architecture. Right now, F-35 users operate the Autonomic Logistics Information System (ALIS) that collects inflight information for maintainers to predict part failures. However, the problem-plagued logistics system has encountered numerous issues that range from directing unnecessary maintenance actions, taking too long to boot up and time-consuming data entry. For example, users told the Government Accountability Office (GAO) that electronic records are frequently corrupt or missing, resulting in ALIS signaling the jet should not fly. This occurs in cases where maintainers know the aircraft is safe for flight. Maintainers at one location told the GAO they experienced as many as 400 issues per week for one six-month period in 2019. The F-35 Joint Program Office (JPO) plans to begin installing hardware this September that can run software from both the legacy and new systems until ODIN is deployed fully. ODIN initial delivery is planned for September 2021. ODIN hardware is designed to have a 75% smaller footprint than the legacy system, and be approximately 94% lighter—50 lb. compared with 891 lb. Another radical difference between the two systems is F-35 prime contractor Lockheed owns ALIS development and the new network is being developed by the JPO. The JPO is using agile software development tools that allow rapid updates and improvements like how Apple updates its iPhones, while Lockheed employs waterfall development that allows for updates every 12-18 months. In January, the JPO hit its first milestone by moving existing F-35 data into a new, integrated environment that will support applications designed by organizations such as Kessel Run, one of the Air Force's software factories. Kessel Run formed a team called Mad Hatter and tasked it to build software applications to render F-35 logistics more user-friendly. A key complaint about ALIS was the lack of realistic operational requirements. In other words, user needs can become outdated. To address this shortcoming, the JPO partner nations agreed in January to update a requirements document for ODIN annually—if needed. Instead of crafting a rigid requirements document that will be outdated in 10 years, the new strategy calls for updating protocols based on reality, according to a program office maintenance systems expert. This strategy complies with the software acquisition policy of Under Secretary of Defense for Acquisition and Sustainment Ellen Lord. It calls for the users, developers and software designers to come together and produce a customer-centric design as development progresses. The requirements document features six capability needs: deployment planning and execution; unit maintenance planning; sortie generation; sustainment readiness; information management, and ODIN support. The document also includes 43 performance measurements that the JPO will use as metrics to track ODIN development. Beyond better programmatic planning, the Pentagon is facing a considerable obstacle as it transitions from ALIS to ODIN. The JPO is having trouble receiving technical data from Lockheed, Lord told the House Committee on Oversight and Reform. “While the department recognizes industry's interest in protecting intellectual property, there is technical data that the department has rights to and needs in order to enable effective organic sustainment,” Lord noted in written testimony submitted to the committee. In response to Lord's comments, Lockheed noted the company does not own all the logistics system's intellectual-property and data rights. “ALIS software is also government-owned, per contract requirements with Lockheed, and our suppliers retaining intellectual property and data rights to portions of software that were developed using industry's investment funds is in accordance with the Defense Federal Acquisition Regulations Supplement,” Lockheed spokesman Brett Ashworth tells Aviation Week. The Pentagon's overarching goal is to drive down F-35 sustainment pricing, which is where most of a program's cost resides. The government is still upgrading ALIS, an effort known as ALIS Next, before ODIN comes online to manage costs. ALIS Next consists of more regular software updates, instead of the program's current 12-18 month cycle. An updated version of ALIS, known as 3.5, is outfitted with 300 stability fixes, says F-35 Program Executive Officer Lt. Gen. Eric Fick. Air Force software developers and Lockheed Martin personnel are simultaneously continuing to issue ALIS software patches. ALIS Next provides an opportunity to reduce the amount of administrative personnel needed to support the logistics system's operations in the field. An important step to lowering the overall F-35 sustainment price is reducing the cost per flying hour. The goal is for the F-35A conventional takeoff and landing jet, the most popular variant, was $25,000 by 2025. “We are confident $25,000 is attainable, but it will require collaboration with the JPO, services, allies and our industry partners to reduce overall cost,” Lockheed F-35 Vice President and General Manager Greg Ulmer submitted in written testimony to the House Committee on Oversight and Reform. Over the past five years, the company has reduced a portion of the F-35's operations and sustainment costs by 38%. Lockheed is responsible for 39% of all F-35 sustainment costs, according to Ulmer. The company estimates it will drive down controlled cost another 50% in the next five years, and it is working with the government to achieve similar savings on the remaining 61% of flight-hour costs that are under the purview of the Defense Department and propulsion suppliers. Although in its infancy, ODIN is set to be the cornerstone for the next major wave of F-35 sustainment improvements over the next two years as ALIS is retired. https://aviationweek.com/defense-space/aircraft-propulsion/pentagon-rethinks-troubled-f-35-logistics-system