2023-06 · NASA ASRS report 2007504
B737 flight crew reported an unstabilized approach resulted in a go-around as the aircraft touched down on the runway. As the aircraft performed the go around; the First Officer felt a bump indicative of a tail strike. The aircraft landed and upon post flight inspection damage was discovered to the tail stinger.
During a visual approach; and on short final; the PF (Pilot Flying) started to drift above the glideslope. At 3 white and 1 red indicators on the PAPI; the PF vocalized high and correcting. At approximately 75 ft. the descent rate slowed; the aircraft continued to drift above the glideslope and a long landing was looking probable. The PF continued to vocalize correcting. Once the aircraft was outside the touchdown zone and a long landing was evident; the PM (Pilot Monitoring) called for a go around. At the same time a call for go around was initiated; the PF had reduced the thrust levers to idle. As the PF initiated the go around; the Main Landing Gear momentarily touched the runway. During the pitch up and engine spool up; the PM felt a bump indicating a possible tailstrike. ATC gave an initial heading and altitude to climb to; as well as a new runway assignment. The PF loaded the ILS for the new runway and sent for landing data since the runway was significantly shorter. During the vectors to intercept; the PM vocalized that his side was not receiving the signal from the ILS frequency. The PF said his side was receiving the signal. ATC gave a vector to intercept; and again; the PM vocalized that the signal was not being received on his side. The aircraft passed through the LOC course and ATC gave a new heading to intercept. The PF acknowledged he was not receiving the signal and the PM loaded the RNAV approach to the runway to provided course and vertical guidance. Once the approach was loaded; the second approach was successful. After arriving at the gate; the PM conducted a post-flight walk-around and discovered damage to the tail stinger.
[At] 500 ft.; aircraft was stable. At approximately 100 ft. AGL; I noticed that the aircraft was above the glide path and PASI (3 White/1 Red). I announced such and that I was correcting. As I retarded the throttles at approximately 20 ft.; the aircraft continued to 'float' down the runway. Just as the Aircraft finally touched down; the FO (First Officer) called for a Go-Around just as the 'Long Landing' aural announced. Initial application of approx 7 to 11 degree; with a transition to 15 degree pitch attitude was applied. As the engines spooled and thrust increased; the Aircraft pitch up; causing the tail-strike in conjunction with the strut compression. Normal Go-Around procedures commenced; followed by vectors to Runway XXR. Normal non-eventful landing. Evidence of tail-strike was discovered on post-flight. Electronic Logbook report and Chief Pilot contacted.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.