KC130FE

160627 is now at Pax.

160626 is the actual BUNO. Here is a link to the story in Marine Corps Times. There is a picture of Nick and the plane.

http://www.marinecorpstimes.com/news/2008/11/marine_boneyard_112308/

We will be going to Okinawa this weekend to pick up 160627. It is coming to VX-20 at Pax River.

Tony V

Happy birthday to you too. Semper Fi

Tony V

“What makes this exceptional is this is a very (rare) problem we see. There is nothing in the manuals on how to handle it,†said Lt. Col. Dom Sarnataro, safety officer for the guard’s 189th Airlift Wing. “There wasn’t a clear-cut emergency procedure to take care of this. There was no checklist to run through, no manual explaining how to save the day. This is not found in (flight) simulator training.â€

Sarnataro said the crew members’ experience and the relatively light plane were what worked in their favor.

It is in the C/KC-130 F/R/T Navy/Marine Corps NATOPS (-1) manual and praticed in the SIM as well. From what I recall, it was put in there as a result of the King 56 mishap. Just another reminder as to why there is a need to have a systems expert on-board for times like these. Kudos to the MSgt for his quick thinking.

The final report is out as of 03 Oct 08. Without getting into too much of it, the primary cause was the MP snatched the throttles back too fast and flamed out three of the four motors while reacting to MWS warning. According to the report #2 engine continued to run all the way to landing. There was never any attempt to relight or feather any of the non-functioning engines. APU was not running. From flameout to touchdown was 57 seconds. I thought the pilot did a great job of landing the plane once he decided that was the only option.

It\'s a good, thorough report. You should check it out if you have access to it.

The final report is out as of 03 Oct 08. Without getting into too much of it the bottom line was the MP snatched the throttles back too fast and flamed out three of the four motors while reacting to MWS warning. According to the report because the fuel control was not working properly (running rich) the #2 engine continued to run all the way to landing. There was never any attempt to relight or feather any of the non-functioning engines but to be fair time from flameout to touchdown was 57 seconds. I thought the pilot did a great job of landing the plane once he decided that was the only option.

PICKUP LINE

Having already downed a few power drinks, she turned around, faced him, looked him straight in the eye and said, \"Listen here, Good Looking, I screw anybody, anytime, anywhere, your place, my place, in the car, front door, back door, on the ground, standing up, sitting down, naked or with clothes on, dirty, clean . . . it doesn\'t matter to me. I\'ve been doing it ever since I got out of college and I just love it.\"

Eyes now wide with interest, he responded: \"No kidding. I\'m a Flight Engineer too. What squadron are you with?\"

Did you ever get any info?

SEFEGeorge wrote:

I read the King 56 report. I know that they looked at the sync and TD amp issues. But wasn\'t the final opinion the engines failed due to fuel starvation brought on by improper fuel management by the FE? - i.e., all 4 engine pumps off and feeding the engines from the fuselage tank using cabin pressure so when the tank was empty the cabin pressure feed overrode the tank to engine gravity feed.

Yes.