Narrative:

A number of factors; weather; experience level; system malfunction; and less-than-ideal decisions lead to a situation where an egpws caution was experienced as a go-around was initiated. ATIS was broadcasting marginal VFR conditions. The planned approach was to the company preferred runway (quickest access to ramp); RNAV (GPS) runway 23 with visual conditions expected in vicinity of FAF. I am very familiar with this approach and had flown it as the pilot not flying the night before in better weather conditions in the same aircraft. The aircraft flew it flawlessly as it usually does. On initial contact to approach control I advised having the ATIS which was the same as the current metar: 21012KT 6SM br OVC016 13/12 A2974. We were not advised that the airport weather was any different; but fwa ATC is notorious (in my experience) for not updating the ATIS in a timely manner around our arrival time in the evening. I later found out it had gone IFR for a period; before returning to VFR.the first officer was pilot flying and had less than 100 hours in type but impressed me as being very competent. He had been to fwa before (but not with me). During the approach briefing we discussed manipulation of the MCP; and the need for VNAV path. Approach clearance was direct slydr; cross slydr at or above 3;000; cleared straight-in RNAV (GPS) runway 23. With autoflight on; the first officer began to slow and configure nicely for a planned approach in visual conditions; though it would have been late for an approach in IMC; which the weather at the field had deteriorated to unbeknownst to us. Over slydr; the first officer performed 'lavs'; setting up the autoflight system to fly the approach. He called for gear; flaps; and the before landing checklist as he slowed the aircraft to vapp. As I performed the checklist I lost my pilot not flying sa (situational awareness) and; in retrospect; things went downhill pretty fast. I recall breaking out of the clouds above 1;000 AGL and reminding the first officer that we had until 500 AGL to be stable as we assumed the airport was VFR. For some reason I was unable to see the airport where I expected it to be; [was] scud obscuring the view? Though I had ground contact as we approached 'minimums'; something definitely did not seem right. For about one second my brain attempted to make sense of the outside picture; and then I called for a go-around. Almost simultaneously; we received an egpws caution 'too low; terrain' as the go-around was in progress. Later during the debrief; the first officer said that once the go-around was commanded; he hit the G/a switch but does not think it engaged (due to lack of force from his finger). He then reacted to the GPWS by abruptly pulling back on the yoke to initiate the climb; but with the power back; we briefly entered 'the foot' on the airspeed tape; and he recalls momentarily getting the stick shaker before manually adding full power. As I was not on the controls; I don't have the same recollection he does; but as I was reaching for the flaps (to raise them to 20) I noticed the airspeed out of the corner of my eye and also reached for the throttles. Again; it all happened very quickly; but my recollection is that we immediately began climbing rapidly at a safe speed; the GPWS had silenced; and I continued to configure the aircraft for the go-around. I don't recall hearing a GPWS warning (i.e. 'Pull up') which would've dictated the egpws escape maneuver (we had visual contact with the ground but it was night); and I'm sure I would not consciously make a decision not to follow the procedure. Knowing the terrain near the airport and observing the airplane's performance; I felt the go-around was an appropriate and satisfactory action at the time. As we leveled at 3;000 ATC asked if we had any issues; and I reported that we did not see the runway at minimums and that the weather seemed lower than reported. They didn't advise us of the latest weather (which had officially returned to VFR) and; for some strange reason; I did not ask. They then asked our intentions; and after briefly discussing the choice of an ILS runway 32 or another RNAV (GPS) 23; we opted to repeat the approach. In retrospect; clearly the correct decision should have been to select an approach with ground-based navaids; vertical guidance and lower minimums. I'm not sure how much of a factor fatigue or schedule pressure played but; at that point; we assumed any problems with the approach had been 'operator error' and runway 23 seemed to be the most efficient option. On the subsequent approach; we would be extremely alert for anything not right. We were vectored to intercept the final between slydr and the FAF; akews; on about a 7 mile final. Looking back; I have no idea why I accepted this clearance instead of requesting to join outside slydr again; but at the time it seemed acceptable. The first officer was again pilot flying and I was pilot not flying; both of us watching the autoflight system very carefully. Approaching babac I noticed the MCP VNAV switch annunciator extinguish and the flch switch illuminate. What the heck? The aircraft was now descending below profile; I took the controls; added power; but before I could say 'go-around' we acquired the runway visually; and I opted to continue the approach visually. The landing was uneventful. I made a logbook entry for the VNAV system malfunction and; after consulting with maintenance control and operational control; we MEL'd the VNAV switch prior to departure. On the next leg; we had a malfunction of the autothrottle system on approach (which was written up upon arrival); and this may have been the root cause of the VNAV malfunction.as usual; a number of factors [contributed to] this event; however; I believe familiarity with the aircraft; airport; and approach; may have led to a level of complacency on my part as pilot not flying. I fault myself primarily for allowing the planning of the RNAV (GPS) approach as a back-up to a visual; instead of planning it as an instrument approach in marginal VFR conditions. Doing so would have required slowing and configuring sooner and; with the before landing checklist complete that much earlier; I could've devoted all my attention to my pilot not flying role. I believe I would've noticed what I now assume was a VNAV malfunction on the first approach. I also believe my first officer's inexperience in the aircraft and with RNAV approaches may have caused him to become task saturated with slowing and configuring the aircraft during the approach and diverted his attention from monitoring autoflight's performance. I should have given more consideration to his experience level; and encouraged him to fly a conservative approach as opposed to allowing him to fly it as I might have. Contributing to the event was lack of appropriate weather updates from ATC; which surely would have prompted a more conservative approach. And lastly; an aircraft system malfunction and failure to recognize it sooner was the final piece to the puzzle. On the second approach; I think I made several questionable decisions; and while I know that schedule never trumps safety; I have to wonder if it was a significant influence to some of my choices. Finally; I have only briefly mentioned fatigue; but I wonder if that was a factor in my sub par monitoring and decision making that night. This particular trip can be challenging; with the amount of block time (around 6 hours); a relatively short layover; and back-side of the clock flying. The layover was further shortened due to delay to the layover destination. While I felt 'fine' when I reported for duty the night of the event; I have to wonder if my decision making was affected by less than normal rest. I've spent many hours this past weekend reflecting on what happened and thinking how to prevent it from happening again. The most significant lesson learned is; when planning an approach to an airport reporting marginal VFR conditions; treat it as an instrument approach. Allow for earlier configuration and checklist completion so that your attention can be devoted to the pilot not flying role (or if pilot flying; monitoring the autoflight). Breaking out into visual conditions over the FAF should just be a bonus. Other things that would have helped are more obvious such as; if you don't get the information you need (i.e. Weather); ask for it! If the first approach is unsuccessful; seriously consider a different one. Never let schedule pressure cause you to make unsafe decisions. And finally; with short layovers; do your best to get adequate rest so you report for duty with a clear head.

