• IP addresses are NOT logged in this forum so there's no point asking. Please note that this forum is full of homophobes, racists, lunatics, schizophrenics & absolute nut jobs with a smattering of geniuses, Chinese chauvinists, Moderate Muslims and last but not least a couple of "know-it-alls" constantly sprouting their dubious wisdom. If you believe that content generated by unsavory characters might cause you offense PLEASE LEAVE NOW! Sammyboy Admin and Staff are not responsible for your hurt feelings should you choose to read any of the content here.

    The OTHER forum is HERE so please stop asking.

MAGA latest F-35 can't fly no engines! Production Problems delayed delivery of F-135 engines, cancel order pse RSAF!

Ang4MohTrump

Alfrescian
Loyal
https://www.courant.com/business/hc...0190702-3izx3jdy4vatziy2dgwfy7z5u4-story.html

Feds say Pratt & Whitney late delivering engines for F-35 fighter jet



By Tony Capaccio

| Hartford Courant |

Jul 02, 2019 | 5:10 PM








R5VT7YAKIFHYDH5LN2WOG7LI2Q.jpg


An Israeli F-35 fighter jet performs during an air show at the graduation ceremony of Israeli pilots in the Hatzerim Israeli Air Force base in the Negev desert, near the southern Israeli city of Beer Sheva, on June 27, 2019. (JACK GUEZ/AFP/Getty Images) (JACK GUEZ/Getty)



A federal agency says that Pratt & Whitney is chronically late delivering engines for the Pentagon’s costliest program, the F-35, raising questions about whether the company is ready for a surge to full-rate production scheduled for next year.

Pratt remains under a previously unreported “Corrective Action Request” from the Defense Contract Management Agency that cites “poor delivery performance” on its current batch of engines for the fighter jet, including for the most complicated version used by the Marine Corps and the U.K. for vertical takeoffs and landings. Pratt & Whitney is a subsidiary of Farmington-based United Technologies Corp.

Pratt & Whitney president to retire next year as UTC and Raytheon combine in aerospace and defense merger »

The agency’s action is likely to be watched not only by the Pentagon and international buyers of the F-35 but also by shareholders and investors assessing United Technologies’ planned merger with Raytheon Co., which would fortify the combined company’s standing as one of the top U.S. defense contractors.

The F-35 engines would be one of the new company’s top revenue producers. The company, which is the sole supplier of engines for the fighter built by Lockheed Martin Corp., must demonstrate by year-end that it has delivered on promised improvements to solve the problems that led to the agency’s formal request in December, spokesman Mark Woodbury said in a statement outlining the issues.

[Business] City will move forward with Downtown North development after jury backs Hartford’s decision to fire Dunkin’ Donuts Park developer in 2016 »

The $428 billion F-35 program is scheduled for approval next year to enter full-rate production, the most lucrative phase of a weapons program for contractors. The decision is contingent on an assessment during the aircraft’s current round of intensive combat testing that it’s effective and can be maintained.

Of the $428 billion, as much as $66 billion is to be spent on at least 2,470 engines -- designated the F135 -- for U.S. jets, including $53.4 billion in procurement, according to the Defense Department’s latest Selected Acquisition Report on the F-35.

Pentagon budget documents indicate the engine program is valued at about $2 billion annually for Pratt, according to Bloomberg Intelligence analyst Douglas Rothacker.

John Thomas, a spokesman for Pratt, said in an emailed statement that “we take seriously our responsibility to meet F135 production commitments. The corrective action plan submitted earlier this year lays out how we are doing that. Over the past year, we have invested more than $200 million for additional capacity, and currently have over 100 Pratt & Whitney employees deployed to our supplier facilities in support of production obligations.”

Pratt & Whitney President Bob Leduc underscored the engine’s revenue potential to analysts June 17 at the Paris Air Show.

[Business] City will move forward with Downtown North development after jury backs Hartford’s decision to fire Dunkin’ Donuts Park developer in 2016 »
“So another way to think about the F135 is a year ago we made about eight engines a month,” he said. “Right now we are between 13 and 14 engines a month. But when you think about the F135, it’s 16 engines a month for the next 30 years. There will be over 4,000 of these airplanes when it’s all said and done,” including foreign sales.

The primary issues resulting in late engine deliveries “have been related to supply-chain capacity, material shortages” and production issues, according to the contract management agency.

“Engine test failures due to high vibrations and foreign object debris continues to plague” production, the agency said in an internal quarterly assessment for January through March.

Deliveries of the Marine Corps model engines “have been consistently late,” it said.

As of early June, Pratt & Whitney was contractually required to deliver 108 engines in the latest production contract, the program’s 11th. Of the 90 delivered, 88 were “late by an average of 40 days,” Woodbury said in his statement.

The Pentagon is close to finalizing the award of the 12th and largest F-35 contract to date with Lockheed and Pratt.

The current delays add to Pratt & Whitney’s spotty track record. Even as deliveries increased to 81 in 2018 from 48 in 2012, 86 percent of those were delivered late, up from 48 percent in late 2017, according to an April report from the Government Accountability Office.

Asked whether the contract management agency has confidence Pratt will be ready for a full-production decision, Woodbury said the agency is monitoring milestones in Pratt’s corrective action plan and needs to see progress before making that judgment.

The agency’s assessment said that in light of Pratt & Whitney’s track record it believes the company “will encounter issues keeping up with demand for any future low-rate and full- rate production contract” that increases quantities.






https://www.bloomberg.com/news/arti...gies-pratt-slow-on-f-35-engines-pentagon-says



United Technologies’ F-35 Engines Chronically Late, Pentagon Says
By
Anthony Capaccio

