37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1610061 |
Time | |
Date | 201901 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | OAK.Airport |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 341 Flight Crew Type 19200 |
Events | |
Anomaly | ATC Issue All Types Inflight Event / Encounter Unstabilized Approach Inflight Event / Encounter Weather / Turbulence |
Narrative:
While on a visual approach; aircraft X had to initiate a go-around due to exceedance of tailwind limitations. Tower was reporting winds of 080/7. While on final; below 1;000 feet AGL; we had tailwinds in excess of 20 knots. Below 500 feet AGL; the tailwinds dropped to between 12-15 knots. Over the runway 30 threshold; the winds were 080/18 knots; resulting in tailwind readout of 12 to 15 knots. We executed a go-around and returned for another approach. When we checked in again with tower; they reported winds of about 080/7 again. We executed another approach but were forced to go-around again for excess tailwinds at 50 feet AGL. The tailwind readout was 15 knots. The wind displayed on the nd was 080/18 knots. We requested and received clearance for an approach and landing on runway 12 which concluded without incident. I contacted tower by phone after the flight to inquire as to what location on the airfield wind data they report to aircraft was collected. Tower personnel were unaware of the location. This is the second such occurrence for me in oakland in the last 12 months requiring a go-around for excessive tailwind component even though tower was reporting winds within limits. After our two go-arounds and subsequent landing on runway 12; aircraft were still departing runway 30. I am writing this report because I believe the wind information being presented to tower personnel in oak may not be from a location that represents conditions at the touchdown zone for that runway.
Original NASA ASRS Text
Title: Pilot reported a go-around due to tailwind limitations and after landing at OAK airport; called Tower to question where the wind indicators were on the airport. Tower personnel did not know the answer.
Narrative: While on a visual approach; Aircraft X had to initiate a go-around due to exceedance of tailwind limitations. Tower was reporting winds of 080/7. While on final; below 1;000 feet AGL; we had tailwinds in excess of 20 knots. Below 500 feet AGL; the tailwinds dropped to between 12-15 knots. Over the Runway 30 threshold; the winds were 080/18 knots; resulting in tailwind readout of 12 to 15 knots. We executed a go-around and returned for another approach. When we checked in again with Tower; they reported winds of about 080/7 again. We executed another approach but were forced to go-around again for excess tailwinds at 50 feet AGL. The tailwind readout was 15 knots. The wind displayed on the ND was 080/18 knots. We requested and received clearance for an approach and landing on Runway 12 which concluded without incident. I contacted Tower by phone after the flight to inquire as to what location on the airfield wind data they report to aircraft was collected. Tower Personnel were unaware of the location. This is the second such occurrence for me in Oakland in the last 12 months requiring a go-around for excessive tailwind component even though Tower was reporting winds within limits. After our two go-arounds and subsequent landing on Runway 12; aircraft were still departing Runway 30. I am writing this report because I believe the wind information being presented to Tower Personnel in OAK may not be from a location that represents conditions at the touchdown zone for that runway.
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.