37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1655406 |
Time | |
Date | 201906 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SYR.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Medium Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Weather / Turbulence |
Narrative:
Gusty winds 220@14g24 with the first officer (first officer) flying the approach into syr runway 28. He took the autopilot off about 200 feet and started to get low. He said he was correcting and I saw him add power and correct pitch. We must have had a gust drop out from under us and he couldn't correct fast enough and he got a dot low on glide slope. We got the GPWS 'glideslope' aural warning and since we were less than 200 feet and had the runway made I opted to continue rather than risk a go around so low to the ground. I felt it was the safer option in this particular scenario; although I know it is not always the best course of action. We both already knew and were correcting; and then the GPWS made the aural warning. First officer got low on glideslope within 200 feet of touchdown; probably due to gusty winds in the area. Corrected pitch and power to continue the approach. Increase target speed with gusty winds.
Original NASA ASRS Text
Title: Air Carrier Captain reported failure to go-around on unstabilized approach due to gusty conditions; fatigue; and complacency.
Narrative: Gusty winds 220@14G24 with the FO (First Officer) flying the approach into SYR RWY 28. He took the autopilot off about 200 feet and started to get low. He said he was correcting and I saw him add power and correct pitch. We must have had a gust drop out from under us and he couldn't correct fast enough and he got a dot low on glide slope. We got the GPWS 'glideslope' aural warning and since we were less than 200 feet and had the runway made I opted to continue rather than risk a go around so low to the ground. I felt it was the safer option in this particular scenario; although I know it is not always the best course of action. We both already knew and were correcting; and then the GPWS made the aural warning. FO got low on glideslope within 200 feet of touchdown; probably due to gusty winds in the area. Corrected pitch and power to continue the approach. Increase target speed with gusty winds.
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.