20190808023679A

Accident · Substantial damage

FAA accident report · Airbus A321-211 · Orlando, FL · August 8, 2019

Date
August 8, 2019 · 15:00 local
Place
Orlando, FL
Airport
Orlando
Phase of flight
Landing: Approach
Operating rules
Air carrier (Part 121)
Operator
F3LA
Damage
Substantial damage
Aircraft
N717FR
NTSB investigation
NTSBDCA19LA193
Reported as
Airbus A321-211
Reported engine
CFM International CFM56-5B3/3
People aboard
228
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Airline transport, flight instructor
Pilot’s flight hours
10,854 total

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Date of event 08AUG2019

N717FR

Flight 1187

Pwm - mco

Overview: on 08 August 2019, N717FR experienced a hard landing, which resulted into a fuselage and a tail strike, causing substantial damage to the aircraft. No injuries were noted.

Details: approach to 18R, rain shafted to right of runway. Aircraft ahead reported smooth in rain under cloud. Flight crew didn?t think there was much vertical buildup to the cloud, affirming the preceding aircraft?s ride report. That same aircraft later reported loss of airspeed on final, followed by an ATC report of wind-shear on 18R. Based on this information and the wind readout on the ND display, flight crew elected to switch to 18L as it appeared that the weather would continue moving to the east. Over runway 18L, just under 30 feet and thrust coming to idle, captain felt the airplane drop/sink, so captain applied toga and began the go-around. As the engines spooled, the aircraft bounced on the runway. Captain elected o-around and circled back to 17L. ATC told to circle back to 18R. Flight crew then heard from ATC that the wind was a 16 knot tailwind. Crew told ATC they were unable to accept that tailwind, which elected another missed approach from intermediate altitude (just below 2,000?). ATC directed flight 1187 to the south, then east, then back to 35R. Third approach was to 35R with a successful landing. Upon landing, the first officer performed the post-flight walk-around and found the tail strike damage. Crew contacted maintenance and wrote it up in the logbook for maintenance inspection.

As the FAA filed it

DATE OF EVENT 08AUG2019

N717FR

FLIGHT 1187

PWM - MCO

OVERVIEW: ON 08 AUGUST 2019, N717FR EXPERIENCED A HARD LANDING, WHICH RESULTED INTO A FUSELAGE AND A TAIL STRIKE, CAUSING SUBSTANTIAL DAMAGE TO THE AIRCRAFT. NO INJURIES WERE NOTED.

DETAILS: APPROACH TO 18R, RAIN SHAFTED TO RIGHT OF RUNWAY. AIRCRAFT AHEAD REPORTED SMOOTH IN RAIN UNDER CLOUD. FLIGHT CREW DIDN?T THINK THERE WAS MUCH VERTICAL BUILDUP TO THE CLOUD, AFFIRMING THE PRECEDING AIRCRAFT?S RIDE REPORT. THAT SAME AIRCRAFT LATER REPORTED LOSS OF AIRSPEED ON FINAL, FOLLOWED BY AN ATC REPORT OF WIND-SHEAR ON 18R. BASED ON THIS INFORMATION AND THE WIND READOUT ON THE ND DISPLAY, FLIGHT CREW ELECTED TO SWITCH TO 18L AS IT APPEARED THAT THE WEATHER WOULD CONTINUE MOVING TO THE EAST. OVER RUNWAY 18L, JUST UNDER 30 FEET AND THRUST COMING TO IDLE, CAPTAIN FELT THE AIRPLANE DROP/SINK, SO CAPTAIN APPLIED TOGA AND BEGAN THE GO-AROUND. AS THE ENGINES SPOOLED, THE AIRCRAFT BOUNCED ON THE RUNWAY. CAPTAIN ELECTED O-AROUND AND CIRCLED BACK TO 17L. ATC TOLD TO CIRCLE BACK TO 18R. FLIGHT CREW THEN HEARD FROM ATC THAT THE WIND WAS A 16 KNOT TAILWIND. CREW TOLD ATC THEY WERE UNABLE TO ACCEPT THAT TAILWIND, WHICH ELECTED ANOTHER MISSED APPROACH FROM INTERMEDIATE ALTITUDE (JUST BELOW 2,000?). ATC DIRECTED FLIGHT 1187 TO THE SOUTH, THEN EAST, THEN BACK TO 35R. THIRD APPROACH WAS TO 35R WITH A SUCCESSFUL LANDING. UPON LANDING, THE FIRST OFFICER PERFORMED THE POST-FLIGHT WALK-AROUND AND FOUND THE TAIL STRIKE DAMAGE. CREW CONTACTED MAINTENANCE AND WROTE IT UP IN THE LOGBOOK FOR MAINTENANCE INSPECTION.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.