Tailscrape on rear fuselage

Aircraft Engineering and Aerospace Technology

ISSN: 0002-2667

Article publication date: 1 December 2000

119

Keywords

Citation

(2000), "Tailscrape on rear fuselage", Aircraft Engineering and Aerospace Technology, Vol. 72 No. 6. https://doi.org/10.1108/aeat.2000.12772fab.019

Publisher

:

Emerald Group Publishing Limited

Copyright © 2000, MCB UP Limited


Tailscrape on rear fuselage

Tailscrape on rear fuselage

Keyword: Safety

The crew of an Airbus A321 was rostered for a double rotation Heathrow to Dublin and the accident occurred on the second landing at Dublin. The first officer was the handling pilot and the aircraft was radar vectored on to the ILS to Runway 28 at Dublin. The weather at the time was given as wind 250° at 14 knots, visibility 10km, clouds scattered 1,300ft broken 2,300ft, temperature 188 QNH 1007. The approach, which was generally stable, was flown initially on autopilot to about 900ft and then manually with autothrust engaged. At 120ft (radio) the aircraft was slightly above the glidepath and the pilot pitched the aircraft down a small amount to correct the flight path. At 80ft (radio) the power was reduced and at 50ft (radio) progressive back stick was applied and the aircraft responded with increasing pitch. However, although the rate of descent decreased, a hard touchdown resulted, from which the aircraft bounced, with the right main landing gear becoming just clear of the ground and the left still just in contact. The crew perceived that the aircraft was airborne again and the pilot flying kept some back stick applied, in order to cushion the landing and the aircraft continued to pitch up.

Almost coincident with the second touchdown, the commander pressed his sidestick take over button and applied forward stick. The aircraft pitched down for a normal landing roll out. The pilots were aware that the first landing was hard but they were unaware that the second touchdown resulted in a tailstrike. They discussed the landing and decided that although a firmer than normal landing had taken place, it did not warrant a formal heavy landing check to be entered into the Technical Log. The aircraft was taxied to the stand and the passengers disembarked.

The aircraft was late on arrival and the crew began their turn round checks for the return flight to Heathrow. The cabin crew reported to the commander that the rear crew members had heard a "clanking" noise in the area of the rear galley. The commander visited the rear galley and after a conversation with the cabin crew he determined that the most likely explanation for the noise was galley equipment moving within its stowage during the firm landing. At the time, the operator's procedures did not require the flight crew to carry out an external inspection of the aircraft during the turn round at Dublin. This inspection was the responsibility of an engineer supplied by a sub-contractor to carry out the turn round inspection and refuelling.

The aircraft departed for Heathrow slightly behind schedule and the operation was normal until, passing FL 150 in the climb, the crew noticed a high rate of climb in the cabin altitude and the rear cabin crew reported a loud "whooshing" sound in the rear of the aircraft. The commander levelled the aircraft at FL 170 and, as the cabin altitude was still climbing to FL 190, a descent to FL 90 was requested. ATC cleared the aircraft to descend initially to FL 110 because of conflicting traffic and, as the cabin altitude had stabilised at 4,200ft, the commander decided to maintain FL 110 for the cruise. The aircraft made an uneventful landing at Heathrow. An after flight inspection of the aircraft revealed damage consistent with a tailscrape, which included an area of ruptured fuselage skin.

Flight recorders and damage to aircraft

The Cockpit Voice Recorder (CVR) was removed and replayed by the AAIB. It had a two-hour recording duration, which began prior to the take off at Dublin and covered the subsequent return flight to Heathrow. The landing at Dublin was not recorded, but the longer duration CVR did provide information on the activities on the ground at Dublin and the subsequent return flight. The Flight Data Recorder (FDR) was replayed by the AAIB. The tailstrike incident was identified from the data as having occurred during the previous landing at Dublin.

