How do you prevent a tailstrike on take-off and landing?

Prevent a tailstrike by using the correct take-off and landing configuration, speeds and trim, then controlling pitch smoothly. Begin rotation at the calculated VR or published liftoff point, respect aircraft-specific pitch limits, fly a stabilised approach, avoid an exaggerated flare, and go around rather than rescuing a slow, bounced or unstable landing.

In real-world aviation and realistic flight simulation, tail clearance depends on the specific aircraft, not a universal pitch angle. Fuselage length, landing-gear geometry, oleo compression, loading and variant all matter. A tail skid or strike sensor limits damage or reports contact; it is not permission to use more pitch.

What causes an aircraft tailstrike?

A tailstrike occurs when the aircraft’s nose-up attitude exceeds the available tail clearance while it is close to the runway. On take-off, this usually follows an early or aggressive rotation. On landing, it commonly results from excessive flare, low airspeed, a high sink rate, mishandled bounce recovery or abrupt pitch during a go-around.

• Incorrect speed: rotating below the calculated speed or allowing approach speed to decay demands more angle of attack and pitch.
• Wrong trim or loading: excessive nose-up trim and an aft centre of gravity can make rotation much more sensitive.
• Configuration errors: incorrect flap selection changes the required speed, attitude and runway performance.
• Control overreaction: pulling harder when the aircraft does not respond immediately can produce a sudden pitch increase once it does respond.
• Compressed main gear: a firm touchdown or bounce reduces tail clearance, so a pitch attitude that seemed acceptable in the flare may no longer be safe.

How do you avoid a tailstrike during take-off?

1. Calculate the take-off properly. Use the actual weight, centre of gravity, flap setting, runway, wind and environmental conditions. Do not borrow a rotation speed from another flight. Our explanation of how VR fits among the take-off decision speeds covers why it is not an arbitrary target.
2. Verify configuration and trim. Confirm flaps, stabiliser or elevator trim, loading and control movement before entering the runway. In a simulator, also check for duplicate elevator assignments, excessive controller sensitivity or an active autopilot.
3. Do not rotate early. If acceleration is abnormal, apply the aircraft’s rejected-take-off criteria rather than trying to force it airborne. Approaching the runway end is never a reason to pull harder.
4. Rotate at the published rate. Make one smooth pitch input at VR and follow the type-specific target attitude or flight-director command. There is no safe generic rotation rate or pitch target for every aircraft.
5. Stop increasing pitch once the target is reached. Vertical speed and flight-director indications can lag slightly at lift-off. Continuing to pull while waiting for them is a common simulator tailstrike error.

If the aircraft reaches VR but refuses to lift off, do not solve it with an abrupt elevator input. Check the likely configuration, loading, trim and control problems in our take-off rotation troubleshooting guide.

Light piston aircraft may use a published liftoff technique rather than airline-style V1 and VR call-outs. Tailwheel aircraft also require their own ground-attitude technique. In every case, the POH, AFM or operator procedure takes precedence over a generic pitch value.

How do you prevent a tailstrike when landing?

A stabilised approach at the correct speed leaves enough lift and control authority for a modest flare. Tailstrike risk rises sharply when the pilot tries to stretch the flare, arrest a high sink rate at the last moment or salvage a poor touchdown.

1. Meet the stabilised-approach criteria. Be configured, on speed, on the intended flight path and using a manageable descent rate by the applicable gate. Go around if those conditions are not met.
2. Fly the calculated target speed. Include only the wind or gust additive required by the aircraft procedure. Too little speed encourages excessive pitch; too much can cause floating and a late attempt to force the aircraft down.
3. Flare to reduce the sink rate. Do not try to eliminate every trace of descent or hold the aircraft off indefinitely. Use the aircraft-specific sight picture and a small, progressive pitch change.
4. Control the attitude after main-gear contact. Do not keep raising the nose merely to hold the nosewheel off. Main-gear compression reduces the remaining clearance.
5. Treat a significant bounce as unstable. Avoid a sharp nose-down correction followed by another large flare. Use the published bounce-recovery technique, and go around when the bounce is substantial or control is uncertain. Apply thrust and establish the go-around attitude smoothly, especially with nose-up trim already set.

For the approach and touchdown technique behind these points, see our practical guidance on stabilised approaches and controlled flares.

Is there one safe pitch angle that prevents every tailstrike?

No single pitch angle is safe for every aircraft or even every variant of one aircraft family. Tail clearance changes with fuselage length, gear geometry, strut compression and sometimes configuration, so use the limits and visual cues supplied for the exact model being flown.

In a simulator, a wide field of view or unusual camera position can make the nose attitude appear lower than it is. Cross-check the attitude indicator rather than relying solely on the view through the windscreen. Understanding how pitch affects attitude and angle of attack also helps separate the required flight path from an excessive nose-up command.

What should you do after a suspected tailstrike?

In a real aircraft, maintain control and follow the aircraft’s checklist and operator procedure. After a take-off strike, do not make an improvised high-speed reject or immediate low-altitude turn; advise air traffic control and use the prescribed abnormal procedure. Structural damage can be hidden, and normal indications do not prove that pressurisation or continued flight is safe.

After a landing strike, clear the runway only if the aircraft can be moved safely, then arrange the required inspection. In a simulator, review the replay, pitch attitude, speed, trim and control inputs. Do not simply increase VR on the next attempt—the calculated performance and the underlying technique or configuration error must be corrected.