Instructor and trainee reported a loss of aircraft control during the takeoff phase of a touch and go landing. Instructor applied excessive braking during rejected takeoff after hearing ATC directions meant for another aircraft.

Date: 2025-08 · Aircraft: SR20 · Phase: takeoff

Anomalies: conflict-ground-conflict|critical|ground-event-encounter-loss-of-aircraft-control

Synopsis

Instructor and trainee reported a loss of aircraft control during the takeoff phase of a touch and go landing. Instructor applied excessive braking during rejected takeoff after hearing ATC directions meant for another aircraft.

Narrative

During landing at ZZZ on the ILS XX Student landed successfully and initiated appropriate technique for a touch and go. During the take off roll IP (Instructor Pilot) heard a similar tail number and the instructions to HOLD SHORT; HOLD SHORT; HOLD SHORT. IP believed the tower had called for our aircraft to hold short due to a truck heading for Runway XX. IP took controls and initiated full braking action. Braking action resulted in left tire failure and a slight lose of control as the aircraft drifted left on the runway. IP contacted tower and informed tower of the loss of tire and tower diverted traffic from Runway XX. I believe that as IP I took necessary action to prevent collision with a vehicle that was approaching Runway XX.Once I determined the safety of the crew I started communication with our supervisor. [The] FBO facilitated the removal of the aircraft from the runway. I assisted as necessary. After the aircraft was parked crew conducted a post flight and ensured the aircraft was in a safe condition (CAPs pin; switches/mags off; chalked; and locked. Inspected aircraft for general damage and only the LH gear tire and wheel pant were noted.Communications were saturated with ATC (approach and tower). Tower was talking to several aircraft and a ground vehicle. Tower was bouncing communication frequently. IP believe that tower told our aircraft to hold short resulting in hard braking to ensure safety. IP could have been listening to comms better ensuring proper tail number before the incident. IP braking technique was too drastic. There was more time to react than initially perceived.

Second reporter narrative

During landing at ZZZ on the ILS XX I landed successfully and initiated appropriate technique for a touch and go. During the takeoff roll IP (Instructor Pilot) heard a similar tail number and the instructions to HOLD SHORT; HOLD SHORT; HOLD SHORT. IP believed the tower had called for our aircraft to hold short due to a truck heading for Runway XX. IP took controls and initiated full braking action. Braking action resulted in left tire failure and a slight lose of control as the aircraft drifted left on the runway. IP contacted tower and informed tower of the loss of tire and tower diverted traffic from Runway XX.Once IP determined the safety of the crew IP started communication with our supervisor. [The] FBO facilitated the removal of the aircraft from the runway. IP assisted as necessary. After the aircraft was parked crew conducted a post flight and ensured the aircraft was in a safe condition (CAPs pin; switches/mags off; chalked; and locked. Inspected aircraft for general damage and only the LH gear tire and wheel pant were noted.Communications were saturated with ATC (approach and tower). Tower was talking to several aircraft and a ground vehicle. Tower was bouncing communication frequently. IP believe that tower told our aircraft to hold short resulting in hard braking to ensure safety.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.