PDA

View Full Version : P-3 Orion VMCa incident.


Trojan1981
8th Aug 2008, 00:16
Apologies if already posted, I recieved this in an email and thought it interesting enough to post here.

The P-3C that almost went into Puget Sound waters a few days ago was
>>> from NAS Whidbey.
>>>
>>> It was a CPW-10 aircraft being operated by VP-1.
>>>
>>> Squadrons don't own aircraft any more.
>>>
>>> The P-3 fleet has so deteriorated because of under-funding and over-use
>>> that there are less than 100 still flyable*.
>>>
>>> The P-3s belong to the wing and are "lent to the squadrons on an
>>> as-needed"
>>> basis.
>>>
>>> The mission was a NATOPS pilot check, with a CPW-10 pilot (LT) aboard, a
>>> VP-1 LT and LTJG, plus VP-1 aircrewmen that included two flight
>>> engineers.
>>>
>>> The word is that the crew finally recovered control of the aircraft
>>> about 100 feet above MSL by pulling 7 Gs.
>>>
>>> The bird was landed back at NASW.
>>>
>>> Max damage was sustained by the aircraft, including almost tearing off a
>>> wing.
>>>
>>> Aircraft BuNo 161331.
>>>
>>> My first thought is that this was a Vmc incident:
>>>
>>> At Whidbey, P-3C 161331 was doing a Functional Check Flight.
>>>
>>> They shut down #1 engine.
>>>
>>> With #1 off, #2 engine exhibited vibrations and was shutdown.
>>>
>>> With two engines off on the same side the aircraft stalled.
>>>
>>> 7 G's were reported to pull it out of the stall.
>>>
>>> 45 consecutive rivets were pulled out on the stbd wing during the 7 G
>>> pull out (rolling pull), after peaking at negative 2.4g's as well.
>>>
>>> They did five spin rotations from 5500 ft -- they bottomed out "between
>>> 50 and 200 ft."
>>>
>>> They could see the inside of the fuel tanks when they landed.
>>>
>>> They were at 160 KIAS, appr flaps during a prop fails to feather drill
>>> on #1 when #2 started surging.
>>>
>>> They bagged #2, but while doing so got to 122 KIAS.
>>>
>>> When they added power, they were way below VMC air, and departed.
>>>
>>> SDRS recorded the flaps being raised and the landing gear being cycled
>>> down and then back up.
>>>
>>> Aircraft released all the fuel in tank #3 when it appears that the seam
>>> between planks 3 and 4 split.
>>>
>>> Tank #4 also lost its fuel load when plank #1 separated from rest of the
>>> aircraft wing.

http://i253.photobucket.com/albums/hh68/trojan1981/strike_1.jpg
http://i253.photobucket.com/albums/hh68/trojan1981/strike_2.jpg
http://i253.photobucket.com/albums/hh68/trojan1981/strike_3.jpg

Kengineer-130
8th Aug 2008, 01:05
oops :uhoh:... Blue line speed anybody? :eek:... Seems like a very lucky "save"...

BEagle
8th Aug 2008, 05:54
That info. came my way yesterday as well - suprised that a Google search didn't come up with anything further.

One imagines that it was rather a quiet flight home.......:\

aviate1138
8th Aug 2008, 06:49
One tough old Lockheed machine.........

Nopax,thanx
8th Aug 2008, 07:16
Photo #1 is actually the wing rib; you can see the lower plank underneath. Lot of damage though, those guys had someone on their side that day.

nacluv
8th Aug 2008, 07:53
I think the local congregation will have seen an increase in numbers in the last week or so! A religion-finding experience if ever there was one. I bet the local laundry saw a bit of an uptick too.

Great save - well done to the crew, but I assume the airframe will now be SOC?

gazbert
8th Aug 2008, 08:04
Immediately after the incident (Well, within a few days) this was the official release from the US Naval Safety Center -

Mishap Date: 07/22/2008 Severity: A FM Time: 13:00 Evt Ser: 69798
Reference: VP-1 221300JUL08
Acft: P003C Count: Y Destroyed: N Major Command: COMNAVAIRPAC
Custodian: VP-1 Fatalities: 0 Buno: 161331
Location: WHIDBEY ISLAND
Summary: AIRCRAFT OVERSTRESSED DEPARTED CONTROLLED FLIGHT.

Had Enough 77
8th Aug 2008, 09:09
Holy S**t :eek:.

That would have concentrated the mind a little. Good job to get it back in one piece (well kind of).

Very lucky fellows.

Truckkie
8th Aug 2008, 10:16
The perils of double assy flight!:eek:

Well done on the recovery:ok:

VMCA2??

Poodles in flight
8th Aug 2008, 19:28
This is the most practiced sim scenario in the P3 world a problem with #2 with #1 loitered dealing with it should have been second nature.