July 2, 2019, 4:00 PM GMT+8

  • Contract agency questions if contractor is ready for a surge
  • A ‘poor delivery performance’ finding remains in effect

LISTEN TO ARTICLE


4:22

SHARE THIS ARTICLE



Share




Tweet




Post




Email

In this article
UTX
UNITED TECH CORP
133.00
USD
+1.04+0.79%

LMT
LOCKHEED MARTIN
370.38
USD
+2.81+0.76%

RTN
RAYTHEON CO
173.45
USD
+0.65+0.38%


United Technologies Corp.’s Pratt & Whitney unit is chronically late delivering engines for the Pentagon’s costliest program, the F-35, raising questions about whether the company is ready for a surge to full-rate production scheduled for next year.


Pratt remains under a previously unreported “Corrective Action Request” from the Defense Contract Management Agency that cites “poor delivery performance” on its current batch of engines for the fighter jet, including for the most complicated version used by the Marine Corps and the U.K. for vertical takeoffs and landings.



The agency’s action is likely to be watched not only by the Pentagon and international buyers of the F-35 but also by shareholders and investors assessing United Technologies’ planned merger with Raytheon Co., which would fortify the combined company’s standing as one of the top U.S. defense contractors. The F-35 engines would be one of the new company’s top revenue producers.



The company, which is the sole supplier of engines for the fighter built by Lockheed Martin Corp., must demonstrate by year-end that it has delivered on promised improvements to solve the problems that led to the agency’s formal request in December, spokesman Mark Woodbury said in a statement outlining the issues.


800x-1.jpg

An F-35
Photographer: Eric Baradat/AFP via Getty Images
Full Production
The $428 billion F-35 program is scheduled for approval next year to enter full-rate production, the most lucrative phase of a weapons program for contractors. The decision is contingent on an assessment during the aircraft’s current round of intensive combat testing that it’s effective and can be maintained.

Of the $428 billion, as much as $66 billion is to be spent on at least 2,470 engines -- designated the F135 -- for U.S. jets, including $53.4 billion in procurement, according to the Defense Department’s latest Selected Acquisition Report on the F-35.
Pentagon budget documents indicate the engine program is valued at about $2 billion annually for Pratt, according to Bloomberg Intelligence analyst Douglas Rothacker.

John Thomas, a spokesman for Pratt, said in an emailed statement that “we take seriously our responsibility to meet F135 production commitments. The corrective action plan submitted earlier this year lays out how we are doing that. Over the past year, we have invested more than $200 million for additional capacity, and currently have over 100 Pratt & Whitney employees deployed to our supplier facilities in support of production obligations.”
Revenue Potential
Pratt & Whitney President Bob Leduc underscored the engine’s revenue potential to analysts June 17 at the Paris Air Show.

“So another way to think about the F135 is a year ago we made about eight engines a month,” he said. “Right now we are between 13 and 14 engines a month. But when you think about the F135, it’s 16 engines a month for the next 30 years. There will be over 4,000 of these airplanes when it’s all said and done,” including foreign sales.
The primary issues resulting in late engine deliveries “have been related to supply-chain capacity, material shortages” and production issues, according to the contract management agency.
“Engine test failures due to high vibrations and foreign object debris continues to plague” production, the agency said in an internal quarterly assessment for January through March. Deliveries of the Marine Corps model engines “have been consistently late,” it said.
As of early June, Pratt & Whitney was contractually required to deliver 108 engines in the latest production contract, the program’s 11th. Of the 90 delivered, 88 were “late by an average of 40 days,” Woodbury said in his statement. The Pentagon is close to finalizing the award of the 12th and largest F-35 contract to date with Lockheed and Pratt.
Spotty Record
The current delays add to Pratt & Whitney’s spotty track record. Even as deliveries increased to 81 in 2018 from 48 in 2012, 86% of those were delivered late, up from 48% in late 2017, according to an April report from the Government Accountability Office.

Asked whether the contract management agency has confidence Pratt will be ready for a full-production decision, Woodbury said the agency is monitoring milestones in Pratt’s corrective action plan and needs to see progress before making that judgment.
The agency’s assessment said that in light of Pratt & Whitney’s track record it believes the company “will encounter issues keeping up with demand for any future low-rate and full-rate production contract” that increases quantities.
— With assistance by Rick Clough


http://www.defense-aerospace.com/ar...the-long-history-of-f_35-engine-problems.html


Home


Releases


Reports


Word for word


Features



AFP News


Order




F-35 Grounded After New F-135 Engine Problems

(Source: JSFNieuws.nl; published February 22, 2013)

By Johan Boeder

There have been several instances of turbine blades breaking off on the Pratt & Whitney F135 engine. Shown here are several broken blades during the first known incident, on Aug. 30, 2007, which ultimately led to the engine’s re-design in 2008. (photo P&W)



KESTEREN, Netherlands --- On Thursday, February 21, 2013, the Pentagon Friday ordered the grounding for all F-35 aircraft, after a routine check at the Edwards Air Force Base revealed a crack in a low pressure turbine blade in the engine of an F-35A.

This is but the latest incident concerning the Pratt & Whitney F135 engine, as during 2007-2009 repeated problems with turbine blades led to significant delays in the test program and a partial redesign of certain parts of the engine.

On February 19, 2013 a routine inspection took place of a Pratt & Whitney F135 engine at Edwards AFB, USA. During the inspection using a borescope, there were indications that there was a crack in a LPT turbine blade. It was confirmed after further investigation. The turbine blade is sent to Pratt & Whitney in Middletown (CT), USA for further investigation.

Statements from JSF Program Office

