PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Rotorheads (https://www.pprune.org/rotorheads-23/)
-   -   G-JSAR (https://www.pprune.org/rotorheads/279380-g-jsar.html)

Jetboxer 9th June 2007 16:35

G-JSAR
 
Was wondering if there had been any further findings with regard to the G-JSAR ditching.

Having googled 'G-JSAR', came accross this video.



YouTube - G-Jsar scramble

Apologies in advance if it's already been posted somewhere!

HeliComparator 9th June 2007 17:09

I have seen some crap videos on youtube but that one is really bad! Unfortunately no clues yet from the Dutch AIB as to possible causes. Yes, it seems to be taking for ever!

HC

NorthSeaTiger 24th March 2009 17:57

G-JSAR
 
What happened to G-JSAR after it's accident ? It still shows as registered on G-INFO . Was it written off or is it still flying ?

NST

Jetboxer 20th December 2009 19:18

Still waiting..........

3 years and 1 month later.

Achilles426 21st December 2009 00:10

JSAR
 
It has been sold to Eurocopter and re-furbished and apparently sold to Romania as a SAR aircraft!

la grua 21st December 2009 17:29

Life after death!
 
Good to hear that jsar has been reborn and now haunts transylvania!!
Heared a wisper ,some time ago, that Bond had been enquiring as to her health. Rumoured, as a addition to the jigsaw pair. They were advised, by ECF, that the rebuild costs would exceed the price of a new build 225.

Senior Pilot 22nd December 2009 18:48

Another video from YouTube:


HeliComparator 23rd February 2010 18:05

The final report is published today by the Dutch Safety Board:

Emergency landing in sea, AS322L2 Search and rescue helicopter, North Sea near Den Helder - De Onderzoeksraad voor veiligheid

HC

ps: Its long!

SASless 24th February 2010 06:59

The Summary is short and to the point!

marcr 24th February 2010 10:26

1996 Eurocopter Internal Report
 
Any further information about the nature of this "significant controllability problem" ?

(Accident Report, Page 120, Conclusion 12.)

SASless 24th February 2010 14:45

HC,

In my experience teaching in the Sim.....I and other instructors noted a distinct tendency amongst pilots of all backgrounds to immediately kick off the AutoPilot and grab manual control when Alarms and Warning Lights of any kind activated.

Is there a technical reason the crew would have had to take the Action they did with the Auto Pilot in this accident? Was there a SOP, Flying Instruction or similar that dictated such a response prior to the onset of control issues or the decision to descend?

Considering the engine issues.....the report states the engines were sustaining flight despite the unusual indications which fit no checklist procedure. Would the aircraft have maintained flight on a single engine at the weight, temps, and altitude they were operating?

If the Factory could obtain a control degradation by test flying the profile used by the crew.....is that a "normal" situation for the Aircraft Model in question and has it been documented before the accident during testing? Is there a design flaw in the flight control system that is inherent to the design?

Is this another example of problems akin to but different of the EC Jack Stall problem in the 350/355 series?

HeliComparator 24th February 2010 17:19

SAS

No, there was no technical reason to dump the upper modes. Use of the upper modes/automation was a key area of training since this aircraft had transition down to a fix, auto-hover etc. However with hindsight I think that too much training time was spent on SAR-type training and not enough on normal and abnormal general flying operations. The Ops Man didn't specifically say to engage upper modes when there was a problem, though that was generally the culture in the company. Of course its now in the manual...

I think the very limited Simulator training these pilots received was an issue - there can be no doubt that Sim training familiarises pilots with how to deal with emergencies as a crew, something that cannot be learned outside the Sim other than by making mistakes.

The engine problems did not cause any loss of power, and to answer your question yes they had easy OEI stayup capability. There was some discussios about why they decended, but as far as I was concerned it was because they were getting close to De Kooy and it was time to descend anyway for a VFR arrival, engine problem or not.

I think EC were trying to prove that it was the AP hydraulic problem, they did some test flying with AP Hydraulics out / cycling and showed that control movements could be made to match those of the accident flight, however there were many other scenarios that could also fit, so it didn't really prove anything. Not quite sure exactly what question you are asking here.

Since that type of aircraft has a millions of flight hours without a reputation for control jams, I doubt there is an inherent design issue, but we can't be certain! Its frustrating that I thought there must be a connection between the engine issue and the control problem (that started only a couple of minutes after the engine issue) but none could be found.

HC

SASless 24th February 2010 20:06

It makes one wonder how an engine power delta (deviation) could lead to cyclic control problems. No doubt they were there as it would take some motivation to put down at night in cold rough water rather than continue to land which was not so far away. As you rightly say....there are so many hours on the fleet it should be a well known flying characteristic if it were common to the aircraft.

One has to assume the engine problem and the flight control problems did not have a common cause as they are two very different systems.

HeliComparator 24th February 2010 21:09

SAS

the engine problem and the flight control problems did not have a common cause as they are two very different systems.
However there is a place where engine governing meets flight controls - the anticipator, which is a pair of potentiometers that set each engine's N2 datum, and therefore have the power to cause the sort of engine fluctuations they experienced. The anticipator is located in the flight control cabinet and whilst its connected only to the collective pushrod, its adjacent to the cyclic pushrods.

Despite my feeling that this must have been the common link, the investigation found no evidence that there was any connection.

HC

SASless 24th February 2010 21:49

How could that cause cyclic problems? I can see where the wandering N2 issues would be possible....which would also affect Ng and other parameters.

Are you suggesting a physical binding of the cyclic controls by the Anticipator or perhaps an electrical or electronic interference? If a physical interference....would it be able for the cyclic controls to be blocked in all directions at one time? That would seem highly unlikely.

I do not believe in "coincidences"....the odds of the aircraft experiencing a some what confusing but relatively benign engine problem then experiencing a serious flight control problem, although not impossible, seems very unlikely from real life experience and from a statistical view.

HeliComparator 24th February 2010 22:12

Yes, it seemed to me likely that there was some physical interaction between the anticipator and the cyclic pushrods, eg wiring harness trapped / caught, bits fallen off the anticipator onto the lower bellcrank etc, but as I said, in fact no evidence to support that.

HC

SASless 24th February 2010 23:50

I view this as a great learning tool.

There are lots of lessons to learned and applied to current operations.

I would think "outside" reviews of one's operations do not harm anyone's job security. The lack of an objective review of policies, practices, and the like, set folks up for the ultimate embarrassment when their hunky dory cozy little world gets turned upside down by events such as this one. That is when folks get the can tied to their tail.

Bristow has been known to hold a "Daddy Knows Best" attitude in the past. Thus this should not come as a big surprise to anyone that is familiar with the evolution of the organization. Every large operator falls prey to that at some point thus Bristow is no different than any other in that regard.

What is important is to move forward with improvements after taking a cold hard look at how business is getting done and look for the holes in the Cheese ahead of time rather than after the fact.

tistisnot 1st March 2010 02:08

P3 Bellows
 
Probably because we do not wish to inflict further pain? As SASless says - a good learning tool .....

But please, and I'll be shot down by many, for heavens sake:

Hanger or hangers may refer to:
  • Hanger, a woodland area on the side of a hill — road going through this woodland may be named 'Hanger Hill'
  • Clothes hanger, device in the shape of human shoulders or legs used to hang clothes on
  • Hanger steak, a tender cut of steak
  • Casing hanger, part of a wellhead assembly in oil drilling
  • Derailleur hanger, a slot in a bicycle frame where the derailleur bolt attaches to
  • Monkey hanger, a British term for people from Hartlepool, England
  • Hanger, part of a skateboard
  • Hanger (weapon), a sword similar to a cutlass, used by woodsmen and soldiers in 17th to 18th centuries
  • Hanger, or specky, a slang term for spectacular mark in Australian rules football
  • Hangers, American slang for large, pendulous breasts
  • Hanger (barbershop music), a long note sung by one voice in a barbershop music song
  • A hanger is a vertical cable or rod connecting the roadway of a suspension bridge to the bridge's main cable or arch
  • Hanger, a type of structural tie.
I think you mean Hangar

Yours irrationally irritated

jonnyloove 30th September 2012 09:19

G-JSAR
 
What ever did happen to G-Jasr in the end was she ever rebuild..?

cyclic 1st October 2012 10:05

It never happened, I don't know what you are talking about ;)


All times are GMT. The time now is 17:13.


Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.