37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1339182 |
Time | |
Date | 201603 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | IAH.Airport |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Experience | Flight Crew Last 90 Days 200 Flight Crew Type 1615 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
We were set up for 8L; visual conditions. Just before turning base leg we were told to expect 8R. We set up the radios and FMS; ATC vectored us to about 2 miles outside maton (FAF) we descended to 2;000 feet; which is the crossing altitude at maton. We were cleared for the visual approach to 8R; it was in sight. Everything was normal; the approach mode was armed. Because we were intercepting both the localizer and GS at the same time very close to maton; we didn't expect to see the GS signal immediately. At maton the airplane pitched up rather dramatically to around 15 degrees and the autothrottles pushed up the power and pulled it back; it was very confused. I clicked off the autopilot immediately and pushed the nose over; and then remembered hearing ATC tell someone else much earlier; when we were still planning for 8L; that the GS was out of service on 8R. We recovered the situation but in the process gained almost 500 feet at maton. Whether it was the right thing to do or not we recovered it and landed. We were certainly configured per the stabilized approach criteria; but our speed was a bit fast; maybe 15 kts fast most of the way down. The landing was in the touchdown zone. So we may not have met stabilized approach criteria; and we definitely gained close to 500 feet coming over the FAF. It is; of course; my job to know that the GS was out of service (OTS); but the runway change happened fast. Either way; I've never seen an autopilot behave that way to a lack of GS signal. I did not write it up as I really wasn't sure what to write up; it was just responding to erroneous signals. I rather felt this was my fault as I never should have engaged the GS; but this is our standard procedure for any approach with an ILS; visual or not. It isn't necessarily the responsibility of ATC to remind every single pilot that the GS is OTS either.
Original NASA ASRS Text
Title: Air carrier Captain reported a late runway change resulted in an unstabilized approach to a landing.
Narrative: We were set up for 8L; visual conditions. Just before turning base leg we were told to expect 8R. We set up the radios and FMS; ATC vectored us to about 2 miles outside MATON (FAF) we descended to 2;000 feet; which is the crossing altitude at MATON. We were cleared for the visual approach to 8R; it was in sight. Everything was normal; the approach mode was armed. Because we were intercepting both the LOC and GS at the same time very close to MATON; we didn't expect to see the GS signal immediately. At MATON the airplane pitched up rather dramatically to around 15 degrees and the autothrottles pushed up the power and pulled it back; it was very confused. I clicked off the autopilot immediately and pushed the nose over; and then remembered hearing ATC tell someone else much earlier; when we were still planning for 8L; that the GS was out of service on 8R. We recovered the situation but in the process gained almost 500 feet at MATON. Whether it was the right thing to do or not we recovered it and landed. We were certainly configured per the stabilized approach criteria; but our speed was a bit fast; maybe 15 kts fast most of the way down. The landing was in the touchdown zone. So we may not have met stabilized approach criteria; and we definitely gained close to 500 feet coming over the FAF. It is; of course; my job to know that the GS was Out of Service (OTS); but the runway change happened fast. Either way; I've never seen an autopilot behave that way to a lack of GS signal. I did not write it up as I really wasn't sure WHAT to write up; it was just responding to erroneous signals. I rather felt this was my fault as I never should have engaged the GS; but this is our standard procedure for any approach with an ILS; visual or not. It isn't necessarily the responsibility of ATC to remind every single pilot that the GS is OTS either.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.