During the approach, on the glidepath and with an IAS of 150 knots, the autopilot was disengaged at about 600ft AGL. The engine power increased, the rate of descent decreased to about 600ft/min and the aircraft began to drift slightly above the glide path (maximum deviation 0.5 dots). As the aircraft descended through 400ft, the engine power reduced, the rate of descent increased to about 900 feet/min and the aircraft regained the glidepath. At about 200ft AGL the power increased to 1.15 EPR, the rate of descent reduced to 500ft/min and the aircraft deviated above the glidepath again; the airspeed was between 146 and 150 knots. At about 80ft the power was reduced. Four seconds before touchdown, at 52ft radio altitude, the First Officer's (FO) sidestick began to be moved to demand a nose-up elevator position. The aircraft touched down at a pitch attitude of 5.3° with a normal acceleration of 2.16g. The FO's sidestick position was 13.4° nose-up with an elevator angle of 11.5° The sidestick demand then started to be moved in a nose-down direction, and the elevator followed. The ground spoilers deployed automatically; this is designed to occur when both the main landing gear oleo switches are compressed. The right main landing gear oleo discrete indicated that the aircraft rebounded slightly.

After the initial touchdown, the pitch attitude continued to increase to a maximum of 10.5°. The FO's sidestick position was moving in a nose down demand direction but was still about 5° nose up. About 0.25 seconds after the maximum pitch attitude, the commander then input a nose down demand of 3° [Note: in the event of simultaneous operation of the sidesticks, the individual outputs are summed together. If the commander operates the override button, the FO's sidestick is isolated. The override operation is recorded on the FDR.] The commander then overrode the FO's sidestick input with a nose up demand of 11° as the nose landing gear of the aircraft lowered onto the runway.

The fuselage underside had suffered abrasion damage consistent with a tailstrike, in the area indicated (Figure 1). The fuselage centreline on the underside lies midway between stringer 41 left and stringer 41 right. Laterally the damage extended to stringer 40 on the right side and to halfway between stringers 40 and 39 on the left side, suggesting the aircraft had been banked slightly to the left at the time of the occurrence. This was confirmed by the FDR which showed the right landing gear oleo switch decompress again after the initial touchdown, with the oleo switch remaining compressed on the left hand side. The damage was most severe over frame Nos. 64, 65 and 66, where the skin had been completely ground away such that the frames and stringers had also been abraded. A section of skin had become detached from the aft edge of frame 65 such that it was free to flap downwards, thus accounting for the pressurisation difficulties on the subsequent flight from Dublin.

Discussion

The aircraft had begun to flare at a radio height of 52ft, some 52 seconds before touchdown. The FO made an initial 78 nose up demand on the sidestick, followed by a 168 (full nose up) demand. The elevator reached 148 (aircraft nose up) at the tail strike. The manufacturer's theoretical elevator position was calculated as 158, using the DFDR parameters (sidestick position, pitch angle and vertical acceleration), which was consistent with the recorded value. The aircraft was descending at a high rate (900ft/min) six seconds prior to touchdown: application of nose up demand by the FO had begun to take effect such that the rate of descent at touchdown had reduced to about 489ft/min.

Figure 1 Location of abrasion damage

After the initial touchdown, the aircraft continued to pitch up, resulting in the tail strike on the second touchdown. This was due to a combination of three effects: the pitch up effect of the automatic ground spoiler deployment, the nose up elevator, which, although the sidestick moved forward, would still produce some nose up demand, and the pitching inertia which had developed during the landing flare.

The manufacturer's database indicates that there have been ten tailscrapes involving the A321 since it came into service, almost all occurred during landing. The non-discovery of the damage during the engineer's external inspection for the turn round is difficult to understand However, there were many items of ground equipment around the aircraft at this time and unless careful attention was paid to the tail area, it may be that the engineer was distracted in avoiding activity by ground equipment.

Had the damage been discovered then undoubtedly the aircraft would not have departed and it would not have suffered the cabin pressurisation problems encountered on the subsequent sector. The commander's actions after encountering the pressurisation problem were entirely correct in the circumstances.

Related articles