37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1418316 |
Time | |
Date | 201701 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DCA.Airport |
State Reference | DC |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach Inflight Event / Encounter Weather / Turbulence |
Narrative:
Our flight became unstabilized below 50 feet during the landing phase and we executed a textbook balked landing on runway 33. The main tires did touch the runway; as expected.unfortunately during the go-around phase; comm 1 radio flip-flop button got pushed. Once we returned to the right frequency; we received vectors back around for another VMC approach to runway 1. On the downwind I did quickly call the flight attendant (flight attendant) and make a quick PA announcement about the go-around and gusting winds. We landed on runway 1 without further gusting wind issues. During the taxi in; tower asked us to give them a call; which I did after we parked at the gate and deplaned. Tower asked me why we went around. I explained that the winds had gusted and we became unstabilized during the flare. Next they asked why I did not stay on the tower frequency. I said; I was sorry; but during the balked landing things got very busy; and somehow the radio flip-flop button got pushed back to approach control. Who ever I was talking to the tower seemed very busy; and basically said don't do it again and make sure you stay on the tower frequency. During deplaning no passengers expressed any concerns to me or my crew. In fact; a few did say good job as they meet back up with us on our next flight.
Original NASA ASRS Text
Title: CRJ-200 flight crew reported a sidestep maneuver to another runway and with gusty conditions the approach became unstable. The flight crew executed a go-around and circle back for a normal landing.
Narrative: Our flight became unstabilized below 50 feet during the landing phase and we executed a textbook balked landing on runway 33. The main tires did touch the runway; as expected.Unfortunately during the go-around phase; comm 1 radio flip-flop button got pushed. Once we returned to the right frequency; we received vectors back around for another VMC approach to runway 1. On the downwind I did quickly call the Flight Attendant (FA) and make a quick PA announcement about the go-around and gusting winds. We landed on runway 1 without further gusting wind issues. During the taxi in; tower asked us to give them a call; which I did after we parked at the gate and deplaned. Tower asked me why we went around. I explained that the winds had gusted and we became unstabilized during the flare. Next they asked why I did not stay on the tower frequency. I said; I was sorry; but during the balked landing things got very busy; and somehow the radio flip-flop button got pushed back to approach control. Who ever I was talking to the tower seemed very busy; and basically said don't do it again and make sure you stay on the tower frequency. During deplaning no passengers expressed any concerns to me or my crew. In fact; a few did say good job as they meet back up with us on our next flight.
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.