 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
On approach in a B737; ATC issued an improper vector which sent the flight crew through the localizer. While attempting to recapture the localizer and glideslope the flight crew began to fall behind the aircraft resulting in breaking out of the clouds to the right of the runway.
| Attributes | |
| ACN | 1322997 |
| Time | |
| Date | 201601 |
| 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 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 144 |
| Person 2 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 125 Flight Crew Type 12000 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
This was the last leg of a four-day for me and I was flying with an older; senior captain that I had never flown with before. I was the pilot monitoring and was a little tired after flying the last four days. I was ready to be done. The captain was the pilot flying (PF). We got along great during the flight; but I guess I felt somewhat intimidated. The weather was IFR when we shot the ILS to runway 4. I think the ceiling was reported at 500 ft ovc and 3 RA. The approach controller gave us a bad vector which put us through the localizer. He gave us another to rejoin. I think this put the captain behind the airplane. I do not think we were fully configured or on speed at the FAF. I think the captain missed pressing app and we did not capture the G/south (glideslope). He proceeded to chase it by vert speeding down for the G/south. We were inside the FAF at this point. I definitely should have called go-around at this point; but at the time; I thought that the captain could get it all back together. He started to deviate from the localizer as well. I think we got a sink rate and two glideslope aural warnings; but I do not remember a pull-up command. The whole time I was thinking I should say go around; but my mouth was frozen shut. I was along for the ride at this point. The captain missed his FAF callout and the 1000 foot callout. I was fixated on willing him to get back on localizer and G/south and missed my callouts as well. We broke out and the runway was to the left of the nose and we were low. The captain corrected and we landed without incident and he made our planned turnoff. I am very upset with myself for not being more assertive and calling go-around when my gut was telling me to. I have learned from my mistake and will never let this situation happen again. From now on; if I think go-around; I will say go-around.
Original NASA ASRS Text
Title: On approach in a B737; ATC issued an improper vector which sent the flight crew through the localizer. While attempting to recapture the localizer and glideslope the flight crew began to fall behind the aircraft resulting in breaking out of the clouds to the right of the runway.
Narrative: This was the last leg of a four-day for me and I was flying with an older; senior Captain that I had never flown with before. I was the Pilot Monitoring and was a little tired after flying the last four days. I was ready to be done. The Captain was the Pilot Flying (PF). We got along great during the flight; but I guess I felt somewhat intimidated. The weather was IFR when we shot the ILS to Runway 4. I think the ceiling was reported at 500 ft OVC and 3 RA. The Approach Controller gave us a bad vector which put us through the LOC. He gave us another to rejoin. I think this put the Captain behind the airplane. I do not think we were fully configured or on speed at the FAF. I think the Captain missed pressing APP and we did not capture the G/S (Glideslope). He proceeded to chase it by Vert speeding down for the G/S. We were inside the FAF at this point. I definitely should have called go-around at this point; but at the time; I thought that the Captain could get it all back together. He started to deviate from the LOC as well. I think we got a sink rate and two glideslope aural warnings; but I do not remember a pull-up command. The whole time I was thinking I should say go around; but my mouth was frozen shut. I was along for the ride at this point. The Captain missed his FAF callout and the 1000 foot callout. I was fixated on willing him to get back on LOC and G/S and missed my callouts as well. We broke out and the runway was to the left of the nose and we were low. The Captain corrected and we landed without incident and he made our planned turnoff. I am very upset with myself for not being more assertive and calling go-around when my gut was telling me to. I have learned from my mistake and will never let this situation happen again. From now on; if I think go-around; I will say go-around.
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.