37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1213939 |
Time | |
Date | 201410 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Component | |
Aircraft Component | Flap Control (Trailing & Leading Edge) |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence Inflight Event / Encounter Unstabilized Approach |
Narrative:
Both the captain and I are new to the aircraft (B-737); I had consolidated last trip with around 120-hours in type. The captain had not yet consolidated; and had less than 100-hours in type at the time of this occurrence. We had discussed possible arrival scenarios; approach options; and reviewed available jeppesen pages as well as flight plan information including ATIS and NOTAM's en route to destination. Extensive prior planning; did not mitigate what turned out to be a high workload scenario close-in to the terminal area. We were cleared for an approach via routing we had not expected; but managed this aspect professionally. During the transition to final; we were told to look out for traffic; a GA aircraft; which I had the impression was not under direct ATC control. About to intercept final; we were told the glideslope was OTS so we transitioned to an RNAV approach. As the pilot not flying; I setup the FMS; MCP; and da's for the cleared approach; and quickly briefed the changes. Still new to the aircraft; I closely monitored the CDU and fmas to make sure the aircraft was indeed doing what we had commanded. The GA traffic was still being called out to us; which effectively divided the cockpit. Starting down final approach; we encountered strong; gusty crosswind conditions. The captain was flying the aircraft; monitor my actions; and looking for GA traffic. I was setting up the instruments; handling the radio; making commanded configuration changes; and when time permitted; I was looking for conflict traffic. We were nearing 1;000 feet on final approach. Our configuration at this time was approach ref for 15; gear down; flaps 25 and the captain was hand flying. The captain verbally made mention of the strong gusty winds he was encountering and said he was going to carry some speed. We were both still looking for conflict traffic and missed the erroneous altitude/flap configuration until below 1;000 ft. I called flaps to complete the checklist. The captain stated due to gusty crosswinds; he wanted to stay at flaps 25. Flaps 25? I honestly had to think for a moment; can we land flaps 25? I did not think so; but given our position; currently around 500 ft on final approach; I was conflicted with situational self doubt (had I missed something in training?; had there been another change to the 737 bulletins/ops procedures that I missed?; had the captain been taught something in training that I hadn't concerning handling gusty crosswinds?). Situationally; I felt that broaching the commanded flaps 25 landing at that phase of flight; close-in to the airport on final approach; while the captain had his hands full of aircraft; would have presented more of a safety issue for us at that time. We landed flaps 25. We had speeds for flaps 15 and landed flaps 25; it was a hot landing. After clearing the runway; I asked the captain; can we land the 737 at flaps 25? Without question; I'm truly embarrassed; disappointed in my performance; and humbled by this experience. I failed in my duties and responsibilities to support the pilot flying and observed a situation that should have been brought to the captain's immediate attention. Without question; I should have exercised the no fault go-around provisions we enjoy and regret not having done so in this case.
Original NASA ASRS Text
Title: B737 flight crew reports landing with a flap setting of 25 due to strong gusty winds which is contrary to the company's authorized landing flap settings. Low time for both pilots in the aircraft; ATC issues and weather were cited as factors in the incident.
Narrative: Both the Captain and I are new to the aircraft (B-737); I had consolidated last trip with around 120-hours in type. The Captain had not yet consolidated; and had less than 100-hours in type at the time of this occurrence. We had discussed possible arrival scenarios; approach options; and reviewed available Jeppesen pages as well as flight plan information including ATIS and NOTAM's en route to destination. Extensive prior planning; did not mitigate what turned out to be a high workload scenario close-in to the terminal area. We were cleared for an approach via routing we had not expected; but managed this aspect professionally. During the transition to final; we were told to look out for traffic; a GA aircraft; which I had the impression was not under direct ATC control. About to intercept final; we were told the glideslope was OTS so we transitioned to an RNAV approach. As the pilot not flying; I setup the FMS; MCP; and DA's for the cleared approach; and quickly briefed the changes. Still new to the aircraft; I closely monitored the CDU and FMAs to make sure the aircraft was indeed doing what we had commanded. The GA traffic was still being called out to us; which effectively divided the cockpit. Starting down final approach; we encountered strong; gusty crosswind conditions. The Captain was flying the aircraft; monitor my actions; and looking for GA traffic. I was setting up the instruments; handling the radio; making commanded configuration changes; and when time permitted; I was looking for conflict traffic. We were nearing 1;000 feet on final approach. Our configuration at this time was approach ref for 15; gear down; flaps 25 and the Captain was hand flying. The Captain verbally made mention of the strong gusty winds he was encountering and said he was going to carry some speed. We were both still looking for conflict traffic and missed the erroneous altitude/flap configuration until below 1;000 FT. I called Flaps to complete the checklist. The Captain stated due to gusty crosswinds; he wanted to stay at Flaps 25. Flaps 25? I honestly had to think for a moment; can we land Flaps 25? I did not think so; but given our position; currently around 500 FT on final approach; I was conflicted with situational self doubt (had I missed something in training?; had there been another change to the 737 Bulletins/Ops Procedures that I missed?; had the Captain been taught something in training that I hadn't concerning handling gusty crosswinds?). Situationally; I felt that broaching the commanded Flaps 25 landing at that phase of flight; close-in to the airport on final approach; while the Captain had his hands full of aircraft; would have presented more of a safety issue for us at that time. We landed Flaps 25. We had speeds for Flaps 15 and landed Flaps 25; it was a hot landing. After clearing the runway; I asked the Captain; can we land the 737 at Flaps 25? Without question; I'm truly embarrassed; disappointed in my performance; and humbled by this experience. I failed in my duties and responsibilities to support the pilot flying and observed a situation that should have been brought to the Captain's immediate attention. Without question; I should have exercised the no fault go-around provisions we enjoy and regret not having done so in this case.
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.