37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1330055 |
Time | |
Date | 201602 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | DAL.Airport |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach Initial Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Positional / Directional Sensing |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 142 Flight Crew Type 12000 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Inflight Event / Encounter CFTT / CFIT |
Narrative:
The first officer was flying a visual approach to 31R at dal. He had the autopilot engaged with approach mode selected. The localizer and glideslope were both captured and the aircraft was approaching target speed and final configuration. As we were approaching one of the buildings east of downtown; the glideslope began to fluctuate. The aircraft began to pitch up and down to regain the glideslope. As it pitched down; we received a caution obstacle alert. The first officer immediately disconnected the autopilot and corrected the flight path. We never received a pull up alert. We realized the glideslope was getting some interference and the first officer flew the aircraft visually without incident. The building was in sight the entire time; but I believe when the airplane began to pitch for the erratic glideslope it sensed a fast closure to the obstacle. After landing; I realized we should have gone around for the caution because it was dark. Since I didn't hear pull up; we had the obstacle in sight and the caution went away immediately we decided to land. However; after reviewing our policy I realized at night with a caution; it requires a go-around and that's exactly what we should have done. The glideslope anomalies for both 31L and 31R are nothing new; and I should have reminded the first officer about them so he could have planned accordingly.
Original NASA ASRS Text
Title: Air carrier flight crew experienced unstable glideslope on short final.
Narrative: The First Officer was flying a visual approach to 31R at DAL. He had the autopilot engaged with approach mode selected. The Localizer and glideslope were both captured and the aircraft was approaching target speed and final configuration. As we were approaching one of the buildings east of downtown; the glideslope began to fluctuate. The aircraft began to pitch up and down to regain the glideslope. As it pitched down; we received a Caution Obstacle Alert. The First Officer immediately disconnected the autopilot and corrected the flight path. We never received a Pull Up Alert. We realized the glideslope was getting some interference and the First Officer flew the aircraft visually without incident. The building was in sight the entire time; but I believe when the airplane began to pitch for the erratic glideslope it sensed a fast closure to the obstacle. After landing; I realized we should have gone around for the caution because it was dark. Since I didn't hear Pull Up; we had the obstacle in sight and the caution went away immediately we decided to land. However; after reviewing our policy I realized at night with a caution; it requires a go-around and that's exactly what we should have done. The glideslope anomalies for both 31L and 31R are nothing new; and I should have reminded the First Officer about them so he could have planned accordingly.
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.