dozzy...possibly the sun will explode.

possibly I will be elected POTUS

now look up the finger laps/joints and how they would SHOW a problem if there were one...

douglas used more rivets

@PA - The Airbus UAS procedure is posted in the AF447 threads. And here:
http://www.bea.aero/docspa/2009/f-cp...nexe.06.en.pdf

The aircraft will not spiral dive for some time if the trimmed pitch and power are OK, which at that point they were.

Hi - yes, I know. I did look things up as you requested and found a very interesting academic paper on the subject here:

http://xa.yimg.com/kq/groups/1451308...wift_Comet.pdf

Admittedly the equations go over my head, but the prose explains it well. It transpires that Douglas's approach on fatigue was very much informed by the information shared from the Comet 1 investigation.

Now - the problem in the Aloha case was not with the design so much as it was the way the aircraft was maintained by the airline (though the NTSB stated that the airline were not to know that their methods may be problematic). It was the disbonding, re-bonding and re-riveting performed as part of an overhaul that caused greater opportunity for corrosion and fatigue. In fact one of the passengers did see a small crack before she boarded, but did not speak up as she assumed it was known about.

Additionally, sometimes making things tough is not the way to do things - witness the MD-11 hard landings that sheared the spar at the gear attachment location.

The autopilot had to be disconnected on Apollo 11 to prevent a crash. Apollo 13 would have been a loss without pilots.

No autopilot today can even handle something as routine as mountain wave. That's just one of many examples. No autopilot today can get an airplane out of an unusual attitude reliably. They can however put you in one.

Drones are not pilotless, they are remotely flown and still crash a lot.

Airliners still on the drawing board are still based on the 2 pilot concept .

You guys thinking large commercial jets will be flying pilotless in 20 years are smoking the funny stuff.

To be fair, that was triggered because Buzz Aldrin (reasonably, though contrary to procedure) left the rendezvous radar on standby during the descent in the event of an emergency abort. What he didn't know was that leaving it on would steal cycles from the guidance computer in the early stages of descent. This resulted in the LEM ending up somewhat downrange of its original intended landing point.

That point aside, I completely agree.

one gust and you can be spiraling in short order...all planes want to spiral but it's is indeed. ususually a slow process if in trim in smooth air...the point is one has to handfly routinely in oorder to be better equipped to deal with more exotic flight conditions...

I'm not arguing that second point PA, I agree!

However - looking at the DFDR traces shows the yaw damper working overtime to successfully keep the aircraft upright during even the most extreme gyrations.

I'm not saying leave the controls alone entirely, just that the first point of order should be to see if the aircraft will remain relatively stable without encouragement - which in most cases it should!

but you get your hands in the flight controls and eyes on the instruments immediately...but in most cases there are no fast hands in a jet...on that point you are corrrect

Yes - as I said about controls - "cover them (meaning get your limbs in a ready position) and be prepared to use them". If you start making inputs without assessing the situation then you're more than likely to get it wrong and end up fighting yourself - as happened with AF447.

It`s (To borrow a USAF term) HOTAS Hands on stick and throttle no inputs necessary but hands on ...

@ 737er - Apollo
 

The Apollo missions were 40 years ago! The damage was most serious for the life support systems which would not have been fitted if the pilots were not installed! Other systems were there to get the humans home, again not required on an autonomous mission.

If I recall, a Lion Air Indonesia B737 went into a gradual spiral at night with devastating consequences. Seems the crew were having difficulties with one of the to IRS. in fact there were many reported snags on that IRS previously.

Again, from memory, the crew decided to trouble shoot and switched off one of the IRS and in turn this caused the automatic pilot to disconnect. Either the crew didn't realise the autopilot had disengaged or if they did, neither pilot was allotted the task of flying the aircraft manually.

While one pilot read from the QRH about IRS non-normal, the other pilot selected the perceived offending IRS to the Attitude mode. This blanked out the PFD on one side. Meanwhile the 737 wandered around the sky at night with no one watching the flight instruments. It eventually went into a gentle spiral which got worse. By the time someone exclaimed WTF, the aircraft was in an unusual attitude.

The captain didn't have a clue how to recover from a UA and instead pulled back hard on the control column while in the spiral. It doesn't take too much imagination to guess why the aircraft eventually broke up in mid-air.

And therefore the Lion Air crew went in...

interesting about lion air

the solution is obvious

the autopilot controls the plane at all times unless you continuously push a button on the yoke, then you fly it , fly it like the old days with no limiters.

and if the button shorts out, it turns the autopilot off and announces it as loud as a san francisco fog horn.

sound familiar? mooneys used this idea for their wing leveler

Quote:
Are you saying that automation contributed to the Asiana 214 crash??? It sure looks like an automated landing would have prevented the crash.

Quite the reverse: the automatics may have been masking a threat in the system. For that particular approach the outcome may have been better if a higher level of automation had been used but that does not address the fact that there was a crew (and still undoubtedly are still crews) out there who given the wrong set of circumstances could not (and cannot) safely guide a serviceable aircraft to a runway in benign meteorological conditions.

The reality is that airlines are best served by having well rounded individuals in the flight deck and a key part of the necessary skill set is piloting skill. Piloting skill is not acquired and maintained by watching screens with one's hands sitting idly on one's knees.

speedrestriction: :D:D:D:D:D

Very succinct, very logical analysis of the root cause.
Matter of fact, the problem is greatly similar to automation in broadcast radio. When unattended, the system chirps merrily away sequencing music, ads, PSAs and other announcements untouched by human hands.

But when I (as a volunteer engineer/producer) take over manually, the computer is put on HOLD, and manual ops are just the same (almost) as during my student days 50 years ago. And executing a fast-paced audio sequence is not so emotionally different from landing in a crosswind. In a taildragger. :)

Pugilistic Animus
Airbus FBW does not get into spiral even with one engine fail and TOGA on live engine because the computers try to hold the position. Any tendency to spiral is prevented by computers by applying rudder upto yaw damper's authority and bank is prevented by applying opposite aileron and spoilers. Since yaw dampers cannot apply the required amount of rudder the aircraft does a skidding turn with MAX 5 to 7 degrees of bank. Even in Unreliable speed the aircraft is in alternate law so behaves the same way except it can be stalled or get into overspeed. You must disconnect AP, ATHR and switch off FDs and the a/c will maintain its pitch and bank.

vilas thankyou for the airbus AP information..very interesting....my knowledge of Airbus systems is nonexistant:)

OK465
I was talking about A320 behaviour OEI in normal law and AEO in unreliable speed in alternate law.

Hands off, in ALT2, roll Direct, A330 with one engine TOGA and one engine failed, the aircraft will spiral (somewhere in the 70-80 degree bank range). It will not however roll over on its back.

What happened to the A330?? from Toulouse on take off being flown by test-pilots that crashed. Was it not something like this? I never did see the final report.

No - that one *was* automation and interface related if I recall correctly. The mode set in the FCU panel was Altitude acquire, which disabled the *autopilot* pitch protection - the FBW alpha protection was unable to correct in time given the incorrect pitch trim, extreme aft CG and power plus very low altitude. They changed the interface soon afterwards.

Airbus Industrie Flight 129 - Wikipedia, the free encyclopedia

Well yes, no argument there - but the original query was talking about AF447, which had no such asymmetric thrust condition.

I'm not sure at what point thrust asymmetry entered the discussion, and in any case you'd want to determine the direction of the thrust asymmetry before making corrective inputs no matter what kind of aircraft you were flying, would you not?