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
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.

There are flight directors that will drive to a 30 degree pitch up?!?!?

Also, didn't 3407 intercept from the South, ie. left traffic? I don't remember from the ATC tapes, maybe someone out there can refresh my memory? Thx.

What a weird accident. Hope something good comes out of it all. Pretty depressing so far.

Q100.
 
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.

The two most accurate sentences I've read on FI in a very long time. Of course the first is a guess, but I think it is spot on.

We need to really circle the wagons and support the families of the crew.

And learn.

-JP
 
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.
Good point, but the problem gets people at both ends and in the middle too.
 
In reading the Q drivers explanation of how the AOA/Stall system is rescheduled in icing, the wing may not have actually aerodynamically stalled until it reached it's critical AOA during the abrupt pull-up maneuver.

There may not have actually been an aerodynamic stall when the pusher activated, since the pusher is biased by 20 knots as a function of being in icing conditions.

Put another way, with the 'icing switch' off, stall speed was shown to be computed at 90 kts or so.

. . .
Likely, as is typically the case, a combination. But it is clear the speed was allowed to decay to a very low value. After this, the abrupt pull-up sealed their fate at such a low altitude.

I agree with this scenario.

We'll know perhaps whether the crew was concerned about a tail stall from the CVR. They seemingly reacted to a perceived tail stall: extend flaps, the AP disconnects and they get shaker, then pusher. In a tail stall the nose drops, the remedy is to retract flaps and increase back pressure. Only thing is, they could've misinterpreted it. Stick shaker and pusher means WING STALL.

Fly the plane first, if the plane is still flying, don't mess with it. I got AP disconnect, shaker and pusher once with the boards out when new in the RJ on a visual. I had focused on descending after ALTS CAP to catch the GS, only a lower ALT hadn't been selected. I had increased thrust, but not enough to compensate for the drag from the flight spoilers. It took the jumpseater behind us to say 'spoilers' (yes this was humbling for me) before I clued in. But in that momemt before I got SA back I had increased thrust some, and done nothing to the pitch attitude.

Pilot error is sad, tragic, and unfortunately often a fact of life in aviation accidents. NBC didn't do regional pilots any favors tonight, explaining how long (short really) each had been employed by Colgan.
 
There are flight directors that will drive to a 30 degree pitch up?!?!?
That was my first thought.
Also, didn't 3407 intercept from the South, ie. left traffic? I don't remember from the ATC tapes, maybe someone out there can refresh my memory? Thx.
Yup, from the south. Last assigned hdg was 260 to join
 
I agree with this scenario.

We'll know perhaps whether the crew was concerned about a tail stall from the CVR. They seemingly reacted to a perceived tail stall: extend flaps, the AP disconnects and they get shaker, then pusher. In a tail stall the nose drops, the remedy is to retract flaps and increase back pressure. Only thing is, they could've misinterpreted it. Stick shaker and pusher means WING STALL.

Fly the plane first, if the plane is still flying, don't mess with it. I got AP disconnect, shaker and pusher once with the boards out when new in the RJ on a visual. I had focused on descending after ALTS CAP to catch the GS, only a lower ALT hadn't been selected. I had increased thrust, but not enough to compensate for the drag from the flight spoilers. It took the jumpseater behind us to say 'spoilers' (yes this was humbling for me) before I clued in. But in that momemt before I got SA back I had increased thrust some, and done nothing to the pitch attitude.

Pilot error is sad, tragic, and unfortunately often a fact of life in aviation accidents. NBC didn't do regional pilots any favors tonight, explaining how long (short really) each had been employed by Colgan.

Your candor about the brain-cramp is refreshing. We all need to work on this.
 
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.

We, as pilots, will make mistakes. But its the severity of the mistakes that we can improve on. I always tell my flying partners that there are 2 types of mistakes: 1) one that we talk and laugh about and 2) one that others talk and laugh about. Lets keep them between the two of us.
 
An operator of mid-sized turboprops had an interesting autopilot anomaly at a Michigan airport about a year or so ago.

Turned out to be the electronics playing tricks on the flight crew. I believe the actual flight control computer had a fault in it.

Maybe I'm just a little too crusty, but I feel that the automation has built a certain set of hazards into the system that we have yet to fully appreciate. And the automation seems to be expanding in new ways.

The biggest problem I have is that the box is often making many decisions that are not even documented in the manuals that pilots are issued.

There is often too much emphasis in 121 training on full reliance on automation. But think about TAWS. If you hear a terrain warning, you click off the AP and fly the escape maneuver. If you get a TCAS alert, you click off the AP and avoid the conflicting aircraft.

Why then, is it not safe to click off the AP in other instances where the pilot is behind the automation, or where the automation is behind the airplane?
 
Last edited:

Latest resources

Back
Top