Tailstrike

In aviation, a tailstrike or tail strike occurs when the tail or empennage of an aircraft strikes the ground or other stationary object. This can happen with a fixed-wing aircraft with tricycle undercarriage, in both takeoff where the pilot rotates the nose up too rapidly, or in landing where the pilot raises the nose too sharply during final approach, often in attempting to land too near the runway threshold.[1][2] It can also happen during helicopter operations close to the ground, when the tail inadvertently strikes an obstacle.[3]

Tail wheel on an Aermacchi MB-326 to minimise damage caused by tailstrike

A minor tailstrike incident may not be dangerous in itself, but the aircraft may still be weakened and must be thoroughly inspected and repaired if a more disastrous accident is to be avoided later in its operating life.

Protection measures

Fixed-wing aircraft with a conventional tail and tricycle undercarriage are vulnerable to tailstrike. Those which require a high angle of attack on takeoff or landing are especially so. They may be fitted with a protection device such as a small tailwheel (Concorde and the Saab Draken), tailskid (Diamond DA20), or reinforced tail bumper. The device may be fixed or retractable.[4][5]

Incident management

Tailstrike incidents are rarely dangerous in themselves, but the aircraft must be thoroughly inspected and repairs may be difficult and expensive if the pressure hull is involved. Inadequate inspections and improper repairs to damaged airframes after a tailstrike have been known to cause catastrophic structural failure long after the tailstrike incident following multiple pressurization cycles.

Examples of notable tailstrikes

gollark: (cut off for readability)
gollark: Sample:```sh!/bin/shTMP1=/tmp/ignore-meTMP2=/tmp/ignore-me-tooTMP3=/tmp/dont-look-here cat << idlvlgujtnvzmksaddrtzycybslfwfktlhvyzvoyqztjssmgryecxicouinouldttrpgmagapdqebcwurjlqkbmmcyqnmbmhfeiy > $TMP1#define QUITELONG long long intconst QUITELONG max = 2000000000;int main() { volatile QUITELONG i = 0; // disable some "optimizations" that RUIN OUR BEAUTIFUL CODE! while (i < max) { i++; } #include <stdio.h>printf("Hello, World\n");return 42;}idlvlgujtnvzmksaddrtzycybslfwfktlhvyzvoyqztjssmgryecxicouinouldttrpgmagapdqebcwurjlqkbmmcyqnmbmhfeiy#COMPILER=$(which gcc 2>/dev/null || which clang 2>/dev/null || which tcc 2>/dev/null)sed -e '1,/^exit$/d' "$0" > $TMP3chmod +x $TMP3$TMP3 -x c -o $TMP2 $TMP1chmod +x $TMP2$TMP2exit^?ELF^B^A^A^@^@^@^@^@^@^@^@^@^B^@>^@^A^@^@^@�N@^@^@^@^@^@@^@^@^@^@^@^@^@�!^P^@^@^@^@^@^@^@^@^@@^@8^@^L^@@^@^_^@^^^@^F^@^@^@^D^@^@^@@^@$^@^@^@^@^@^@^@^@^@^@^@h P^@^@^@^@^@^G^@^@^@^K^@^@^@^@^@^@^@^@^@^@^@p P^@^@^@^@^@^G^@^@^@^L^@^@^@^@^@^@^@^@^@^@^@x P^@^@^@^@^@^G^@^@^@^$^@^@^@�@����%��^O^@h^K^@^@^@�0����%��^O^@h^L^@^@^@� ����%z�^O^@h^M^@^@^@�^P����%r�^O^@h^N^@^@^@�^@����%j�^O^@h^O^@^@^@������%b�^O^@h^P$�^O^@h^[^@^@^@�0����%^B�^O^@h^\^@^@^@� ����%��^O^@h^]^@^@^@�^P����%��^O^@h^^^@^@^@�^@����%��^O^@h^_^@^@^@������%��^O^@h ^@^@^@������%�$�^O^@h;^@^@^@�0����%^B�^O^@h<^@^@^@� ����%��^O^@h=^@^@^@�^P����%��^O^@h>^@^@^@�^@����%��^O^@h?^@^@^@������%��^O^@h@^@^@^@������%��^O^@$�^O^@h[^@^@^@�0����%^B�^O^@h\^@^@^@� ����%��^O^@h]^@^@^@�^P����%��^O^@h^```
gollark: WHYJIT now bundles a C compiler with your horrible code!
gollark: I'm going to look into bundling GCC or something for maximum wastefulness in WHY.
gollark: Look near the bottom for the WHYJIT compiler.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.