The F-35 JSF Program Office said in a Feb. 22 statement to the press: “It is too early to know the fleet-wide impact of this finding, however as a precautionary measure, all F-35 flight operations have been suspended until the investigation is complete and the cause of the blade crack is fully understood. The F-35 Joint Program Office is working closely with Pratt & Whitney and Lockheed Martin at all F-35 locations to ensure the integrity of the engine, and to return the fleet safely to flight as soon as possible.”

Lt. Gen. Chris Bogdan, head of the JSF Program Office, suggested in a briefing in Australia that if the crack's cause was as straightforward as a foreign object striking the turbine, or a basic manufacturing defect, “I could foresee the airplane back in the air in the next week or two.”

Bogdan added that “If it's more than that, then we have to look at what the risk is to the fleet,” adding than a verdict on the cracking's cause was expected "by the end of this week", Reuters reported from Melbourne.

Some facts about what happened

It was a F-135 engine with 700 hours, of which 409 flight hours. The aircraft was the F-35A test aircraft AF-2. The half-inch wide crack was found in a turbine blade of the low pressure turbine section. This makes it unlikely that it is caused by so-called FOD (Foreign Object Damage), such as a bird strike, because such an object has to pass the Fan Section (3 stages) Compressor Section (6 stages), combustor and high pressure turbine section before reaching the low pressure turbine section.

Cracks in turbine blades in the low pressure turbine section usually are caused by high thermal or other stressing loads of the turbine blades. The forces in the 40.000 lb (about 29.000 hp) engine are enormous. A grounding after such a discovery usually takes relatively short (e.g. one week), normally a manufacturing error or some incident is the root cause.

Until then, for safety reasons a grounding may be the standard procedure. Reuters reported Feb 24 that “In fact, two jets were airborne at air bases in Maryland and Arizona and had to be recalled, said one of the sources.” At this moment, all 51 F-35s, of all versions, in use at several airfields to support the test and training program, are grounded.

Long history of engine problems since 2006

It cannot be excluded that the root cause of the current problem is more structural than a simple manufacturing error or an isolated incident. Since 2006 there had been a series of engine problems with the F-135 engine.

In May 2006, Aviation Week reporter David A. Fulghum wrote a detailed article “Joint Strike Fighter F135 Engine Burns Hotter Than Desired” and described the risk of a shorter engine life or engine damage caused by higher than expected temperatures on the F-135 engine.

In August 2007 and February 2008 there were serious problems. Turbine blades broke off suddenly by a form of metal fatigue. The cause was sought in a combination of factors.

On 30 August 2007 in test engine FX634, after 122 hours of testing, a turbine blade in the 3rd LPT stage broke off completely. On February 4, 2008 something similar happened to engine FTE06, also in the 3rd LPT stage, after 19 hours.

These problems with the engine contributed significantly to the delays in the JSF test program for the period 2007-2008.

Redesign of the engine in 2008

In early 2008, an engine, the FX640 ground test engine, was equipped with numerous sensors and instruments. On April 21, 2008 a test process was started to find the cause of the problem. Through a detailed test plan the forces and tensions that arise in the engine were mapped in different power ranges.

At that moment it seemed to be primarily an issue of the F-35B STOVL (vertical landing) version. The cracks in the turbine blades were created in exactly the same place, and seemed to occur when switching from forward to vertical drive. Later in 2008, the results became available. The blade cracks seemed to have been caused by certain vibrations that triggered a material failure.

This led to a redesign of a number of elements in the engine. One of the upgrades was a change of the distance between the turbine blades. After the redesign the engine was retested and recertified. At the end of 2008 Pratt & Whitney issued a press statement, saying that they were convinced that the problems were solved.

(UPDATE: A link to a July 22, 2008 briefing by Pratt & Whitney on F135 blade failures was removed on Feb. 28 at the request of the F-35 Joint Program Office. The "information in those slides has the potential to compromise the safety of our pilots," the request stated -- Editor.)

In 2009, problems with redesigned engine

In July 2009, the then head of the JSF Program Office, Marine Corps Maj. Gen. David R. Heinz, was still was not happy with the F-135 problems. He told the press: “The problems include too many individual blades that fail to meet specifications, as well as combined “stack-ups” of blades that fail early. I’m not satisfied with the rates that I’m getting.”

A few days later he was ordered by the Pentagon not to comment publicly on problems with the F-135 engine.