Unless the vibrations on #2 were incredibly severe why didn't they restart #1 before shutting down #2 ?

How did they get so slow on three engines before shutting down #2?

If they were getting slow why didn't they restart #1.

What the &^%* were the Flight engineers doing ?

well done to the aeroplane for surviving being put into a situation it was not designed to be flown in.

More questions when I think of them.

NutLoose
8th Aug 2008, 19:34
Glad to see they made it........ tin can be fixed or recycled...... people can't be.. :D

Seem to remember a certain Tristar doing autoland when the system was off.... creaks and groans would probably be heard in Oxford when they moved that thing to base hangar AFTER it did a circuit........

West Coast
9th Aug 2008, 00:44
I'd love to hear that phone call.

"Err Skipper...you have a minute?"

herkman
9th Aug 2008, 04:23
Believe they pulled 7G, lost ov 5000ft and five complete rotaions.

But having pulled No 1 , why did they not set it up for air start, prior to pulling No 2.

What happened to the CRM, were two engineers on that aircraft, 4 sets of eyes and 4 mouths, should not have happened.

Regards

Col

hello1
9th Aug 2008, 05:25
They were at 160 KIAS, appr flaps during a prop fails to feather drill
on #1 when #2 started surging.

Maybe this is why they didn't restart #1 before shutting down #2. A good reminder of the potential for things to go wrong on those lovely old engineering test flights.

Poodles in flight
9th Aug 2008, 10:42
Ok so you have a prop failed to feather ,again a well practised and very common sim scenario, in that case why shut down #2 for surging if you are slow? Surging is not a mandatory shut down in a P3 , there are several things you could try to stop the surging Td system , prop govenor , mean while you have either got #1 to feather or set yourself up in a safe flight regime before you bag #2 They had at least 5000 ft so it still begs the question why they ended up slow with 2 engines shut down spinning towards the sea .

bayete
9th Aug 2008, 15:52
Makes you wonder how sensible the 6 months practise assy currency rule is.
Seem to remember shutting down 4 engines in one sortie not that long ago!!! Increases the odds somewhat.:ooh:

Trojan1981
10th Aug 2008, 00:26
One tough old Lockheed machine.........
An RAAF Orion went into the lagoon in the Cocos islands due to the wing structure not being constucted to manufacturers specs. This led to a re- winging program. Not related but interesting none the less.
http://i253.photobucket.com/albums/hh68/trojan1981/RC_DG_3A9_754_sized.jpg

An RAAF 707 also went down off the coast of East Sale, Victoria, Australia in 1991 after what was described as a "Sudden and extremely violent departure from controlled flight" during double assymetric training. All five crew were killed. It seems this is not a unique incident.

KeepItTidy
10th Aug 2008, 01:25
Well as a person not connected in aviation i think the fleet should be grounded ,its common practise these days

Brian Abraham
10th Aug 2008, 03:02
Trojan1981, the accident was caused by a combination of three factors,
namely, pilot induced overload in that the pilot exceeded the aircraft’s
operational limit of 3 g, manufacturing deficiency in that several wing leading
edge ribs were below the specified thickness, and under the conditions of the
accident, the onset of transonic compressibility effects that increased the
aerodynamic loads on the leading edges beyond the level that the sub - standard ribs could bear.
Notably, the ribs as designed had a failure point of 3.9 g and the below specification ribs had a failure point of 3.4 g. During the aircrafts design no allowance had been made for transonic compressibility effects. It was the compressibility effects that lead to the rib overload. Its ironic that a US Navy P-3 also had an identical LE failure (also at Cocos, must be some thing in the water there) 3 years previously, but landed safely. An opportunity lost to nail the problem?
Full report here
http://dspace.dsto.defence.gov.au/dspace/bitstream/1947/4157/1/DSTO-TR-0008%20PR.pdf

porch monkey
11th Aug 2008, 08:13
Fleet should be grounded? Are you on drugs?

Vija
30th Nov 2008, 03:00
The US P3 incident wasn't a problem with the aircraft at all, it was a human factors incident which was luckily saved and the old girl survived the ensuing pullout.

Pontius Navigator
30th Nov 2008, 09:04
Fleet should be grounded? Are you on drugs?

AFAIK it is not uncommon for the US, particularly the USAF, to institute fleet-wide technical stand-downs.

The RAF has done this on rare occasions. The V-Force had a period of no engine starts on the Vulcan QRA force. The Valiants were grounded temporarily before they were scraped.

Hastings were grounded world-wide when the elevator failed on one.

There have probably been others.

It really depends on the immediate evaluation of event and risks.

BEagle
30th Nov 2008, 09:26
Wasn't there once some fleet grounding of the Belslow? I was told that a signal was sent to all airborne Bels, instructing them to land at the nearest suitable aerodrome....

Which, of course, turned out to be places like Bermuda and Hickam...:ok:

Probably an urban myth, I suspect.