Fire damages F-35A

luke_sandoz · by **luke_sandoz** » 23 Jun 2014, 20:59

A Lockheed Martin F-35 Joint Strike Fighter was severely damaged — possibly destroyed — in a Monday morning fire on the runway at Eglin Air Force Base, Fla., USNI News learned.

No injuries were reported and officials have begun an investigation into the incident, defense officials told USNI News on Monday.

“The aircraft was preparing to conduct a continuation training mission at the time of the incident, but aborted during takeoff at Eglin Air Force Base due to a fire in the back end of the aircraft,” according to a Monday statement provided to USNI News from the Air Force.
“Emergency responders extinguished the fire with foam.”

The aircraft was a F-35A — the Air Force variant of the fighter — assigned to the 33rd “Nomads.” Fighter Wing. The wing is schoolhouse for all versions of the JSF and trains sailors, airmen and Marines.

Source: http://news.usni.org/2014/06/23/breakin ... pilot-safe

spazsinbad · by **spazsinbad** » 23 Jun 2014, 21:06

Good news that the pilot is OK. I'll hope that a relatively intact? aircraft makes the problem solving/finding easier?

neurotech · by **neurotech** » 23 Jun 2014, 21:48

spazsinbad wrote:Good news that the pilot is OK. I'll hope that a relatively intact? aircraft makes the problem solving/finding easier?

Glad the pilot made it out OK.

I'm waiting for the stupid comments in the media to start.

A fire like this could never happen with a Skyhawk, Hornet, Raptor or Rhino could it? I've heard of engine/fuselage fires on 3 out of 4 during takeoff, causing major damage or complete destruction. A few years ago, a F/A-18C had an engine explosion just before launch. The jet was destroyed by fire, even though it stayed on the catapult. An F-22 was lost due to a fuselage hydraulic leak, causing a fire, except it wasn't on takeoff.

My wild a__ guess says this F-35 blew a major fuel line, or FOD damaged a fuel tank, causing a massive fuel leak. If this had been a catastrophic/uncontained engine core failure bad enough to cause a major fire, the pilot probably would have ejected out during take-off. Pilots have aborted takeoff after catastrophic engine failures in F-16s with ground egress, so my guess is that it wasn't the engine itself this time.

arrow-nautics · by **arrow-nautics** » 23 Jun 2014, 21:50

Thank goodness the pilot is OK. On the downside "Bring Out the Knives"

cantaz · by **cantaz** » 23 Jun 2014, 22:30

Well, time to abstain from internet for a few weeks.

cola · by **cola** » 23 Jun 2014, 23:05

neurotech wrote:I'm waiting for the stupid comments in the media to start.

No need, all were expended on that PAKFA incident, already...now, if I could only find that thread...wait!

viewtopic.php?f=22&t=25623

sprstdlyscottsmn · by **sprstdlyscottsmn** » 23 Jun 2014, 23:25

so it took 15,000hours across over 100 airframes to have one major "oops"

neurotech · by **neurotech** » 23 Jun 2014, 23:36

cola wrote:
neurotech wrote:I'm waiting for the stupid comments in the media to start.

No need, all were expended on that PAKFA incident, already...now, if I could only find that thread...wait!
viewtopic.php?f=22&t=25623

In other news... "US test pilot flies MiG-21 and immediately demanded to be transferred to F-35 training squadron, citing safety concerns"

Note: The USAF have been known to send both USAF TPS students and test pilots up in MiGs. I don't think they fly Flankers..

neptune · by **neptune** » 23 Jun 2014, 23:55

spazsinbad wrote:Good news that the pilot is OK. I'll hope that a relatively intact? aircraft makes the problem solving/finding easier?

Amen,

With the a/c somewhat intact the root cause analysis should determine if it is either an infant mortality system design issue or a "loose fuel system fitting" (maintenance??), or "other".

Mishap classification will be determined, "Class A mishaps, which involve at least $2 million of damage, a permanent total disability or a fatality".

If repairs are effected, the comparison of the time and materials cost estimates can be evaluated versus the estimates from both operations and engineering.

local news....

By LAUREN SAGE REINLIE / Daily News
Published: Monday, June 23, 2014 at 18:51 PM.

EGLIN AFB — An F-35 fighter jet caught on fire during takeoff on Monday morning.

The pilot noticed the fire in the back of the airplane about 9:15 a.m. and aborted the flight while still on the runway at Eglin Air Force Base.

The pilot was safely able to shut down the engine and get out of the plane and no one was injured, said Navy Lt. Hope Cronin, a spokeswoman for the 33rd Fighter Wing.

“He went through all the proper processes and procedures for a ground emergency,” Cronin said. “That’s something we go through in training and something we need to be prepared for in any aviation environment.”

Firefighters were able to put the fire out using fire suppressing foam.

[...]
The extent of damage to the plane involved in Monday’s accident was still being assessed, but Cronin said the fire was significant.

All Air Force F-35 flights at Eglin have been suspended while the cause of the fire is investigated, she said.
[...]

Source: http://www.nwfdailynews.com/military/to ... 6917?tc=cr

Nothing more at the jump, still looking.... :wink:

araya · by **araya** » 23 Jun 2014, 23:59

Unfortunately this is the worst what was possible to happen for the F35 Program. Now the F35 enemy’s will not stop over and over again to point out this incident as argument to kill the F35 Program. I see it already coming a 1 Year IOC delay and a cut or even a delay of the planned order of 34 to 38 airframes for FY2015.

Has everyone find a picture of the damaged F35? Possible it sounds stupid but let’s hope what the Pictures are not impressive because why this will be another big gift for all F35 heater and boulevard press for their anti F35 campaign.

lookieloo · by **lookieloo** » 24 Jun 2014, 00:10

Well, it was a good 14 year run. Just glad I kept my mouth shut over the mishaps of other fighters (for the most part), although I'm not looking forward to the teacup $hitstorm to come...

count_to_10 · by **count_to_10** » 24 Jun 2014, 00:26

In some sense, it's a relief to get the first one out of the way.

luke_sandoz · by **luke_sandoz** » 24 Jun 2014, 00:52

Still very little news on this.

Another version, less dramatic

http://www.nwfdailynews.com/military/to ... y-1.336917

tokenblkguy1785 · by **tokenblkguy1785** » 24 Jun 2014, 00:58

Hot brakes.

lookieloo · by **lookieloo** » 24 Jun 2014, 01:04

luke_sandoz wrote:Still very little news on this.

Another version, less dramatic

http://www.nwfdailynews.com/military/to ... y-1.336917

The pilot noticed the fire in the back of the airplane about 9:15 a.m. and aborted the flight while still on the runway at Eglin Air Force Base.

Wait what?... I thought rear viz was nil :shrug: