Narrative:

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.

Related reports:

Google
 

Original NASA ASRS Text

Title: 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.

Narrative: 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.

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.