 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Crj-900 captain reported an unstable approach and go-around resulting from other errors in the cockpit.
| Attributes | |
| ACN | 1655876 |
| Time | |
| Date | 201906 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | CLT.Airport |
| State Reference | NC |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Regional Jet 900 (CRJ900) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Unstabilized Approach |
Narrative:
During the descent checklist; I mistakenly thought I had set the landing data. Once we were cleared for the approach I realized this was not the case. To make sure we had the data; I sent for the numbers which came back in time. My first officer and I were distracted by this. The 1;000 feet callout was made by my first officer (first officer) as I finished setting the landing bug speeds and my first officer responded to the call with the appropriate response. Shortly thereafter we received the GPWS (ground proximity warning system) warning 'too low; flaps.' I then called for a go-around. My first officer executed the go-around; we contacted ATC. Came back and landed uneventfully. I then contacted maintenance to inform them of the go-around.I allowed myself to be distracted by bugging the landing speeds and the departing traffic ahead of us. This oversight led to a compressed workload on short final which distracted both my first officer and I.we discussed the event after landing and what we had learned from it. I was disappointed that the error made it by both of us as long as it did. But we discussed the importance of verifying checklist items such as landing data in the descent checklist and more and how that oversight led to this error. I believe this was a good learning opportunity for both my first officer and myself.
Original NASA ASRS Text
Title: CRJ-900 Captain reported an unstable approach and go-around resulting from other errors in the cockpit.
Narrative: During the descent checklist; I mistakenly thought I had set the landing data. Once we were cleared for the approach I realized this was not the case. To make sure we had the data; I sent for the numbers which came back in time. My First Officer and I were distracted by this. The 1;000 feet callout was made by my FO (First Officer) as I finished setting the landing bug speeds and my FO responded to the call with the appropriate response. Shortly thereafter we received the GPWS (Ground Proximity Warning System) warning 'too low; flaps.' I then called for a go-around. My FO executed the go-around; we contacted ATC. Came back and landed uneventfully. I then contacted Maintenance to inform them of the go-around.I allowed myself to be distracted by bugging the landing speeds and the departing traffic ahead of us. This oversight led to a compressed workload on short final which distracted both my FO and I.We discussed the event after landing and what we had learned from it. I was disappointed that the error made it by both of us as long as it did. But we discussed the importance of verifying checklist items such as landing data in the descent checklist and more and how that oversight led to this error. I believe this was a good learning opportunity for both my FO and myself.
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.