37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 845298 |
Time | |
Date | 200907 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Experience | Flight Crew Last 90 Days 187 Flight Crew Type 8000 |
Person 2 | |
Function | Pilot Flying First Officer |
Experience | Flight Crew Last 90 Days 227 Flight Crew Type 2500 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Flight to ZZZ to an ILS. We were at 5000' MSL 10 miles northwest of the field at 180 knots; dropped the gear when we were vectored to the dogleg; and cleared the approach. Weather was expected to be 2500' sct with a ceiling of 4000' broken; 5 miles visibility due to -RA/br. Captain was pm and first officer was PF. We leveled off; configured to flaps 40; and tried to descend aggressively to below the 4000' ceiling and into VMC. Rain precluded us from picking up the runway; and a steady 18-20 knot tailwind kept us high on final. We crossed the FAF approximately 1000 feet high (2900' MSL); with the glideslope coming off the bottom of the case. PF engaged the approach mode when we were within a dot; and then soon thereafter realized this was a false glideslope when it showed us going below the glideslope. We then told tower we were initiating a missed approach; since we were still IMC. They told us to turn to 330 heading at the departure end; which pm read back. We initiated a go-around; tried to find the departure end through the rain and clouds; and then were told by tower to turn to 330 heading and contact approach. 30 to 40 degrees into the right turn; approach told us to turn left to the 330 heading. They later asked us why we made the right turn instead of going left which would in hindsight have been the shortest direction. I couldn't explain the thought process very well; which was we flew from a right downwind with an approach to the right runway with simultaneous traffic to the left runway and felt we needed to turn from any departures that might be on the other runway during our go-around. They asked us to call the supervisor when we landed. The following approach was uneventful. Missed approaches are very busy! Flap cleanups and takeoff warning horns; trying to find the end of the runway through the weather in IMC when they think you are VMC; and radio calls. It's just important to pay attention to everything approach tells you and read it back.
Original NASA ASRS Text
Title: A B737NG turned the wrong way on a missed approach; causing an airborne conflict. Contributing factors were workload and weather.
Narrative: Flight to ZZZ to an ILS. We were at 5000' MSL 10 miles NW of the field at 180 knots; dropped the gear when we were vectored to the dogleg; and cleared the approach. Weather was expected to be 2500' SCT with a ceiling of 4000' BKN; 5 miles VIS due to -RA/BR. Captain was PM and F/O was PF. We leveled off; configured to flaps 40; and tried to descend aggressively to below the 4000' ceiling and into VMC. Rain precluded us from picking up the runway; and a steady 18-20 knot tailwind kept us high on final. We crossed the FAF approximately 1000 feet high (2900' MSL); with the glideslope coming off the bottom of the case. PF engaged the approach mode when we were within a dot; and then soon thereafter realized this was a false glideslope when it showed us going below the glideslope. We then told Tower we were initiating a missed approach; since we were still IMC. They told us to turn to 330 heading at the departure end; which PM read back. We initiated a go-around; tried to find the departure end through the rain and clouds; and then were told by Tower to turn to 330 heading and contact Approach. 30 to 40 degrees into the right turn; Approach told us to turn left to the 330 heading. They later asked us why we made the right turn instead of going left which would in hindsight have been the shortest direction. I couldn't explain the thought process very well; which was we flew from a right downwind with an approach to the right runway with simultaneous traffic to the left runway and felt we needed to turn from any departures that might be on the other runway during our go-around. They asked us to call the Supervisor when we landed. The following approach was uneventful. Missed approaches are very busy! Flap cleanups and takeoff warning horns; trying to find the end of the runway through the weather in IMC when they think you are VMC; and radio calls. It's just important to pay attention to everything Approach tells you and read it back.
Data retrieved from NASA's ASRS site as of April 2012 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.