Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Flight Crew Total 8
Situational Awareness; Distraction
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter FOD; Inflight Event / Encounter Fuel Issue; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition
Airport; Human Factors
Initial approach to Runway 26 PHX plan arrival fuel approximately 9.0. On final to Runway 26 aircraft reports FOD (Foreign Object Debris) on runway; a dislodged concrete on runway near Taxiway B7. Crew asked if we are cleared to land - Tower responds yes. Crew then asks if full length is available. Tower responds cleared to land your discretion FOD reported on runway. Crew elected to GA (Go Around). Vectors on departure initially to Runway 26 again; crew informed Controller of GA due to FOD; controller was unaware but then informed 8/26 now closed expect vectors Runway 25L. On final 25L Tower reports winds gusting with tailwind above 10 knots. Crew elected to GA due to excessive tailwind reported on short final. Additional aircraft reported unable to accept tailwind for both takeoff and landing. Airport then changed runways to 8; 7L; 7R. ATC vectored to 8 or 7R with ATIS reporting 7R closed. Crew planned 7R. During extended vectors crew declared Pan Pan due to approaching minimum fuel. Planned arrival fuel was 5.0 with reserves 4.1. Vectors for visual Runway 7R. On initial check in with Tower for Runway 7R winds again shifted to a tailwind. Offered longer Runway 8 and accepted due to tailwind and low fuel state. While maneuvering for Runway 8 approach became unstable with flap over speed which required a GA. On downwind for Runway 8 [requested priority handling] due to possible landing below fuel reserves. Uneventful approach and landing Runway 8. Shut down at gate with approximately 3.8 fuel. Initially event was due to FOD on runway followed by unexpected tailwind and shifting winds. Unstable approach; flap over speed and final GA was due to task saturation; concern over tailwind/short runway; automation; and concern over low fuel state. Remain vigilant during high stress events task saturation can result in unstable approach and deviation. Strict adherence to SOP. I will stress this during my 'possible threats' brief each departure and arrival.
Initial approach to Runway 26. Tower reported a piece of the runway coming up around B7. Confirmed cleared to land. Asked if entire runway was usable. Tower said at your discretion. Elected to go-around because of the uncertainty of the runway surface. Vectors to Runway 25L. On final for 25L Tower gave us the current winds and were reporting a tailwind gusting over the limitation. Executed a second go-around. Discussed our reserve fuel and we needed to land with 4.1. Made several attempts to get a plan from ATC whether they were planning to change landing direction. On the third attempt; got confirmation they would be landing east. While being vectored for 07R declared Pan Pan. On final for 07R received another wind report that was a gusting tailwind. Asked for 08 and was given 08 and cleared to land. Became unstable and had a flap over speed on approach. Executed another go around. [Requested priority handling] because we were low on fuel. Vectored around and landed 08. Arrived at gate with 3800 lbs of fuel. FOD (Foreign Object Debris) on runway. Changing winds. Task saturation. High stress because of low fuel.
A321 flight crew reported going around due to FOD; then wind; unstable with flap over speed; eventually landing on the fourth attempt with fuel issues.