Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Not so good news about flight 3407

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
I was under the impression that the stall warning did not activate and the autopilot did not disconnect until the aircraft pitched up rapidly.

I'll have to go look at the report, but I believe the NTSB reported the AP was on until the stick shaker activated. A Q driver indicated this is system design.

Oddly enough, with all the press-releases the NTSB has been putting out in the media, they haven't bothered to even publish the preliminary report of the factual data yet.
 
Ok, that makes sense-except if their actual stall speed was down around 100kts and the AOA sensor got adjusted to go off at closer to 120kts how did the wing actually stall?
If the stall speed was 90 and they saw 2 g's in a pull up, the stall speed jumps to 127 on a clean wing. SInce the flaps were in transit and the airspeed was slowing rapidly with the gear and flap extension, that was surely met.
 
They are leaking this out slowly so that when it fully comes out it is not a bomb shell.

FWIW, it could be any of us, and if you think you are above it, you have not been aviation long enough.


I understand what you meant, but your statement should read:

......and if you think you are above it, you have been in aviation too long already.
 
FWIW, it could be any of us, and if you think you are above it, you have not been aviation long enough.

My briefings incorporate your sentiments exactly. I am just as prone as the next guy to screw something up, so I expect you to speak up if you see something unusual.
 
Indicated airspeed (IAS) is the airspeed read directly from the airspeed indicator on an aircraft, driven by the pitot-static system.

Calibrated airspeed (CAS) is the speed shown by a conventional airspeed indicator after correction for instrument error and position error.

Your J3 may read indicated airspeed. Modern airplanes read calibrated airspeed no matter what the indicator. Its part of the flight testing. You can check Part 25 and Part 23.

Uh, last time I checked, an air data computer driven airspeed indicator is not "conventional".

Manufactured in 2007 or 1927, you can't get CAS from a "conventional" airspeed indicator unless it's fed through a correction algorithm first. Only a computer can do that.

Your Wikipedia semantics are suspect. Try again.
 
Last edited:
I was under the impression that the stall warning did not activate and the autopilot did not disconnect until the aircraft pitched up rapidly.

I dont think any of us know exactly what happened and in what order, but I do think...

...that the Q400 is a safe plane.
...fatigue was not a factor.
...and sadly, Pilot Error will be the final cause.
 
It will come out that sterile cockpit, or rather lack of, was a large factor.

Impossible to say fatigue not a factor. Rebecca commuted in the night before on Fed ex.

I am really hoping for some twist to explain how a simple stall recovery went wrong.
 
...and sadly, Pilot Error will be the final cause.

It is sad that pilot error is even still allowed to be labeled as the direct cause of an accident. It is well established that humans will always err, but our aviation system has evolved to a state of being able to trap most errors. The only way to prevent further accidents is to explore why the system failed to trap the error. This cannot be meaningfully done by simply closing the case with "pilot error" yet again.
 
Anyone hearing about the latest warning about possible glideslope problems at BUF? Some talk on PPRUNE about it.
 
Safety Alert 2009-1
BUF ILS Hazard


Hazard to ILS to runway 23 in BUF
SWAPA Pilots,

There is a potentially significant hazard concerning the ILS to runway 23 in BUF.

Information has been received indicating it is possible to obtain a significant nose pitch up, in some cases as much as 30 degrees, if the glide slope is allowed to capture before established on centerline. Pilots who are preparing to configure and land have the potential to experience abrupt pitch up, slow airspeed, and approach to stall if conditions present themselves in a certain manner.

This effect is the result of an earthen obstruction close enough to the ILS to affect the integrity of the glide slope signal. This has resulted in the issuance of an advisory given on ATIS which states that "the ILS Glide Slope for runway 23 is unusable beyond 5 degrees right of course."
When attempting to intercept the runway 23 ILS from right traffic, the ILS glide slope indication may read full deflection down. Just prior to intercept it may then move up in such as manner as to enable approach mode to capture in such a way as to result in a nose up pitch and loss of airspeed.

Southwest Airlines has issued a notice reading: "Until further notice, when executing the KBUF ILS/LOC Runway 23, DO NOT select Approach Mode until established on the localizer inbound."
This issue is being addressed on several levels in an attempt to address procedures, facilities, and communication regarding this matter. If you experience any issues related to this, please file an ASAP form and or call SWAPA Safety at SWAPA toll free.

This could put a whole new slant to what happened.
 

Latest posts

Latest resources

Back
Top