![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
![]()
PS2727 wrote:
Could someone refresh my memory.... what is the definition of maneuvering speed again? Design manouvering speed applies to pitch changes. |
#12
|
|||
|
|||
![]()
Before or after the loss of this aircraft?
PS2727 wrote: Could someone refresh my memory.... what is the definition of maneuvering speed again? |
#13
|
|||
|
|||
![]()
"Corky Scott" wrote in message
... It was just a news blurb this morning on the local TV news, but they claimed that investigators now blame the loss of the Air Bus 300's tail on the improper use of the rudder by the co-pilot. If true (that the co-pilot is actually being blamed), I find that difficult to believe. As Ron says, if you want to know what the NTSB says, you need to read their report. The news media often corrupts matter of fact into alarmist finger-pointing. The truth is that, when there's an aircraft accident, the NTSB almost always winds up blaming the pilot in their report. They will often assign additional blame elsewhere, but the truth is that aircraft failures rarely occur absent pilot input, and so pilot input winds up part of the report. For example, if an airplane crashes due to an engine failure caused by a manufacturing defect or maintenance error, followed by poor engine-out landing, the pilot will be blamed for the poor engine-out landing. Another crash might be a result of the aircraft stalling and spinning to to the ground. The accident report will often simply say that the pilot lost control of the airplane, without offering insight into WHY the pilot lost control. If you recall the Alaska Airlines accident in which the elevator trim screw failed, I would be willing to bet that somewhere in the NTSB report, they fault the pilots for not landing at the first sign of trouble. Which is not to say that the maintenance practices involved weren't the primary cause. (I would have checked the report before posting this, except the NTSB web site is *really* slow today...possibly related to the Airbus accident report having just been released; I've been waiting 15 minutes already, have no idea when my query will come back, and figure there's at least even odds it will simply time out with an error ![]() The NTSB simply reports whatever errors they feel they've found. In the Airbus crash, my understanding is that it's reasonably well-established that the pilot DID use a control input that led to the failure of the rudder, by exceeding the design standards for that control. There may be a host of other reasons why the pilot did so (I am especially intrigued by the point that Airbus claims that their fly-by-wire system is supposed to protect against such event), but the fact remains that the pilot is who made the control input that ultimately caused the accident. There is nothing fundamentally wrong with the NTSB stating that. So, seems that what we have here is a clear case of the NTSB reporting facts, with the media filtering the report to suit whatever agenda they have at the moment. [...] Either way, I find it difficult to blame the co-pilot for reacting in what is likely a normal pilot response to turbulence. Surely all airliners aren't so tempermental when it comes to rudder input are they? For what it's worth, the certification standards do not preclude all airliners being so temperamental. FAR 25.351 requires only that a single full-scale deflection be possible, followed by returning the rudder to center, and an immediate full-scale deflection in the other direction may well cause failure of the aircraft. Whether any airliners exceed this design standard, I don't know, but it wouldn't surprise me to find that most don't. Pete |
#14
|
|||
|
|||
![]() In deference to the NTSB, it has been mentioned here before that, left to their own devices, they would not have initiated the "probable cause" reporting that the news media and most of the rest of the world zooms in on, but would have preferred to keep their report factual. This said, the "C" and "F" shorthand we have become accustomed to ("C" for causal and "F" for factor) appear to favor a superficial reading and attribution of blame. I agree we find, at times, and almost surreal ability to put the blame on the shoulders of the flight crew, and this latest incident is an example. After all, one of the oft-cited criteria for assigning crew responsibility (or "pilot error"), is the determination of whether the crew acted in accordance with their training. It is after all unreasonable to expect the crew to become test pilots and invent hitherto unexplored techniques in dealing with an emergency, or to consider them at fault for not having done so. Yet, from the information we have, this would appear to be the standard being applied to this flight crew. Clearly, nothing in their basic training, advanced training or type certification indicated they could not use full rudder deflection for airplane control within maneuvering speed. If we accept the arguments submitted by Airbus, who claim they tried for years to improve the training program at American to reflect this reality, this further vindicates the flight crew, as we understand that this training was never implemented. In our world today, had the unfortunate first officer had the miraculous chance to survive the accident, having been found at fault, he would certainly be fired, and could even face involuntary manslaughter charges - a criminal. This smacks of scapegoating, and one is hard pressed not to see a political expedient at work here. G Faris |
#15
|
|||
|
|||
![]()
Stefan wrote:
PS2727 wrote: Could someone refresh my memory.... what is the definition of maneuvering speed again? That you can fully deflect any control surface without structural damage. However, this does *not* necessairily imply that you can waggle from one extrem to the other! Actually, you can't do so with many airliners. I recently read an article on this subject; I just cannot recall where. It's not just "waggle from one extreme to another" that's not covered by Va, but also multiple inputs (ie. aeleron and rudder) in directions which cause opposing (or concurring?) forces. Anyone recall this article? Otherwise, I'll be digging through some magazines tonight. - Andrew |
#16
|
|||
|
|||
![]()
Peter Duniho wrote:
The truth is that, when there's an aircraft accident, the NTSB almost always winds up blaming the pilot in their report. They will often assign additional blame elsewhere, but the truth is that aircraft failures rarely occur absent pilot input, and so pilot input winds up part of the report. In this particular case, though, it appears that the [co]pilot was doing as he was trained. If he was trained to do the wrong thing, it was the training at fault and not the pilot. As I read the article, while it does say that the pilot's actions caused the crash, it does not appear to afix blame to the pilot. - Andrew |
#17
|
|||
|
|||
![]() |
#18
|
|||
|
|||
![]() "Andrew Gideon" wrote in message online.com... As I read the article, while it does say that the pilot's actions caused the crash, it does not appear to afix blame to the pilot. Exactly. In Canada the TSB tries to make it very clear that they determine the cause, the do not assign blame... quote from their mandate: it is not the function of the Board to assign fault or determine civil or criminal liability. unquote... I thought it was the same with the NTSB. (Their site does not respond today, so I cannot refresh my memory on their mandate...) It seems pretty clear that the "Cause" was the excessive waggling of rudder by the pilot-flying. "Blame" will be debated for a long time after the official report. |
#19
|
|||
|
|||
![]()
On Tue, 26 Oct 2004 11:15:09 -0400, Ron Natalie
wrote: G Farris wrote: Though it may not be fair to the NTSB, it is sometimes hard not to conclude that placing the blame on a pilot, who is no longer here to defend himself, is far less "costly" than implicating an airline or major airfarme manufacturer. The NTSB has no interest in what is "costly" or not. It frequently makes recommendations that the FAA and the airlines decide not to heed for "cost" reasons. Obviously we haven't seen the print of the "fimal" report, but I suspect that the results will be improper control input by the pilot flying with some blame on the training by the manufacturer or airline on how to deal with wake turbulance encounters. I recall some question concerning a weakness in the design of the rudder itself, in that the supports to the composite structure were too few. Not too long after the accident, I saw it was explained on TV that the manufacturer should have distributed the load over more points for the sake of the composite material. The known and understood weakness of composites, compared to metals, is their lesser ability to handle bearing stress. So Airbus should've known better, presumably. I think I heard this on CNN, and their expert (probably Boeing, but I don't recall) seemed to know what he was talking about; even supplying drawings of the rudder. From current discussion, I assume this is not considered valid anymore, and so I may not be valid in bringing it up. But I thought the problem close to being solved way back when. If the control inputs are controlled, as I believe Airbus is, then the pilot cannot be blamed for over-controlling; unless the manufacturer pointedly states not to do that. So I'm thinking Airbus is really getting a free one from the NTSB on this. Or the report we are reading is premature. Typical structure failure is from stabilizer abuse, not the rudder, I thought. But now do I need to be concerned with what I do with my feet? --Mike |
#20
|
|||
|
|||
![]()
"Andrew Gideon" wrote in message
online.com... In this particular case, though, it appears that the [co]pilot was doing as he was trained. If he was trained to do the wrong thing, it was the training at fault and not the pilot. IMHO, that's an oversimplification. For example, some Private pilots are trained to fly the VASI glideslope, while others are trained to fly a steeper, power-off gliding approach. A pilot flying the VASI glideslope who experiences a power failure will wind up crashing short of the airport, but that doesn't mean that the practice of training pilots to fly the VASI glideslope is necessarily wrong. Each method has positive and negative aspects, and it's up to the pilot to make a decision regarding how to apply their training. As far as this particular accident goes, are you saying it's the case that the pilot training specifically *instructed* the pilot to make large back and forth rudder inputs? I haven't seen any documentation of that claim. What I have seen are statements that the training neglected to mention that multiple full deflection rudder inputs were bad; that's an entirely different claim. After all, flying the airplane into a mountainside is also bad, but I would be surprised if pilot training spends much time covering that topic. One could argue that pilots ought to be familiar with the certification rules and understand that the rules only grant the pilot a single full deflection of the rudder in one direction, after which the rudder can be returned only to the neutral position. Regardless of training. Now, that's a debate for another time, and I don't even feel that it's a strictly "either/or" debate anyway. But my point is that ultimately it was the pilot who over-controlled the aircraft, contrary to the certification rules that govern the design of the aircraft. To that extent, it is patently obvious that the pilot shares at least some of the blame. Beyond all that, it is still factually true that the pilot's control inputs are what *caused* the accident. My original point is that the NTSB will state a fact like this, and the media will misinterpret to mean that the NTSB is assigning blame or fault to the pilot. That's simply not the case. The pilot can still be the cause of an accident without being to blame, either partially or wholely. My use of the word "blame" obviously distracted from what I was really trying to say. As I read the article, while it does say that the pilot's actions caused the crash, it does not appear to afix blame to the pilot. Which article? This thread started with a "news blurb" Corky wrote about. We were not afforded the opportunity to review the media report Corky wrote about. If you mean the article that was posted here, that may or may not be relevant to Corky's post. In any case, the article to which you refer seems to more accurately convey the NTSB's likely position (which we'll know once the report is actually available). Pete |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
AOPA Stall/Spin Study -- Stowell's Review (8,000 words) | Rich Stowell | Aerobatics | 28 | January 2nd 09 02:26 PM |
Dover short pilots since vaccine order | Roman Bystrianyk | Naval Aviation | 0 | December 29th 04 12:47 AM |
[OT] USA - TSA Obstructing Armed Pilots? | No Spam! | Military Aviation | 120 | January 27th 04 10:19 AM |
[OT] USA - TSA Obstructing Armed Pilots? | No Spam! | General Aviation | 3 | December 23rd 03 08:53 PM |
AOPA Stall/Spin Study -- Stowell's Review (8,000 words) | Rich Stowell | Piloting | 25 | September 11th 03 01:27 PM |