37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1411389 |
Time | |
Date | 201612 |
Place | |
Locale Reference | SNA.Airport |
State Reference | CA |
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 Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Weather / Turbulence |
Narrative:
Flying sna received ATIS for landing prior to descent into orange county; weather reported VFR 3;500 scattered. The only thing that made the approach different than usual was landing on 2L. We briefed a visual approach to 2L with localizer back course as a backup. As we were vectored for the approach I had the aircraft stable at 170 knots 1;600 feet; at the final approach fix we were fully configured gear down flaps 40 with all checklist completed. We were surprised that we were still in the clouds (marginal weather) I figured we'd pop out and the airport would be in sight as soon as we started down. I made the mistake of a too aggressive descent rate that put us in a low position too far from the airport. I notice a FMC disagree light called it out to my first officer when we then got a terrain warning and immediately executed a missed approach. Tower told to us fly runway heading and would be vectored for a right downwind RNAV 2L approach; I also let them know that the visibility was much worse that reported and moderate rain. At this point we briefed the RNAV approach flew it all the way down to minimums when we finally got the runway in sight and landed safely.a couple of things that contributed to the situation was we both did not sleep well and both of us were a little tired. Also we noticed at 1;600 we were still in the clouds even though it didn't appear that bad and that we would pop out I should I have executed the missed approach there. I have been with this airline for [many] years and a captain for [almost as many] and I have never had anything happen to me like this and was a definite slap to my ego. I consider myself a pretty good guy and a very good pilot and always take responsibility for my crew and aircraft at all times while on duty or off duty!inaccurate ATIS report and not planning a full approach to minimums and fatigue.
Original NASA ASRS Text
Title: B737NG Captain reported flying a visual approach with LOC Back Course back up to SNA Runway 2L; executed a missed approach at an EGPWS TERRAIN Warning in weather far worse than reported on ATIS. The second RNAV 2L approach was flown to minimums for a successful landing.
Narrative: Flying SNA received ATIS for landing prior to descent into Orange County; weather reported VFR 3;500 scattered. The only thing that made the approach different than usual was landing on 2L. We briefed a visual approach to 2L with LOC Back Course as a backup. As we were vectored for the approach I had the aircraft stable at 170 knots 1;600 feet; at the final approach fix we were fully configured gear down flaps 40 with all checklist completed. We were surprised that we were still in the clouds (marginal weather) I figured we'd pop out and the airport would be in sight as soon as we started down. I made the mistake of a too aggressive descent rate that put us in a low position too far from the airport. I notice a FMC disagree light called it out to my First Officer when we then got a terrain warning and immediately executed a missed approach. Tower told to us fly runway heading and would be vectored for a right downwind RNAV 2L Approach; I also let them know that the visibility was much worse that reported and moderate rain. At this point we briefed the RNAV approach flew it all the way down to minimums when we finally got the runway in sight and landed safely.A couple of things that contributed to the situation was we both did not sleep well and both of us were a little tired. Also we noticed at 1;600 we were still in the clouds even though it didn't appear that bad and that we would pop out I should I have executed the missed approach there. I have been with this airline for [many] years and a Captain for [almost as many] and I have never had anything happen to me like this and was a definite slap to my ego. I consider myself a pretty good guy and a very good pilot and always take responsibility for my crew and aircraft at all times while on duty or off duty!Inaccurate ATIS report and not planning a full approach to minimums and fatigue.
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.