New FACTS from NTSB on Colgan 3407
#192
Do you not fly that much? In my logbook, I break down my landings to ILS, LOC, VOR, NDB, VISUAL, PRM ILS, CATII, CATIII.
On my last rotation, I flew LGA-SRW-BOS-ATL-BNA-ATL-BWI-CVG-SRW-LGA. I flew 1 PRM ILS, 3 ILS, and 3 Visuals. The CA had 1 Visual and 1 ILS.
I'm sure this varies with the seasons and location, but, I have no problem staying proficient. Also, making sure you can use the automation for approaches is something you don't want to forget how to do. As an examiner, I've seen many folks who could fly the ILS like crazy ... but choked when it came to telling George what to do.
#193
Moderator
Joined APC: Oct 2006
Position: B757/767
Posts: 13,088
#194
Gets Weekends Off
Joined APC: Aug 2007
Position: Satan's Camaro
Posts: 397
I personally have seen the dangers of an erratic glideslope. The north runway's glideslope going into KAVL is erratic. It has been reported on numerous ASAP reports. In solid IMC, the glideslope immediatly shot way down. The autopilot suddenly pitched down to follow it. Then the slope shot back up, and the airplane pitched up to follow it, causing a rapid decrease in airspeed. I managed to firewall the power just in time to avoid a stickshaker. At that time, I had to hand fly the rest of the approach and try to stay in the middle of the dancing glideslope. Not a very safe situation. Had i not been paying attention, it could have had a drastic outcome.
#195
Um, why the hell did you continue the approach? You have no idea if the "middle" that you're flying is the actual glideslope, or simply the average of the occilations, which may or may not be anywhere near the actual glideslope. The glideslope going "way down" then "shooting back up" resulting in a "rapid decrease in airspeed" almost resulting in the stickshaker in "solid IMC" requires a go-around, not trying to "to stay in the middle of the dancing glideslope". An ILS is a precision approach, not something thatyou guestimate where the glideslope is. You might end up only 100 feet high when your break out, or you might end up 100 feet low. Either your story doesn't add up, or you're a dangerously unsafe pilot.
#196
Gets Weekends Off
Joined APC: Aug 2007
Position: Satan's Camaro
Posts: 397
You weren't there, so you don't know all the circumstances. What you don't know is that the weather we encountered wasn't forecast, we didn't have enough fuel for an alternate, plus our aircraft has other means of backing up the ILS. So until you understand all the facts, please keep your criticism to yourself. Save it for your students in your Chickenhawk.
Ad hominem attacks against me aren't going to keep me awake at night. A CRJ crashing after following erroneous G/S information and stalling out will. It might turn out just fine, the way it did that time for you, or it might turn out with you being a smoking hole, which is almost certainly what has happened for other people. I tend not to backseat fly, because you're correct when you say that you never know all the factors, but looking at your situation, you shouldn't have continued that approach unless you had already declared an emergency and had no other options. And if you did declare an emergency, you should have noted that in your story.
#197
You weren't there, so you don't know all the circumstances. What you don't know is that the weather we encountered wasn't forecast, we didn't have enough fuel for an alternate, plus our aircraft has other means of backing up the ILS. So until you understand all the facts, please keep your criticism to yourself. Save it for your students in your Chickenhawk.
You're asking for criticism when you describe an approach which clearly should have been broken off, yet which you continued. AVL is no place to be guestimating the GS. If the weather was unforecast, then it was likely not that widespread, and if you didnt have enough gas for an alternate, then starting the approach in the first place wasnt a a great move. GSP has 2+ miles of very inviting pavement about 15 minutes south of AVL, CLT isnt much further to the east, and TYS is about the same to the west. Starting an ILS knowing that you dont have fuel for an alternate if things dont go well shows a lack of planning well before the glideslope problems...
#198
The pitch up was caused by the auto pilot chasing the glideslope (which it is programmed to do). I was vigilant, therefore, I remedied the issue prior to a stall occuring. The answer was to disengage the autopilot, hence, the airplane would no longer chase the slope. Once the autopilot was disengaged and aircraft stability restored, the glideslope became stable as well. Again, you were not there. Go read the ASAP report if you desire more details.
Nevertheless, before all the Monday-Morning Captains decided to critique the story, the point of the story is:
Do not become complacent with the autopilot. It does exactly what it is programmed to do; and in some cases, it can cause big problems. It is possible that this is what could have happened to the Colgan flight.
Nevertheless, before all the Monday-Morning Captains decided to critique the story, the point of the story is:
Do not become complacent with the autopilot. It does exactly what it is programmed to do; and in some cases, it can cause big problems. It is possible that this is what could have happened to the Colgan flight.
#199
Gets Weekends Off
Joined APC: Aug 2007
Position: Satan's Camaro
Posts: 397
The pitch up was caused by the auto pilot chasing the glideslope (which it is programmed to do). I was vigilant, therefore, I remedied the issue prior to a stall occuring. The answer was to disengage the autopilot, hence, the airplane would no longer chase the slope. Once the autopilot was disengaged and aircraft stability restored, the glideslope became stable as well. Again, you were not there. Go read the ASAP report if you desire more details.
Originally Posted by texaspilot76
At that time, I had to hand fly the rest of the approach and try to stay in the middle of the dancing glideslope. Not a very safe situation.
Like it or not, it's this kind of get-there-itis that results in incidents. Anyways, kudos on being vigilant about the autopilot, no kudos for continuing the approach.
#200
Moderator
Joined APC: Oct 2006
Position: B757/767
Posts: 13,088
The pitch up was caused by the auto pilot chasing the glideslope (which it is programmed to do). I was vigilant, therefore, I remedied the issue prior to a stall occuring. The answer was to disengage the autopilot, hence, the airplane would no longer chase the slope. Once the autopilot was disengaged and aircraft stability restored, the glideslope became stable as well. Again, you were not there. Go read the ASAP report if you desire more details.
Nevertheless, before all the Monday-Morning Captains decided to critique the story, the point of the story is:
Do not become complacent with the autopilot. It does exactly what it is programmed to do; and in some cases, it can cause big problems. It is possible that this is what could have happened to the Colgan flight.
Nevertheless, before all the Monday-Morning Captains decided to critique the story, the point of the story is:
Do not become complacent with the autopilot. It does exactly what it is programmed to do; and in some cases, it can cause big problems. It is possible that this is what could have happened to the Colgan flight.
Perhaps you should know that one should also not become complacent with the automation. Is it in your company's procedures to check the FMS database before every flight? Are you certain that the database is up to date EVERY time you go fly? Is it really safe to rely on that as your SOLE GS indication? You might have a hard time explaining that one to the NTSB and FAA.
Also, reading through your first post you did not mention anything about the glidslope becoming stable. I also don't believe this investigation is closed yet so perhaps you should follow your own advice, and not arm chair quarter back until you have all the facts.
Thread
Thread Starter
Forum
Replies
Last Post