 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
CRJ200 first officer reported receiving a below glide slope warning on approach to atl.
| Attributes | |
| ACN | 1542395 |
| Time | |
| Date | 201805 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ATL.Airport |
| State Reference | GA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Unstabilized Approach |
Narrative:
During a visual approach to 9R atl ATC kept us a little fast and we began to configure a little late while attempting to configure the aircraft and switch from approach to tower. I was heads down in the cockpit for a while; the captain was hand flying. The captain called check spoilers flaps 45 and I noticed the spoilers were still out so I retracted them. About that time I heard the glide slope warning as we had both switched to green needles a while back for guidance. I set the flaps to 45 and looked up at our altitude and saw that it was around 1700-1800 ft and the captain was correcting for the warning. It took me a few moments to realize that the field elevation was 1020 ft and that we were in fact around 750 ft hat (height above threshold) and by that time we were stabilized again so I did not call for a go around.the cause of the event was waiting a little too long to configure the aircraft and getting a high workload condition late in the approach and my failure to split my attention properly between my monitoring duties and configuring the aircraft. In the future I should make sure to include altitude in my scan instead of just airspeed for configuring the aircraft as well as recognized that this condition was leaving us in the red and called for a go around.
Original NASA ASRS Text
Title: CRJ200 First Officer reported receiving a below glide slope warning on approach to ATL.
Narrative: During a visual approach to 9R ATL ATC kept us a little fast and we began to configure a little late while attempting to configure the aircraft and switch from Approach to Tower. I was heads down in the cockpit for a while; the Captain was hand flying. The Captain called check spoilers flaps 45 and I noticed the spoilers were still out so I retracted them. About that time I heard the glide slope warning as we had both switched to green needles a while back for guidance. I set the flaps to 45 and looked up at our altitude and saw that it was around 1700-1800 ft and the Captain was correcting for the warning. It took me a few moments to realize that the field elevation was 1020 ft and that we were in fact around 750 ft HAT (Height Above Threshold) and by that time we were stabilized again so I did not call for a go around.The cause of the event was waiting a little too long to configure the aircraft and getting a high workload condition late in the approach and my failure to split my attention properly between my monitoring duties and configuring the aircraft. In the future I should make sure to include altitude in my scan instead of just airspeed for configuring the aircraft as well as recognized that this condition was leaving us in the red and called for a go around.
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.