In September 2009, serious engine problems were again revealed during testing of the Pratt & Whitney F-135 engine. At a crucial moment in the debate in the U.S. Congress on the choice of two competing engine types (the Pentagon wanted to axe the alternate engine (the GE / Rolls Royce F-136), a Pratt & Whitney F-135 engine broke down. Again, the cause seemed to lie in broken turbine blades. However, this time the same problem occurred in the new, redesigned engine with redesigned turbine blades.

Engine problems continue until now

After the problems in 2009, officials no longer publicly commented about the engine problems. Also there were no indications that there actually were problems with the engine or that there were any reliability issues.

In April 2011, however, Admiral Venlet, the then Head of JSF Program Office, told reporters that some engine problems were impacting on the delivery schedule.

The grounding last week puts the engine back in the publicity spotlight. However, this time it is not the complex F-35B STOVL version, but the much simpler engine in the F-35A, the Air Force version, that failed, which has led some observers to speculate that the problem could be more deeply ingrained in the engine’s design.

History of previous F-35 groundings

May 2007: The first incident was recorded in May 2007, when the F-35A prototype AA-1 experienced an electrical short that disabled flight controls on the horizontal stabliser. A grounding was ordered and continued until December 2007, due to time needed to redesign several parts of the 270-volt electrical system and F-135 engine problems.

July 2008: On July 23, 2008, both flying F-35 prototypes were grounded after problems were detected with ground cooling fan electrical circuitry, DCMA reported on Aug 18, 2008 that tests were delayed as a result of testing anomalies on the 28 Volt and 270 Volt Battery Charger/Controller Unit, the Electrical Distribution Unit and the Power Distribution Unit. It was due to design problems. Flights were resumed first week of September-2008.

December 2008: On Dec 12, 2008 the F-35 was grounded again as a result of engine and ejection seat anomalies. Seat anomalies were observed in ejection seat sequence during an escape system test on Nov. 20, 2008. It took nearly 3 months to solve the problems and aircraft AA-1 did not return to the skies until Feb. 24, 2009.

May 2009: The F-35 fleet didn’t fly between May 7, 2009 (84th flight of prototype AA-1) and Jun 23, 2009. No comments were available from JPO or L-M.

October 2010: F-35 fleet grounded after the fuel pump shut down above 10,000ft (3,050m). The problem was caused by a software bug.

March 2011: The entire F-35 fleet was grounded some weeks after test aircraft AF-4 experienced a dual generator failure. After both generators shut down in flight, the IPP activated and allowed the F-35’s flight control system to continue functioning. The problem was traced to faulty maintenance handling.

June 2011: Carrier-based F-35C suspended from flying after engineers at NAS Patuxent River discovered a software problem that could have affected the flight control surfaces. Grounding was from 17 June until 23 June, 2011.

August 2011: A precautionary grounding of all 20 F-35s that had reached flying status was ordered Aug. 3, 2011 after a valve in the Integrated Power Package (IPP) of F-35A test aircraft AF-4 failed. On 18 August 2011 the flight ban was lifted to allow monitored operations. A permanent resolution would be installed later.

January 2012: 15 Lockheed Martin F-35s are grounded for about 12 days to repack improperly installed parachutes (reversed 180 degrees from design). The grounded aircraft are equipped with new versions of the Martin Baker US16E ejection seat, designated as -21 and -23.

January 2013: The F-35B STOVL variant was grounded Jan 18, 2013 after detection of a failure of a fueldraulic line in the aircraft's propulsion system. The Pentagon cleared all 25 F-35B aircraft to resume flight tests on February 12, 2013. Problem caused by a manufacturing quality problem (wrongly crimped fuel line).

February 2013: On Feb. 21, 2013, the Pentagon ordered a grounding for all F-35 aircraft, after a routine check at the Edwards Air Force Base revealed a crack in a low pressure turbine blade in an engines of a F-35A.

-ends-
 

Ang4MohTrump

Alfrescian
Loyal
http://www.defense-aerospace.com/ar...updated-overview-of-f_35-engine-problems.html

F-35 Report: Overview of Problems with F-135 Engine

(Source: JSFNieuws.nl; published July 09, 2014)

(By Johan Boeder, editor, JSF Nieuws)



KESTEREN, Netherlands --- Last week’s grounding of the F-35 fleet puts the Pratt & Whitney F-135 engine back in the public spotlights, just one week before the planned international debut of the F-35B at the RIAT 2014 and Farnborough Airshows.

During 2007-2009, repeated problems with turbine blades contributed to significant delays in the F-35 test program, and required a partial redesign of certain parts of the engine. The grounding in February 2013 was caused by a crack, found in a Low Pressure LPT3 turbine blade. Investigations of the latest engine fire seem to focus at the same problem.

The question is whether these recurring F135 problems should be considered as isolated incidents, or as signs of a basic design fault? And do F-35 operators have a structural problem?

Long history of engine problems since 2006

It cannot be excluded that the root cause of the current problem is more structural than a simple manufacturing error or an isolated incident. Since 2006 there has been a series of engine problems with the F-135 engine.

In May 2006, Aviation Week reporter David A. Fulghum wrote a detailed article “Joint Strike Fighter F135 Engine Burns Hotter Than Desired” and described the risk of a shorter engine life or engine damage caused by higher than expected temperatures on the F-135 engine.

In August 2007 and February 2008 there were serious problems. Turbine blades broke off suddenly by a form of metal fatigue. The cause was sought in a combination of factors. On 30 August 2007 in test engine FX634, after 122 hours of testing, a turbine blade in the 3rd LPT stage broke off completely.

On February 4, 2008 something similar happened to engine FTE06, also in the 3rd LPT stage, after 19 hours.

At the time, the JSF Program Office told the press that the engine failures in both cases were due to “high cycle fatigue testing”. These problems with the engine contributed significantly to the delays in the JSF test program for the period 2007-2008.

Redesign of the engine in 2008

In early 2008 an engine, the FX640 ground test engine, was equipped with numerous sensors and instruments. On April 21, 2008 a test process was started to find the cause of the problem. Through a detailed test plan the forces and tensions that arise in the engine were mapped in different power ranges.

At that moment it seemed to be primarily an issue of the F-35B STOVL (vertical landing) version. The cracks in the turbine blades were created in exactly the same place, and seemed to occur when switching from forward to vertical drive. Later in 2008, the results became available. The blade cracks seemed to have been caused by certain vibrations that triggered a material failure.

This led to a redesign of a number of elements in the engine. One of the upgrades was a change of the distance between the turbine blades. After the redesign, the engine was retested and recertified. At the end of 2008 Pratt & Whitney issued a press statement, saying that they were convinced that the problems were solved.

In 2009, problems with redesigned engine

During testing in May 2009, Pratt & Whitney found that at high speed with full after burner and at low altitude, certain pressure pulsations occurred. This “screech” problem, that prevented the engine from sustaining full thrust, was addressed by modifications in 2010 and included design modifications in the fuel system, upgraded software and reductions of aerodynamic leakages.

In July 2009, the then head of the JSF Program Office, Marine Corps Maj. Gen. David R. Heinz, was still was not happy with the F-135 problems. He told the press: “The problems include too many individual blades that fail to meet specifications, as well as combined “stack-ups” of blades that fail early. I’m not satisfied with the rates that I’m getting.”

A few days later he was ordered by the Pentagon not to comment publicly on problems with the F-135 engine.

On September 11, 2009, again serious engine problems were revealed during testing of the Pratt & Whitney F-135 engine. At a crucial moment in the debate in the U.S. Congress on the choice of two competing engine types (the Pentagon wanted to axe the GE / Rolls Royce F-136 alternate engine), a Pratt & Whitney F-135 engine broke down. Again, the cause seemed to lie in broken turbine blades. However, this time the same problem occurred in the new, redesigned engine with redesigned turbine blades.

Pratt & Whitney stated that a defected bushing led to damage of the some fan blades. Pratt & Whitney also announced that a “minor modification” would be incorporated in all ISR (Initial Service Release) engines.

Engine problems continuing in 2011

After the problems in 2009, program officials no longer publicly commented about the engine problems. Also, there were no indications of any recurring problems with the engine; or that there were any reliability issues.

In April 2011, however, Admiral Venlet, then Head of JSF Program Office, told reporters that some engine problems were impacting on the delivery schedule. Pratt & Whitney confirmed to the press that “a small number” of F135 engines had been replaced with spares since March 2011 “with no impact to the F-35 test programme.” These replacements were ordered after detection of a mis-assembled ground test engine and further checks had identified the same problem on other (production) engines.

Two groundings in 2013

The F-35B STOVL variant was grounded Jan 18, 2013 after detection of a failure of a fueldraulic line in the aircraft’s propulsion system. The Pentagon cleared all 25 F-35B aircraft to resume flight tests on February 12, 2013. Pratt & Whitney engineers diagnosed the problem as a crimp in one of the fluid lines of the fuedraulic system, which is a system that uses jet fuel (rather than standard hydraulic fluid) to lubricate mechanical parts.

A more serious issue was found when on February 19, 2013 a routine inspection took place of a Pratt & Whitney F135 engine at Edwards AFB, USA. During the inspection using a borescope, there were indications that there was a crack in a LPT turbine blade. It was confirmed after further investigation. The turbine blade was sent to Pratt & Whitney in Middletown (CT), USA for further investigation.

On Thursday, February 21, 2013, the Pentagon Friday ordered the grounding for all F-35 aircraft. The F-35 JSF Program Office said in a Feb. 22 statement to the press: “It is too early to know the fleet-wide impact of this finding; however, as a precautionary measure, all F-35 flight operations have been suspended until the investigation is complete and the cause of the blade crack is fully understood.”

Some facts about the February 2013 incident

Involved in the February 2013 incident was the tenth F-135 engine with 700 hours, of which 409 flight hours. The aircraft was the F-35A test aircraft AF-2. The half-inch wide crack was found in a turbine blade of the low pressure turbine section. This makes it unlikely that it is caused by so-called FOD (Foreign Object Damage), such as a bird strike, because such an object has to pass the Fan Section (3 stages) Compressor Section (6 stages), combustor and high pressure turbine section before reaching the low pressure turbine section.

March 6, 2013 the JSF Program Office told the press that the problem was caused by thermal creep from stressful high-temperature, high-intensity testing at supersonic speeds and at low altitudes for a prolonged period of time, generating significantly more heat than expected.

New significant test failure December 2013

On December 23, 2013 ground engine FX648 experienced a “significant test failure” during accelerated mission tests (AMT) at Pratt’s West Palm Beach facility.

The engine suffered a failure of its 1st stage fan integrally bladed rotor (IBR, also known as a “blisk”) while doing ground accelerated mission durability testing. The stages are made up of integrally bladed rotors (IBR), the first of which is constructed from hollow titanium (the second and third are made of solid titanium).

The engine involved was the highest-time F135 in the test fleet, with about 2,192 hours of running time, or approximately nine years of service as a test engine -- more than four times the hours of any operational F-35 engine (By comparison, the high time SDD flight test engine has 622 flight hours and the high time operational engine has less than 250 flight hours).

This event was revealed months later, on March 26, 2014, by F-35 Program Executive Officer Lt. Gen. Christopher Bogdan during testimony to the US House of Representatives. Later, he told the press that “they had underestimated the stress at low-cycle fatigue.”

Pratt & Whitney said in a statement: “Our investigation is ongoing, but we have determined this incident does not pose a flight safety risk and will have no near-term impact to the operational fleet.” In April 2014 the root cause of the problem was still unknown.

In-flight emergency F-35B after major oil leak - June 2014

A new fleet-wide grounding order was issued on June 13, 2014 after an in-flight emergency with an F-35B. The pilot landed safely at Marine Corps Air Station Yuma (Ariz.) after what NAVAIR said in a statement was “a major engine oil leak, the source of which appears to be a separated oil inlet line from the oil flow management valve (OFMV) Rosan fitting. The fitting is common to all F135 engines.”

After engine-by-engine checks, most of the F-35 fleet (104 units at that time) was cleared to fly again some days later, but two other F135 engines were declared to have “suspect findings”.

F-35A with extensive engine fire at Eglin – June 2014

On Monday June 23, 2014 at 9:15 p.m. an F-35A assigned to the 33rd Fighter Wing’s 58th Fighter Squadron at Eglin Air Force Base caught fire as the instructor pilot was taking off as part of a two-ship formation for a continuation training mission. First reports said the “significant fire” originated in the tail of the aircraft, mentioning it a Class-A (big) incident.

The pilot successfully shut down the plane and escaped unharmed and the fire was extinguished with foam by a ground crew. The aircraft involved is the AF-27, s/n 10-5015, a LRIP-4 series aircraft that made its first flight on April 22, 2013 and was delivered on May 29, 2013 to the US Air Force. The F-35A was towed to a hangar. Accident investigators have collected any related foreign object debris at the same hangar for review.

No any pictures are known or published of the damaged F-35A. Unconfirmed reports claim the F-35A will be written-off.

Later, one eye-witness said, according to some press reports, that “The engine ripped through the top of the plane.” And, about debris was found on the runway six feet around the aircraft.

All F-35A flight operations were temporarily suspended at Eglin as they investigated the nature of the incident, but flight operations elsewhere continued.

However, after a week the Pentagon said July 3 it still had not found the cause of the fire, that the engine was the cause (not the Integrated Power Pack) and the technical air worthiness authorities of the Department of the Air Force and Department of the Navy issued a directive to ground the F-35 fleet based on initial findings from this incident. Additional inspections of F-35 engines had been ordered, and return to flight would be determined based on inspection results and analysis of engineering data.

The investigation is said to be focused – again - to the third stage turbine of the F135 engine as the likely source of the fire. The third stage turbine is the second stage in the low-pressure turbine section and common to all F-135 variants – the F-35A, F-35B and F-35C versions.

Preparations continued for F-35 participation in two major air shows in the United Kingdom, RIAT 2014 at RAF Fairford and the Farnborough Air Show. A final decision is expected July 10, 2014.

A spokeswoman of the Joint Program Office (JPO) told IHS Jane’s that they had “temporarily suspended” negotiations for the next lot of F-135 engines and that negotiations about the LRIP-8 series of F135 engines would resume when the scope of the latest engine issue and downstream effects would be known.

(The LRIP 7 engine contract was due to be awarded in fall 2013, as the LRIP 7 airframe contract was awarded on Sept. 27, 2013. The latest engine contract awarded to P&W, on Oct 23, 2013 is for LRIP 6 engines—Ed).

Conclusion

The repeated problems with the same part of the engine may be an indication of a serious design and structural fault with the F-135 engine.

A future F-35 fleet-wide grounding will paralyze Western airpower. Also, the lack of reliability will contribute to low service ability and to higher operating and support costs of the F-35 fleets in several countries, putting more pressure on low defense budgets.

Since the F-35 will be the cornerstone of NATO airpower and US homeland defense for the next decades, the problems with the F135 engine need the attention of the highest political decision-makers.

BACKGROUND: History of previous F-35 groundings

May 2007 (electrical system, engine): The first incident was recorded in May 2007, when the F-35A prototype AA-1 experienced an electrical short that disabled flight controls on the horizontal stabliser. A grounding was ordered and continued until December 2007, due to time needed to redesign several parts of the 270-volt electrical system and F-135 engine problems.

July 2008 (cooling, electrical): On July 23, 2008, both flying F-35 prototypes were grounded after problems were detected with ground cooling fan electrical circuitry, DCMA reported on Aug 18, 2008 that tests were delayed as a result of testing anomalies on the 28 Volt and 270 Volt Battery Charger/Controller Unit, the Electrical Distribution Unit and the Power Distribution Unit. It was due to design problems. Flights were resumed first week of September-2008.

December 2008 (engine, ejection seat): On Dec 12, 2008 the F-35 was grounded again as a result of engine and ejection seat anomalies. Seat anomalies were observed in ejection seat sequence during an escape system test on Nov. 20, 2008. It took nearly 3 months to solve the problems and aircraft AA-1 did not return to the skies until Feb. 24, 2009.

May 2009 (most likely engine): The F-35 fleet didn’t fly between May 7, 2009 (84th flight of prototype AA-1) and Jun 23, 2009, shortly after reports of new engine problems (the “screech” problem). No comments were available from JPO or L-M.

October 2010 (engine, fuel pump): F-35 fleet grounded after the fuel pump shut down above 10,000ft (3,050m). A fuel pump sequence error, caused by a software bug, could have initiated an engine stall.

March 2011 (Integrated Power Package): The entire F-35 fleet was grounded some weeks after test aircraft AF-4 experienced a dual generator failure on March 9, 2011. After both generators shut down in flight, the IPP activated and allowed the F-35’s flight control system to continue functioning. The problem was traced to faulty maintenance handling.

June 2011 (software): Carrier-based F-35C suspended from flying after engineers at NAS Patuxent River discovered a software problem that could have affected the flight control surfaces. Grounding was from 17 June until 23 June, 2011.

August 2011 (Integrated Power Package): A precautionary grounding of all 20 F-35s that had reached flying status was ordered Aug. 3, 2011 after a valve in the Integrated Power Package (IPP) of F-35A test aircraft AF-4 failed. On 18 August 2011 the flight ban was lifted to allow monitored operations. A permanent resolution would be installed later.

January 2012 (ejection seat): 15 Lockheed Martin F-35s are grounded for about 12 days to repack improperly installed parachutes (reversed 180 degrees from design). The grounded aircraft are equipped with new versions of the Martin Baker US16E ejection seat, designated as -21 and -23.

January 2013 (engine, fueldraulic line): The F-35B STOVL variant was grounded Jan 18, 2013 after detection of a failure of a fueldraulic line in the aircraft’s propulsion system. The Pentagon cleared all 25 F-35B aircraft to resume flight tests on February 12, 2013. Problem caused by a manufacturing quality problem (wrongly crimped fuel line).

February 2013 (engine, crack 3rd stage): On Feb. 21, 2013, the Pentagon grounded all F-35 aircraft, after a routine check at Edwards Air Force Base revealed a crack in a low pressure turbine blade in the engine of an F-35A.

June 2014 (engine, oil inlet line): Fleet-wide grounding order was issued on June 13, 2014 for several days after in-flight emergency of F-35B at MCAS Yuma after major oil leak. Root cause: separated oil inlet line from the oil flow management valve.

June 2014 (engine) (current): Fleet-wide grounding from July 4, 2014 after F-35A engine fire at AFB Eglin during take-off on June 23, 2014. Root cause unknown at time of writing (July 9, 2014).
Investigation focused on third stage turbine of the F135 engine.


(EDITOR’S NOTE: And still no explanation has been provided to date by Lockheed Martin or the F-35 Joint Program Office about the mysterious incident at Lubbock Texas.
On March 11, 2013 aircraft AF 23, a US Air Force F-35A en route from Fort Worth to Nellis AFB, diverted to the commercial airport in Lubbock, Texas, after a “warning light” came on.
The aircraft remained at Lubbock for four weeks, while Lockheed personnel performed unspecified work, and finally was able to fly out on April 8.
At the Paris air show in June 2013, Lockheed spokesman Michael J. Rein told Defense-Aerospace.com that JPO had issued a statement on the incident, but this is not the case.
The mystery continues.)


-ends-





https://www.defensenews.com/air/201...f-35-operational-tests-threat-of-delays-loom/







Breaking News
Heading into F-35 operational tests, threat of delays loom

By: Valerie Insinna   October 17, 2018



EFRQBPFK6BHUBDUMLG45LBB5CU.jpg
U.K. F-35 Lightning fighter jets are shown conducting their first night flying trials off the United Kingdom’s largest warship, HMS Queen Elizabeth. (Dane Wiedmann/DVIDS)



WASHINGTON — The F-35 is set to move into operational testing next month — a major milestone that precedes the Pentagon’s decision on whether to begin full-rate production of the jet — but there are already signs that it may not be able to complete testing on time.

Furthermore, the F-35 joint program office is still assessing what impact a recent fleet-wide inspection of the F-35 enterprise for faulty fuel tubes will have on its Nov. 13 start date — though the JPO remains confident that it can wrap up needed repairs in time for operational tests to begin in November.

The Pentagon is aiming to wrap up initial operational test and evaluation, or IOT&E, on schedule in July 2019 despite a two-month delay in starting the tests, according to a Sept. 14 PowerPoint presentation by F-35 test director Air Force Col. Varun Puri, which Defense News obtained.



Most F-35s return to flight operations after fuel tube problem

Around 80 percent of F-35 jets have been cleared of an issue that grounded the fleet last week.

By: Valerie Insinna

However, it will but will have to move through test points at a rapid pace and accept additional risk in order to make that deadline, stated the document, which described the readiness of the F-35 to begin testing.

Puri’s presentation specifies a Nov. 13 target date for the F-35 to begin the formal IOT&E process.

Nov. 13 remains the projected start data “pending completion of the remaining readiness actions,” stated F-35 JPO spokesman Joe Dellavedova in response to emailed questions, although “impacts from a mandatory fuel system inspection are being assessed,” he acknowledged.

Last week, all U.S. and international F-35s were momentarily grounded to allow for a fleet-wide inspection of the jets for a defective fuel tube that was found in the Marine Corps’ investigation into a Sept. 28 F-35B crash near Marine Corps Air Station Beaufort in South Carolina.

Get breaking news in your inbox
Don't miss the latest breaking news from the Defense Industry. Sign up today






By Monday morning, more than 80 percent of about 300 F-35s already in service had returned to flight, and about half of the impacted jets can be fixed using the existing spare parts inventory. Pratt & Whitney, which produces the F135 engine for all F-35 variants, is racing to procure more parts so that the remaining aircraft can be cleared in the coming weeks. However, questions still remain on whether Pratt or the U.S. government will be on the hook for paying for retrofits.

While a short deferment of a couple days or a couple weeks is usually not a significant barrier — and could turn out inconsequential in the F-35 program’s case — the test plan does not leave much room to absorb delays.

The Joint Strike Fighter Operational Test Team, or JOTT, still believes it can complete IOT&E by the original July 2019 goal, but only by “reducing re-fly assumptions and assuming more risk” — or in layman’s terms, lowering its estimates of how many tests it will need to redo in order to complete the test program and leaving little margin for flight cancellations due to weather or other factors.

In the “worst case scenario,” completion of operational testing could occur as late as Sept. 2019, which could add budget pressure to the program, Puri’s presentation said.



F-35 price falls below $90M for first time in new deal

Prices for all three models of the F-35 went down in the deal for the 11th lot.

By: Valerie Insinna

It’s unclear what form those budget pressures would take. “IOT&E is fully funded through September, if required,” said DellaVedova, but the JPO did not respond to a question on whether additional funding would be needed if testing slipped even further, into the new fiscal year starting on Oct. 1.

When asked about the specific types of risk the Pentagon will assume in order to complete IOT&E on time, the JPO did not provide specifics, saying that it was up to the JOTT and the Pentagon’s Director of Operational Test and Evaluation to lay out the schedule.

“Operational testing will be executed in the most expeditious and efficient manner possible, while ensuring test adequacy is met, with continuous assessments of progress toward test objectives based on collected data,” DellaVedova said.

The formal IOT&E period was initially scheduled to begin Sept. 15, but was pushed back two months to allow for the delivery of the latest version of software, called 30R02.03. Robert Behler, the director of operational test and evaluation (DOT&E), said in an Aug. memo that the new software was needed to correct deficiencies with the F-35’s Air-to-Air Range Infrastructure system, which will allow testers to evaluate the jet during range-based testing.

Preliminary IOT&E activities began earlier this year, and included two ship missions against low-end threats, cold weather tests and a close-air-support assessment.

Earlier this month, the Defense Department’s top acquisition official — Ellen Lord, undersecretary of defense for acquisition and sustainment — certified that the F-35 was ready to begin IOT&E, concurring with the F-35 joint program office’s recommendation to start testing in mid-November, said her spokesman Lt. Col. Mike Andrews in a statement. The decision was made after an Oct. 2 operational test readiness review.

Currently, the Defense Department is slated to make a decision on full rate production by the end of 2019, but IOT&E activities will need to be complete before a declaration is made.





About
this
Author

About Valerie Insinna
Valerie Insinna is Defense News' air warfare reporter. She previously worked the Navy/congressional beats for Defense Daily, which followed almost three years as a staff writer for National Defense Magazine. Prior to that, she worked as an editorial assistant for the Tokyo Shimbun’s Washington bureau.




http://www.sohu.com/a/324650930_229282?spm=smpc.home.mil-pics.1.1562179548367vUixqCj




两机动力控制


914文章 2386万总阅读
查看TA的文章>


0

  • 分享到


原创 五角大楼担忧普惠F135发动机长期延迟交付

2019-07-03 23:38

导读:普惠长期为五角大楼的F-35战机提供动力引擎——F135发动机,同时也是该战机的发动机唯一供应商。近日,五角大楼公开表示担忧该公司是否已准备好迎接明年发动机批产的需求。

eaa19b13601e4583b79bf12d3f259c3a.png


目前,普惠仍然受到国防合同管理局此前未披露的“纠正行动请求”的影响,该请求是由于之前的一批F-35战斗机发动机的“交付性能不佳”,特别是海军陆战队和英国使用的垂直起降版本。

F-35战斗机具备3种主要的衍生版本,包括采用传统跑道起降的F-35A型,短距离起降/垂直起降的F-35B型,与作为航母舰载机的F-35C型。对应的F135发动机也有三个不同的型号,F135-PW-100将作为F-35A空军型的动力系统,而F135-PW-600将作为F-35B海军陆战队短距起飞/垂直降落型的动力,F135-PW-400将作为F-35C海军舰载型的动力。

普惠的行动很可能不仅受到五角大楼和F-35的国际买家的关注,也受到股东和投资者评估。特别是近期,普惠母公司联合技术公司计划与雷神公司合并,而F135发动机也是合并后新公司的主要收入来源之一。

根据国防合同管理局在去年12月正式提出的要求,作为洛克希德-马丁公司制造的F-35战机的唯一发动机供应商,必须在今年年底前证明它已兑现承诺的改进措施,五角大楼发言人马克-伍德伯里在一份声明中概述了这些问题。

这项耗资4280亿美元的F-35战机计划于明年获得批准进入全面量产阶段,这是承包商最有利可图的武器计划阶段。该决定取决于飞机本轮强化作战测试期间的评估,该评估结果必须是有效且可维持的。

根据美国国防部关于F-35战机的最新选定采购报告,在4280亿美元中,至少有660亿美元用于采购2470台F135发动机。此外,根据彭博社情报分析师Douglas Rothacker的说法,五角大楼的预算文件显示,F135发动机预计每年为普惠公司带来约20亿美元的营收。

普惠发言人约翰-托马斯在一封电子邮件声明中表示:“我们已经认真履行F135发动机生产承诺的责任,今年早些时候提交的纠正行动计划列出了我们如何做到这一点。在过去一年中,我们已投入超过2亿美元用于增加产能,目前已向我们的供应商工厂部署了100多名普惠工程师,以支持这一生产义务。“

同时,普惠总裁Bob Leduc在6月17日的巴黎航空展上对分析师们强调了F135发动机的收入潜力。他表示:“考虑F135发动机营收的另一种方式是一年前我们每月制造大约8台发动机,现在我们每月可以生产13~14台发动机。而当你想到F135发动机时,你会发现这里将有超过4,000架飞机,并且远销全球,因此未来30年每月会有16台F135发动机被交付。”

根据国防合同管理局的说法,导致F135发动机延迟交付的主要问题“与供应链能力,材料短缺”和生产问题有关。

该机构在1月至3月的内部季度评估中表示:“由于高振动和异物碎片导致的发动机测试经常失败,这一问题继续困扰着生产,导致海军陆战队的发动机型号F135-PW-600交付一直很晚。”

截至6月初,普惠在合同中被要求在最新的生产合同中交付108台发动机(该项目的第11批发动机)。伍德伯里在声明中表示,在交付的90台发动机中,88台“平均延迟了40天”。而五角大楼即将完成与洛克希德和普惠签订第12批也是最大的F-35战机合同。

目前的发动机数量增加还加剧了普惠的不稳定交付记录。根据美国政府问责办公室4月份的一份报告,虽然交付量从2012年的48台提升到了2018年的81台,但是其中有86%的发动机交付时间延迟,高于2017年底的48%。

当被问及美国国防合同管理局是否有信心对普惠已为全速量产做好准备时,伍德伯里表示,该机构正在监控普惠纠正行动计划中的里程碑,并需要在做出判断之前看到进展。返回搜狐,查看更多
 

KuanTi01

Alfrescian (Inf)
Asset
Singapore has no balls to cancel any orders from the USA! At most, it will let out a little whimper and ask for clarification.:rolleyes:
 

tun_dr_m

Alfrescian
Loyal
They will fall off the sky in Pee Sai, fucking failed engine, and plunged into HDB blocks.
 
Top