Google
 

Original NASA ASRS Text

Title: The flight crew of a Boeing RNAV capable; GPS equipped; twin jet cleared for the RNAV (GPS) Runway 23 at FWA were alerted by an EGPWS warning and a low altitude alert from the Tower that they had descended excessively below the RNAV generated glidepath. Simultaneous with the warning the crew was surprised to see that the autoflight system had somehow reverted from VNAV PATH to FLCH. An immediate EGPWS escape maneuver was executed by the pilot flying who applied insufficient pressure to the go-around button to activate go-around guidance and autothrottle response and a short duration stick shaker warning occurred; silenced quickly by manual thrust lever advancement. A subsequent approach under close observation repeated the anomaly with VNAV/FLCH.

Narrative: A number of factors; weather; experience level; system malfunction; and less-than-ideal decisions lead to a situation where an EGPWS Caution was experienced as a go-around was initiated. ATIS was broadcasting marginal VFR conditions. The planned approach was to the Company preferred runway (quickest access to ramp); RNAV (GPS) Runway 23 with visual conditions expected in vicinity of FAF. I am very familiar with this approach and had flown it as the pilot not flying the night before in better weather conditions in the same aircraft. The aircraft flew it flawlessly as it usually does. On initial contact to Approach Control I advised having the ATIS which was the same as the current METAR: 21012KT 6SM BR OVC016 13/12 A2974. We were not advised that the airport weather was any different; but FWA ATC is notorious (in my experience) for not updating the ATIS in a timely manner around our arrival time in the evening. I later found out it had gone IFR for a period; before returning to VFR.The First Officer was pilot flying and had less than 100 hours in type but impressed me as being very competent. He had been to FWA before (but not with me). During the approach briefing we discussed manipulation of the MCP; and the need for VNAV PATH. Approach clearance was direct SLYDR; cross SLYDR at or above 3;000; cleared straight-in RNAV (GPS) Runway 23. With autoflight on; the First Officer began to slow and configure nicely for a planned approach in visual conditions; though it would have been late for an approach in IMC; which the weather at the field had deteriorated to unbeknownst to us. Over SLYDR; the First Officer performed 'LAVS'; setting up the autoflight system to fly the approach. He called for gear; flaps; and the Before Landing Checklist as he slowed the aircraft to Vapp. As I performed the checklist I lost my pilot not flying SA (Situational Awareness) and; in retrospect; things went downhill pretty fast. I recall breaking out of the clouds above 1;000 AGL and reminding the First Officer that we had until 500 AGL to be stable as we assumed the airport was VFR. For some reason I was unable to see the airport where I expected it to be; [Was] scud obscuring the view? Though I had ground contact as we approached 'Minimums'; something definitely did not seem right. For about one second my brain attempted to make sense of the outside picture; and then I called for a go-around. Almost simultaneously; we received an EGPWS caution 'TOO LOW; TERRAIN' as the go-around was in progress. Later during the debrief; the First Officer said that once the go-around was commanded; he hit the G/A switch but does not think it engaged (due to lack of force from his finger). He then reacted to the GPWS by abruptly pulling back on the yoke to initiate the climb; but with the power back; we briefly entered 'the foot' on the airspeed tape; and he recalls momentarily getting the stick shaker before manually adding full power. As I was not on the controls; I don't have the same recollection he does; but as I was reaching for the flaps (to raise them to 20) I noticed the airspeed out of the corner of my eye and also reached for the throttles. Again; it all happened very quickly; but my recollection is that we immediately began climbing rapidly at a safe speed; the GPWS had silenced; and I continued to configure the aircraft for the go-around. I don't recall hearing a GPWS Warning (i.e. 'PULL UP') which would've dictated the EGPWS escape maneuver (we had visual contact with the ground but it was night); and I'm sure I would not consciously make a decision not to follow the procedure. Knowing the terrain near the airport and observing the airplane's performance; I felt the go-around was an appropriate and satisfactory action at the time. As we leveled at 3;000 ATC asked if we had any issues; and I reported that we did not see the runway at minimums and that the weather seemed lower than reported. They didn't advise us of the latest weather (which had officially returned to VFR) and; for some strange reason; I did not ask. They then asked our intentions; and after briefly discussing the choice of an ILS Runway 32 or another RNAV (GPS) 23; we opted to repeat the approach. In retrospect; clearly the correct decision should have been to select an approach with ground-based navaids; vertical guidance and lower minimums. I'm not sure how much of a factor fatigue or schedule pressure played but; at that point; we assumed any problems with the approach had been 'operator error' and Runway 23 seemed to be the most efficient option. On the subsequent approach; we would be extremely alert for anything not right. We were vectored to intercept the final between SLYDR and the FAF; AKEWS; on about a 7 mile final. Looking back; I have no idea why I accepted this clearance instead of requesting to join outside SLYDR again; but at the time it seemed acceptable. The First Officer was again pilot flying and I was pilot not flying; both of us watching the autoflight system very carefully. Approaching BABAC I noticed the MCP VNAV switch annunciator extinguish and the FLCH switch illuminate. What the heck? The aircraft was now descending below profile; I took the controls; added power; but before I could say 'go-around' we acquired the runway visually; and I opted to continue the approach visually. The landing was uneventful. I made a logbook entry for the VNAV system malfunction and; after consulting with Maintenance Control and Operational Control; we MEL'd the VNAV switch prior to departure. On the next leg; we had a malfunction of the autothrottle system on approach (which was written up upon arrival); and this may have been the root cause of the VNAV malfunction.As usual; a number of factors [contributed to] this event; however; I believe familiarity with the aircraft; airport; and approach; may have led to a level of complacency on my part as pilot not flying. I fault myself primarily for allowing the planning of the RNAV (GPS) approach as a back-up to a visual; instead of planning it as an instrument approach in marginal VFR conditions. Doing so would have required slowing and configuring sooner and; with the Before Landing Checklist complete that much earlier; I could've devoted all my attention to my pilot not flying role. I believe I would've noticed what I now assume was a VNAV malfunction on the first approach. I also believe my First Officer's inexperience in the aircraft and with RNAV approaches may have caused him to become task saturated with slowing and configuring the aircraft during the approach and diverted his attention from monitoring autoflight's performance. I should have given more consideration to his experience level; and encouraged him to fly a conservative approach as opposed to allowing him to fly it as I might have. Contributing to the event was lack of appropriate weather updates from ATC; which surely would have prompted a more conservative approach. And lastly; an aircraft system malfunction and failure to recognize it sooner was the final piece to the puzzle. On the second approach; I think I made several questionable decisions; and while I know that schedule never trumps safety; I have to wonder if it was a significant influence to some of my choices. Finally; I have only briefly mentioned fatigue; but I wonder if that was a factor in my sub par monitoring and decision making that night. This particular trip can be challenging; with the amount of block time (around 6 hours); a relatively short layover; and back-side of the clock flying. The layover was further shortened due to delay to the layover destination. While I felt 'fine' when I reported for duty the night of the event; I have to wonder if my decision making was affected by less than normal rest. I've spent many hours this past weekend reflecting on what happened and thinking how to prevent it from happening again. The most significant lesson learned is; when planning an approach to an airport reporting marginal VFR conditions; treat it as an instrument approach. Allow for earlier configuration and checklist completion so that your attention can be devoted to the pilot not flying role (or if pilot flying; monitoring the autoflight). Breaking out into visual conditions over the FAF should just be a bonus. Other things that would have helped are more obvious such as; if you don't get the information you need (i.e. weather); ask for it! If the first approach is unsuccessful; seriously consider a different one. Never let schedule pressure cause you to make unsafe decisions. And finally; with short layovers; do your best to get adequate rest so you report for duty with a clear head.

Data retrieved from NASA's ASRS site as of July 2013 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.