Search

Notices
Regional Regional Airlines

ILS 23 in BUF

Thread Tools
 
Search this Thread
 
Old 02-20-2009 | 07:45 AM
  #41  
TPROP4ever's Avatar
Gets Weekends Off
 
Joined: Oct 2008
Posts: 1,154
Likes: 0
From: none ya...
Default

Originally Posted by DeltaPaySoon
I just did this approach and can state, without hesitation, that there is a major issue with the glide slope.

Approach had us turn to intercept the loc between the LOM (Klump) and the fix outside of the LOM (Trava). When we were approximately 2 miles north of course at 2300, and 3 miles from Trava, the GS was showing that we were above it. (First glaring issue)

As we were intercepting the loc, I watched the GS go from one dot low to full scale high in about 1/4 mile and about 1.5 to 2.5 from Klump.

If we would have had the approach mode set to capture the GS, the autopilot would have had a very significant nose up attitude to chase the GS.

Since I saw the notice to the SWAPA, we did the same thing and only armed the nav until the glideslope made sense.

We were in hard IFR with 30 xwinds and blowing snow and had to turn the autopilot off to handle the conditions.

BE CAREFUL WITH THIS APPROACH!!!
Nice description, and am I missing somthing here, or does any of this sound familiar? Once I again, I hope ( and Am sure) the NTSB is looking at this info also..and I refuse to jump to any conclusion, but I will say reading this thread has been interesting.
Reply
Old 02-20-2009 | 07:47 AM
  #42  
TPROP4ever's Avatar
Gets Weekends Off
 
Joined: Oct 2008
Posts: 1,154
Likes: 0
From: none ya...
Default

Originally Posted by The Juice
CNN just had "breaking news" about the ILS in BUF. I think this was the first time I have heard a report on 3407 where they did not blame Marvin and his actions.
Im willing to bet someone on APC works for CNN what do you think??? HMMMM
Reply
Old 02-20-2009 | 11:34 AM
  #43  
Gets Weekends Off
 
Joined: Sep 2005
Posts: 120
Likes: 0
From: AB F/O
Default

Originally Posted by DeltaPaySoon
I just did this approach and can state, without hesitation, that there is a major issue with the glide slope.

Approach had us turn to intercept the loc between the LOM (Klump) and the fix outside of the LOM (Trava). When we were approximately 2 miles north of course at 2300, and 3 miles from Trava, the GS was showing that we were above it. (First glaring issue)

As we were intercepting the loc, I watched the GS go from one dot low to full scale high in about 1/4 mile and about 1.5 to 2.5 from Klump.

If we would have had the approach mode set to capture the GS, the autopilot would have had a very significant nose up attitude to chase the GS.

Since I saw the notice to the SWAPA, we did the same thing and only armed the nav until the glideslope made sense.

We were in hard IFR with 30 xwinds and blowing snow and had to turn the autopilot off to handle the conditions.

BE CAREFUL WITH THIS APPROACH!!!
I saw this going into AVP recently as well. GS was captured and went full scale down then back up. Disconnected the autopilot right away but the flight director was going up and down at least 10 degrees each way.
Reply
Old 02-20-2009 | 12:13 PM
  #44  
New Hire
 
Joined: Feb 2009
Posts: 1
Likes: 0
From: Lear
Default

This ILS approach into BUF is not unsafe or unlike any other approach in the world. In fact many ILS approaches I've come across have similar notes associated with them. Whether or not there is a note warning of possible interference outside of a specific range, it all comes down to the one and only constant that is prevelent in every aspect of flying......Fly the plane. If the magic autopilot starts pitching up dramatically, the PF should disengage it immediately, not wait and try to figure out "What's this stupid thing doing now." Too many times in my experience, I have seen fellow crew members with their hands in their laps and in a total relaxed state just depending on the autopilot to do its magic. Maybe this tragic accident will remind us all to never get that relaxed and confident in the autopilot, and be ready with our hands on the controls ready to disconnect at a moments notice our trusty autopilot.... and one more thing don't leave the autopilot on in icing.

I'm not implying that either one of these issues is the cause of the BUF tradgedy, but it is a good time to remember to get back to the basics......fly the airplane.
Reply
Old 02-20-2009 | 03:20 PM
  #45  
KC10 FATboy's Avatar
Gets Weekends Off
 
Joined: Jun 2007
Posts: 4,218
Likes: 60
From: Legacy FO
Default

I wish the airline section of the forums were only for Airline Pilots. The hiring and additional forums could be open. You bet, the news media is lurking here. They've even quoted members here in their broadcasts and reports.

-Fatty
Reply
Old 02-20-2009 | 10:52 PM
  #46  
DeltaPaySoon's Avatar
Gets Weekends Off
 
Joined: Jul 2008
Posts: 366
Likes: 0
From: Stage Left
Default

Originally Posted by Learyear
This ILS approach into BUF is not unsafe or unlike any other approach in the world. In fact many ILS approaches I've come across have similar notes associated with them. Whether or not there is a note warning of possible interference outside of a specific range, it all comes down to the one and only constant that is prevelent in every aspect of flying......Fly the plane. If the magic autopilot starts pitching up dramatically, the PF should disengage it immediately, not wait and try to figure out "What's this stupid thing doing now." Too many times in my experience, I have seen fellow crew members with their hands in their laps and in a total relaxed state just depending on the autopilot to do its magic. Maybe this tragic accident will remind us all to never get that relaxed and confident in the autopilot, and be ready with our hands on the controls ready to disconnect at a moments notice our trusty autopilot.... and one more thing don't leave the autopilot on in icing.

I'm not implying that either one of these issues is the cause of the BUF tradgedy, but it is a good time to remember to get back to the basics......fly the airplane.
I agree with everything you said....except the first line. I found the glideslope issue extremely unsafe and extremely abnormal for flights in the US. My workload increased immensly once the PF disconnected the autopilot. We were in hard IFR. I've not, in 20 plus years of IFR flying, seen a glideslope have that much travel that close to the loc and in that short of distance.

Minor issues from time to time, yeah we've all seen those, this is not a minor or safe issue.
Reply
Old 02-20-2009 | 11:21 PM
  #47  
KC10 FATboy's Avatar
Gets Weekends Off
 
Joined: Jun 2007
Posts: 4,218
Likes: 60
From: Legacy FO
Default

I'm not calling anyone out here, but, did any of you guys who experienced these problems ever report it officially?

Nothing will get fixed if we don't complain about it.
Reply
Old 02-21-2009 | 09:14 AM
  #48  
Line Holder
 
Joined: Jan 2008
Posts: 53
Likes: 0
Default

Originally Posted by flynavyj
I've seen phantom localizers as well, and watched the autopilot capture and try to follow it, there are a couple airports that it's happened at, but i cant remember which ones. Also had a situation in MKE with a localizer bouncing moving from side to side, half scale deflection and immediately back the other way.
I had this happen while flying the ERJ135 for Eagle. We were being vectored for an ILS 22 at JFK and the autopilot suddenly thought it captured a localizer and began turning. We were about 80 degrees from the actual localizer when it turned. I turned the autopilot off and handflew the rest of the approach raw data. I didn't trust the AP/FD at all.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
igbyjet
Regional
62
02-19-2009 05:01 PM
Ryan274
Regional
401
02-13-2009 09:13 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Your Privacy Choices